Three mappings sit between a dish and a printed ticket. All three must be in place.
1. Product to product group
Every sellable dish and drink belongs to a product group. This is set on the item itself. An item with no product group cannot be routed.
2. Product group to station
Each product group is mapped to a kitchen station — hot kitchen, cold kitchen, tandoor, bar, dessert. This mapping is what the backend uses to decide which station receives the item.
3. Station to printer
Each station is mapped to a physical printer through the bridge’s station target mappings, using the Windows printer name on the machine running the bridge.
Worked example
| Item | Product group | Station | Printer |
|---|---|---|---|
| Chicken momo | Hot kitchen | KITCHEN-1 | EPSON TM-T82 (Kitchen) |
| Green salad | Cold kitchen | PANTRY | EPSON TM-T82 (Kitchen) |
| Everest beer | Beverages | BAR | XPrinter XP-58 (Bar) |
Note that two stations can share one printer. That is normal in a small kitchen, and the ticket header still shows which station it was for.
Splitting one order
An order containing items from several groups produces several tickets, one per station. Each station sees only its own items, which is the point — the bar does not need the food order.
Did this answer your question? If not, our support team can look at your actual configuration.
Contact support