Migrating Store Credit and Store Points from NCR to a New Platform

When NCR confirmed the discontinuation of NCR Retail Online, retailers running their day-to-day operations on NCR Counterpoint were left with a narrow window to move their online storefronts to platforms such as Magento or WooCommerce. For most shops, the visible work centres on products, categories and shipping rules. The less visible, and considerably more delicate, task involves the loyalty balances sitting inside Counterpoint — the store credit dollars, promotional vouchers and store points that customers have accumulated over years of trading.

Store credit is unusual because it sits at the intersection of finance, marketing and customer trust. A point earned during a Brisbane Boxing Day promotion three years ago still carries monetary value today, even though the rules that issued it have long since been archived. Move that data carelessly and you create a silent liability: customers who believe they hold a balance, records that disagree, and a support inbox full of disputes during what should be a fresh start on a new platform.

Australian retailers feel this pressure acutely. Loyalty schemes are deeply embedded in suburban shopping culture, from independent gift stores in Perth to multi-store footwear chains across Melbourne and Sydney. With the Australian Consumer Law requiring that gift cards and store credit honour stated expiry terms, and the Australian Competition and Consumer Commission watching unfair contract practices closely, a botched migration is a compliance risk as well as an operational one.

The remainder of this article walks through the five stages of moving store credit and store points from NCR Counterpoint to a replacement platform without losing a cent — or a customer.

How NCR Counterpoint Stored Customer Credit and Points

Counterpoint treats store credit and store points as two distinct constructs. Store credit lives against a customer record as a monetary value, typically denominated in AUD and tracked alongside loyalty tier status. Store points sit in a separate accrual ledger, often with expiration dates, tier multipliers and promotional bonuses layered on top. Both can be issued at the point of sale, refunded onto the original tender, or applied as tender in a future transaction.

For retailers who used NCR Retail Online as their connected web channel, customer identities were synchronised back into Counterpoint, which meant the loyalty ledger was the source of truth. The online store simply read those balances on demand. If you operated a homewares and lifestyle range alongside fashion or food lines, the same customer might carry three different balances across different point pools.

That single-source architecture is helpful during migration, because there is only one ledger to extract. It is also risky, because every downstream assumption — that a balance is current, that an expiry date is intact, that a refund path still works — depends on a clean export.

The Technical Hurdles of Extracting Loyalty Data

The first obstacle is the export itself. Counterpoint does not natively publish a customer-balance report in a format that maps cleanly onto Magento or WooCommerce schemas. Most integration partners rely on ODBC queries, custom Crystal reports or direct SQL against the Counterpoint database to extract point ledgers, store-credit movements and customer-tier assignments. Each of those approaches has its own quirks, particularly around historic transactions and voided sales.

The second obstacle is reconciliation. A customer's store credit balance at midnight on the day of cutover must equal the sum of all transactions in their ledger, including manual adjustments, refunds and expired points. If even a handful of records fail to import — say, a batch of returns processed in Adelaide the day before go-live — the new platform will inherit a balance that contradicts Counterpoint's books.

This is where precision really matters. Aligning tens of thousands of records requires the same disciplined approach you would use when finding satellite azimuth: small angular errors compound over distance, and the further downstream you discover the misalignment, the more expensive it is to fix. A nightly reconciliation report run for at least two weeks before cutover catches most discrepancies before they freeze into the new platform.

Rebuilding the Loyalty Schema on a New Platform

Magento and WooCommerce each handle store credit very differently. Magento Commerce ships with a native store-credit extension that supports balances, history and partial redemption out of the box, but its point and tier functionality usually requires an add-on. WooCommerce has no native store-credit feature, which means balances, expiry rules and customer-tier logic all live in third-party plugins or in custom code written by your implementation partner.

The rebuild typically begins with a mapping document: every Counterpoint balance type, every expiry rule, every promotional point pool gets translated into a corresponding field in the new system. Balances issued as prepaid gift representations need to be modelled alongside everyday store credit, because the Australian Consumer Law treats them differently from promotional points earned through spend.

Many Australian retailers pair their new ecommerce stack with a managed-services partner who handles the integration between Counterpoint and the web store, so that point-of-sale redemptions continue to update the new platform's balance in real time. If you are evaluating such partners, look for one that publishes transparent integration documentation and offers an Australian support desk. A reliable integration specialist such as the DigiSNS team can scope the data-pipeline work, build the middleware that mirrors Counterpoint balances into the new system, and stand up the reconciliation reports needed for sign-off.

Notifying Customers Under Australian Consumer Law

Once the new platform is ready to receive balances, customers must be told. Under the Australian Consumer Law, gift cards and store credit sold or issued in trade must be honoured for at least three years from the date of purchase, and any expiry date shown on the card or at the point of issue is binding on the retailer. Promotional points sit in a slightly different category, but the ACCC's guidance on misleading conduct still applies if the points were promoted as having a particular value.

A clear communication plan needs to cover several groups. Long-tenured customers with substantial balances — typically those who shop regularly at suburban stores in cities like Hobart, Canberra or Geelong — should receive a direct email showing their current balance and confirming that it will transfer. Casual customers can be reached through a banner on the new web store. Loyalty members who earned points through a specific promotion should be told whether those points will carry over, expire on the original date, or be converted into store credit at a stated rate. Vouchers originally sold at a Christmas hampers counter carry a separate disclosure obligation, because they were sold for a stated dollar value rather than earned.

Store credit and point balances also have GST implications when they are redeemed. A $50 store credit redeemed against a $75 purchase does not reduce the taxable sale by $50; the GST treatment depends on whether the original credit was issued against a taxable sale. Most accounting teams in Australia handle this through their existing point-of-sale reconciliation, but it should be confirmed with your tax adviser before the cutover.

Reconciling Balances Once the New System Is Live

The cutover itself is rarely the end of the work. For the first thirty days, every redemption on the new platform should be cross-checked against Counterpoint's records to confirm that the migrated balance is decrementing correctly. A small percentage of mismatches is normal, particularly for customers who held a balance at cutover and made a purchase within hours of the new system going live.

Build a daily report that compares the total store-credit and point liability on the new platform with the equivalent figure in Counterpoint. The two should match within a defined tolerance, often less than 0.5 percent of total liability, once the cutover settles. Investigate any customer who falls outside that tolerance immediately, before the discrepancy propagates through refunds, exchanges and EOFY reporting.

End-of-financial-year reporting in Australia (30 June) is a natural checkpoint for this work. By the time the new platform has been live for a full quarter, you should have a closed loop: balances migrated, reconciliations clean, customers informed, and liability figures that match between the new ecommerce platform and Counterpoint. From there, the loyalty programme can be enhanced on a foundation of accurate data.

Book the cutover for a Sunday evening outside of any promotional period, and run the first reconciliation report within four hours of the new platform going live.