Link a ticket template to kitchen destinations
Categories and articles
Link a template to a kitchen destination to use it there. You can also make it the restaurant default; destinations without their own template selection will then use it.
Step 1 — Open the Destinations tab
Go to Admin → Bongning and pick the Destinationer (Destinations) tab (to the left of the Mallar 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)
- Type: printer or KDS
- 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 to Mall (Template) and find Bong-template.
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 Mallar tab
Pick the one you want. For example:
| Destination | Template |
|---|---|
| Kitchen | Kitchen-big-font |
| Pass | Kitchen-big-font (same as kitchen – shared layout) |
| Bar | Bar-small-font |
| Dessert | Standard (restaurant default) |
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 – whether it comes from the POS, an online order, course firing or a Magic Button.
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 Mallar 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
Check the default layout when changing it, since the change can affect several stations.
If the templates cannot be read at the moment, the ticket still prints, using Vendion's standard layout. A ticket is never lost because its template could not be fetched.
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:
- Go to Destinations → Bar → Edit
- Swap the dropdown back to "Standard (restaurant default)" or another layout
- Save
Next ticket is on the new format. Check the next printout to confirm that the correct template is in use.
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:
- Go to the Destinations tab
- For every destination using the template you want to delete — pick another
- Then go to the Mallar 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.
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?
Related articles
Ticket Templates – customize your kitchen tickets
Choose fields, text sizes and layout for kitchen tickets. Use one shared template or different templates for each station.
Create and customize your first ticket template
Create and name a kitchen ticket template under Bongning → Mallar. Adjust fields and text sizes, preview the layout and check the printed result.
Customize header, items and footer on the ticket
Walkthrough of every field you can toggle, disable or resize in ticket templates. Header, items and footer — with concrete tips.
