A voucher belongs to a particular bill
A guest presents a voucher at checkout. Before anyone reduces a table bill, the team needs to know which voucher is involved, which sale it applies to and what value may be used. Bonzumo has voucher assignments, totals and a remaining-payment flow. This helps keep the voucher within the transaction rather than on a note beside the register. It does not mean that every external voucher provider is connected automatically. The voucher source and its conditions need to be checked during setup.
Check the value and balance together
A 78-euro restaurant bill is partly covered by an eligible 50-euro voucher, leaving 28 euros arithmetically. During service, mental arithmetic is not enough. The server checks that the correct voucher was applied and can explain the visible amount still due. A later order or a request to split the bill changes the context. The team should read the open amount from the current transaction rather than from a scrap of paper showing an earlier subtotal.
Do not treat all vouchers as the same product
A value voucher, a discount promise and a prepaid experience raise different questions. Your team needs to know what each document does and who may check it. Bonzumo can keep voucher and payment steps in the checkout flow, while supported types and technical connections are agreed for your venue. Make a short list of your actual vouchers: where they come from, their value, where they may be redeemed and any conditions. A demonstration can then use real cases rather than a generic example.
Explain mixed payments at the table
After a voucher has been applied, one guest may pay the rest in cash while another prefers a card and wants to leave a tip. In a group, that can quickly become confusing. First clarify which part of the original bill the voucher has settled. Then agree with the guests how to pay the remaining sale amount. A tip is a separate voluntary choice. After each confirmed step, the server reads the current balance so a colleague can take over the table without guessing.
Avoid duplicate redemption and uncertain status
If a voucher has already been assigned or part of the balance has been paid, the same step should not be repeated simply because someone is unsure. This matters particularly when a card attempt for the balance was interrupted. A payment request is not proof of confirmed payment. Decide who checks the voucher status and an absent terminal response. Record the table, value and time before starting a new attempt. Guests and colleagues then receive one consistent account of what happened.
Bring a real voucher case into the demo
Prepare an anonymous example with a voucher value, the original bill, another payment method and a receipt request. Ask where the voucher is applied, how the balance changes and what remains visible after a shift handover. Also ask what happens with a split bill or an incorrect choice. These answers show whether the proposed flow fits your service. Only after that should you decide which of your existing voucher sources can be supported technically and operationally.
When a voucher plan changes during service
A group decides only at the end that the person holding the voucher will not cover the entire bill. It should instead settle an agreed part. Before redeeming it, the server clarifies which items or amount it applies to and who will pay the remainder. Shared dishes can require another question when the bill is split by item. Bonzumo keeps the voucher and remaining payment in the table context, but the allocation must reflect what the guests actually agreed. If that agreement changes after the first payment, an authorised colleague checks the existing status before starting another step.
An unused part of a value voucher is also a specific question. Whether it remains available depends on the voucher type and agreed terms; the checkout total alone does not answer it. Include a voucher worth more than the bill in your introduction. Ask what voucher information is visible and which route is intended for this type. Do not promise the guest a cash payout or automatic future use unless those conditions have been checked for your venue. A clear explanation at the table is better than a quick answer that later proves wrong.
Finish with a handover exercise. An evening shift takes over a table where a voucher has been assigned but the balance is still open. A second colleague should be able to explain the value applied, which payment has been confirmed and whether a receipt request remains. They should not need a private note from the first server. This reveals whether the voucher action stays within the shared transaction. That connection helps prevent duplicate redemption and confusion the next day.
