Loyalty automation should make a promise easier to keep. A member understands what they can earn, your colleague can explain the benefit, and checkout applies the right conditions. For a Singapore shop, the useful question is not how many tasks can run unattended. It is which repeatable steps have clear rules and which decisions still need a person.

This updated guide uses a fictional neighbourhood tea and pantry shop preparing a small member-rewards pilot. LoyaltyOS manages configured benefits, CommerceOS supports the sale, and PaymentOS helps the team review payments and discounts. AInstein can explain the setup; separate reporting tools help investigate results. This is a planning example, not a customer outcome or a claim that every module and channel is included.

Start with one customer promise

Choose a benefit staff can describe in one sentence: a welcome voucher for a new member, or points earned under a defined programme. Decide who qualifies, what they receive, where it works and when it expires. The tea shop might start with one welcome benefit rather than launch points, tiers and several promotions together. Fewer rules give the first rehearsal a clearer purpose.

The Retail Industry Digital Plan announcement of 26 May 2026 organises solutions around business touchpoints and encourages workforce development alongside technology. This is older sector guidance, not a new October launch. Apply that practical approach to the joining, checkout and review experience. The announcement does not establish funding eligibility for a particular Rewardly package.

Connect membership to the actual earning rules

In Rewardly, a membership tier and a loyalty programme do different jobs. The tier identifies the member's level; the linked programme defines what they earn. Create the tier first and review the earning rule before making the programme live. A tier alone earns nothing. For the tea shop, one clearly explained tier is a useful starting point before introducing more levels.

Points are calculated after payment and appear in the member app afterward. Current documentation says the POS does not show points earned during the sale. Train colleagues to explain when the customer should check, rather than promise an immediate on-screen award. Decide who investigates a missing balance, and use a representative completed purchase to test the explanation before inviting members.

Check what actually issues the welcome reward

A voucher's name is not its automation rule. Rewardly documents the First time shopper event as issuing a live welcome voucher when the customer joins as a member, not on their first purchase. The similarly named Newly joined member event is a reporting label and does not issue it automatically. Confirm the selected event in your setup, then test the joining journey.

Also check the customer's voucher copy: availability, expiry, eligible products, minimum spend, outlet and channel. A successful issue is only the start; staff still need to apply an eligible benefit correctly at CommerceOS checkout. Link your training to the voucher redemption guide. Avoid promising that a voucher works on every purchase simply because it appears in the member wallet.

Use AI guidance without handing over the decision

Ask AInstein to explain a setting or help your colleague find the right screen. The support chat guides; it does not edit programmes, issue vouchers or change settings for you. Your authorised staff configure and save the rules. Keep the AInstein Concierge walkthrough handy for onboarding, and finish the exercise with the actual merchant task rather than only reading an answer.

Smart Report Builder is a separate tool for sales questions. Choose the date range, outlet and source, then read its chart and explanation alongside the underlying table. A question about outlet sales can help frame a review, but it does not prove why members returned or whether a promotion caused a purchase. The merchant decides what action, if any, follows.

Illustration of tea shop colleagues testing reward eligibility and reviewing a simple checklist
AI-generated editorial illustration. People and screens are fictional.

Rehearse the channels your members will use

Test an eligible basket, an ineligible basket and an expired benefit. At the counter, practise attaching the right member, explaining the remaining amount and answering a rejected-redemption question. Add online, QR or kiosk tests only for channels in your intended configuration. The customer's explanation should remain clear even when the steps or restrictions differ.

One important difference concerns points: documented Loyalty Conditions limit redemption at online or QR checkout and on kiosks, while the POS does not apply those same conditions and permits redemption up to the member's balance. Do not assume a digital-channel cap protects the counter. Confirm the intended staff procedure and permissions, then include both journeys in the pilot.

Review payments, discounts and the cost of the offer

PaymentOS reports group received money by payment method and separate programme discounts from manual discounts. Use a consistent date range, outlet and source when reviewing the pilot. Compare those records with the relevant sales and loyalty evidence, plus the cost of supplying the benefit. A voucher issued, a voucher redeemed and a payment received describe different events; none alone proves profit.

A Singapore Business Review report published on 23 October 2026, covering discussion at the Retail Asia Summit 2026, stresses specific business needs and clear rules for AI use. It is current-morning coverage; the event's exact date is not established here. For this pilot, assign one owner to check records and staff feedback before expanding, rather than attribute every sales change to automation.

Launch a small routine your team can maintain

Write a short launch sheet with the customer promise, eligibility conditions, responsible colleague and review date. Rehearse joining, receiving the benefit, completing payment and asking for help. Record exceptions without exposing customer details in shared training material. Set a review for the first completed trading week and allow for different opening days, promotions and customer mix when comparing periods.

Bring that launch sheet to a Rewardly demonstration. Ask to see LoyaltyOS rules, the CommerceOS checkout and PaymentOS records across the complete journey, with AInstein guidance where useful. Confirm included modules, training, support and total costs. The goal is a reward routine that members understand and colleagues can support confidently, with evidence for the next decision.