A regular guest returns, but the team cannot find the right membership record. A new manager receives a spreadsheet without knowing when it was exported. A restaurant changes systems and discovers that a contact list does not explain the outstanding rewards. These are customer-service problems before they are technology problems. Useful restaurant CRM starts with records your team can identify, interpret and handle responsibly.

For Singapore F&B operators, Rewardly CommerceOS, LoyaltyOS and PaymentOS connect different parts of that work. This guide explains what to check before a staff handover, a new outlet or a proposed migration. The café examples are fictional; no automatic transfer from every external system is implied.

1. Know which customer record you are looking at

In Rewardly, the Members list describes a customer’s relationship with your merchant, including their membership and balances. It is not a directory of everyone using Rewardly. A person can belong to different merchants through one account, while each merchant works with its own member relationship. That distinction helps an outlet team answer the right question without assuming it can inspect another business’s customers.

Keep the order record and the loyalty record distinct. On Rewardly POS and online ordering, a guest order does not create a member Sales Transactions row. Find the guest sale under Orders; use the member’s transaction history to investigate their rewards. An empty loyalty search does not prove that the restaurant never served that guest. See the loyalty programme guide for the wider checkout journey.

2. Check identity, balances and communication choices separately

Before correcting a record, confirm that it belongs to the guest in front of you. A familiar name or similar phone number is not enough. In an illustrative café handover, the supervisor checks the member identity, current tier and relevant transaction before resolving a missing benefit. Points and store credit shown in the member profile are read-only; authorised adjustments belong in History & Transactions. Keep the reason and supporting sale reference with the correction.

A customer record can show marketing acceptance separately from acceptance of terms. Do not turn a service enquiry, an imported contact or a shared spreadsheet into a new marketing permission. Decide which information the team needs, who handles correction requests and how long working copies remain useful. Review your organisation’s privacy and retention arrangements with the responsible person; more collected data does not automatically create a better relationship.

3. Understand what a member export actually contains

The current Members documentation describes a verified export request: select the merchant admin recipient, send the request, and the Rewardly team verifies it before emailing an Excel workbook. It is not an instant browser download. Confirm the authorised recipient and expected timing before a handover, rather than promising the next shift an immediate file.

The optional marketing-only switch can narrow that export. Other filters visible on the Members screen do not narrow it, and guests are excluded. The workbook contains contact details and current loyalty/store-credit balances; it is not the full transaction history, programme configuration or evidence of every communication choice. Check the agreed export scope before sharing a file or treating it as a complete business archive.

For a proposed system change, ask both suppliers which fields can be provided and accepted. A balance without its programme, expiry or supporting history may be difficult to interpret. Record missing information and agree how guest questions will be handled. An available export is valuable, but it does not establish universal compatibility, unrestricted portability or a guaranteed recovery time.

4. Rehearse an import before changing live records

Rewardly documents a classic CSV importer for members. Use its current sample template and expected column order. The Excel member export and a member-import CSV serve different purposes; do not assume that renaming the file creates a safe round trip. Agree the treatment of existing identities, balances, tiers and historical activity with the implementation team before loading an external customer list.

Begin with a small, authorised test file using synthetic records in an agreed test environment. Check accepted and rejected rows, then compare the resulting records with the intended outcome. Correct failed rows and review the result log before proceeding. A spreadsheet that opens successfully has not necessarily passed the importer’s rules, and a successful contact import does not prove that every old reward was migrated.

Smart Import is a separate AI-assisted workflow for products and stock-related records; members use the classic importer. Its mapping preview still requires human review. This boundary matters when comparing an AI POS system: assistance with menus or ingredients is not evidence that AI can merge customer identities, migrate consent or repair loyalty balances automatically.

Restaurant colleagues rehearsing a fictional member enquiry with a receipt and training records
AI-generated editorial illustration. People and screens are fictional.

5. Give each colleague the access their work needs

Rewardly’s role permissions govern actions such as viewing, creating and editing records. POS-user permissions separately control practical till actions, including refunds and discounts. Review both with the owner before the next staffing change. A cashier who can serve a guest does not automatically need the same access as the person handling a customer-data export or a manual balance correction.

Keep a named escalation route for cases the cashier cannot resolve. AInstein’s support guidance can help staff find and understand the relevant screen; it does not make the correction on their behalf. Rehearse the handover with a fictional missing-reward enquiry so each colleague knows who checks the evidence and who is authorised to act.

6. Ask how records can be recovered, not just displayed

Backup is an established business-continuity concern. CSA’s 17 October 2024 initiative note includes backup among cybersecurity measures. IMDA’s current backup-solution assessment asks about separation from the operating environment, backup frequency and authorised access. These are sourcing references, not a claim that Rewardly holds a particular certification or that an Excel export is a full-system backup.

Ask the proposed provider what is backed up, who can request recovery, which period can be recovered and how a recovery is checked. Keep approved working exports protected and accessible only to the people responsible for them. Include the contact route for a disruption in the operating handbook. Agree these responsibilities in the service scope instead of relying on an untested assumption that “cloud” means every record is instantly recoverable.

7. Reconcile the handover across orders, rewards and payments

Use CommerceOS order evidence to confirm what was bought, and LoyaltyOS records to check the associated member benefit. For groups, repeat the rehearsal with the relevant outlet and programme rules; the multi-outlet operating guide explains why locations need not share identical offers. Keep a dated record of what was checked and what still requires investigation.

PaymentOS payment reports can be filtered and exported for the payment-side review. Keep a recorded tender separate from provider confirmation and a later bank payout. Moving a customer list does not transfer payment credentials, settle an outstanding refund or reconcile old receivables. Agree those payment responsibilities separately; the integrated-payments guide provides a practical closing checklist.

A usable handover ends with an owner, a checked sample and a written list of exclusions. Confirm the modules, migration work, support, charges and access arrangements in the quotation. Avoid assuming lifetime access, free upgrades or unlimited data services unless they are explicitly part of the current agreement.

Book a Rewardly walkthrough with a synthetic member example and your handover questions. Ask to see the profile, transaction evidence, export request, import result and payment report in the proposed setup. Clear records help the team resolve a guest’s question with confidence, while keeping important decisions with the merchant.