When a tax setting changes for direct online orders, test more than one checkout total. Confirm the intended treatment with a qualified tax adviser, list the items and order types affected, and calculate expected results before changing the setting. Then compare those expectations with the checkout and receipt in a safe test environment.
The goal is to find where the customer-facing result differs from the decision you intended to apply. A single meal at pickup may look right while a discounted order, delivery fee, or mixed basket does not.
Confirm the treatment and assign the work
Start with a written decision from your qualified tax adviser. Give the adviser the facts about what you sell, where you operate, how customers receive orders, and the date the change should take effect. Ask about the items, charges, and discounts that matter to your restaurant rather than relying on a broad label in a software menu.
For each affected case, record the expected treatment in plain language. Include whether menu prices are meant to stay the same, whether tax appears separately at checkout, and how relevant fees and discounts should be handled. If the adviser needs more detail, provide a sample receipt and the wording used for each charge.
Split the practical work among named people, even if one owner fills several roles:
- Adviser: confirms the treatment, effective date, and any cases needing separate review.
- Owner or manager: approves menu prices, fees, and customer-facing wording.
- System administrator: records the existing configuration and makes the authorized change.
- Tester: calculates expected baskets and compares them with the checkout and receipt.
Ask your ordering provider where the setting is applied and whether a change affects existing orders, scheduled orders, or only new orders. Agree on a time to make it, who can approve it, and how to restore the previous setting if results do not match the approved decision. Keep a copy of the old and new settings and the approval with the test results.
A setting can be correct while a price decision is still unresolved. For example, if the intended change raises a guest's total, decide whether to leave the menu price alone or review it separately. Don't alter prices just to make a test pass; the expected total needs to reflect the owner's approved price and the adviser's treatment.
Build a list of affected orders
Make an inventory of the actual paths a direct-order customer can take. Use your menu, ordering settings, and recent order patterns to choose cases. You do not need to test every possible combination, but you do need to cover each distinct treatment and each way the order can reach the restaurant.
Start with pickup and delivery if you offer both. A delivery order may include a delivery charge that does not appear on pickup. Check whether the treatment of that charge has been decided, and whether the guest sees it clearly before placing the order. If you offer scheduled orders, ask how the system handles an order placed before the effective time for fulfillment afterward.
Next, group menu items by the treatment your adviser specifies. Include a representative item from each group and at least one mixed basket. Add common modifiers, such as an extra topping or a size change, if they affect the price. A modifier should not disappear from the calculation simply because it is selected inside another item's screen.
Finally, list adjustments: a coupon, an item discount, an order-level discount, and any other charge you actually use. Ask how each adjustment is applied and rounded. If your menu includes a special item or promotion that changes infrequently, decide whether it needs its own case rather than assuming the most common basket covers it.
Check every customer entry point that uses the ordering setup. A guest may begin on your restaurant website, but the relevant question is whether the same current menu and checkout treatment appear along each route. If you are also comparing systems, the online ordering buying guide can help frame the wider purchase; keep this test focused on the tax change.
Write expected totals before testing
Calculate the expected result for each basket in cents before looking at the changed checkout. Record the menu price, adjustments, guest-facing fees, expected tax, and final amount. Use the treatment and rounding instructions supplied by your adviser; do not infer a tax rule from the examples below.
Hypothetical test assumptions: The owner has approved the prices and fees below, and the adviser has supplied the expected tax amounts for these particular baskets. Amounts are shown in dollars and cents. Discounts reduce the amount charged to the guest. The delivery charge is a guest-facing fee, not a courier expense. These are test expectations, not a tax calculation or a statement about Fleksa's settings.
| Test basket | Prices and adjustments | Expected tax | Expected guest total |
|---|---|---|---|
| Pickup: one meal | Meal $12.00; no discount or fee | $0.90 | $12.90 |
| Pickup: mixed basket with discount | Items $18.00; discount −$2.00; no fee | $1.05 | $17.05 |
| Delivery: meal and modifier | Meal $12.00; modifier $1.50; delivery fee $3.00 | $1.20 | $17.70 |
The table separates the guest-facing pieces so a mismatch can be traced. In the delivery case, $12.00 plus $1.50 plus $3.00 plus $1.20 equals $17.70. In the discounted pickup case, $18.00 minus $2.00 plus $1.05 equals $17.05. A correct final total alone is not enough: compare the individual lines too.
These examples include menu prices, the stated discount, the guest-facing delivery fee where applicable, and expected tax. They exclude tips and any other guest charges. They are not an operating-cost estimate: fixed subscription costs, variable processing or courier costs, and exception costs such as refunds are excluded. If any excluded guest charge appears in your checkout, add a separate expected case for it.
Write down the expected cents for boundary cases as well, especially small discounts or quantities that may create rounding differences. If a result differs by a cent, check the agreed rounding method and whether the system calculates at the item or order level. Ask the provider to explain the calculation rather than quietly changing a price to hide the difference.
Run the tax change test basket checklist
Use a sandbox, preview, or other provider-approved simulation that cannot create a real charge, send a guest message, or dispatch a courier. Confirm those safeguards before starting. If a safe simulation cannot show the receipt or another required result, ask the provider how to check it safely; do not use a real guest order as a practice case.
- Capture the starting point. Save the current setting, its effective time, and a sample of the current checkout and receipt. Record the approved new treatment beside them.
- Enter the new setting in the safe test environment. Confirm the correct location, menu, order channel, and effective time. Ask whether any separate setting controls fees, modifiers, or scheduled orders.
- Run the representative baskets. Include a simple pickup, a mixed-item basket, a common discount, a modifier, and delivery with its fee where offered. Add scheduled orders and other exceptions relevant to your restaurant.
- Compare each line and total. Check item quantities and prices, discount placement, fees, tax, and the final amount against the written expectations. Note the basket, time, expected result, and actual result for every mismatch.
- Inspect the receipt or order confirmation. Check that the same amounts and clear charge labels appear there. Also check what the restaurant receives, if the safe test environment exposes the order details.
- Resolve and retest. Ask the adviser about treatment questions and the provider about configuration or calculation questions. Repeat affected baskets after any correction, then have the owner approve the results.
Simulated checks are different from a live service pilot. If you decide a live pilot is needed after simulation, plan it separately with the provider and staff, including how real orders and any communications or dispatch would be handled. Do not present it as a harmless practice transaction.
After approval, make the authorized live change at the agreed time. Check early real order records and receipts against the approved expectations without interfering with guest fulfillment. If a mismatch appears, document it, involve the right people, and use the agreed rollback or correction procedure. Review affected orders as well as the setting; changing the configuration does not by itself resolve an earlier incorrect receipt.
Use this checklist to review your current setup, then ask Fleksa about restaurant online ordering, safe testing options, and verified availability in your US location.
Frequently asked questions
Should I change menu prices when tax treatment changes?
Not automatically. First confirm the treatment with your adviser, then decide whether your existing menu prices and resulting guest totals fit your pricing plan. Record any approved price change separately from the tax setting.
Is one successful checkout enough?
No. Test representative item groups, discounts, modifiers, and fulfillment modes. Compare the individual lines and receipt as well as the final total, because different errors can produce the same total.
What if the ordering system total differs from my expected total?
Save the basket and both results. Ask your adviser to confirm the expected treatment and your provider to explain the configuration and calculation. Correct the cause and rerun the affected cases before approval.
