Link a ticket template to kitchen destinations

A ticket template without a link does nothing. For your new layout to start coming out of the printer, you have to link it to at least one kitchen destination.

Step 1 — Open the Destinations tab

Go to /admin/bongdestinationer and pick the Destinations tab (to the left of the Templates tab).

You see every kitchen station you have: Kitchen, Bar, Dessert, Pass or whatever you've named them. Each row shows:

• Destination name
• Linked printer (if any)
• Output type (paper, KDS, or both)
• An "Edit" button

Step 2 — Pick destination and click Edit

Click Edit on the destination you want to update. A dialog opens with every setting for that destination.

Scroll down to the "Ticket template & behavior" or "Print behavior" section (name may vary slightly). You'll find the "Template" field there.

Step 3 — Pick template from the dropdown

The dropdown contains:

• "Standard (restaurant default)" — destination uses the restaurant's default template
• Every named template you've created under the Templates tab

Pick the one you want. For example:

As you see, multiple destinations can share the same template. Kitchen and pass usually have almost identical needs, so they often share a layout. Bar and dessert on the other hand have completely different tempo and layout preferences.

Step 4 — Save

Click Save in the dialog. The next ticket sent to that destination uses your new template.

Important: already-printed tickets don't change retroactively. It's only new tickets from this moment on that are affected.

What happens if the destination has no template?

If you don't pick anything (dropdown stays on "Standard (restaurant default)"), the restaurant's default template is used automatically. The default template is the one marked with a gold star in the Templates list.

That means:

• You can start tailoring one destination without touching the rest
• New destinations created in the future automatically get the default
• If you change the restaurant's default, every inheriting destination updates instantly

It's a safety net. You'll never accidentally have a destination printing something weird or blank.

One destination – one template

Each destination can only have one template linked at a time. You can't say "use Kitchen-big-font for starters, Kitchen-small-font for mains" — that's not how the system is designed.

But you can have as many templates as you want in the list. The constraint is only per destination.

Change template whenever

Nothing is forever. If your new "Bar-small-font" turns out too compact, you can:

1. Go to Destinations → Bar → Edit
2. Swap the dropdown back to "Standard (restaurant default)" or another layout
3. Save

Next ticket is on the new format. No restart, no deploy, no weirdness.

Example: mixing old and new templates

A common scenario combo:

• Kitchen and Pass share Kitchen-big-font (big text, chef signature, table number on top)
• Bar has Bar-small-font (compact, no category headers)
• Cold kitchen and Dessert use Standard (restaurant default)

Kitchen gets its optimal layout, bar gets its, and cold kitchen/dessert don't need their own layout because it works fine anyway.

New destinations – how does it work?

If you create a brand new destination (e.g. adding a Wine Cellar destination for sommelier tickets):

• The destination has no template linked by default
• It automatically uses the restaurant's default template
• You can then go in and pick a specific template whenever you want

That means you don't have to think about templates when creating new destinations — it "just works".

Deleting a linked template

If you try to delete a template that's actively linked to one or more destinations, those destinations will automatically fall back to the restaurant's default template.

It's not dangerous, but for clarity we recommend:

1. Go to the Destinations tab
2. For every destination using the template you want to delete — pick another
3. Then go to the Templates tab and delete

Saves you ambiguity over which destinations suddenly got a new layout.

Tips

• Name destinations AND templates clearly — "Kitchen" + "Kitchen-big-font" is self-explanatory. "Station 2" + "New template 3" isn't.
• Always have a working default — even if you never use it directly, it's your safety net.
• Test after every change — do a real ticket and confirm the layout looks as you imagined.