Skip to main content
Reasons are codes that explain why a line item was voided, comped (given free to the customer), or gifted (staff perk). Every void, comp, or gift line on a ticket must have a reason, creating an audit trail of what happened and why. Reasons help you spot patterns — for example, if “Customer Request” voids spike on a particular shift, you might coach staff on how to prevent those errors, or if comps are high, you can track which managers are giving them away most frequently.
Reasons list screen showing VOID, COMP, and GIFT categories with associated codes

​
Reason Fields

​
Reason Type Examples

Use this table to understand which reasons belong in each category:
Keep reason codes focused on the why, not the what. Don’t create separate reasons for every item type — just for the circumstances that drive voids/comps/gifts. Most restaurants need 8–12 reason codes total (2–4 per type). Too many options slow down staff and dilute your reporting.

​
Create a Reason

1

Go to Manage → Reasons

Click Reasons in the left sidebar under Manage.
2

Click New Reason

Enter a Code, Name, and select the Type (VOID, COMP, or GIFT).
3

Save

Click Create. The reason is immediately available when staff voids, comps, or gifts a line item.
Reason codes are stored with historical line items. Deleting a reason does not delete past line items with that reason — they keep a snapshot of the reason code. Deactivate reasons you no longer use instead of deleting them, so reporting remains consistent.

​
Frequently Asked Questions

No. Each reason code belongs to exactly one type. If you have a situation that applies to both (e.g. “Promotion”), create two separate reasons: one marked COMP for comped items, another marked GIFT if staff can claim it. This keeps your reporting clear.
The POS requires a reason to be selected before the void/comp/gift can be completed. This ensures every adjustment is tracked and no reason-less adjustments slip through.
The Item Reason Summary report shows the financial impact of voids, comps, and gifts grouped by reason. This lets you see exactly which reasons cost you the most money and identify trends — for example, if “Damaged Item” is high, you might have a food quality problem.
Changing the type of a reason that has already been used in tickets is not recommended — it would retroactively change how past line items are categorised in reports. Create a new reason instead and use it going forward.

Transaction Types

Understand ledger categories on a ticket

Item Reason Summary Report

View void, comp, and gift financial impact by reason

Ticket Summary Report

Drill into individual tickets and line-item details

Setup Checklist

Configure reasons as part of initial setup