Separate guest receipts from production tickets
A production ticket helps kitchen or bar prepare work. A guest receipt belongs to the sale and payment. Both can arise from one order, but they have different recipients and timing. When planning devices, ask not just which printer you own, but who needs which document and when. Bonzumo connects order, payment and receipts in the operating flow. Actual output must fit your service style, workstations and equipment.
Test an order that kitchen prepares first and the guest pays for later at the table. Look at the details delivered to kitchen and the information the paying guest receives. The distinction prevents internal production notes going to guests or a payment receipt looking like a kitchen job. It also helps training: new colleagues can recognise what each printout means at its location instead of sorting paper by chance.
Keep counter movements short
At a busy counter, one payment follows another. A receipt printer several steps away adds a trip after every sale; put it in a narrow passage and the person collecting paper blocks colleagues. Test the workstation using a real shift movement: where does the guest stand, where does staff operate checkout, where is the receipt taken and where would a reprint appear? The best location is not necessarily the closest power outlet.
Two counter tills may share one printer if output can be identified and collected clearly. Separate devices may make sense when workstations are far apart. Existing hardware compatibility with Bonzumo must be checked in the actual setup. Regardless, decide how staff distinguish receipts when both tills sell at once. A short simulated rush is more informative than a floor-plan sketch alone.
Clarify the bill before printing at the table
At a table, printing is often the last step of a longer conversation. Do guests pay together, split by items or divide into equal shares? Are invoice recipient details needed? Bonzumo supports different splits and entering invoice recipient data. Before printing, service should confirm the selected amount and the intended recipient. A well-positioned device does not replace that content check.
Groups can produce several receipts from one table context. Decide who processes each part, how completed portions remain visible and where each receipt is collected. A guest who has already paid by card should not accidentally receive paper for the still-open balance. Rehearse a split bill with cash and card payment. The mapping should also make sense to a colleague taking over after a shift change.
Check payment status before the receipt
A receipt printer responds to a process, but paper alone does not prove payment was confirmed. With card terminals in particular, an attempted connection, displayed request and confirmed payment may be different states. Check which state the payment actually reached before treating an amount as settled. If a terminal gives no clear answer, neither a printed nor a missing receipt should be taken as proof of money movement.
A simple team rule helps: when status is unclear, inspect the existing transaction and involve the responsible person before deciding whether to retry. Otherwise duplicate payment requests or receipts inconsistent with the final result can follow. In a demonstration, test a normal success and an interruption. Ask what service, shift lead and guest each see. Receipt output should document a clarified outcome, not hide uncertainty.
Collect invoice details at the right point
Business guests sometimes provide invoice details only when paying. If the group has already split the bill, the details must clearly belong to the right part. Bonzumo offers editable recipient fields in the invoice dialogue. Agree when staff ask for details, who enters them and how they are checked before output. A brief question at the table may prevent later rework on the wrong printout.
Test with four guests, two partial invoices and an address needed for only one part. Service should be able to explain which payment the address belongs to. Check legibility on the intended printer too. Details that look tidy in an entry field must still be readable on paper. The restaurant should review tax requirements for its invoices with its advisers; the printing process is not a blanket legal check.
Distinguish reprints from the original
A guest loses a receipt or later needs another copy. That differs from an open sale. Decide who finds the existing transaction, who may issue another printout and how the team treats the copy. Reprinting must not accidentally start a fresh payment or second sale. This matters especially when a colleague who did not serve the table handles the request.
In a demonstration, try a closed table from the previous day and a partial bill paid moments ago. Which information helps locate each transaction, and which roles may issue output? The guest request should be handled quickly without confusing checkout with the archive. Bonzumo provides receipt and archive context; specific rights and output routes are choices for your venue. A documented standard avoids improvised corrections later.
Assign multiple devices deliberately
A printer beside each fixed till sounds simple, but mobile service devices change the picture. Service takes payment at a table while paper emerges far away and the guest waits. Plan separately for fixed checkout points, mobile service and any central output. Whether a particular device can connect to a particular printer must be checked against your hardware. The benefit comes from a suitable route from confirmed payment back to the guest.
Have two people perform the same type of payment at different workstations. Can they identify the printout without searching? Must they cross another area? What happens when service changes device? These answers guide assignment better than a general feature list. If existing hardware is unsuitable, finding out early helps choose a replacement that fits the intended workstation.
Rehearse paper, network and backup routes
Small faults appear at awkward moments. Paper runs out, a cable loosens or a network device is unavailable. Decide who stores spare rolls, who checks the printer and what safe route applies during a short outage. Staff should first establish whether payment and receipt records exist before restarting anything. A fault in output is not automatically a fault in the payment.
Rehearse an empty roll after a table payment has been confirmed. Service explains the delay, checks status and obtains the correct receipt after replacing the roll. A second exercise disables printing before payment so the shift knows its temporary route. Actual Bonzumo options depend on the specific setup and should be reviewed during implementation. A clear sequence protects guests and staff better than repeatedly pressing “print”.
Test setup with real payment cases
Bring three sale types to a demonstration: a quick counter item, a full table bill and a group with two payment methods and an invoice recipient. Follow each case from order through confirmed payment status to output. Ask the person who will take payments during service to explain the paper route. If that person finds the receipt only after coaching, the workstation needs more thought.
Keep technical questions about existing devices separate from workflow decisions. Printer compatibility needs testing; deciding who handles split bills belongs to the venue. Both matter, but they are different tasks. Bonzumo is easier to assess when the demonstration includes real exceptions and the final receipt reaches the place the guest expects. The device then becomes an understandable part of service.