To identify unusual discount activity, compare each adjustment with your restaurant’s approved offers and review rules. Then trace exceptions to the original order, check who applied the discount and why, and record what the manager found. A large discount is a reason to ask a question, not proof that someone did anything wrong.
Keep discounts separate from voids and refunds. A discount reduces the price charged on an order. A void or refund reverses an item, transaction or payment under the restaurant’s process. Those events may appear near each other, but they answer different questions and should not be added together as if they were all discounts.
Define the discounts your team can use
Start with a short list of discount categories and the rules for each. The list gives managers a consistent way to interpret a report and gives employees a clearer way to explain an adjustment.
- Authorized promotions: Offers approved for a particular item, guest group, time or order. Record the offer’s terms and who can apply it.
- Staff meals: Reductions allowed for employees. State which items qualify, when the benefit applies and whether another manager must approve it.
- Manual adjustments: Reductions entered for a specific situation, such as an approved service recovery. Define who can enter them and what explanation is expected.
Make the categories specific enough to be useful without creating a long list that slows down service. For example, “promotion” can be a valid reason if the order can also be tied to the applicable offer. “Other” may be necessary occasionally, but it should prompt a short explanation rather than becoming the default.
Write down the boundaries that matter to your restaurant: eligible items, maximum amounts or percentages, approval roles and whether multiple offers can be combined. Keep expired offers on a dated reference list so a manager can check the rules that applied when an older order was placed.
Also agree on how to handle mistakes. If an employee selects the wrong reason but the discount itself is valid, the follow-up may be a correction to the record or a reminder about the right category. If the amount is outside the rules, the manager needs more detail before deciding what happened.
Choose report fields that support a real review
A useful discount report should help a manager move from a summary to an individual order. When evaluating a restaurant POS, ask to see how a discount appears in a report and how the manager opens the related transaction. Do not assume a total by itself provides enough context.
Ask whether the report can show or export these details, and whether each field is recorded when a discount is applied:
- Order identifier: A reference that connects the adjustment to the original order.
- Employee: The person whose login applied the discount, plus any recorded approver.
- Time and date: When the adjustment was entered, so it can be compared with the shift and offer period.
- Reason or category: The selected reason and any available note.
- Amount and basis: The dollar reduction, the price it reduced and, where relevant, the percentage.
Ask whether the reduction applies to one item or the whole order. A $10 reduction on a $20 item tells a different story from $10 off a $200 check. If the report shows a percentage, confirm which amount the system uses as its base and whether it accounts for more than one adjustment.
It also helps to see the order status and any recorded changes. A discount followed by a void is not automatically suspicious, but the sequence matters. Review the discount as a price adjustment, then examine the void separately using your normal reversal process. Avoid counting both as a single loss figure.
Check access as well. Who can run or export the report? Can a manager limit it by date, employee, location or reason? If the system cannot show a detail you need, ask how the team would document it elsewhere and who would maintain that record. That answer belongs in your buying decision alongside the other tools in your restaurant management software workflow.
Use a worksheet to inspect an exception
Set review triggers that fit your menu and policies. They are filters for a closer look, not automatic findings. A manager might review unusually large reductions, repeated use of an open-ended reason, discounts outside an offer’s hours or adjustments entered under an unexpected login. Compare like with like: a staff-meal benefit should be checked against the staff-meal rule, not against a guest promotion.
Hypothetical example: A restaurant’s review rule flags any single discount over $20 or over 25% of the eligible order subtotal. An order has an $84 eligible subtotal and a $30 discount, leaving $54 before any other charges. The discount is about 35.7% of that subtotal, so it meets both review triggers. The figures show an order price adjustment, not profit or all-in operating cost. Fixed costs, variable costs and exception-handling costs are excluded; no other charges or adjustments are included.
The worksheet below shows how a manager could move from the flag to a decision. The stated rule triggers review; the order details determine the outcome.
| Review step | Example finding | Manager action |
|---|---|---|
| Identify the adjustment | Order 417; $30 off an $84 eligible subtotal | Open order 417 and confirm the discount amount and basis. |
| Check context | Manual adjustment, entered during the dinner shift | Check the employee login, timestamp, reason note and any recorded approval. |
| Compare with policy | The reduction exceeds both review triggers | Check the manual-adjustment rules and ask the employee or approver for context if needed. |
| Record the outcome | Manager confirms an approved service recovery and records the explanation | Close the review; note whether the original record needs a correction. |
The outcome depends on the explanation being supported by the restaurant’s records and policy. If approval cannot be established, the manager should leave the review open and follow the restaurant’s escalation process. If the original order shows a different subtotal or another adjustment, recalculate before reaching a conclusion.
Look for patterns only after checking individual orders. Several reductions under one login might reflect a manager handling approved service recoveries, shared credentials or a training issue. Ask which explanation fits the records. A count or total can direct attention, but it cannot establish intent.
Document the decision and make the process usable
For each reviewed exception, keep a concise record of the order identifier, discount amount, reason for review, evidence checked, person consulted, decision and review date. If a question remains, assign an owner and a follow-up date. Store the record where authorized managers can find it without exposing unnecessary guest information.
Choose the response to match the finding. An approved adjustment may need no action beyond documentation. An incorrect category may call for a record correction and a reminder. An unclear policy may need a rewrite and a shift briefing. An adjustment that remains unexplained should go through the restaurant’s established escalation process rather than an accusation in a report.
Give managers a regular review window that fits the volume of transactions. During a busy shift, they may only have time to note an issue; a later review can check the order and speak with the people involved. Decide who covers the review when the usual manager is away, and periodically check whether the triggers produce useful questions or too many routine flags.
Before buying or changing systems, walk a provider through a simulated discount review. Use sample order data and ask how a manager would find the employee, time, reason, amount and order identifier, then document the outcome. Keep the exercise in a training or demonstration environment and ensure it cannot charge a card, send a guest message or dispatch a courier. A live service pilot is a separate decision: agree on its scope and staff responsibilities before using the system for actual orders.
Bring your discount categories, review triggers and worksheet to a provider discussion. Ask to see the full path from report to order and how missing context would be recorded. You can also discuss these POS requirements with Fleksa as part of your evaluation.
Related guide: How to switch POS systems without losing a service day.
Frequently asked questions
Does a high discount mean an employee committed fraud?
No. It means the adjustment meets a review trigger. Check the order, applicable policy, recorded reason and approval before deciding whether further action is needed.
Should voids appear in a discount audit?
They can provide context for an order, but review them separately. A discount changes the price; a void reverses an item or transaction under the restaurant’s process.
What if the POS does not record a discount reason?
Ask the provider how managers can capture and retrieve the explanation. Until you have a reliable process, assign someone to maintain a separate record tied to the order identifier.
