To confirm that a receipt matches what a guest approved, capture the final checkout summary and compare it with the resulting receipt line by line. Check the items and options first, then compare discounts, fees, tax, tip, and total in cents. Also check fulfillment details, such as pickup time or delivery address.
Run the comparison with several different baskets, not just your simplest order. A matching total alone is not enough: two errors can cancel each other out, or a receipt can show the right price for the wrong meal. This is a check of the guest-facing order confirmation, not a reconciliation of deposits or payment-processing fees.
Select baskets with fees, options, and tips
Start with the order paths your guests actually use. A manager can supply the menu and pricing rules; the person who handles online orders can identify common substitutions and service issues. Ask your ordering provider how to run a safe simulation and access both the final checkout view and its corresponding receipt.
Build a small set of baskets that puts different rules to work:
- Simple pickup: one item with no options, discount, or tip. This gives you a baseline.
- Customized meal: an item with a paid add-on, a free substitution, and a preparation note. Check that the kitchen-facing description and guest receipt are understandable.
- Delivery: include a delivery charge and address, if you offer delivery. Check the promised fulfillment details as well as the amount.
- Discount and tip: apply an eligible promotion and add a tip. Note whether each appears as a separate line.
- Edge case: use multiple quantities of an item with options, or remove an option before submitting. Check that the final basket, rather than an earlier version, appears on the receipt.
Use a simulated environment or a provider-approved practice mode that cannot trigger a real payment, guest message, or courier dispatch. Ask the provider to confirm those safeguards before you begin. If that environment cannot produce a representative receipt, arrange a separate, controlled live service pilot with staff oversight and the provider’s guidance. A live pilot is not a simulation; agree in advance how to handle any real payment, message, or delivery action.
Choose the receipt a guest would actually receive, whether that is an on-screen confirmation, an email, or another available format. If your setup offers more than one, compare each one. A correct screen does not establish that a later message contains the same information.
Compare checkout and receipt lines in cents
Use the final screen immediately before submission as the record of what the guest approved. Capture the entire summary, including the order type and any text that explains a charge. Then compare it with the receipt for that same order. Keep screenshots or other records together so you do not accidentally compare two different baskets.
The following is a hypothetical simulation. Prices, tax, and charges are assumptions, not a quote or a tax calculation. The basket has a burger, a paid add-on, a salad, a delivery charge, tax, and a tip. The table compares the guest-facing amounts; it does not include restaurant operating costs or payment-processing fees.
| Line | Final checkout | Receipt | Check |
|---|---|---|---|
| Burger | $12.99 | $12.99 | Match |
| Paid add-on | $2.00 | $2.00 | Match |
| Salad | $8.99 | $8.99 | Match |
| Items subtotal | $23.98 | $23.98 | Match |
| Delivery charge | $1.99 | $1.99 | Match |
| Assumed tax | $2.00 | $2.00 | Match |
| Tip | $3.00 | $3.00 | Match |
| Total | $30.97 | $30.97 | Match |
The subtotal is $12.99 plus $2.00 plus $8.99, or $23.98. Adding $1.99, $2.00, and $3.00 produces $30.97. The table makes each component visible, so a correct total cannot hide a misplaced tip or delivery charge.
Now compare the descriptions. Does the receipt name the paid add-on and attach it to the burger? Does it preserve the quantity, free substitution, and preparation note, if those were selected? A note may not change the price, but leaving it out can still produce the wrong order.
Labels matter too. If checkout calls $1.99 a delivery charge but the receipt calls it a service charge, ask what the label means and whether it can be made consistent. Do not assume the restaurant receives a guest-facing charge or that it covers the cost of delivery. Those are separate operational questions.
For a discount, check both eligibility and arithmetic. If a receipt groups an add-on into the item price rather than showing a separate line, compare the combined amount and description with checkout. Grouping can be understandable, but the guest should still be able to recognize what was ordered and paid for.
Investigate differences with the provider
When something differs, record exactly where it appears. A missing add-on description, a different fee label, and a different total are separate issues, even if they occur on the same receipt. Give each a short description rather than reporting only that the receipt is wrong.
For example, suppose the simulated receipt above shows the correct $30.97 total but leaves out the add-on name. The amount check passes; the order-content check does not. Save the final checkout view and the receipt, record the basket and fulfillment type, and ask the provider whether the option can appear on the guest receipt. Also check what the restaurant receives for preparation. Do not assume a guest receipt and a kitchen ticket contain identical details.
If the total differs, compare each line before deciding where the error started. A discount might be missing, a tip might be included under an unexpected label, or a fee may have changed between screens. Ask the provider to explain the calculation and when each amount becomes final. If the provider says the difference is a configuration issue, ask which setting needs to change and who controls it.
Useful questions include:
- Which version of the order does each receipt format use: the final approved basket or a later update?
- How are option prices, quantities, discounts, fees, tax, and tips displayed when they are grouped?
- What happens on the guest-facing receipt if the restaurant changes or cancels an order after submission?
- Can we reproduce the issue safely without a real payment, message, or dispatch?
- Who owns the fix, and which receipt formats and order types should we retest?
A later change deserves its own record. Compare the original receipt with the original checkout, then compare any revised confirmation with the authorized change. Do not treat an amended order as proof that the original receipt was correct. Agree on how staff should explain a discrepancy to a guest while the provider investigates.
Record evidence and retest after changes
Keep a simple log for each basket: date, order type, receipt format, final checkout details, receipt details, and the result. Mark each line as matching, different, or not shown. Record the provider’s explanation and the owner of any follow-up. Store only what you need, restrict access, and avoid keeping unnecessary guest or payment information.
Set your acceptance rule before retesting. For each basket, the visible item quantities, selected options, relevant notes, fulfillment details, individual charges, and total should be consistent with the final checkout. If a receipt combines lines, the combined description and amount should still let a guest understand the purchase. Record any limitation you decide to accept, along with who approved it.
After a change, rerun the affected basket and at least one nearby case. For a missing add-on, repeat the customized meal, then check multiple quantities or another option. For a fee-label change, check both pickup and delivery where offered. Use the same safe simulation safeguards as before; do not use a practice run to send a real guest message, charge a card, or dispatch a courier.
A successful simulation checks the cases you ran. It does not establish that every menu configuration or future software change will behave the same way. Repeat a short set of checks when you change menus, fees, promotions, fulfillment settings, or receipt formats, and keep a route open for staff to report guest confusion.
If you are assessing a new setup, use the same baskets to compare what each provider can demonstrate. The online ordering buying guide covers broader selection questions, while the restaurant website page is relevant when ordering starts on your own site. For the operational difference between order channels, see the direct and marketplace order guide.
Next step: Run the checklist against your current setup and bring any unresolved differences to your provider. If you are evaluating Fleksa’s restaurant online ordering, ask which receipt formats and practice safeguards are available for your setup and confirm current US availability.
Frequently asked questions
Is a matching total enough?
No. Check the individual items, quantities, options, discounts, fees, tax, and tip as well. Two line errors can offset each other, and a correct total can accompany an incorrect order description.
Which checkout screen should I compare with the receipt?
Use the final summary immediately before the guest submits the order. Compare it with the receipt for the same order, then check any later amendments separately.
How often should I repeat the audit?
Run a baseline before relying on a new setup, then repeat relevant baskets after changes to menus, charges, promotions, fulfillment, or receipt formats. Investigate a guest-reported mismatch promptly.
