Void an Order
Void is Vendion's function for removing an unpaid order that was created incorrectly. For paid orders, the return/refund flow applies instead – see article 16. The distinction matters for tax compliance.
Void vs. return – what's the difference?
| Action | Order state | Fiscal effect | Requires |
|---|---|---|---|
| Void | Unpaid order | Order is removed, no receipt sequence consumed | Permission or PIN approval + reason |
| Return (refund) | Paid order | New return order with negative amount created | Original receipt, reason and permission |
A paid receipt remains available after a refund. Do not create a new unpaid order to correct a paid purchase.
How to void an order
- Click Void in the quick buttons
- Dialog: "Anledning" / Reason (mandatory) – pick a quick option or type your own:
- Felbongad (mis-fired)
- Gäst ändrade sig (guest changed mind)
- Dubbelregistrerad (duplicate entry)
- Test
- Övrigt (other)
- Or type your own reason in the free-text field (free text overrides the quick option). Without a reason you can't confirm.
- Enter the manager PIN if you don't have the void permission yourself
- Confirm
- The tab is marked as voided. The table becomes available when no other active tabs remain.
Permission and PIN approval
Voiding is permission-gated:
- Junior staff (no permission): a dialog opens, a senior enters their PIN
- Staff with the required permission: Can void without extra approval
Both the triggering staff member and the approving manager are logged in journal memory. That means you can always trace who did what, even when staff share responsibilities.
What happens in the system?
- The order is flagged as voided
- The tab closes without being recorded as a paid sale
- The table becomes available if it has no other active tabs
- Journal memory gets a row with the void action and the reason
- If the items were already fired to the kitchen, KDS shows a red STOP COOKING banner (with the reason) so the kitchen can notice the change. Also inform the kitchen if preparation has started
- The Z report reports number of voids and total amount – the Swedish Tax Authority wants this as a control point
History
The voided tab remains in history. Enter a clear reason so the restaurant manager can follow up incorrect orders.
Common issues
| Problem | Cause | Fix |
|---|---|---|
| "Can't void – order is paid" | Order already finalized | Use Return from order history instead |
| "Manager PIN required" | You lack the capability | Ask a senior to log in or enter their PIN |
| Action blocked | The tab may have changed or a payment may be running | Read the message and check the current tab status |
| Item already served | Voiding only removes the order in the system, not the food that left the kitchen | Handle as a comp (discounted/free line) or return after payment |
Tips
- Use the same reason consistently across the team (quick option or free text) so reports stay meaningful
- Train staff: think before voiding – it's easier to fix a mistake than to create new ones
- Review weekly voids in order history (shows who voided and why) – trends can reveal issues (shared PINs, training gap)
- Follow up recurring reasons together with the team.
This feature is part of Vendion POS.
Curious how it looks in practice? Read more about the product or book a short demo.
Was this article helpful?
