Moving Loyalty Points From NCR Retail Online To A New Platform

When NCR Retail Online was discontinued, merchants had to move more than product listings and order history. Customer loyalty balances, earning rules, redemption records and member contact details also needed a careful migration path. A points balance that appears simple in an export can depend on transaction dates, returns, promotions and expiry conditions.

For Australian retailers, the change may involve a Magento or WooCommerce store connected through an NCR Counterpoint partner. The best destination is not necessarily the platform with the most features. It is the one that can preserve customer value, support accurate accounting and make rewards easy to understand across online and physical shops.

A sound transition begins with an inventory of the old loyalty programme. Record how points were earned, whether bonuses had different values, which balances were pending, and how refunds affected rewards. Capture the original terms as well as the numerical balance, because a new system needs to reproduce the meaning behind each figure.

Customers in Sydney, Melbourne, Brisbane and regional areas should experience the change as a continuation rather than a reset. Their account history, available rewards and communications should remain consistent, whether they shop from a phone, visit a counter or collect an order from a local store.

Define The Loyalty Data Before Export

Start by separating the current balance from the events that created it. A member with 2,400 points may have earned 3,000, redeemed 500 and received a 100-point manual adjustment. Importing only 2,400 makes future disputes difficult to investigate. Export the ledger wherever possible, including order ID, event type, amount, timestamp, staff adjustment and reason.

Use a consistent customer key during the move. Email addresses are useful for matching, but they are not always reliable: customers change addresses, share household accounts or use different addresses for online and in-store purchases. A Counterpoint customer number, combined with verified contact details and a duplicate review, is usually safer than an email-only match.

Keep monetary and points values separate. A reward might be 100 points for every dollar spent, while another campaign offers a fixed voucher. Store the points event and the reward liability independently so that rounding, refunds and partial redemptions do not create unexplained differences.

Recreate Earning And Redemption Rules

Document the old programme in plain language before configuring the replacement. Include qualifying products, exclusions, minimum spend requirements, bonus periods, return treatment, redemption thresholds and expiry. Retail categories can behave differently: a bookseller may award points on most titles but exclude gift cards, while an entertainment retailer may use promotional bundles with special conditions. Useful category context can be found in books and entertainment when reviewing catalogue-specific rules.

Pay close attention to returns. If a customer earned points from a $120 purchase and later returns one $40 item, the new system should remove the appropriate points rather than reversing the entire transaction. Test exchanges, cancelled orders, split payments, partial refunds and staff-issued credits before the programme goes live.

Australian Consumer Law makes clear, accurate reward terms important. If points expire, the expiry period and applicable conditions should be presented prominently rather than hidden in dense copy. Avoid telling customers that points are “permanent” if the new platform will remove them after inactivity, and ensure promotional claims match the actual earning rate.

Protect Customer Information And Consent

A loyalty migration contains personal information, including names, email addresses, purchase patterns and potentially postal details. Review the Australian Privacy Act requirements that apply to the business, document why each field is being transferred and limit the export to information the new service genuinely needs. Remove obsolete test accounts and duplicate records before sending data to a platform or implementation partner.

Marketing permission should move separately from ordinary account data. A customer may agree to receive order updates without agreeing to promotional emails or SMS messages. Preserve the source and date of consent where available, suppress unsubscribed contacts and check that the new provider supports unsubscribe handling under the Spam Act 2003.

Use encryption during transfer and restrict access to staff who need it. A temporary spreadsheet containing names, balances and emails should not circulate through personal inboxes or unsecured file-sharing links. Keep an import log, a copy of the approved mapping and a record of who authorised the transfer.

Connect The New Store With Retail Operations

A loyalty programme is most useful when its balance reflects every sales channel. Connect the replacement store to inventory, point-of-sale and customer records so that an online sale in Melbourne, a counter purchase in Perth or a click-and-collect order in Adelaide follows the same earning and redemption logic.

Real-time stock and order events can help prevent loyalty rewards being issued for cancelled or unfulfilled purchases. Technical teams moving from the old environment can review guidance on real-time inventory webhooks, then adapt the event design for orders, refunds and fulfilment changes rather than copying it without testing.

Define which system is authoritative for each event. The ecommerce platform might create an order, Counterpoint might confirm payment, and the loyalty service might post points only after fulfilment. Without a clear sequence, duplicate webhooks can award points twice, while delayed refunds can leave a customer with an inflated balance.

Test The Migration Before Customers See It

Run a trial import using a representative sample: active members, dormant members, high-balance accounts, recently refunded orders, manually adjusted balances and customers with duplicate profiles. Compare the old and new totals at member level and across the entire programme. A small sample of easy accounts can conceal serious problems in edge cases.

Reconcile the financial impact as well as the record count. The total points liability, redeemed rewards, pending points and expired balances should be explainable. Investigate differences caused by rounding, time zones, cancelled orders or rules that the new platform cannot reproduce exactly.

Test the customer journey on Australian devices and networks, including mobile checkout and click-and-collect. Confirm that a customer can sign in, view a balance, redeem a reward and receive a clear confirmation. Ask staff in several locations to process returns and redemptions, because a workflow that works in a head office sandbox may fail at a busy Saturday counter.

Manage The Cutover And Customer Message

Choose a cutover window that avoids major sales periods such as Boxing Day, end-of-financial-year promotions or a large local campaign. Freeze loyalty-changing activity briefly, export the final ledger, load it into the new system and reconcile the totals before reopening redemptions. If a full freeze is impossible, record transactions created during the migration and replay them in a controlled order.

Tell customers what is changing, what is staying the same and what they need to do. A concise email can explain that their points have moved, show the current balance and link to updated terms. Do not ask customers to create a second account unless necessary. If passwords cannot be transferred securely, explain the reset process without implying that their points have been lost.

Controls That Reduce Migration Risk

• Keep an immutable copy of the final points ledger and export manifest.
• Reconcile member counts, total balances and reward liability before and after import.
• Test duplicate orders, refunds, exchanges, cancellations and manual adjustments.
• Preserve unsubscribe records and separate service messages from promotional campaigns.
• Provide staff with a short procedure for investigating disputed balances.

After launch, monitor failed imports, duplicate events, unusual redemptions and customer service contacts. Set a defined period for honouring verified legacy balances when a record cannot be matched automatically. A controlled exception process is better than asking a genuine customer to prove every purchase from memory.

What Customers Should Remember

Moving loyalty points is a data and accounting project as much as a software change. The balance shown to a customer should be backed by a traceable history, correctly linked to purchases and governed by terms that remain fair and understandable.

For Australian retailers, privacy obligations, marketing consent, Consumer Law, local store workflows and mobile shopping habits all belong in the migration plan. When the new Magento, WooCommerce or partner-connected system preserves those details, customers can continue earning and redeeming rewards without feeling the disruption behind the scenes.