Yes—a manager can review voided and comped items without treating them as paid sales if the POS records those actions separately and its reports make the distinction clear. Before buying, ask the vendor to demonstrate the full path from the check to the sales report and the exception report. Do not assume that a missing item on a sales report is also available for review elsewhere.
The useful question is not simply whether a system has a void button. You need to know what the reports count, what dollar value they show, who approved each action, and whether a manager can trace an unusual entry back to the original check.
Start with the action and when it happened
A void commonly means an item was removed from a check. A comp commonly means an item was provided without charging the guest, often as a service recovery or courtesy. Vendors may use these words differently, so ask each one to define its terms and show how an employee selects them.
Timing matters. Removing a drink entered by mistake before it reaches the kitchen is different from removing a meal after it has been prepared. Both may appear as a void, but only the second might involve food waste. A comped dessert might have been served and eaten; a comp does not automatically mean the item was wasted.
For each action, ask whether the POS records when the item was entered, when it was removed or comped, and whether it had already been sent for preparation. Also ask whether a manager can see the original item and its value after the action. If the report only shows a total, it may be hard to tell a frequent entry mistake from a recurring kitchen or service problem.
The people affected differ too. A server needs a straightforward way to correct an entry. A manager needs enough context to approve and investigate exceptions without slowing service unnecessarily. An owner needs totals that can be compared with paid sales without treating removed or complimentary items as cash collected.
A restaurant POS system should be evaluated against those everyday jobs, not just a list of report names. Write down the terms the vendor uses during the demo; its definition of a void or comp may determine which report you need.
Run one sample check through the reports
The following figures are hypothetical and describe a simulated check, not a claim about any vendor's software. Use a training or demo environment that cannot process a real payment, send a guest message, or dispatch a courier. Ask the vendor to show the records rather than assume the system behaves like the example.
- One sandwich is kept on the check and paid: $14.
- One $6 drink is entered by mistake and voided before preparation.
- One $8 dessert is served and comped after a service issue.
The intended result is one paid item worth $14, one voided item with an original value of $6, and one comped item with an original value of $8. The original menu values add up to $28; the $14 difference from the paid item consists of the $6 void and $8 comp. The drink and dessert values are not paid sales. They are menu values used to review exceptions, not estimates of food cost or profit.
This is an item-value example, not an operating-cost calculation. It excludes fixed costs, variable costs such as ingredients and processing fees, and exception-handling costs such as staff review time. It also excludes other check adjustments. A sales or payment report may use different definitions or include other amounts; ask the vendor to explain them rather than forcing the example to match a report label.
Have the demonstrator enter the three items, apply the actions, and open both the check detail and the relevant reports. Record the vendor's response to these questions:
- Where does the paid sandwich appear, and does the report show $14 as the amount paid for it?
- Where can a manager find the voided drink and comped dessert, including their original values?
- Are the two exceptions counted separately, and can the manager see the reason and approving person for each?
- Can the manager navigate from each report entry back to the sample check?
Ask for the report names and definitions in writing. If a vendor calls the original $28 a gross sales figure, find out whether and where it also shows the $14 paid amount. A report can use a broad sales label without making its treatment of exceptions obvious.
Compare counts, values and check detail
Look at three kinds of evidence together: the item or check detail, a sales or payment view, and the void and comp entries. For the sample, the expected exception count is two actions: one void and one comp. The expected exception value is $14 at original menu prices. That does not mean $14 was collected, or that $14 of ingredients was discarded.
First compare the counts. If the check detail shows both actions but a report shows only one, ask whether the report combines categories, uses a different time range, or excludes an action under its current filters. Then compare values. Confirm whether a reported amount is the original item price, an adjustment amount, or an amount actually paid.
Next, compare the timing and reason. In the sample, the drink was removed before preparation, while the dessert was served. Grouping both as “waste” would overstate what the check alone proves. The dessert may be a useful service-recovery measure even if no food was thrown away. To establish actual waste, a manager may need preparation or disposal evidence beyond the exception report.
One result should change the buying decision: imagine the demo shows the paid amount correctly, but the voided drink disappears without an item-level record. The sales total alone would not satisfy an owner who wants to investigate removed items. Ask whether another report, permission, or configuration exposes that record. If the vendor cannot demonstrate it, treat the requirement as unmet for your decision rather than assuming a later setup will solve it.
Check the same date range and location across reports, and ask how reopened checks or later corrections affect the figures. A manager should be able to explain a difference rather than spend every close guessing which number to trust. For the broader close process, see payments, processing cost, cash close and POS reports.
Review exceptions with a reason and follow-up
The table turns the sample into a manager's review. The approver entries describe what the restaurant wants to capture; they do not imply that a particular POS records those people automatically. The follow-up compares the reason against another piece of evidence before drawing a conclusion.
| Item and action | Reason to record | Approver to record | Manager follow-up |
|---|---|---|---|
| $6 drink void | Entered by mistake before preparation | Shift manager, if approval is required | Check the action time and preparation status; look for repeated entry errors. |
| $8 dessert comp | Service recovery after an issue | Manager who authorized the comp | Compare the note with the check and ask whether the same issue is recurring. |
During the demo, ask whether reasons come from a selectable list, free text, or both. A short list makes patterns easier to compare; a note can explain an unusual situation. Find out whether staff can skip a reason, change it later, or approve their own action. Also ask whether the report identifies the employee who made the change separately from the person who approved it.
Set a review routine that fits the restaurant. A shift manager might check that day's unusual entries against check detail, then bring repeated issues to the owner. The point is to resolve a question: Was an item entered twice? Did a service problem justify a comp? Was an item prepared before it was removed? An exception is a prompt for review, not proof that an employee did something wrong.
Before selecting a system, ask each vendor to show the report filters, available detail, approval controls, and an export or other practical way to share the results. Confirm whether the same records remain visible after a check is closed or corrected. Ask who can access them and whether access can be limited by role. If a requirement depends on a setting, have the vendor identify the setting and include it in the written response.
Compare the demonstration with your existing management routine, not just the appearance of a dashboard. Your restaurant management software may need to support a manager reviewing the detail while an owner reviews totals. Use the POS questions as a starting point for other setup questions.
Next, request a demo of Fleksa's restaurant POS system using the sample check above. Ask the vendor to document where each item appears, what each report value means, and which reason and approval details a manager can review.
Frequently asked questions
Should a voided item appear in paid sales?
An item removed without payment should not be treated as money collected. Ask the vendor how its sales and payment reports define their totals, and where the original voided item can be reviewed.
Is a comp the same as food waste?
No. A comp records an item given without charging the guest; it may have been served and eaten. A waste assessment needs evidence about what was prepared or discarded.
What should a manager check if exception totals do not match?
Compare the date range, location, action type, report definitions and individual check details. Ask whether later corrections or report filters account for the difference before treating it as an error.
