Order settings
What this is for
The settings that shape how orders behave, gathered because anyone changing one is usually changing the others.
Under Settings › Order Settings, plus the cancellation and refund reason screens.
Order numbering
Every order gets a number, and you control its shape.
| Setting | What it does |
|---|---|
| Enable Order Prefix Settings | Turns custom numbering on. Off gives plain numbers — #23. |
| Prefix Type | A custom prefix, the current date, or branch plus date. |
| Custom Prefix | Your own short code — ODR, BR01, CF. |
| Separator | What goes between the parts. |
| Number Digits | How many digits — 007 or 7. |
| Reset Sequence Daily | Start from 1 each day. |
A live Preview shows the next number as you change things. Use it.
Decide once. Changing numbering later gives you two eras of orders that sort differently, and anyone looking back has to know when the change happened.
Points worth weighing:
- Branch prefixes are essential on multi-site.
CF-0042andTM-0042are two different orders;0042and0042are a support call. - Daily reset keeps numbers short but repeats them across days. Fine when the date is always alongside.
- Enough digits that you don't roll over mid-year.
Token numbers
Short numbers for counter and pickup service — the number called out or shown on the board.
Enable per order type under Token Number Settings. Tokens reset daily and are unique per order type.
Show Order Number on Board displays the full order number alongside the token on the customer order board.
Tokens exist because CF-2026-0042 is impossible to shout across a room and 14 isn't. Turn them
on for any order type where a customer waits and collects.
Order type behaviour
| Setting | What it does |
|---|---|
| Allow Custom Order Type Options | Enables custom order types. |
| Disable Order Type Popup | Stops the POS asking every time. |
| Default Order Type | What's used when the popup is off. |
Turn the popup off for a single-purpose operation — a delivery-only kitchen, a dine-in-only bistro. Staff can still change the type on an order.
Marking paid orders complete
Mark paid orders as completed automatically does what it says: any order reaching Paid also gets the progress status Completed, so dine-in tables and lists treat it as finished.
This is a real operational choice, not a preference:
Turn it on for counter and quick service. Payment is the end of the transaction, and making staff close orders manually adds a step nobody will do reliably.
Leave it off for table service. A guest who has paid is still sitting at the table, and you want that table to show Running until they actually leave. Otherwise your floor screen says a table is free while four people are still on the dessert.
Get this wrong for table service and your floor screen becomes untrustworthy — which means staff stop using it.
What customers can order
| Setting | What it does |
|---|---|
| Allow Customer to place Orders | Ordering from the customer site at all. |
| Allow Customer to place Delivery Orders | Delivery specifically. |
| Allow Customer to place Pickup Orders | Pickup specifically. |
Use these to run a browse-only menu, or to take pickup online while keeping delivery to phone calls. See The customer ordering site.
Cancellation reasons
Under Settings › Cancellation Reasons.
The list staff pick from when cancelling an order or removing an item after the kitchen ticket has gone. There's also Other with a free-text custom reason.
This list is the quality of your cancellations report. A set of one generic reason produces a report with no information in it.
A workable set:
- Wrong item ordered
- Customer changed mind
- Kitchen error
- Item out of stock
- Long wait
- Quality issue
- Duplicate order
Each of those points at a different fix. That's the test for whether a reason earns its place.
Refund reasons
Under Settings › Refund Reasons, and the same logic applies — these become your refund report.
A workable set:
- Food quality
- Wrong order delivered
- Late delivery
- Item unavailable after ordering
- Customer complaint
- Duplicate charge
- Waste / write-off
Keep both lists short enough that people read them and long enough that "Other" is rare.
Good to know
- Order settings are per branch where they concern order types and tokens; numbering is set per branch too.
- Cancellation and refund reasons are per restaurant, so all branches share the same list.
- Changing reasons doesn't rewrite history. Past orders keep the reason they were given.
- Manage Settings covers all of this. See What each role can do.