Yes, a restaurant POS may be able to document an exemption without changing tax on unrelated items. But do not assume every system handles that workflow the way your restaurant needs. Ask the vendor to demonstrate a mixed sale: one approved exempt item, one item that remains taxable, an authorized staff action and a record of what changed.
The buying decision is whether staff can complete that sequence clearly during service and whether a manager can review it afterward. A button labeled “tax exempt” is not enough if it removes tax from the whole ticket or leaves no useful explanation.
Define the exemption workflow before the demo
Start with your restaurant’s requirements, not the vendor’s default screen. Decide what information staff must receive before applying an exemption, who may approve it and whether it applies to a guest, a transaction or particular items. Your qualified tax adviser can help determine the appropriate treatment and documentation for your circumstances.
Turn those requirements into a short service scenario. For example, a cashier starts an order with two items. A guest presents exemption documentation for one item. The cashier needs a manager to approve the change, while tax remains on the other item. The cashier then needs to see a clear total before completing the sale.
Write down the expected result at each handoff:
- Proof: What information must be recorded, and where should staff find or enter it?
- Authority: Which role can apply or approve the exemption? Can an ordinary cashier proceed without that approval?
- Scope: Which item or charge should change, and which should stay as it was?
- Review: What should appear on the receipt and in the manager’s records?
Also decide what staff should do when proof is missing or a manager is unavailable. They need a route that follows your approved policy, not an improvised override. This decision belongs in the requirements for any restaurant POS system you are considering.
Compare the workflow, not the feature label
Give each vendor the same scenario and ask for a demonstration from the cashier’s screen through the manager’s review. Toast lists restaurant POS, hardware, online ordering, payments, KDS and integrations. Square offers restaurant point of sale and related payment and order tools. Fleksa offers restaurant POS connected with direct ordering, reservations and related tools. Those descriptions do not establish how any of them handles your exemption scenario.
Ask the person demonstrating the system to show the starting ticket, the attempted action by a cashier and the approved action by a manager. Then add an unrelated item or change its quantity. Does the exemption stay limited to the approved scope? If the approved item is removed and added again, what happens? Have the vendor show the result rather than describe what should happen.
Check the places your staff actually work. If the restaurant uses a counter terminal and a handheld device, ask to see the relevant steps on both. If an order can be edited from another screen, ask whether permissions and exemption details carry through. Discuss the devices you intend to buy alongside your POS hardware choices; do not assume every device has the same workflow.
For documentation and audit records, ask:
- Can staff record a reference to the proof supplied without putting sensitive information on a guest receipt?
- Does the record identify the approving user, the affected item and the change made?
- Can a manager find the transaction later and see the original and final amounts?
- What happens if the sale is voided, refunded or edited after approval?
- Does the workflow require a particular plan, processor, device or additional setup?
Record each answer as demonstrated, unavailable or still to be confirmed. Ask for any dependencies and costs in writing. Separate the quoted processing fees from the broader operating cost, which may include software, hardware and other charges. The guide to payments, processing cost, cash close and POS reports can help frame those quote questions.
Use an exemption test card with expected receipt lines
The following example is hypothetical. It is a workflow check, not a statement that these items qualify for an exemption or that these tax amounts apply to a real restaurant. The restaurant has already decided, with appropriate advice, that the first item should receive an exemption and the second should not.
Set up a simulated ticket with a $12 meal and a $6 beverage. For this example, assume the POS would otherwise calculate $0.96 in tax on the meal and $1.20 on the beverage. The starting total is $20.16: $18.00 in items plus $2.16 in tax. The approved exemption removes only the $0.96 meal tax, leaving a $19.20 total.
The table is the test card. Its expected amounts are the acceptance target; record actual results separately only after an authorized test. The figures describe sale amounts and tax, not processing fees or operating costs. Fixed, variable and exception costs are excluded.
| Step or line | Action or amount | Expected result |
|---|---|---|
| Proof and approval | Cashier records the required reference; manager approves | Approval is attributed to the authorized user |
| Meal | $12.00; exemption approved | Meal remains $12.00; its $0.96 tax is removed |
| Beverage | $6.00; no exemption | Beverage remains $6.00; $1.20 tax remains |
| Receipt total | $18.00 in items plus $1.20 tax | $19.20 total; receipt communicates the adjustment as required by the restaurant |
| Manager review | Open the simulated transaction record | Manager can find the approval, affected item and final amounts |
Before applying the exemption, try the action as a cashier without the required authority. The expected result is that the cashier cannot complete the override independently. Then have the authorized user approve it and inspect the item lines, tax and total. If the system displays tax only as an aggregate, ask how staff can verify that the unrelated item retained its tax.
Next, change the beverage quantity in the simulation and ask the vendor to explain the recalculated ticket. Separately, remove and re-add the meal. The restaurant should decide in advance whether that action requires a new approval. Compare the system’s behavior with that rule, including what the manager can see afterward.
Run practice checks in a vendor-provided demo or another approved simulation environment. Do not use a real card payment, send a guest message or dispatch a courier. A simulated receipt or report is sufficient for the initial check. If a later live service pilot is necessary, plan it separately with authorized staff and an approved operating procedure; do not treat a simulation as proof of live performance.
Set an operating rule and resolve exceptions
Assign one manager to own the test card and another authorized person to cover when that manager is away. Keep the approved proof requirement, permission rule and fallback together where staff can find them. Train cashiers to pause and request approval rather than guessing which items to change.
A practical acceptance rule for the example is: an authorized user can apply the approved exemption to the meal, the beverage tax remains $1.20, the ticket totals $19.20, and the manager can find the approval and affected item afterward. If any part fails, the workflow has not met that rule, even if the final total happens to be correct.
Agree on a fallback before service. That might mean holding the transaction for a manager or following another restaurant-approved procedure. Do not ask staff to use a broader exemption simply to finish the ticket. For refunds, split checks, edited items or missing records, ask the vendor to demonstrate the exact behavior and ask your qualified adviser how your policy should address the situation.
Before signing or changing the setup, get unresolved plan, processor, support and contract terms in writing. Ask what setup assistance is included and who can change permissions later. If a requirement cannot be met, decide whether an approved manual procedure is workable during a busy shift or whether it is a reason to keep evaluating.
Next step: Request a Fleksa POS demo and bring your completed scenario, expected receipt lines and acceptance rule. Ask the demonstrator to show the cashier, manager and review steps on the devices you plan to use.
Frequently asked questions
Can a cashier apply an exemption without a manager?
That depends on your restaurant’s authority rules and the system’s permissions. Ask the vendor to show what happens when a cashier attempts the action and how an authorized user approves it.
Should an exemption appear on the guest receipt?
Decide what the receipt needs to communicate under your policy and consult a qualified adviser where necessary. Ask the vendor what the receipt shows and whether sensitive documentation can remain out of guest-facing printouts.
Is a correct total enough to pass the test?
No. Check that the exemption affected the intended item, unrelated tax remained in place, the right person approved the change and a manager can review the transaction record.
