One bar rarely means one printer
A small café may handle coffee, cold drinks and receipts from one counter. A venue with a dining room, terrace and club works differently: orders come from several areas, some drinks are made at one station only and staff routes change over the day. Sending every drink to one printer offers a simple setup at first, but often produces questions during service. Bonzumo has configurable bar printing rules to help define the intended path for your range.
Start with a floor plan and your drinks menu, not a list of printer addresses. Mark where each product is prepared, where it is handed over and who takes it to the guest. These may be three different places. A bottled drink may be available on the terrace, a cocktail made at the club bar and a coffee collected by the restaurant pass. Once those paths are visible, the printing rule and device can be set around the work.
Check range and workplace together
A product group alone does not always identify the right bar. Two stations may both offer soft drinks, but only one has the syrup or equipment for a particular serve. Do not stop the mapping at a broad category such as “drinks”. Check individual items and local ranges. Bonzumo offers configurable bar printing rules. Use your menu and stations in a demonstration to check whether item, category and local range can be handled as separate layers in your setup, and which rule takes priority.
For setup, choose awkward examples: a beer served at two bars, an evening-only cocktail, a drink requiring special equipment and a seasonal item. Ask staff at each station where they would expect the order. Different answers are not yet a software fault; they reveal a business decision that has not been made. Settle that decision before configuring the rules. The resulting setup can then reflect an agreed workflow instead of pretending to replace one.
Distinguish guest area from production area
A terrace guest orders a cappuccino. That does not automatically mean the terrace bar makes it. The coffee machine may be inside, with service carrying the drink out. Conversely, an indoor guest may order something made only at the club bar. Decide whether table area, item or a combination determines the destination. This prevents staff looking for an order in the wrong place simply because the guest is sitting elsewhere.
Handover matters as much as printout. A ticket at the correct machine is little help if nobody knows where the finished drink is collected. Give each station a simple route: who reads the job, where the prepared drink waits and how service knows it is ready. A trial order from one table in each area exposes gaps faster than checking a printer list. Bonzumo supplies order context; your team designs the physical route.
Account for shift times and closed outlets
Not every outlet is staffed all day. A terrace may open later, while the club bar begins in the evening. If an unchanged rule sends work to a closed station, the order can look tidy in the system while nobody prepares it. Decide which products remain on sale during the transition, where they are made and who authorises a change of responsibility. An evening rule cannot quietly explain the lunch service.
Test opening and closing an area as separate situations. What happens to an order placed just before the change? Which jobs remain at the old station, and when does the new one take over? Agree a shift handover that both teams understand. It would be unreliable to promise automatic switching without checking the actual setup. A demonstration can instead show the rules you need and who will maintain them.
Split mixed orders without double reading
A table orders beer, cocktails, water and dessert. Several outlets may work on that order. Service needs the whole table context, while each production station should see its own tasks clearly. If everyone receives a long combined ticket, each person must decide which lines belong to them. If items are split too aggressively, the shared table reference may disappear. Test a real mixed table, not just isolated drinks.
A useful station output answers at least these questions: what is being made, how many, for which table and with which relevant notes? Collection by service must also work. During a demonstration, ask two people to read the same mixed job independently. If one must ask where a line belongs, improve the item setup, rule or station name. This practical check says more than a broad claim about supporting multiple printers.
Maintain local offers and exceptions
A new drinks menu changes more than prices. It may introduce ingredients, glassware and preparation points. If an item is created but its production destination is forgotten, the first job may arrive at the wrong printer. Connect new product approval to a quick review of the bar rule. The person releasing the item should know which station makes it and which other stations merely sell it.
Exceptions also deserve an explicit place. A special drink for an event may use a different route from the standard range. Record when the exception begins, which items it covers and when it ends. Have the affected area place a trial order. A maintained rule set reduces later searching because changes do not exist only in one persons memory. It also helps new colleagues understand the route without knowing the history of every rule.
Do not confuse printing with production status
A bar may work from tickets while the kitchen uses a screen, and both contribute to one table order. Keep technical output separate from work status. A ticket shows that information was produced at one point; it does not prove the drink is ready or handed over. Agree how each station confirms its work and how service recognises items still outstanding. With larger orders, that distinction prevents one completed part being mistaken for the whole handover.
Bonzumo connects the order with production context. A normal trial run should show which screens and printouts are useful in the agreed setup. Watch an order from entry through several stations to the final handover. Where does it wait? Does someone need to check twice? What information does service lack when a guest asks? These observations lead to more useful changes than merely confirming that a printer receives a signal.
Keep ownership clear during an outage
If a bar receives no ticket, the cause might be the rule, the device or an order that has not yet been sent. Immediately trying again on several devices makes the job harder to understand. First check the order context to see whether the item was released and where it should go. Ask the intended outlet whether it has already started. A named person can then decide whether a new output or a temporary route is needed.
A useful temporary route needs clear words: who informs the bar, how do they identify table and item, and who records preparation already underway? If an older ticket prints later, nobody should treat it as a fresh order. Rehearse this with an empty paper tray or unavailable station during a quiet period. The aim is not to promise that equipment never fails; it is for the shift to share one view of the order despite an interruption.
Name places and owners clearly
In a multi-area venue, “the bar” is not a precise location. Use names that mean the same thing on the rota, at the workstation and in output rules. Ground-floor bar, terrace and club should not have three different labels in three lists. When a colleague covers another area, they need to find the station and know which work it handles. A simple floor plan beside the setup notes may be more helpful than an abstract feature list.
Decide who may change rules and who tests each change. A temporary diversion by a shift lead needs a different process from a lasting menu change. Send a small control order to the affected station after any adjustment. Without that check, a well-intended fix can silently stop output elsewhere. Clear ownership protects service from surprises while leaving the team able to handle routine issues.
Use your own floor plan in the demo
For a useful Bonzumo demonstration, bring a floor plan showing bars, an example menu and three typical shifts. Place an order from dining room, terrace and club, then a mixed order and an item made at only one station. Ask to see more than the rule editor: observe the output and explain back why each job reached its destination. If that explanation works without guessing, the setup is understandable.
List unresolved points under devices, range and people. An existing printer needs a technical check; an ambiguous item needs a product decision; an unstaffed outlet needs a shift route. Bonzumo can support several work areas within a shared order context. The benefit appears when the rules fit your venue: fewer trips looking for drinks, clearer handovers and more attention available for guests.
