Worked example: what should staff test before launch?

Illustration: a pet shop offers 5% back as store credit on eligible purchases. An eligible S$40 purchase earns S$2 for a later visit under that example rule. It does not reduce today’s bill to S$38 or send S$2 to a bank. Try a second purchase and check the credit actually used, the balance left and the amount due.

Cashback

Compare all eight loyalty tools

A reward is useful when the customer understands what they receive and the team can honour it consistently. For a Singapore café, bakery or restaurant, the first decision is simple: reduce today’s bill, award points, or give store credit for a later visit. Those choices can have a similar advertised value but create different checkout experiences, cash collections and future commitments.

The Restaurant Association of Singapore’s 6 October 2026 review reported that F&B sales fell 1.6% year on year in August, while online orders accounted for 20.6% of sales. This is older sector context, not a new October trading result or a forecast for your shop. Our practical response is to make each offer understandable and test its cost across the channels you actually use.

Discounts, cashback and points answer different needs

A discount reduces the current bill. In an illustrative S$20 basket, a S$1 discount leaves S$19 to collect. It can suit a clear, immediate price benefit. Agree which items qualify and how the offer interacts with other promotions. The final amount must reflect the outlet’s actual tax and service-charge settings.

Rewardly cashback returns value as store credit for a future visit. In a separate illustrative S$20 qualifying purchase, 5% cashback creates S$1 of store credit after payment; it does not reduce that purchase to S$19 or send S$1 to the customer’s bank. Explain when the credit becomes available and when it expires.

Points use an earning rule and a separate value. Suppose an illustrative programme awards 20 points on that S$20 purchase and defines 20 points as S$1. The possible future value is S$1, subject to redemption settings. These are examples for comparison, not Rewardly’s default rates or an offer combining all three benefits.

Budget the future benefit before choosing the headline

If 100 qualifying orders each earn S$1 of store credit, S$100 of credit has been awarded. That is a simple exposure check, not a forecast of redemption or extra sales. Decide what the programme can afford before increasing an earning rate. Keep customer-funded top-ups separate from promotional credit when reviewing the sources of a wallet balance.

Look beyond the reward amount. Consider ingredient and packaging costs, any discount already granted, payment fees and the work needed to answer questions. A returning customer may use credit on an order they would otherwise have paid for. Review the overall transaction and service cost; an attractive headline alone cannot demonstrate that the programme is profitable.

LoyaltyOS: define the promise and its conditions

LoyaltyOS supports cashback based on the whole bill, a fixed amount or specified products. Current documentation describes membership restrictions, credit validity and a programme end date. Configure the programme in Draft, review its description, then activate it when ready. Confirm the precise eligible basket and membership with the implementation team before advertising it.

Store credit is a monetary wallet balance used as a payment method at the POS. It can come from top-ups, top-up bonuses, rewards or point conversion. A paid top-up and earned cashback reach the same type of balance through different routes. Keep their customer explanations and internal records clear, including expiry where configured, rather than describing every increase as cash returned.

Points need the same care. A programme belongs to a membership tier; the earn rate and the merchant’s point value are separate decisions. The documentation also distinguishes redemption channels: Loyalty Conditions limit points at online, QR and kiosk checkout, while the POS permits redemption up to the member’s balance without that same condition check. Demonstrate the channel your team will actually use.

CommerceOS: test the next purchase as well as the first

With CommerceOS, take one familiar menu basket through the proposed checkout. Identify the correct member, inspect any current discount, complete payment and check the resulting reward in the member experience. Then simulate a return visit and spend the available benefit. Repeat for the channels and outlets in scope; a counter test does not establish identical behaviour on every device or online shopfront.

The Competition and Consumer Commission of Singapore’s price-transparency guidance, whose page is dated 26 September 2025, stresses accurate prices and clearly communicated conditions. Use it as a practical prompt to make the benefit, eligible items and promotional period easy to find before checkout. This is established guidance, not a new October policy announcement.

Give staff a short explanation they can use naturally: what changes on today’s bill, what is saved for later, and where the member can see it. Test an expired balance, an ineligible purchase and a guest who needs help. Agree who handles cancellations, refunds or disputed rewards, and demonstrate the relevant workflow instead of assuming every benefit automatically reverses.

PaymentOS: keep the reward and the money records distinct

PaymentOS provides the payment-handling and reporting context for the sale. A discount changes the amount due; spending store credit uses an existing balance as tender. Newly earned cashback is a future benefit. Keep those events distinct when reviewing the bill and the payment record. Manual PayNow and team-enabled gateway integrations also require different confirmation checks.

Use payment reports to review the relevant tender, outlet, register and source, then compare provider takings with the settlement statement. Review reward earning and spending alongside member transaction history. Store credit redeemed is not a new card receipt, and a successful card transaction is not the same event as a bank payout.

Ask the team to show a mixed payment where supported, a return-visit redemption and a refund case. The useful outcome is a traceable explanation of what the customer paid, what balance was spent and what benefit was awarded. Confirm compatible payment services and the required modules in the quotation; do not assume a loyalty rule makes every external payment integration available.

Two bakery colleagues reviewing simple reward cards and a blank receipt
AI-generated editorial illustration. People and screens are fictional.

Run a small pilot and measure useful return visits

Choose a manageable audience and a defined review period. Record eligible purchases, rewards awarded, rewards spent, outstanding balances, return visits and staff questions. Compare like-for-like trading periods and keep existing members separate from newly enrolled members. A return visit after an offer is an observation, not proof that the offer alone caused the visit.

Start with one understandable benefit rather than several overlapping programmes. Review the wording and the costs with the outlet team, then change only the rule that needs attention. For wider membership design, use the existing membership-tier guide. For a voucher-based offer, review the separate redemption guide instead of treating vouchers, points and wallet credit as interchangeable.

Book a Rewardly walkthrough with a sample menu, one proposed benefit and your current payment arrangement. Ask to see CommerceOS, LoyaltyOS and PaymentOS together on the first purchase, the return visit and the closing review. A well-designed reward begins with a clear promise and records that make it possible to keep.