Correction, transfer and void tickets – automatic special tickets

One of the most common friction points in restaurant kitchens: the server changes something on the order after it was sent, but the kitchen doesn't know. The chef cooks the wrong quantity, wrong modifier or a dish that's already cancelled.

We fixed it with three automatic special tickets sent at exactly the right moment:

Correction ticket — when something changes

When you modify a row that's already been sent (e.g. change quantity from 2 to 3, or add "No onion" to a burger already in the kitchen), a correction ticket is automatically sent to the relevant destination.

The correction ticket has a clear bold banner at the top:

*** CORRECTION ***

The banner is in large format (size 3×, inverted text with black background and white letters) so the chef can't miss it. Below the banner, only the changed row is shown — not the entire order. The kitchen sees what's up quickly without having to compare with the original ticket.

Example:

*** CORRECTION ***

Table 12 – Tab 1
#047

3× Ribeye 200g
+ Medium
! No pepper sauce (new!)

Transfer ticket — when the table changes

When you move a tab from one table to another, a transfer ticket is sent to every destination that had sent rows on that tab.

The transfer ticket banner shows where the tab moved from and to:

*** MOVED: Table 5 → Table 12 ***

That means a chef who has a dish half-prepared and looks at the ticket still knows which table the dish is for — even if the table changed after the order was placed.

Void ticket — when something is cancelled

When you cancel a row already sent (e.g. guest changes their mind and removes dessert after it's gone to the kitchen), a void ticket is sent.

Banner:

*** CANCELLED ***

Shown in the same bold inverted format. The row below the banner shows which product was cancelled so the kitchen can stop prep.

Enable per destination

You control the three special tickets per destination, not per template. That's because different stations have different needs:

• The kitchen wants all three (they need to know everything immediately)
• The bar maybe only wants correction and void (table changes are irrelevant — the drink is already in the glass)
• A takeaway station maybe only cares about cancellations

How to enable

1. Go to /admin/bongdestinationer → Destinations tab
2. Pick destination and click Edit
3. Scroll to the "Special tickets" or "Print behavior" section
4. Toggle on/off as needed:

Save. Done.

Extra settings in the same section

Besides the special tickets, two more buttons in the same dialog that many restaurateurs like:

Beep on print

Turn on if you want the printer to beep every time a new ticket comes out. Good in loud kitchens where tickets are easily missed. Turn off in restaurants where the sound would disturb guests.

Auto-cut

When multiple tickets are sent at once (e.g. a large order with both starters and mains in the same send-to-kitchen batch), the printer can cut between each ticket so the kitchen gets them separately. Recommended on, especially if several stations share the same ticket paper.

Best practice per station type

After a few months with restaurants in Stockholm and Gothenburg, we've seen a clear pattern:

Kitchen

• Correction: on
• Transfer: on
• Void: on

The kitchen wants to know everything. Their cooking is on the line.

Bar

• Correction: on
• Transfer: off
• Void: on

The bar doesn't care about table changes (the drink is made). But correction and void are equally important.

Dessert / cold kitchen

• Correction: on
• Transfer: on
• Void: on

Same as kitchen. Dessert can also be changed or cancelled late (guest got full).

Pass / delivery

• Correction: on
• Transfer: off
• Void: on

Pass usually handles delivery or takeaway where table is irrelevant.

Takeaway station

• Correction: on
• Transfer: off
• Void: on

Takeaway has no "table" in the traditional sense.

These are guidelines, not rules. Adjust to what works for your restaurant.

What happens visually on the ticket?

All three special tickets use the same template as normal tickets for that destination. What differs is the banner at the top — the rest of the ticket is unchanged. Your custom settings (big font, table number on top, notes in bold) apply to special tickets too.

The banner is hardcoded to bold + size 3× + inverted (black bg, white text) so it stands out even in the worst lighting. You can't customize the banner's text, look or size — we've deliberately locked it so every special ticket is immediately recognizable regardless of restaurant.

Common questions

What if a tab is moved several times in quick succession? Every move gets a new transfer ticket. Deliberate — the kitchen should know about every change. If it becomes too noisy in practice, tell support and we'll add a small debounce.

Is the special ticket sent to the same destination as the original? Yes. A correction for a bar item goes to the bar, a void for a kitchen dish to the kitchen, etc. Each destination gets its own special ticket.

Can I disable special tickets for certain evenings? No, not currently. But you can turn them off per destination in advance and turn them back on when you want.

What if the guest changes to something more expensive — what's on the correction ticket? Only the changed row, with the new quantity/modifiers/note. Price isn't usually on the correction ticket (unless you've turned on "Show prices per row" in the template).