After your first day of direct online orders, compare each accepted order with a fulfillment record and a payment record. Then compare the payment processor’s captures, refunds and fees with its deposit report. A matching sales total alone does not prove that every guest received an order.
Start with order IDs, not just dollar totals. One missing order and one duplicate can cancel each other out in a count. Keep unresolved items on a short exception list, assign an owner and decide whether the next service should use the same hours until the gaps are understood.
Compare accepted orders with fulfillment records
Choose a reporting window first. For example, use the restaurant’s opening through closing time, and note the time zone. Orders placed before closing but scheduled for the next day need a separate line: they may be accepted today without being due for fulfillment today.
Ask the person managing online orders for the accepted-order list, including order ID, time, status, promised fulfillment time and order total. Ask the shift lead for the kitchen, pickup and delivery records available for that same window. These might include tickets, a pickup log or a delivery handoff record. Ask the person responsible for payments for transaction and settlement reports.
Make one row per order ID. Record whether it was accepted, whether it was due that day, and what evidence shows it was prepared and handed off. A printed ticket shows that an order reached a printer; it does not by itself show that the guest collected the food. For delivery, a dispatch record and a completed handoff are also different events.
Pay particular attention to these cases:
- Accepted but no kitchen record: Check whether the order was scheduled later, routed elsewhere or missed.
- Kitchen record without an accepted order: Check for a duplicate print, a manual entry or a record from another channel.
- Prepared but no handoff record: Ask the shift lead what happened before marking it complete.
- Canceled order: Record when it was canceled and whether preparation, payment or a refund had already occurred.
A restaurant website may show guests an order confirmation, but your reconciliation still needs an operational record. If you are evaluating a new restaurant website, ask how staff can find an order by ID and see status changes after a busy shift.
Reconcile item totals and payments in cents
For each order, add item amounts and modifiers, subtract discounts, then add any applicable charges shown on the order. Compare that result with the accepted order total. Work in cents to avoid rounding confusion, and use the actual amounts charged rather than a menu price remembered by staff.
Next, match the order ID to payment activity. An authorization, a capture and a refund are different events. An authorization is not necessarily money collected; a capture is a payment collected; a refund reduces what is retained. A cash-on-pickup order, if offered, needs a separate cash record rather than an expected card capture.
Do not compare sales directly with a bank deposit and call the difference a missing order. A deposit can reflect processing fees, refunds, adjustments and a settlement period that differs from your service day. A delivery charge on an order is part of the guest’s total; a separate courier or dispatch expense is an operating cost. They should not be treated as the same payment.
Use this first-day sheet as a model. All figures below are hypothetical assumptions, not a description of a particular provider’s reports or fees. The 12 accepted orders are all due on the first day and each has the same assumed total. The processor’s settlement report is assumed to cover the same transactions.
| Check | Expected or recorded | Comparison | Action |
|---|---|---|---|
| Accepted orders | 12 order IDs | 11 have fulfillment evidence; one does not | Investigate the unmatched ID |
| Accepted order totals | Items 18,000 cents + tax 1,200 + delivery charges 4,800 = 24,000 cents | 12 orders at 2,000 cents each | Check each order’s components |
| Captured payments | 11 captures of 2,000 cents = 22,000 cents | One order has no capture; its payment is pending | Check status and fulfillment together |
| Processor deposit | 22,000 cents captured; no refunds; 660 cents in assumed processing fees | Expected deposit: 21,340 cents | Match to settlement report and bank entry |
The sheet separates accepted sales from captured money and from the expected deposit. The assumed processing fee is 3% of captured payments: 22,000 × 0.03 = 660 cents. This deposit calculation includes that variable fee and assumes no fixed processing fees, refunds or exception charges. It excludes subscription, hardware and courier costs, so it is not an all-in operating-cost calculation.
The missing fulfillment record and pending payment belong to the same order in this example. That is useful for investigation, but neither status proves the other caused it. The owner still needs to establish what happened to the guest’s order and whether a payment later captured or was canceled.
Investigate gaps and duplicates
Start with the unmatched ID. Check its timestamps and status history, then ask the shift lead whether the order appeared on a screen, ticket or other working list. Check whether the promised time was changed. If the order was missed, follow your restaurant’s normal process for contacting the guest and resolving the payment. Record the outcome without putting full card details on the reconciliation sheet.
For a suspected duplicate, compare IDs, item details, timestamps and payment references. Two similar orders may be legitimate orders from different guests. Two tickets with the same ID may represent one order printed twice, not two sales. Do not cancel or refund solely because the amounts match.
Also look for a pattern. Several orders missing from a kitchen record could point to routing or staff workflow. One missing handoff record could be a logging gap rather than a missed meal. Separate what is known from what needs a follow-up, and preserve the relevant report or ticket reference so another manager can trace it.
If you need to check a suspected workflow issue outside service, use a simulation that cannot create a real payment, guest message or courier dispatch. A simulation can help staff practice the steps; it does not establish that a real service-day order will flow correctly. Review the next live shift separately using actual records and normal guest-service procedures.
Ask any ordering provider what staff can see when an order changes status, how duplicate submissions are identified, and how to export order and payment references. The online ordering buying guide can help frame those questions alongside your other buying requirements.
Assign fixes before expanding hours
Turn each exception into a small task with a named owner and a due time. The shift lead might confirm a handoff; the payment manager might check a pending capture; the ordering provider might investigate a routing issue. The owner should review the results before adding more ordering hours or increasing volume.
Use a simple decision rule: expand only when staff can account for the previous shift’s accepted orders and understand material differences in payment and settlement records. A deposit that has not arrived yet may simply fall outside the processor’s settlement schedule. Keep it open until the expected date and amount can be checked rather than treating timing as proof of a lost payment.
For the next shift, retain the same reporting window and assign someone to collect the records at close. Note scheduled orders separately, carry open refunds or pending payments forward, and mark an issue resolved only when its evidence and outcome are recorded. If a workflow remains unclear, keep hours manageable while the responsible person follows up.
Use the sheet to review your current setup, then ask Fleksa about restaurant online ordering and verified availability in your US location. Bring one or two unresolved examples so you can ask how staff would find the records they need.
Frequently asked questions
Should every accepted order have a completed payment on day one?
Not necessarily. A payment may be pending, an order may be canceled, or a permitted payment method may be collected later. Match each order to its actual payment status and follow up on unresolved amounts.
What if the order count matches but the totals do not?
Compare each order’s items, modifiers, discounts and charges in cents. Then check captures and refunds separately. Matching counts can hide an incorrect amount or offsetting errors.
How long should an unresolved order stay on the sheet?
Keep it open until someone records the outcome and supporting reference. Set a follow-up date for pending payments, refunds or deposits rather than removing the item at the end of the first shift.
