After a restaurant POS reconnects, compare four sets of records: the interruption timeline, order records, payment processor outcomes, and the manual notes your team kept during service. Match individual transactions before relying on shift totals. An order that appears in the POS is not necessarily paid, and a payment approval does not prove an order was recorded correctly.
Start with the affected time window and devices. Then review queued and missing orders, verify payment status using processor references, and assign each discrepancy to someone who can resolve it. Do not resend an order or charge a card simply because a record looks incomplete.
1. Mark the interruption window
Write down when staff first noticed the problem and when each affected system was working again. Those times may differ: an internet connection might return before every terminal, printer, or ordering channel is ready. Record the time zone and whether each time came from a device log or a staff estimate.
List the affected terminals and any other equipment involved, such as printers or kitchen displays. Note which channels continued to take orders: the counter, phone, direct online ordering, or another source. A problem on one device does not automatically mean every channel stopped recording transactions.
Gather the records created during the window and keep them together until reconciliation is complete:
- Handwritten tickets, order books, and cash drawer notes.
- POS order lists, queue screens, and device messages, where available.
- Processor transaction records and any printed payment receipts.
- Kitchen tickets, pickup notes, and delivery handoff records.
- Staff notes about voids, refunds, discounts, or orders abandoned during the interruption.
Capture relevant order numbers, timestamps, amounts, and device names. If a clock was wrong, note that rather than silently changing the record. Check a little before and after the estimated window so a transaction near the boundary does not disappear from the review.
The goal is to establish which records deserve attention, not to assume every order during the period failed. If a terminal has an unresolved queue, ask the provider how to view its status without triggering a resend. Keep the device available until you know whether restarting or resetting it could affect pending records.
2. Match orders before resubmitting anything
For each interruption-period order, compare the original ticket with the POS record and any kitchen or handoff record. Look for the order identifier first. If that is missing, use a combination of time, items, amount, channel, and staff notes. Similar orders can belong to different guests, so a matching total alone is not enough.
Put each order into a practical review category: matched, possibly missing, possible duplicate, or unresolved. A ticket may be present in the POS but still need attention if the items, modifiers, discount, or final amount differ. Likewise, two similar records are not necessarily duplicates; check whether they represent two separate orders before changing either one.
The following hypothetical example shows how a manager might handle a small interruption. It describes orders, not payments; payment status requires a separate check.
| Ticket | Records found | Review status | Next action |
|---|---|---|---|
| A: $18 | Paper ticket and one matching POS order | Matched | Check payment separately. |
| B: $24 | Paper ticket; no matching POS order found | Possibly missing | Inspect the queue and confirm whether it was served before adding anything. |
| C: $12 | One paper ticket; two similar POS orders | Possible duplicate | Compare identifiers and kitchen records; do not void solely on amount. |
| D: $21 | Paper ticket and POS order with a different modifier | Unresolved | Ask the staff member who handled it and correct the record under the restaurant's procedure. |
The four paper tickets total $75. That is a reference amount for these tickets, not a claim that $75 was collected or that the POS sales total should already equal $75. The table identifies what to investigate; it does not authorize a charge, refund, void, or resend.
If ticket B was served but never reached the POS, determine the provider's supported way to record it without creating another kitchen request. If C is confirmed as a duplicate, document which record represents the real order before making a correction. For D, establish what the guest received and what was agreed before changing the order.
Ask your restaurant POS provider how queued orders are displayed after reconnection, which status means an order was accepted, and what happens to kitchen routing when an order is entered or resent. The answers shape the recovery steps your staff can safely use.
3. Compare payment outcomes with POS records
Use the payment processor's transaction view alongside the POS payment record. Match a transaction using its reference, amount, approximate time, and other details available to the manager. Keep full card details out of the reconciliation notes. If a receipt has only a partial reference, record that limitation and use other evidence before declaring a match.
Check the actual status, not just the presence of a transaction. An authorization, a captured payment, a decline, a void, and a refund represent different outcomes. An authorization is not the same as a completed capture, and a captured payment is not the same thing as an order record. Processor labels and timing vary, so ask the processor what each status means and when it can be treated as final.
For each difference, note both sides. For example, a POS order might show an amount due while the processor shows a payment captured for the same amount. That requires investigation, not an immediate second charge. Conversely, a POS may show a payment while the processor record is declined or still unresolved. Check the reference and status before deciding how to correct the record or contact the guest.
Cash needs its own trail. Compare cash tickets and drawer notes with recorded cash sales and the actual drawer count, following your normal cash-handling procedure. A cash shortage or overage is a discrepancy to investigate; it does not by itself identify which order was missing. Keep tips, refunds, and adjustments distinct when comparing totals so they are not mistaken for sales.
Once individual transactions are matched, compare the relevant subtotals and investigate the remaining difference. Separate order sales from payment activity: refunds, tips, timing differences, and unmatched transactions can make the figures differ. Do not treat a processor deposit as the same measure as sales or assume a deposit amount alone proves every order was captured.
4. Close exceptions and document recovery
Create one exception entry for each unresolved order or payment. Give it an owner, a next action, a target follow-up time, and a reference to supporting records. A shift manager might confirm whether an order was served, while an authorized account holder checks a processor status. Assigning a name matters more than leaving a general note that the totals need review.
Use a short handoff format:
- Reference: Order or ticket number, time, channel, and relevant payment reference.
- Difference: What each record shows and what remains unknown.
- Owner and action: Who will check the queue, speak with staff, or contact the processor.
- Outcome: The correction made, its time, and the supporting reference.
Leave an item open if the evidence is incomplete. Record when it will be checked again, especially if a payment status has not settled. For a correction, preserve the original reference and follow the restaurant's approval procedure. If a guest needs to be contacted about a real discrepancy, use the restaurant's normal contact process and confirm the facts first.
When the shift is reconciled, save the interruption window, affected devices, exception list, and final handoff in the place managers use for shift records. Agree on who can access payment information and how long your business keeps records. Ask a qualified adviser about any applicable recordkeeping obligations.
Turn the incident into a short recovery drill. Use fictional tickets and simulated statuses to practice matching records and assigning exceptions. The drill should not create a real card payment, guest message, kitchen order, or courier dispatch. If you later run a live service pilot, plan it separately with the provider, identify who will monitor actual orders, and use normal controls for real guest transactions.
Before the next interruption, review how your restaurant POS hardware is identified and who can access each queue or processor account. Also decide where paper tickets and exception notes belong alongside your restaurant management software records.
Next step: Bring a sample interruption timeline and exception list to a POS provider. Ask them to walk through queue visibility, payment-status checks, and safe correction steps for your setup. You can discuss these requirements with Fleksa as part of that conversation.
Frequently asked questions
Should I resend every order that appears stuck?
No. First check its queue status, POS record, and kitchen or handoff evidence. Resending without confirming the original status can create a duplicate. Ask your provider how to resolve a stuck record safely.
Does an approved payment mean the order is complete?
Not necessarily. Confirm what the processor's approval status means, whether the payment was captured, and whether the corresponding POS order and service record match. An authorization alone is not a completed capture.
What if the shift totals still do not match?
Keep the difference open with an owner and follow-up time. Review unmatched transactions, cash notes, refunds, tips, and timing differences. Compare like measures before making an adjustment, and retain the reference for any correction.
