The ticket starts when the order is taken
A kitchen ticket is useful only when it carries a clear job. Imagine a table ordering two drinks, one starter and three main courses. The bar should not have to scan the main courses, while the kitchen needs to know about the food at the right time. Before choosing printers, map who takes the order, which station prepares each part and when work is released. Bonzumo brings order entry, production context and configurable output paths together as the starting point for that conversation.
The route taken by information matters more than the number of devices. Another printer will not solve an unclear mapping of items to stations. Walk through your menu with kitchen, bar and service staff, marking borderline cases: coffee, desserts, bottled drinks, sides and products made in different places at different times. You can then discuss output using real work, instead of mistaking a technically connected device for a workable service process.
Use station work rather than a general ticket pile
A ticket containing every item may be enough for a small single work area. When several stations work in parallel, it can create sorting work. The grill cook must pick out the relevant lines, the cold kitchen may interpret the same order again and the bar receives paper that asks it to do nothing. A useful station assignment shows which team owns a task and what information that team needs. The output may be paper, a screen or a deliberate combination of both.
Consider an evening with indoor tables and a terrace. Both areas use the same service team and kitchen, yet drinks may be prepared at different bars. Routing only by table location could send a drink to the wrong outlet. Routing only by product group could miss local ranges. Bonzumo offers configurable bar printing rules; work through typical mixed orders to decide which rule makes sense for your work areas.
Menu maintenance shapes the printing route
An item in the wrong category does not merely confuse a later report. It can send the production job to the wrong place immediately. When adding a menu item, check its production destination as well as its name and price. This is easy to miss for a dessert with a drink or a menu that includes sides. Who maintains the menu, who checks output and how are changes communicated to kitchen and bar? A short joint release check is often more useful than answering questions during service.
Use three test orders: a simple dish, a mixed table and a less common combination with a special request and a side. Follow each item from service selection to the team that actually prepares it. The test should prove more than the appearance of paper. It should show whether quantities, table reference, notes and timing make sense to the station. When these details are clear, colleagues need less verbal translation across the restaurant.
Special requests must reach the right place
A ticket must not flatten the details that make an order different. No onion, a changed side or a question about an ingredient may be central to preparation. Bonzumo supports order notes. Agree which requests your team records as a structured choice and when a free-text note is needed. A note visible only on a general screen is of little help to the station doing the work. Check the actual output for such a case before calling the setup complete.
An allergy question also needs human clarification. Service staff must know who to ask in the kitchen, how the answer reaches the guest and when the order is released. Bring a difficult example to the demonstration and watch the handover. If several stations need the same information, decide who owns the overall answer. A clear route reduces misunderstanding; it is not a blanket guarantee about the safety of every ingredient.
Think about kitchen screens and paper together
A kitchen display can show open work and its progress. A production ticket may still make sense when paper travels with food to the pass or a station cannot see the screen. Bonzumo includes kitchen status and printing paths, but the useful combination depends on the room and the process. Put a screen where the person doing the work can actually see and operate it. A display mounted away from preparation will not stop people asking each other for updates.
Decide which view is authoritative at each point. If both a display and paper show the same order, a later printout must not look like a new job. Equally, an item marked complete should not remain in a paper pile without context. Test a normal order, a change and the completion step in a demonstration. Only the whole path shows whether the two outputs support each other or create duplicate work.
Courses change the timing
For a set menu, the question is not only where a job goes but when the next course should begin. An early information ticket can support preparation, while immediate production for every course could put the kitchen under pressure. Bonzumo supports releasing menu courses individually. Separate knowing that a course was ordered from the instruction to start making it. Service can follow the guests pace while the kitchen has a clear starting signal.
Walk through a starter, main and dessert. Let the starter proceed, release the main later and then change an accompanying item. Which station receives what? Could someone accidentally trigger the same course twice? Who can see that the change has been understood? These questions matter more than a polished sample ticket. A coherent course process helps explain waits and gives service and kitchen a shared language for what happens next.
Printer placement is part of the workflow
A printer needs power and a suitable connection, but its position is primarily a service decision. Put it behind a hot work surface and someone has to take a detour for every ticket. Put it by the only passage and the team may bunch up at peak time. Check visibility, reach, paper replacement and noise at the actual work area. A sensible position does not automatically shorten every wait, but it prevents output from becoming an obstacle itself.
If you want to keep existing printers, collect their models, connection types and current positions before the conversation. Technical suitability must be checked for your configuration; a broad compatibility statement cannot replace that step. Decide who notices an empty roll, who replaces it and who verifies output after a change. The routine should work for the shift team, not only for the person who first configured the device.
Resolve failures without duplicate jobs
A missing ticket can have several causes: the order was not released, it went to another station, the device lost its connection or it ran out of paper. Blindly resending can turn one missing printout into several production jobs. Check order status in the system and ask the expected station before triggering the action again. Agree who makes that check so service and kitchen do not improvise independently.
Write down a simple temporary route for a short outage. Who can read the order, who passes it to production and how will the team later recognise that the job was already handled? This is a working rule, not a claim about an automatic Bonzumo fallback. Test it with a deliberately unavailable printer. When output is restored, old and new jobs must be distinguishable so food is not prepared or served twice.
Follow a change through to the station
An order does not always stay unchanged during service. A guest changes a side, an item is cancelled or another course is added. The original ticket may already have reached production. Check how the team records the change, how the affected station recognises it and who decides when preparation has already begun. A fresh printout with no reference to the existing job may make matters worse. Your working rule should make clear what is replaced, added or withdrawn.
Run a normal order first, then introduce a specific change. Ask service and kitchen separately what they now believe should happen. If their answers differ, the gap may lie in the teams shared terms or the layout of work areas. Bonzumo can place information in the order and production context; people on site still have to decide how to handle food already in preparation.
Watch the entire job in a demonstration
A printer demonstration should be more than a single test-print button. Bring your menu, a rough floor plan and five real order patterns. Alongside a simple table, include a mixed bar-and-kitchen order, a menu with a later course, a special request and a change after release. Follow the action from service entry to completed output. You will see whether information arrives at the right time, with sufficient detail and at the right station.
Write down the decisions still open after the test: which devices need checking, which items need a different destination, who maintains rules for new menu items and how the team covers an outage. The result is a concrete setup plan for your restaurant. Where Bonzumo fits the work, colleagues can hand orders over with fewer questions and give more attention to guests instead of searching for paper.