Protecting Your Bottom Line: The Void & Delete Report 🛡️📋
In a busy restaurant environment, tracking items that are removed from an order is just as critical as tracking sales. The Void & Delete Report is designed to answer one crucial question: "What was removed from orders, why, and who did it?"
This report provides a complete, time-stamped record of every voided item across your checks. It gives managers the complete visibility needed to verify that all order removal activity is legitimate, properly authorized, and consistent with your venue's established security policies. 🔎✨
📊 What You'll See on the Report
Every item removed from a check is displayed individually, giving you the complete backstory behind the modification.
Line-Item Breakdown: Each row features a single voided item, its quantity, and the financial value of the removal.
Full Operational Context: The report lists the exact date and time of the void, the associated order number, the employee who entered it, and any custom manager notes.
The Approval Chain: The report tracks exactly who approved the removal, making it simple to verify authorization loops.
Running Totals: A cumulative total of the voided dollar value appears at the bottom of each section so you can measure the overall impact at a glance.
📝 Report Example
🔄 Grouping Options: Tailoring Your View
You can reorganize how the data is structured depending on the type of operational audit you are conducting:
Void Reason (Default View): Groups your data by the reason codes selected at the POS terminal. This is best for measuring how often each reason code is used and its total cost to your business.
None: Creates a flat, unfiltered chronological log of every single void. This layout is ideal for a full-period security audit or when you are investigating a specific time-sensitive incident.
🛠️ Strategic Ways to Use This Data
Reviewing your void data regularly opens up several excellent opportunities for team accountability and operational coaching:
Loss Prevention: Because order removals are a common vector for internal theft and fraud, tracking them closely is a major security shield. A high void count—especially on high-dollar items, concentrated on a single employee, or occurring after a check has been printed—warrants immediate managerial follow-up. 🛑
Accountability by Reason: Grouping data by your custom reasons surfaces whether your team is using your POS codes correctly, or if certain reasons (like "Other") are being overused as lazy catch-alls.
Approval Chain Verification: Use the Approved By column to confirm that voids requiring supervisor intervention were signed off properly. Any blank entry on a void that requires a supervisor's authorization highlights a security compliance gap.
Targeted Training Opportunities: A high volume of "Wrong Item" or "Customer Changed Mind" voids linked to a specific staff member usually points to an order-taking or communication issue that can be easily fixed with a bit of server coaching. 🗣️
Kitchen Error Tracking: Notice a high concentration of voids tied to kitchen-related reasons (like "Incorrect Cook Temp" or "Wrong Prep")? This is a great signal to pull your back-of-house team together to streamline kitchen communication. 🍳
🎛️ Filters and Special Considerations
Filters Available
Void Reasons: Easily narrow the report down to one or more specific reason codes (such as filtering exclusively for Manager Comps or Kitchen Waste) to simplify your audit.
💡 A Note on $0.00 Voids
Many modifier and add-on items carry no additional charge, so their voided dollar amount shows as $0.00. This is completely expected! These entries are still highly valuable to review—removing a modifier still affects inventory accuracy and represents a production or service error, even when there is no direct revenue impact on the check.
Need Help? 💡
Why is an item that a server deleted missing from this report?
If an item was added to a check but deleted before the order was sent to the kitchen or saved, it won't trigger a void record. This report strictly tracks finalized items that were sent to preps and subsequently removed from an open check.
Can I create custom void reasons for my staff to select at the terminal?
Yes! You can configure your custom reason database in the back office. Reach out to your system administrator to add specific codes tailored to your restaurant's workflows.