Canteen customers wallets and balances
Distinguish customer payments, prepaid wallet top-ups, and running balances in a canteen operation.
Customer balances let a canteen support prepaid accounts or a running balance for later settlement. Establish the canteen's policy before staff start using these routes.
Distinguish the transactions
| Event | Meaning |
|---|---|
| Payment for an order | Money settles that purchase |
| Wallet top-up | Money is added for future purchases |
| Order using prepaid credit | A purchase uses the customer's available funds |
| Order on a running balance | The purchase is recorded for later settlement under your canteen's policy |
A top-up and an order payment are not interchangeable. Check what the transaction is intended to do before saving it.
Work from the correct customer
Find the customer and review the relevant contact details, purchase history, and balance. Use the canteen's agreed identifier when names are similar. Confirm the customer before adding a top-up or charging an order to the account.
For an order, review the amount and configured payment route. After completion, check the resulting transaction and balance. If a customer disputes a balance, compare the transaction history with the original order and payment records rather than entering an unexplained adjustment.
Set the policy customers need
Explain whether customers must prepay, whether a pay-later balance is allowed, how they add funds, and who handles discrepancies. Ensure staff follow the same rules at each counter.
The available controls depend on the canteen configuration. Ask support to confirm the wallet and payment setup for your operation before introducing a new balance policy or payment device.
See counter ordering for the complete service sequence. A school lunch preorder collected through an ordinary form does not automatically provide the canteen wallet workflow described here.