We have been analyzing the NCR Retail Online (NRO) business and our NCR Industry Solutions Board, an internal team that helps set strategy, has decided to set the NRO product to End of Life on March 31, 2018 . The CPOnline Product was also recently announced with an end of life date of September 30th, 2017 . The End of Life terms indicate that all current customers will need to be transitioned off their respective product and the servers turned off by 9/30/17 (CPO) & 3/31/18 (NRO) . Your NCR Counterpoint business partner has been notified of this decision in advance and has started taking steps to help you transition your eCommerce solution.
Next Steps
As of today, we are encouraging all customers to reach out to your current NCR Counterpoint Partner to begin the transition to a new eCommerce platform. Your partner will be your best resource in planning and transitioning to a new eCommerce solution.
NCR has worked with several partners to create options for your new eCommerce solution. Please refer to the below chart for information about these options. Your partner can provide you with further documentation about these solutions to assist you with the decision process. You can also view a list of FAQ’s about moving from NRO to one of the below options by clicking here .
We will be discussing this transition directly with the users that attend our Synergy User Conference at the end of June. We will be offering a presentation on eCommerce and we will have representatives at the exhibit booth to handle your questions. In the meantime, please reach out to your partner to help determine your next steps.
We appreciate your business and look forward to taking this next, innovative step together.
Recommended eCommerce Solutions
| Solution | Cost | Platform | Additional Notes | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Commerce5 |
|
Magento | Most tightly integrated with Counterpoint and offers the most advanced features | ||||||||||||||||||||||||
| CP Magento |
|
Magento | Integrated with Counterpoint and offers features similar to NRO | ||||||||||||||||||||||||
| CP Shop |
|
Woo Commerce | Catalog, Inventory, and Orders are integrated with Counterpoint | ||||||||||||||||||||||||
Loyalty points migration to Magento rewardsNCR Retail Online has been discontinued, and customers have been directed towards Magento and WooCommerce through NCR Counterpoint partners. Migrating NCR Retail Online’s Loyalty Points to Points and Rewards for Magento is therefore more than moving customer records: balances, earning history, redemption rules and customer expectations need a controlled path. For Australian retailers, that path must reconcile ecommerce data with what happens in physical stores. A shopper may earn points at a till in Brisbane, redeem them on a later Melbourne order or use them during a click-and-collect purchase in Sydney. The aim is one usable balance rather than separate web and store accounts. The work also affects finance and compliance teams. Points may create significant redemption obligations and reporting judgements, while loyalty data can contain names, contact details, purchase histories and preferences. A disciplined migration keeps the ledger auditable, applies the Australian Consumer Law and Privacy Act 1988 fairly, and avoids exposing payment data to the rewards system. Compare the target architecture with careMagento, now commonly presented as Adobe Commerce, offers a rich catalogue, pricing and extension model suited to complex retail programmes. That flexibility also creates more configuration decisions. For retailers considering a lighter alternative, WooCommerce transition guidance provides a useful starting point, particularly where the loyalty programme is relatively straightforward.
Neither route transfers NCR loyalty balances automatically. Choose based on programme complexity, integration capacity and the cost of maintaining custom logic. Magento becomes the stronger candidate when points must interact with segmented pricing, multiple brands or a broader loyalty ecosystem, provided the selected extension supports the required behaviour. Inventory every point obligationBegin with a reconciliation report from NCR rather than a customer-list export. It should distinguish available points, points awaiting approval, unredeemed balances, expired credits, pending rewards and manual adjustments. Each customer needs an opening balance traceable to transactions, promotions and previous redemptions, with finance agreeing how outstanding balances are classified for reporting. Define the unit of value before importing anything. One point might equal A$1, A$0.01 or a discretionary benefit. Document minimum redemption values, maximum order discounts, expiry rules, blackout periods, exclusions and tier thresholds. These choices determine whether the Magento rules reproduce the promise customers already hold. Consider every channel that touches points. If customers can exchange rewards for event tickets, record ticketing as a separate fulfilment path with its own cancellation and refund rules. NCR’s event ticket workflows provide useful context for keeping ticket status separate from points accounting. Map customers, balances, and transactionsCustomer matching is the most likely source of silent errors. Normalise names and email addresses, agree a durable customer identifier, and decide how duplicate households, shared email addresses and migrated guests will be handled. Never create a second Magento customer merely because a source record lacks a matching field; review and merge records according to a documented policy. Use an idempotent import so a rerun cannot award points twice. A practical sequence is to import customer records, load a verified opening-balance ledger, replay eligible earning transactions only when required, then reconcile counts and totals against the NCR report. Keep the source extract and audit files unchanged so every adjustment has supporting evidence. Separate the accounting ledger from the displayed balance. The ledger should explain each debit or credit; the customer-facing balance can be calculated from it. When comparing platform options, keep customer-facing loyalty references separate from technical evaluation. This Picukis platform reference is one external starting point for that comparison, not a substitute for compatibility testing in your own Magento environment. Configure earning and redemption rules with careMagento customer groups and cart price rules are not a substitute for a points ledger. Configure the Points and Rewards for Magento extension to mirror approved commercial rules, confirm its supported Magento or Adobe Commerce version, and establish who owns future changes. Start with earning events, redemption values, customer groups and expiry dates, then test refunds, cancellations and promotions against the legacy programme. If the extension lacks the required historical ledger format, use a controlled custom importer rather than creating balances manually. Reward configuration checkpoints
Migration controls to agree
Although unrelated to retail loyalty, a Dutch explainer on slot paylines and wilds shows how another sector uses promotional language. Keep your own documentation focused on what customers earn, what they can buy and when unused points expire; test whether those statements are understood without staff interpretation. In Australian operations, test purchases in Australian dollars, including a standard-rated 10% GST invoice, discounted redemptions and refunds. Ask the finance team to confirm how loyalty discounts appear on invoices and in GST reporting rather than treating extension behaviour as accounting advice. Customer-facing terms should meet Australian Consumer Law requirements by presenting conditions clearly before redemption. Protect loyalty data and limit accessExport only the fields needed for the migration and agree retention arrangements with NCR and relevant Counterpoint partners. Apply the Australian Privacy Principles under the Privacy Act 1988, including purpose limitation, secure handling and appropriate access. Loyalty records should not become a general-purpose marketing database simply because customer data is available. Keep payment data out of the points tables wherever possible. The programme may need a token or link to a PCI DSS-compliant payment service, but it should never store sensitive card authentication data. Encrypt transfers and backups, use role-based permissions, log administrative changes, and separate staff who approve adjustments from those processing routine redemptions. Before the live migration, review Magento extensions, hosting locations, support access and analytics tools for unnecessary exposure. Document who can see balances, why a manual adjustment was made, and how a customer can request correction or deletion where the law permits. Security controls should survive a change of platform, not end when the NCR environment is retired. Validate the launch and protect the customer relationshipRun a parallel period in a staging environment, followed by a controlled production trial with selected stores and online customer groups. Reconcile total and per-customer balances, test online earning and in-store redemption, and verify refunds, expiry jobs and customer communications. Include busy trading periods and staff handovers, since a reward queue left unresolved at close of business can create a support surge. Give store employees a short script explaining balances, expiry and exclusions, while support teams receive escalation procedures for mismatches. Preserve the NCR source report, import logs and approval records through the agreed retention period. Customers should receive clear timing, notice of any changes to legacy terms and a direct route to assistance before the old platform is switched off. The concrete next step is a two-week points-ledger audit, ending with a signed-off balance report that reconciles every NCR customer account to a proposed Magento record and identifies every rule requiring a business decision. |
|||||||||||||||||||||||||||
After you have completed your move to a new eCommerce platform, don’t forget to submit the Store Closure Request form to close your NRO site and cancel your billing subscription.