When seated reservation covers and POS covers differ, first explain what each report counts. The reservation figure usually describes guests on bookings marked seated. The POS figure describes guests entered on checks. Walk-ins, changed party sizes, split checks, and missing links can make those totals different without either system being wrong.
Start with the same service period, then trace the bookings and checks behind the difference. A manager should be able to say how much of the gap is expected, how much is a counting-rule difference, and what still needs investigation.
Define the two counts before comparing them
A reservation cover is a guest counted against a reservation. For this reconciliation, use the party size recorded when the reservation is marked seated. That is different from the size originally booked: a party of four may arrive with three people. Ask your reservation vendor which party-size field its seated-cover report uses and whether later edits change that report.
A POS cover is a guest count entered on a check or otherwise recorded in the POS. It is not necessarily the number of checks. Four guests can pay on two checks, and one check can cover several guests. Ask how your POS handles guest counts when a check is split, transferred, merged, reopened, or voided.
Walk-ins matter too. If the reservation report includes only seated bookings but the POS report includes every dining-room check, walk-in guests belong in the POS total but not in the reservation total. Some restaurants may record walk-ins in the reservation system; confirm whether the report includes them before treating the difference as expected.
Align the scope before looking for errors. Compare the same location, local service date, dining areas, and service window. Decide whether takeout, bar tabs, private events, canceled bookings, and no-shows belong in either count. A dinner report ending at midnight may not match a POS report that assigns late checks to the following calendar day.
Trace one service from bookings to checks
The following example is hypothetical. The reservation report counts the final seated party size for reservations only. The POS report counts guests entered on all dining-room checks, including walk-ins. Each guest is counted once across split checks.
| Party | Seated reservation covers | POS checks and covers | Explanation |
|---|---|---|---|
| Booking A | 3 | Two checks: 2 + 1 = 3 | Booked for 4; 3 arrived. Split checks do not add a cover. |
| Booking B | 2 | One check: 2 | Party size and POS count agree. |
| Walk-in party | 0 | One check: 2 | No reservation; both guests appear in the POS count. |
| Total | 5 | Four checks: 7 covers | The POS total is 2 higher because it includes the walk-in party. |
The original bookings were for six guests: four on Booking A and two on Booking B. The seated reservation total is five because Booking A arrived with three. The POS shows seven covers: those five reservation guests plus two walk-ins. There are four checks, but check count is not cover count.
A useful manager explanation would be: “We seated five guests on reservations and recorded seven POS covers. Two POS covers were walk-ins. One booking arrived with three rather than four, and its guests paid on two checks.” That accounts for the gap without calling the split check an extra party or an error.
Now suppose Booking A’s two checks each showed three guests instead of two and one. The POS total would be ten, not seven. Two covers would still be explained by walk-ins, while three would need investigation as a possible duplicate guest count. The check totals alone would not establish which number was entered correctly; staff would need the reservation record and service context.
Classify the difference before correcting it
Missing or unclear links
A check can be valid even when nobody can match it to a reservation. The server may have opened it under a table rather than a booking, or the party may have moved tables. A split or transfer can also make the trail harder to follow. Use table, time, party size, and staff notes to narrow the match, but do not assume that two similar parties are the same guests.
Mark an uncertain match for follow-up rather than forcing it into the reconciliation. If the systems offer a booking-to-check reference, ask how it is created and whether it survives a split or transfer. If they do not, agree on a practical identifier staff can record consistently without adding unnecessary guest information.
Different counting rules
Both reports may be accurate within their own rules. One may include walk-ins while the other excludes them. One may use the original booking size while the other uses the size at seating. A POS report might count guests on closed checks, while a reservation report counts parties seated during the service window. A late check can therefore land in a different reporting period.
Document the rule and adjust the comparison, not the underlying transaction. For example, subtract POS walk-in covers from the all-dining POS total when comparing it with reservation-only seated covers. Keep the original totals visible so the adjustment can be understood later.
Genuine data errors
A host may forget to update a party size or mark a booking seated. A server may enter the same guest count on both halves of a split check. A duplicate check or an incorrect service date can also distort a report. These are candidates for correction, but confirm them against the available records before changing historical data.
Record who made a correction, what changed, and why. If the systems retain an audit history, ask how to view it. If they do not, keep a separate manager log. Do not overwrite a valid original booking size merely to make a seated-cover report match the POS.
Set an investigation rule for each shift
Give one person ownership of the comparison. A closing manager can review the two totals after service, while the host lead confirms seating changes and the POS lead helps trace checks. Choose a threshold that fits the restaurant: for example, review every service with an unexplained gap, then decide whether a small, documented difference needs further work. Expected walk-ins should not be treated as unresolved exceptions.
Use a short closeout routine:
- Pull both reports for the same location and service window. Write down the rules used by each report.
- Separate known scope differences, such as walk-ins or excluded dining areas, from the remaining gap.
- Match reservation parties to checks using available references. Pay particular attention to changed party sizes, split checks, transfers, and late closures.
- Log unresolved items with an owner and a follow-up time. Correct confirmed entry errors through the appropriate system process.
- Review recurring causes with staff. A repeated split-check issue may call for a clearer entry procedure rather than a one-time fix.
Ask vendors for an export that can support this work. On the reservation side, request booking reference, location, local date and time, original and seated party sizes if available, status, status-change time, table, and booking channel. On the POS side, request check reference, location, open and close times, table, guest count, check status, and any available split, merge, transfer, or booking reference. Ask which fields are retained after edits and how voided checks appear. Limit access to staff who need it and avoid exporting guest details that the reconciliation does not require.
Before changing the closeout procedure, walk staff through a simulation using fictional bookings and checks. Verify how they would classify each difference and record a correction. Keep the exercise separate from live service: it must not charge a card, send a guest message, or dispatch a courier. If you later run a live service pilot, assign a manager to review actual exceptions and confirm that normal guest-facing operations remain under staff control.
When comparing a restaurant reservation system with a restaurant POS system, ask for a demonstration of the exact reports and matching workflow you need. Broader restaurant management software may bring several workflows together, but confirm the fields, connections, and reporting setup for your location rather than assuming the two cover counts reconcile automatically.
Next step: Bring one recent service’s reservation and POS reports to a vendor discussion. Identify the unexplained gap and ask how staff would trace it. Compare your reservation requirements with Fleksa’s available workflows.
Frequently asked questions
Should seated reservation covers always equal POS covers?
No. POS covers can include walk-ins or other guests outside the reservation report. The counts become comparable only after you align their scope, timing, and counting rules.
Does a split check create extra covers?
Not by itself. A split changes the number of checks, not the number of guests. Check how guest counts are entered across the resulting checks so the same people are not counted twice.
What should a manager do with an unexplained difference?
Assign an owner, trace the relevant bookings and checks, and record what remains uncertain. Correct a confirmed entry error through the appropriate process; do not change a valid record simply to make the totals match.
