Worked example: what should staff test before launch?

Illustration: a dance studio invites members to refer friends. Write the invitation from both perspectives: what the friend needs to do and when the existing member qualifies. Test an eligible referral and a second attempt involving the same person. Review exceptions before announcing any reward, and compare reward cost with qualifying introductions rather than links shared.

Customer referrals

Compare all eight loyalty tools

A customer loves your shop and wants to introduce a friend. A useful referral programme makes that introduction easy, explains the thank-you clearly, and keeps its cost manageable. For Singapore cafes, salons and neighbourhood retailers, the aim is a welcome your team can deliver consistently. A recommendation deserves the same care as the first sale that follows it.

This refreshed guide uses a fictional neighbourhood florist planning a small referral pilot. It connects LoyaltyOS reward rules, CommerceOS service and PaymentOS review without assuming every channel behaves identically. The example is a planning exercise, not a customer result. Start with one understandable reward, confirm the qualifying event, and rehearse how a member uses the benefit before inviting customers.

Start with the customer relationship you want

Choose a specific purpose: introduce local residents to a new shop, thank regular customers for recommendations, or encourage a return visit after an introduction. These goals need different measures. A new membership is not automatically a purchase, and a reward issued is not proof of repeat business. Decide what a useful introduction means before choosing a headline or reward amount.

The Retail Industry Digital Plan factsheet of 26 May 2026 organises solutions around business touchpoints, including customer experience and operations. This is older industry context, not a new October announcement. Apply that practical approach here: connect the invitation, reward and checkout rather than treating a referral promotion as a separate poster.

Make the invitation and qualifying event clear

Rewardly's referral documentation describes a member sharing through the member app, a friend joining the loyalty programme, and a configured reward reaching the referring member once the referral qualifies. The available reward types are voucher, loyalty points and store credit. Explain who receives the reward and what counts. Avoid advertising an automatic benefit for the friend unless that separate benefit is configured and verified.

For the florist, a first pilot might thank existing members for qualifying introductions. Before announcing it, demonstrate the complete joining journey in the intended setup. Confirm whether qualification depends on joining, a purchase, or other supported rules; do not infer the trigger from a marketing headline. Explain how customers should ask for help when an introduction is missing, and nominate someone to investigate.

Choose one reward and a budget you can explain

A voucher can communicate a specific treat or saving. Points suit an established points programme whose value members already understand. Store credit gives a balance to spend with the merchant. Pick the format that fits a typical visit and your economics. Include the cost of providing the benefit and the staff time needed to answer questions. There is no universal reward amount that suits every business.

LoyaltyOS referral settings include a gift amount limit and a view of the amount already gifted. Use these to keep the pilot bounded, then confirm how the limit applies to your chosen reward type. Current documentation says the referral expiry-date field is not enforced; stop the programme by changing its status to Draft. Assign an owner and a calendar reminder for the review date instead of relying on that field to close it.

Illustration of two florists planning a referral reward at a workbench
AI-generated editorial illustration. People and screens are fictional.

Make the earned benefit useful at checkout

The referral reward and its later use are separate moments. Rewardly documents automatic granting once a referral qualifies, with no POS step for granting. CommerceOS supports the subsequent sale. Rehearse member identification, the selected benefit and the amount still payable. Your cashier should be able to explain the outcome without manually inventing a replacement discount when a customer cannot find their reward.

Check the reward's own conditions. A voucher can have eligible products, minimum-spend requirements, outlets and redemption channels. Store-credit redemption channels also need configuration. Demonstrate the exact POS, online or kiosk journey you intend to promote, including an ineligible purchase. The voucher redemption guide explains those choices, while the loyalty software guide helps compare broader programme needs.

Keep rewards and money received understandable

PaymentOS reports group payment methods and allow filters for dates, outlet and source. Its discount report distinguishes programme discounts from manual discounts. Use the relevant records with order details when reviewing a reward redemption. A store-credit payment, a voucher discount and a new cash or card payment represent different things; train the team to describe them accurately rather than calling every benefit cashback.

Singapore Business Review's 19 October 2026 coverage of the OCBC SME Index discusses the third quarter of 2026 and cautions that higher transaction values may partly reflect prices. This is recent context already reviewed in our previous daily research, not a fresh 20 October development. The merchant lesson is to review costs and actual customer behaviour alongside takings. Payment totals alone cannot establish a referral programme's profit or additional sales.

Test a small pilot before widening the invitation

Use test accounts and walk through a valid introduction, an incomplete joining journey, an unavailable benefit and a reward that cannot be redeemed against the chosen basket. Check the payout limit and how to stop new qualifying rewards. Agree how staff handle cancellations, refunds and disputes in the actual configuration. Keep the explanation short enough for a colleague covering a shift to understand.

For an online invitation, let the member use the supported referral flow. A general online-ordering link is not proof that a referral has been attributed. CommerceOS browser ordering can support a later purchase where configured, but confirm reward availability and payment handling separately. Use clear member-facing instructions and collect only the information needed for the journey; do not ask members to upload friends' contact lists.

Review introductions, redemption and repeat visits separately

At the review date, record qualifying referrals, benefits granted, benefits used, customer questions and reward cost using available records. Review subsequent visits separately when you have comparable evidence. A small pilot will not prove that every new sale came from the programme. Seasonality, other offers and existing relationships can all affect results. Adjust the invitation or reward only after understanding where customers and staff encounter friction.

Bring one typical customer journey to a Rewardly demo. Ask to see LoyaltyOS referral qualification and limits, CommerceOS handling of the resulting sale, and PaymentOS records for the selected benefit and remaining payment. Explore the referral programme overview, then confirm the exact supported rules before launch. A modest promise that your team can explain is a sound starting point for a lasting customer relationship.