Start by asking each vendor to trace an order for your exact location, delivery channel and POS: where does the item's tax information come from, and which system calculates the amount the guest sees? Then compare that channel order with the order received by the POS. A connection that sends the right item name does not, by itself, establish that the tax treatment or total is right.
The answer may differ by channel and location. Get the responsibilities in writing, agree on expected results with a qualified local adviser, and check representative orders before launch. Your goal is a clear path from menu item to channel total to POS record, with an owner for any difference.
Identify who supplies tax information and calculates the total
Draw the route an order takes. It may begin with a menu in your POS, pass through an integration, appear on a delivery channel and return to the POS as an order. At each handoff, ask what moves: an item name, a price, a tax category, a calculated tax amount or some combination.
Make a separate list for each restaurant location and active channel. Include the POS, any integration or middleware, the channel and the person who maintains the menu. Two locations with the same menu may need different decisions; two channels serving one location may handle order data differently.
Ask the channel, integration provider and POS vendor these questions together:
- Where is the tax category or other tax information for each item entered and maintained?
- Does the integration send that information, a calculated amount, both or neither?
- Which party calculates the tax shown to the guest? Which party sends the final total to the POS?
- What happens when the channel total and the POS calculation or record differ?
- Are delivery charges, service charges, discounts and modifiers handled separately from the base item?
- Who changes the mapping when an item, location or menu configuration changes, and how is the change checked?
Record an answer only for the actual combination being evaluated. If a vendor says a field is mapped, ask to see where it appears at the receiving end. If an action requires a person to update the channel menu, note that as manual work rather than assuming it happens automatically.
When comparing restaurant integrations, distinguish a connection's availability from its behavior. A connection being listed does not answer who supplies item tax or how a particular order total reaches your POS. Ask for a demonstration using the channel and location you intend to operate.
Build item cases before checking orders
Choose a small set of menu cases that reflect your operation. Start with a taxable item and, if a qualified local adviser identifies one that applies, an exempt scenario. Add a modifier, discount or fee only where it helps answer a real question about your menu. Ask the adviser what result should be expected for each case; don't infer local treatment from a vendor's default category.
For each case, write down the item and modifier identifiers, menu price, location, channel, expected tax treatment and expected order total. Note who approved the expected result and when. A description such as “no tax” is not enough on its own: record the circumstances under which that result is expected.
Then ask the vendor to show the same case in the source menu, the channel order and the receiving POS. Check whether the item and its modifier arrive as intended, not merely whether the final number looks plausible. A correct total can conceal an incorrect item mapping or an offsetting difference elsewhere.
Use this worksheet as a starting point. The figures are hypothetical, not tax advice or a claim about any provider. For this illustration only, an adviser has supplied an expected $2 item tax on a $20 item and an expected $0 tax on a separate $10 exempt case. The first order also has a $3 delivery charge assumed to have no tax; the second has no delivery charge. There are no discounts, service charges or other order fees. These are order totals, not the restaurant's operating costs: fixed costs, processing fees and exception-handling costs are excluded.
| Case | Expected channel order | What to check in the POS | Owner and next decision |
|---|---|---|---|
| Taxable item | Item $20 + item tax $2 + delivery $3 = $25 | Item, tax, delivery charge and $25 total match the channel record | Manager records results; vendor explains any missing or different field |
| Applicable exempt case | Item $10 + item tax $0 + delivery $0 = $10 | Correct item and $0 item tax appear; total is $10 | Adviser confirms applicability; manager checks the POS record |
The table states expected results, not observed results. During a check, add the actual channel and POS values to your own record. If the POS shows $24 against the first channel order's $25, identify the specific $1 difference and ask which system supplied it. Don't adjust an unrelated menu price just to make the totals match.
Compare channel and POS results safely
First ask vendors for a simulated or sandbox check that cannot charge a real card, message a guest or dispatch a courier. Confirm those safeguards before creating the order. Give the simulation a unique test identifier so the source order can be matched to the POS and kitchen result without using private customer information.
Capture the relevant screen values or a redacted order record at each step. For each case, compare:
- The source menu item, location, price and tax information that should apply.
- The channel's item, modifiers, charges, tax and displayed total.
- The order received by the POS, including the same item details and total.
- The kitchen result, to confirm the intended item and modifiers reached the right destination.
Mark each field as matching, different or not visible. If a field is not visible, ask how staff can verify it. Keep expected values separate from observed values, and record whether a staff member had to re-enter or correct anything. A vendor demonstration should show the actual channel and POS combination, not just a generic order screen.
Also ask how the provider handles a supported exception, such as an order that cannot be sent to the POS. Who receives an alert, what information is available for correction, and how does staff know whether the order was eventually received? If a case is intentionally unsupported, record it as a limitation and decide whether your team can operate around it.
A simulation checks the configured path; it is not the same as running a live service pilot. If you later plan a live pilot, agree on its scope and safeguards with the vendors and your team. A practice scenario should never require a real payment, guest message or courier dispatch. Neither a successful simulation nor a pilot removes the need to monitor actual orders after launch.
Assign unresolved questions and decide whether to launch
Turn the worksheet into a short responsibility register. For every channel and location, record the system that maintains item tax information, the party that calculates the guest-facing total, the receiving POS behavior and any manual step. Add the named owner, the evidence or order record to review, and a date for the next decision.
Separate operational decisions from tax decisions. A manager can check whether two displayed totals match; a qualified adviser can help determine the expected treatment for the jurisdiction and circumstances. Ask the vendors to explain their configuration and data flow rather than treating a vendor's screen as a substitute for that advice.
For example, if the taxable case matches but the applicable exempt case cannot be demonstrated for your channel and POS, do not mark the whole integration verified. Ask whether the case is supported, whether a manual process is available and who owns it. Proceed only after the responsible people have agreed on an acceptable process and how staff will check it.
Review the register when you add a location, change a menu item or switch a channel or POS. For the broader connection decision, the guide to direct POS integration and middleware covers the operational tradeoffs. You can also ask how the order should appear in your restaurant POS system.
Next step: Bring your channel and location list, POS details and sample cases to a Fleksa integration discussion or demo. Ask the team to trace each case and confirm availability for your restaurant's location.
Frequently asked questions
Does the POS always determine delivery item tax?
Do not assume it does. Ask which system supplies the item's tax information and which party calculates the channel total for each location and connection.
What should I do if channel and POS totals differ?
Compare the item, modifiers, discounts, charges and tax line by line. Record the difference and ask the responsible vendors to trace it before making a correction.
Can I verify an exempt scenario without a live order?
Ask for a safeguarded simulation using an applicable case approved by your local adviser. Confirm that it cannot trigger a real payment, guest message or courier dispatch, and compare the simulated channel and POS records.
