A customer collects breakfast, asks for a receipt and later wonders why a reward is missing. Your team needs a clear way to find the sale, check the member and explain the payment. For a Singapore café or restaurant, a POS receipt loyalty programme should begin with that practical service journey. A printed slip can help locate an order; it should not carry promises that the configured programme cannot honour.
Think of three connected records: what was ordered, which member benefit applied, and how the bill was paid. They answer different questions. Keeping them understandable helps staff resolve a query without guessing, charging again or awarding an unexplained benefit. This guide brings CommerceOS, LoyaltyOS and PaymentOS together around that handover, with illustrative tests rather than promised sales results.
Start with a receipt your guest and team can understand
Review the actual outlet name, date, order reference, item descriptions, selected extras, discounts and final amount on your proposed receipt. Where tax or service charge applies, confirm the correct business settings and wording with your adviser. A kitchen instruction, a customer bill and a card-terminal slip serve different purposes; do not train staff to treat every piece of paper as the same confirmation.
IRAS’s record-keeping guidance for companies explains the importance of retaining source documents and being able to explain business transactions. That is established guidance reviewed for this article, not a new October announcement. Use it to discuss your complete record-keeping process; choosing a POS alone does not establish that every accounting or tax requirement has been met.
CommerceOS: connect the paper to the correct order
Rewardly’s printing documentation distinguishes customer receipts, kitchen chits, delivery dockets and labels. Printer settings belong to the register, and the appropriate output depends on its configuration. For a merchant, the useful question is whether the right document reaches the person who needs it. Confirm printer compatibility and the intended counter, kitchen and collection setup during your walkthrough.
Consider a fictional breakfast order with two drinks, one paid extra and a takeaway item. Compare the customer receipt with the basket and the preparation instructions. Can the guest understand the charge, and can the team identify which drink needs the extra? Repeat the test with an unavailable item and a corrected order. The purpose is a clear handover, not a longer printout or a claim that every printer behaves identically.
The documented order screen lets staff reopen an existing order and reprint its receipt. This differs from cloning an order into a new basket for another sale. Teach the distinction before a busy service: a guest requesting another copy needs the existing record, not a second charge. Decide who may handle corrections and refunds, and demonstrate the actual permissions and payment method in use.
LoyaltyOS: identify the member before promising a reward
The current counter loyalty workflow is to attach the member, build the basket and take payment. The cashier can search for a member or scan the member’s QR code. A member QR code is different from an arbitrary code printed on a receipt. In this documented flow, a sale without an attached member can complete, but does not earn member points.
LoyaltyOS connects a membership tier to its loyalty programme. After a qualifying paid sale, the earning is calculated on the server and can be checked in the member experience and admin history. Do not promise an exact earn merely because a membership label appears. Confirm the active programme, qualifying purchase and configured benefit. Explain where the guest can see the result instead of inventing a points figure on the receipt.
Rewardly also supports retrospective cashback claims for eligible purchases under the supported claim journey. Confirm the claim window, purchase verification and programme conditions before advertising it. This does not mean that every receipt, past order or scanned code automatically earns every kind of reward. Offer a simple explanation and a staff-assisted route when a guest needs help.
For a missing-points query, locate the original order and review History & Transactions before making a correction. The documented manual point adjustment can reference a receipt and is controlled by role permissions. Assign an authorised person to check the member, outlet and programme, record the reason and resolve the query. A goodwill adjustment should remain distinguishable from the original earning.
PaymentOS: separate a receipt from the payment review
PaymentOS helps the team review how a sale was paid. Its payment reports group tenders and provide date, outlet, register and source filters. Compare the order with the relevant payment record and provider evidence when investigating a disputed charge. A printed receipt is useful context, but a bank payout is a separate event from the sale or its payment confirmation.
Confirm how the proposed payment service works. A connected gateway, Manual PayNow and a custom tender recorded from a separate card machine require different checks. Rewardly’s documentation describes a custom tender as a recorded tally reconciled against the machine total at shift close. Do not assume that selecting a payment label means the POS independently verified money arriving from every external device.
In an illustrative S$18 purchase, a guest might spend S$3 of existing store credit and pay S$15 by card, where the configured setup supports that combination. The order total remains S$18; the new card receipt is S$15. Check the credit movement and card record separately. This is a staff-training example, not a default offer, fee quotation or promise about settlement timing.
Make the handover helpful without adding pressure
The CCS price-transparency guidance, on a page dated 26 September 2025, supports clear prices and conditions. Apply that principle before checkout as well as afterwards. A receipt should help explain the agreed purchase, not be the first place a guest encounters an unexpected charge or a restriction on an advertised reward.
Give staff a short service script: confirm the order, offer the receipt, and explain where an eligible member can check the benefit. Keep optional membership or marketing conversations separate from providing the requested receipt. Avoid unnecessary personal details on printed copies, and keep staff copies appropriately. Agree what the team should do if the printer fails or the customer needs a readable replacement.

Test the difficult cases before the next busy shift
Run a small acceptance test with the actual outlet team: an ordinary sale, a member sale, a guest without membership, a receipt reprint, a mixed payment where supported, and a refund query after shift close. Verify the original order reference, the relevant benefit movement and the payment record each time. Ask the team to explain the outcome in everyday language.
Track useful service measures such as missing-reward questions, time spent locating orders and avoidable repeat prints. Compare similar trading periods and note changes in staffing or order volume. These observations can guide training and configuration; they do not prove that a receipt design alone caused a return visit or increased revenue.
For a wider buying decision, use the existing Singapore POS system guide. For the difference between points, discounts and store credit, read the separate reward-design guide. Keep the receipt conversation focused on a clear purchase record and a benefit the team can actually explain.
Book a Rewardly walkthrough with a sample order, one member scenario and your required payment method. Ask to see CommerceOS, LoyaltyOS and PaymentOS together from basket to receipt, benefit history and closing review. A useful receipt is part of a dependable service process, supported by people who know what to check.



