To compare restaurant POS systems for item-level discounts, ask each vendor to show the same order from entry through receipt. The essential question is simple: can an authorized staff member discount the intended item, leave excluded items alone and see the right total before payment?
Do not stop at a demonstration of a percentage button. A discount applied to one unit, every unit on a line or the whole order can produce three different totals. Your buying decision should rest on the result your restaurant actually needs, including how staff handle quantities and corrections.
Set the discount rule before the demo
Start with an offer your staff might reasonably need to apply. Decide whether it covers one unit or every unit of an eligible item, whether modifiers count, and which items must remain at full price. Also decide who may apply it and when: before an order is sent, after it is sent, or both.
For example, a manager might approve a discount on one entrée because of a service issue. If a party ordered three of that entrée, the manager may intend to reduce just one. A system that discounts the entire line could give away more than intended. Conversely, forcing staff to split a line into separate items may be workable, but it adds steps during a rush.
Write the expected result in cents. Specify whether the discount is calculated on the original item price or after another offer, and how fractions of a cent are rounded. If your restaurant allows multiple discounts on the same order, decide whether they can be combined. If it does not, ask what happens when someone tries.
The server needs to see a clear result before presenting the check. The guest needs a receipt that makes the charge understandable. The manager needs a way to resolve an incorrect selection without asking the guest to interpret the software. These are separate requirements, so include all three in the demonstration.
Compare the workflow, not just the feature name
Give each vendor the same written scenario and ask them to operate it using the roles and devices your restaurant expects to use. 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 alone do not establish how any of them handles your discount rule.
Ask the vendor to show the order on the screen where a server enters it. Then ask to see the discount applied by the intended staff role, the revised total and a sample receipt. If managers approve discounts on a different device, include that handoff. Check the relevant POS hardware configuration as well as the software.
Use questions that expose the actual steps:
- Can an authorized server select one unit from a line with several units, or must the line be split first?
- Can the server see which item received the discount and which item was excluded?
- Can the discount be removed or corrected before payment? What happens if the order has already been sent?
- Does the receipt identify the discounted item, the amount deducted and the final total clearly enough for a guest to follow?
- What can a staff member without permission do, and how does a manager approve or apply the offer?
- Does the same rule work in each ordering channel and on each device you plan to use?
Ask to see the relevant report as well, if you need a manager to check discounts after service. This comparison is about whether the calculation and display are right; a separate review of discount activity may require additional reporting requirements.
Record a function as unavailable if the vendor cannot provide it in the configuration being quoted. If a workaround is offered, write down the extra steps and who must perform them. Ask whether the workflow depends on a particular plan, device, payment processor or setup. Get those dependencies and the full quoted operating costs in writing. Processing fees alone are not the total cost of operating the system.
Use a cents-based discount worksheet
The following example is hypothetical. The order contains three identical eligible items at $4.35 each and one excluded item at $5.20. The intended offer is 15% off one unit only. For this worksheet, round the resulting discount to the nearest cent, with half a cent rounded up.
The eligible line totals $13.05, and the order subtotal is $18.25. The table compares three possible scopes. Only the first meets the stated rule. Amounts shown exclude tax, payment processing, other fees and any additional discounts; the table compares order calculations, not the restaurant’s operating costs.
| Discount scope | Calculation | Discount | Total before excluded charges |
|---|---|---|---|
| One eligible unit | $4.35 × 15% = $0.6525, rounded | $0.65 | $17.60 |
| All three eligible units | $13.05 × 15% = $1.9575, rounded | $1.96 | $16.29 |
| Whole order | $18.25 × 15% = $2.7375, rounded | $2.74 | $15.51 |
For the approved one-unit offer, the expected display is three eligible units and one excluded item, with a $0.65 reduction and a $17.60 total before the excluded charges. The excluded $5.20 item remains at full price. A receipt should make the $0.65 reduction and its target understandable; ask the vendor to show exactly how its receipt represents that calculation.
The other totals are useful warning signs. A $16.29 total indicates that the worksheet’s line-level calculation was used. A $15.51 total indicates the worksheet’s order-level calculation was used, including the excluded item. If a system shows a different figure, do not guess why. Ask whether it rounds each unit separately, applies the percentage to another base or uses a different rule for the selected scope.
Keep an expected-result sheet separate from your observations. During an authorized simulation, record the selected item, staff role, device, displayed discount, total and receipt wording. Mark any result you could not reproduce as unresolved. Run the simulation without a real card payment, guest message or courier dispatch. A later live service pilot is a separate decision and should use the restaurant’s normal controls.
Choose the rule and handle exceptions
Use the worksheet as an acceptance test, not as a promise that every offer must work the same way. For the example above, acceptance means an authorized person can apply 15% to one $4.35 unit, leave the $5.20 item undiscounted and verify a $0.65 reduction and $17.60 pre-charge total on the order and receipt. If the POS needs a line split to do that, decide whether the extra step is acceptable before signing.
Assign one person to own the rule and train staff on the exact selection. Set a fallback for a result that does not match: pause before payment, remove the incorrect discount if permitted and ask the manager to correct the order. If the manager cannot produce the expected result, use the restaurant’s approved alternative rather than improvising a new percentage.
Test changes that are likely to happen during service. What if a guest removes one of the three items after the discount? What if the server adds a modifier, changes the quantity or transfers the check? Can the authorized person identify and correct the discount after each change? Ask the vendor to demonstrate the states your staff will encounter, rather than assuming the original selection follows every edit.
Also settle the business rules around combinations, returns and adjustments. Ask the vendor how its configuration handles the applicable charges and receipt when a discount changes. For contract, legal or tax treatment questions, consult a qualified adviser. Keep those decisions separate from the arithmetic in the worksheet.
When comparing quotes, list any required hardware, setup, recurring charges, processing fees and costs for exceptions or changes. Ask about contract duration, cancellation and processor requirements rather than assuming they are the same across vendors. The broader restaurant management software workflow matters too: a discount that is easy to enter but hard for the manager to review may not fit your operation.
Bring your own item prices, excluded items and expected receipt to a restaurant POS system demo. Ask Fleksa to run the scenario and show whether the staff role, quantity handling and displayed total meet your acceptance criteria.
Frequently asked questions
What is the difference between an item and an order discount?
An item discount applies to a selected item or units, depending on the rule and system. An order discount uses an order-wide base. Ask the vendor to show which items are included before relying on either label.
How should a POS handle a quantity of several identical items?
It should support the scope your offer requires, whether that is one unit or the full line. If staff must split the line to select one unit, check that they can do so accurately in your service workflow.
Should the receipt show the discount?
Set a receipt requirement that lets a guest understand the reduction and resulting total. Ask for a sample showing the discounted item and amount, then decide whether its wording is clear enough for your restaurant.
