A kiosk should let guests request a usable receipt without making staff guess whether a payment went through. Compare paper, digital delivery, and a clear option to decline a receipt. Then decide what staff will do if the printer fails after the transaction is complete.
The best mix depends on your guests, your hardware, and the delivery methods the vendor can demonstrate. Paper is familiar but can run out. Digital delivery avoids a paper handoff but requires a working delivery method and guest contact information. Declining a receipt is convenient for some guests, but it should not erase the staff transaction record.
Choose the receipt options your guests need
Paper: A printed receipt gives a guest something to keep without entering an email address or phone number. Check where the receipt emerges, whether the print is legible, and whether someone using the kiosk can reach it. Ask how staff learn about low paper, an open cover, or a disconnected printer. A visible warning is useful only if someone owns the response.
Digital: A digital receipt may be a good choice for guests who prefer not to carry paper. Ask which delivery methods are available in your setup and what the guest sees after choosing one. For example, Fleksa lists SMS receipt options as dependent on setup. Confirm the workflow you would actually use rather than assuming every kiosk configuration includes it.
Decline: Some guests want no receipt. The screen should make that choice understandable and distinguish it from a delivery failure. Ask whether staff can still find the transaction if the guest changes their mind or needs help later. Also ask what information staff need to locate it without asking for a full card number.
A receipt is proof or a record of purchase. A pickup number or name serves a different purpose: helping match a guest to an order. One piece of paper or one screen might contain both, but a pickup token alone may not show the payment or item details a guest needs. Decide what information your operation requires on each, and ask the vendor to show it.
Start with inputs you can observe: how guests currently ask for receipts, how often staff replace paper, and which records cashiers use to answer payment questions. Then add assumptions for anything you cannot yet observe, such as how many kiosk guests might choose digital delivery. Keep the two separate when comparing vendors.
Use a decision worksheet before choosing
The following worksheet is hypothetical. Assume a restaurant handles 100 kiosk transactions during a busy period. The owner expects 50 guests to request paper, 30 to choose digital, and 20 to decline a receipt. These are planning assumptions, not results from an operating kiosk. Assume each transaction is completed and recorded before a simulated printer fault affects the next paper request.
| Decision input | Planning assumption | What to confirm |
|---|---|---|
| Paper choice | 50 of 100 guests request it | Can staff see and resolve a failed print? |
| Digital choice | 30 of 100 guests choose it | Which delivery methods and statuses are available? |
| Declined receipt | 20 of 100 guests decline | Can staff still locate the transaction? |
| Printer fault | The next paper request cannot print | Can staff provide an alternative without another charge? |
The first three rows describe assumed choices, not guaranteed demand. The final row tests a failure, not an additional sale. Replace those figures with your own observations after opening, and check whether a change in guest preference affects paper supply or staffing.
Now compare two possible demonstration outcomes. In outcome A, the kiosk identifies the failed print, the cashier finds the completed transaction, and an approved alternative receipt can be provided without charging again. In outcome B, the screen leaves the guest unsure what happened and staff cannot find the transaction promptly. Outcome A supports a paper option with a staffed fallback. Outcome B means the restaurant should not accept that workflow until the vendor resolves it and demonstrates the fix.
Digital delivery is not automatically the fallback in either outcome. The vendor must show that the chosen method is available, that the guest can choose it, and that staff can understand its status. If those conditions are not met, ask about a cashier-issued receipt or another documented alternative.
For the broader purchase, compare the installed quote as well as the workflow. Ask for hardware, software, installation, paper, support, and payment-related costs to be identified separately. A printer that is cheap to install may be costly to operate if staff cannot diagnose it or obtain replacement supplies quickly. The kiosk break-even guide can help frame those wider costs; the receipt worksheet answers the narrower service question.
Test a completed transaction and a failed print
Run the vendor demonstration in a test environment using a simulated completed payment. The test must not charge a real card, send a guest message, or dispatch a courier. Ask the vendor to show how the simulation represents a completed transaction and how staff can tell test records from live ones.
- Build a small order and request a paper receipt. Use the normal order-review flow so the receipt question appears at the point a guest would encounter it.
- Complete the simulated transaction. Record the test transaction identifier and the status shown to the guest and staff.
- Simulate a printer failure at the receipt step. Ask the vendor what fault is being simulated and whether it represents a paper-out, connection, or other problem.
- Have the cashier locate the same transaction in the staff system. Compare its identifier, items, total, and payment status with the test order.
- Ask the cashier to use the proposed fallback. If it involves digital delivery, simulate that step too; do not send a real message.
- Restore the printer and ask whether the receipt can be printed or reprinted, who can authorize it, and how staff avoid confusing it with a new purchase.
The key distinction is between a guest-facing receipt and the staff transaction record. A receipt that fails to print does not, by itself, tell the guest whether payment succeeded. Conversely, a staff record is not automatically a receipt in the guest's hands. The cashier should check the transaction status before suggesting another payment or restarting the order.
Give one person responsibility for detecting and resolving the problem. In a small restaurant that may be the cashier; during a rush, a shift lead may need to take over. Agree on where the alert appears and what the cashier says while checking: the transaction is being verified, not assumed to have failed.
Ask to see this alongside the restaurant POS system staff would use, including the permissions needed to search and reprint. The kiosk cart workflow is useful context for order entry, but receipt handling and failure recovery should be demonstrated separately.
Set acceptance criteria and a cashier fallback
Write the acceptance criteria into your vendor discussion before choosing hardware. A clear pass condition makes the demonstration useful even if several products offer the same receipt choices.
- Guest choice: The guest can identify the available receipt choices and deliberately decline one. The screen does not present a failed print as a successful delivery.
- Transaction check: The cashier can find the simulated completed transaction and distinguish it from a new order. No second charge is needed to investigate the first.
- Fallback: Staff can follow a documented route to provide an available receipt alternative, or clearly explain that one cannot yet be provided and how the issue will be followed up.
- Fault ownership: The shift lead owns unresolved exceptions, including checking supplies, contacting support when needed, and recording the transaction reference for follow-up.
- Recovery: Staff can confirm the printer is working again with a test print and know how pending receipt requests will be handled.
Pass the demonstration only when the guest-facing status, staff record, and fallback agree for the simulated transaction. Fail it if the cashier cannot verify the payment status, the screen implies a receipt was delivered when it was not, or the only proposed solution is to charge the guest again. Ask the vendor to correct the workflow and repeat the demonstration.
For digital receipts, collect only the contact detail needed for the guest's chosen delivery method. Ask whether it is retained, who can see it, how long it is kept, and whether it is used for anything else. Do not make receipt delivery an unexplained marketing signup. Have a qualified adviser review contract or legal questions about the handling of guest information.
Train staff first with simulations, then evaluate the agreed workflow during a supervised live service pilot. In live service, use actual guest choices and normal payment procedures; do not manufacture failures that could disrupt a purchase. Record practical issues, assign them to the shift lead, and agree on changes before making the kiosk the only ordering route.
Next step: Take this worksheet to a vendor demonstration. Compare your kiosk requirements with Fleksa and confirm current support for each receipt choice, printer fault, and cashier fallback before choosing a workflow.
Frequently asked questions
Should a kiosk always print a receipt?
Not necessarily. Offer choices that suit your guests and can be supported reliably. If guests may decline a receipt, make sure staff can still locate the transaction when help is needed.
What should a cashier do when a receipt does not print?
Find the transaction and verify its status before suggesting another payment. Then use the documented fallback or involve the shift lead if a receipt cannot be provided immediately.
Is a pickup number the same as a receipt?
No. A pickup number helps match an order to a guest. A receipt records purchase details; the restaurant should check that its chosen format provides the information guests and staff need.
