First establish what is actually missing
“The ticket did not come out” describes a symptom, not a cause. The order might be saved but not released. It may have gone to another station. The printer could be out of paper or disconnected. Start in the order context: which job is it, what state has it reached and where should output go? Then ask the station whether the job is already visible on a screen or an earlier printout.
This sequence matters most under pressure. Resending blindly can create two tickets when staff were looking for only one. With a multi-item order, only one portion of output may be missing. Note table, time, item and expected station. Service, kitchen and shift lead can then discuss the same case rather than three similar orders. Bonzumo provides order and production context; your team agrees the diagnosis route.
Distinguish a paper problem from an order problem
An empty roll is a device problem. The order may already exist in the system, and kitchen may be working from another signal. Replace paper according to your workstation procedure and check whether an older job then prints automatically or needs deliberate output. If the same ticket appears again, the station must recognise that it is not a fresh order. A brief check before restarting avoids unnecessary preparation.
Keep spare rolls where the shift can find them, and show new staff how to replace paper on the actual device. It sounds small, but it saves questions during a rush. Check whether the printer visibly indicates that paper is missing too. Software cannot always infer this state. For the restaurant, what matters is that someone notices the fault, watches open jobs and restores one shared view after replacement.
Narrow down connection and workstation faults
If paper is present, check the affected workstation. Does the printer have power, can it be reached and do other stations still work? An outage at just one bar differs from a problem with the shared network. Avoid changing several rules at once. Otherwise nobody knows which adjustment helped or where new work now goes. One named person investigates the device while the team follows its temporary route for active jobs.
Record models, connection types and locations for existing equipment. This helps during Bonzumo setup and makes later faults less mysterious. It does not claim that every printer is supported. A short device list instead describes your actual configuration. When a device is replaced or moved, use a test job to establish whether the intended station again receives the correct information.
Make the temporary handover unambiguous
Kitchen still needs complete jobs during a short printing outage. Agree a temporary route that carries table, item, quantity, special request and timing. Service might read the order on a screen and speak to the station, or another output point may be suitable. The choice depends on the room and available devices; this page does not promise automatic failover. One person should own the handover.
Ask the receiving station to confirm the job, especially when special requests or courses are involved. Mark that the order has already been passed by the temporary route. If printing returns later, a delayed ticket must not become a second production instruction. A short note or agreed verbal signal can prevent confusion. The route should work even while a shift lead handles another issue.
Reconcile old and new tickets after recovery
When output resumes, older tickets may appear together. Do not sort them by paper order alone. Compare each underlying order with work status: what has begun, what is ready and what still genuinely waits? Kitchen owns the physical production; Bonzumo provides the order and status context. A named person reconciles both before the shift relies only on the normal output route again.
This is especially important across stations. Coffee may already have been served while a kitchen ticket for the same table appears later. Treat every printout as new and you may duplicate food or drinks; discard all of them and a real job may be missed. Spend a few minutes establishing the shared position. Guests notice a missing or duplicated item more than a short internal check.
Handle receipts and payments separately
A guest receipt that did not print is not the same as a missing kitchen ticket. More importantly, it does not prove a card payment failed. Check payment status and the linked transaction first. If the terminal response is unclear, missing paper alone is no reason to trigger payment a second time. Ask the responsible person which amount is confirmed and which receipt belongs to it.
Rehearse two cases: a paid table bill with no printout, and an open bill where the printer also fails. In the first, staff need the matching receipt; in the second, payment status must first be clarified. Bonzumo connects payment and receipt context, while a specific device link must be checked. The distinction protects guests from confusing amounts and staff from later questions.
Keep guests and service informed honestly
During an output fault, guest communication should not become vague. Service needs to know whether the order was entered, handed to kitchen and started. Staff can then give an honest update without inventing a completion time. If receipt by production is unclear, they can say they are checking it and do exactly that. A short transparent update is more professional than repeated enquiries with no visible progress.
For a receipt fault, staff may be able to explain that payment status is being checked and output will follow. The confirmed state determines what can actually be promised. Give the team wording for both situations: unclear production handover and unclear payment or receipt. The aim is not a long technical speech at the table, but a safe next action. Bonzumo should make the internal position understandable so colleagues do not have to guess.
Review causes after service, not mid-rush
An active fault calls for a safe handover, not redesign of every rule during dinner. After recovery, note when the issue began, which device was affected, which jobs were checked and what temporary action the shift took. Look for patterns: only after a menu change, only at one station or only for certain items. That evidence supports a focused technical and working review.
Avoid broad blame. A wrongly routed product, empty paper and a network fault require different improvements. Ask staff whether the temporary route was clear and whether guests waited unnecessarily. Change only the affected part, then repeat the same test case. Calm follow-up improves the next service more than a rushed wholesale redesign after one incident.
Rehearse a small outage regularly
A backup route is only as good as the person who can use it under pressure. During setup, run a short exercise: a bar printer is unavailable, kitchen receives a special request through the temporary route and a delayed ticket appears when output resumes. Colleagues should explain the order state themselves. If they need the original installer to do so, names, ownership or guidance are still unclear.
Repeat the exercise after major changes to layout, range or team. A new counter changes walking routes, a seasonal menu changes mapping and new staff do not know an older agreement. A few specific tests keep the process alive. Bonzumo can bring information together in daily work while your team knows how to proceed when output is interrupted.
Decide on devices after the workflow
Printer model and network matter when choosing or reusing hardware. For the restaurant, where the ticket is read and what decision follows matter too. Bring a basic device list, a station plan and examples of printing problems to a Bonzumo conversation. Have existing equipment checked without assuming universal compatibility. Record which workstation must be retested after a later change.
The best demonstration shows not only normal service but interruption and recovery. Can service explain the current state? Does kitchen know what is already being made? Is there a traceable path to the guest receipt? When these questions have answers, peripheral equipment becomes a dependable part of work. The benefit is less duplicate effort, fewer unresolved jobs and a calm response to guests when something does not go as planned.
