A base-item price check will not catch every checkout error. A sandwich can appear at the right price while its required side, extra cheese, or second sauce is charged incorrectly. The way to catch those errors is to compare the approved direct-order menu with the choices and totals in the cart, one valid combination at a time.
Start with a small matrix of modifier groups, expected charges, and actual cart results. Include required choices, optional extras, repeated quantities, and combinations that exercise the ordering rules. Calculate the expected item subtotal in cents before you open the cart. Then trace each difference through the menu, ordering configuration, and checkout display.
Choose modifier groups for the audit
Use the approved prices for your direct-order menu as the starting point. Choose one dated version and identify who can approve changes. If your printed menu or another channel has different prices, do not assume it is the direct-order source of truth. This audit is about what a guest should pay through your own ordering channel.
List the base items and their modifier groups. A group is a set of choices attached to an item, such as sides, protein substitutions, toppings, or sauces. Record whether the guest must choose an option, may skip it, or may select more than one. Include any limits on quantity and note whether a charge applies once per selection, per unit, or only after an included allowance.
Prioritize groups that are easy to misread or expensive to get wrong:
- Required choices: A side may be required even when one option costs nothing and another has an upcharge.
- Optional extras: Cheese, avocado, or a sauce may have a separate price that is easy to overlook when the base item matches.
- Quantity-based choices: Two portions of an extra should follow the approved per-unit rule, not automatically receive a single charge.
- Included allowances: A menu may include one topping and charge for the next. Confirm how the rule treats different combinations and quantities.
- Size or variant differences: An addition may have a different approved price on a small item than on a large one.
- Unavailable or changed options: A retired option or an old price can remain visible if the direct-order setup was not updated with the menu.
For a large menu, begin with the highest-risk groups rather than trying every possible basket at once. Pick items with several modifier rules, recent price changes, or extras ordered often. Then work through the remaining groups on a schedule. Record coverage so that an untested option is not mistaken for a passing one.
Also note where the price appears to the guest. A selection screen may show an upcharge, while the cart shows the final item price or a separate modifier line. Both views should support the approved price and make sense together. The online ordering buying guide can help frame broader checkout questions; the matrix below focuses specifically on modifier charges.
Calculate valid option combinations
The following is a hypothetical audit of one direct-order sandwich. Assume the approved base price is 1,200 cents. The guest must choose one side: chips add 0 cents, and a salad adds 150 cents. Cheese is optional and adds 125 cents. Extra sauce is optional, costs 50 cents per portion, and is limited to two portions. These are sample menu rules, not Fleksa prices or product claims.
The table gives expected item subtotals before any order-level charges. Calculate each row independently. A choice that violates the approved selection or quantity limits is not a valid priced basket; check separately that the ordering setup prevents it.
| Audit case | Valid selections | Expected calculation | Expected item subtotal |
|---|---|---|---|
| Required choice only | Sandwich and chips | 1,200 + 0 cents | 1,200 cents ($12.00) |
| Required upcharge | Sandwich and salad | 1,200 + 150 cents | 1,350 cents ($13.50) |
| Optional addition | Sandwich, chips, and cheese | 1,200 + 0 + 125 cents | 1,325 cents ($13.25) |
| Multiple rules | Sandwich, salad, cheese, and two sauces | 1,200 + 150 + 125 + (2 × 50) cents | 1,575 cents ($15.75) |
These rows test different things. The first establishes that the free required choice does not add a charge. The second checks the paid side. The third isolates an optional extra. The fourth combines the paid side, cheese, and the maximum sauce quantity, making it easier to catch a charge that is applied once instead of twice.
Keep the item subtotal separate from the full order total. The examples include the base item and selected modifiers only. They exclude delivery charges, service charges, discounts, tips, and applicable tax; they do not estimate fixed operating costs or exception costs. If the cart shows only an order total, account for every other displayed charge before deciding that a modifier caused the difference.
Build more rows for your own menu. For an included allowance, calculate a selection within the allowance and another just beyond it. For a size-dependent extra, test the same addition on each applicable size. For a required group, try proceeding without a choice and confirm the setup requires a valid selection. For quantity limits, try to select more than the allowed amount without completing an order.
Do not treat an impossible combination as a price failure. If the approved rules allow only one side, a basket containing two sides should be blocked or otherwise handled according to the approved menu rules. Record an incorrect selection rule separately from an incorrect price so the person fixing it knows what to investigate.
Trace each mismatch to its source
For each test, compare three points: the approved direct-order menu, the direct ordering configuration, and the guest-facing selection and cart. A difference at any point deserves a record, but it does not always require the same fix.
- Confirm the approved rule. Check the item, size, modifier name, price, quantity limit, and effective date. Ask the menu owner to resolve an unclear or conflicting rule before anyone changes the system.
- Inspect the configured choice. Compare the option and its pricing rule with the approved menu. Look for an old amount, a charge attached to the wrong option, or a quantity rule that does not match the intended menu.
- Reproduce the guest path. Select the same item and options in direct checkout. Record what appears on the selection screen and in the cart, including quantity and any separate lines.
- Assign the next action. The menu owner approves the intended price; the person responsible for the ordering setup investigates configuration; a vendor support contact can help investigate behavior the operator cannot explain or change.
A useful mismatch record names the item and variant, modifier group, selected options, approved calculation, actual result, date, and person responsible for the next step. Save a screenshot if it helps show the guest path, but do not include guest details. Record the ordering link or location being checked when you operate more than one location.
Suppose the fourth hypothetical basket above appears at 1,525 cents instead of 1,575 cents. The 50-cent gap is consistent with one sauce portion being omitted, but it does not prove the cause. First confirm that two portions were selected. Then inspect the sauce rule and the cart presentation. If the configured rule and guest result disagree, send the exact steps and expected calculation to the support contact. Do not change the base sandwich price to cover an unexplained modifier difference.
Also separate a confusing label from a wrong total. A cart might present a bundled item subtotal rather than list every addition separately. Check the arithmetic and ask whether the display gives the guest enough information to understand the charge. If the total is correct but the selections are unclear, log that as a display issue rather than marking the price calculation wrong.
If your restaurant website links guests to direct ordering, follow the same path a guest would use. You are checking the direct menu and checkout here, not trying to make every marketplace price match. For the broader commercial comparison, see the guide to direct and marketplace order contribution.
Retest corrected baskets and keep the audit current
After a change, rerun the exact failed basket and record the new actual item subtotal beside the expected subtotal. A fix is not complete simply because someone edited a price. The guest-facing result must match the approved rule, and the selection constraints must still behave as intended.
Then retest nearby cases. If a sauce quantity rule changed, check no sauce, one portion, and the permitted maximum. If a required side changed, check both the free and paid choices. If an item has several sizes, check the sizes affected by the change. This makes it less likely that a correction to one option creates a new problem elsewhere.
Use a simulated check that stops before order submission. It must not charge a real card, send a guest message, or dispatch a courier. Ask the provider how to inspect the cart safely or use a non-live test environment if the normal checkout cannot be checked without those actions. A live service pilot is a separate decision: if you later run one, use authorized staff, agree on the workflow in advance, and understand which real notifications, payments, and fulfillment actions it may trigger.
Mark each matrix row as passed, failed, blocked, or not yet tested. A blocked case needs an owner and a reason; it is not a pass. Record the date of the retest and the menu version used. When an approved price or modifier rule changes, add the affected cases to the next audit rather than relying on the original result indefinitely.
Start with one item that has a required choice and a quantity-based extra. Build its matrix, calculate the expected subtotals, and check the cart without submitting an order. If you are evaluating Fleksa restaurant online ordering, bring those cases to Fleksa and ask about current US availability and how your specific modifier rules would be configured and safely tested.
Frequently asked questions
Why check modifiers if the base item price is correct?
Modifiers can have their own prices, quantities, and selection rules. A correct base price does not show whether a paid side or multiple portions of an extra are charged correctly.
Should I compare the whole order total?
Compare the item subtotal first. If only a full total is visible, account separately for displayed fees, discounts, tips, and applicable tax before attributing a difference to a modifier.
How often should I repeat the audit?
Retest affected cases after menu or configuration changes and schedule periodic checks of the remaining groups. Prioritize complex rules and recently changed prices, while keeping a record of what has not yet been tested.
