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 | ||||||||||||||||||||||||
Automating Customer Accounts After an NCR Retail Online MigrationWhen NCR Retail Online was discontinued, retailers had to move their ecommerce operations to platforms such as Magento or WooCommerce through NCR Counterpoint partners. The technical migration often receives the most attention, yet customer identity deserves equal care. If shoppers must recreate accounts manually, businesses can lose purchase history, saved addresses, loyalty connections and the trust built over years. Automated account creation provides a smoother bridge between the former store and the replacement platform. It can combine imported customer records, guest checkout data and new registrations while applying consent, security and data-quality rules. For Australian retailers, the process also needs to fit local payment habits, delivery expectations and privacy obligations across both online and physical shops. Why Account Automation Matters After CutoverA customer account is more than an email address and password. It may connect orders, returns, wish lists, loyalty points, store credit, preferred fulfilment locations and marketing permissions. During a migration, these details may sit in separate exports from the old ecommerce system, Counterpoint, a CRM and in-store point-of-sale terminals. Treating every record as a new signup creates duplicate profiles and weakens reporting. An automated process can invite existing shoppers to activate a new account without exposing old passwords or transferring insecure credentials. The customer receives a secure link, confirms their email address and sets a fresh password on the new platform. Where the data matches confidently, order history and account benefits can be linked behind the scenes. This approach is useful for retailers serving customers in Sydney, Melbourne and Brisbane, where shoppers may buy online and collect from a nearby shop. It also supports customers in regional Queensland, Western Australia or Tasmania, who may rely more heavily on delivery and need their saved address to remain accurate after the move. Design Registration Around Australian ShoppersThe registration form should ask only for information needed to operate the account. A name, email address and password may be enough at activation, while delivery details can be collected when an order is placed. Optional fields such as birthday or product preferences should have a clear purpose. Reducing unnecessary fields matters on mobile devices, especially for shoppers using a phone on a commute through Sydney or Melbourne. Australian conventions should be supported without making the form confusing. Use suburb, state or territory and postcode fields that accept local formats, and allow addresses such as “Unit 4” or “Shop 12” without forcing them into a rigid overseas template. Retailers should also account for PO Boxes and delivery destinations in remote areas where carrier rules differ from metropolitan services. Personalisation can become part of the account journey rather than a separate data-collection exercise. For example, a gift retailer might connect registration with personalised gifting options, allowing a shopper to save recipient details only when needed. The customer should understand what is being stored and be able to edit or delete it later. Build Reliable Identity And Consent FlowsThe safest migration workflow begins with a data audit. Remove obvious test accounts, standardise email addresses, identify bounced contacts and flag records with conflicting names or addresses. Matching should use several signals, such as a verified email, loyalty identifier and recent order reference. A shared surname alone is not reliable enough to merge profiles. Do not copy old passwords into the new platform. Send activation messages from the replacement system, use expiring tokens and require a password reset. Rate limits, bot protection, multi-factor authentication for sensitive actions and alerts for unusual sign-ins help defend accounts after launch. Staff accounts should use stronger permissions than ordinary customer profiles. Consent requires separate handling. An existing customer may be eligible for service communications about orders or account activation, but that does not automatically authorise every promotional message. The Australian Privacy Act and the Spam Act 2003 make it important to document why an email or SMS was sent, how marketing permission was obtained and how unsubscribing works. A streamlined checkout flow can present these choices clearly without adding unnecessary friction. Compare Automation PatternsRetailers do not need to automate every account decision at once. The right model depends on data quality, catalogue complexity, the number of stores and how closely the new platform integrates with Counterpoint. A staged approach is often safer than attempting a large, irreversible import on launch day.
Invitation-based activation usually provides the best balance for a retailer with a dependable email database. Just-in-time creation works well where many shoppers use guest checkout, while staff-assisted registration can help customers who are less comfortable with digital processes. Fully automatic imports should be reserved for clean data with strong rollback procedures. Every method needs a failure path. If an email is shared by several profiles, an address is incomplete or a loyalty number conflicts, the record should enter a review queue rather than being merged silently. Customers should still be able to place an order as guests while the identity issue is resolved. Equip Teams To Support The New ProcessAutomation changes the questions received by store staff and contact-centre teams. A customer may ask why an old password no longer works, why two purchase histories appear, or whether a new account can be used at a different branch. Clear scripts and access to account-status information prevent staff from improvising answers. Training should reflect the unified inventory model as well as customer identity. A sales assistant in Adelaide may need to locate stock held in another store, while a team member in Perth may explain a delivery or transfer timeline to a shopper ordering from interstate. Practical sales team training helps staff connect account details with fulfilment and returns rather than treating ecommerce as a separate department. Useful operating recommendations include:
Staff should never ask customers to disclose passwords or send identity documents through ordinary email. If manual verification is necessary, define an approved process, record the decision and remove temporary evidence according to the retailer’s retention policy. Measure And Refine The New JourneyThe migration should be monitored as a customer journey rather than a single technical event. Track invitation delivery, activation rate, password-reset failures, duplicate-profile volume, guest checkout use and support contacts. Segment results by device, store region and customer type to identify problems that a total average might hide. An unusually low activation rate may point to outdated email addresses, a confusing message or a domain reputation issue. A high duplicate rate may indicate that the matching rules are too strict or that shoppers are registering with a different email from the one used for past purchases. A sudden increase in abandoned checkout sessions can signal that account creation has been made mandatory at the wrong point. Australian retailers should also compare metropolitan and regional performance. A process that works smoothly on fast broadband in Melbourne may be less forgiving for customers on slower connections or mobile networks in remote areas. Delivery estimates, local pickup availability and postcode validation should be tested across every state and territory before promotional campaigns drive extra traffic. The strongest design makes account creation feel helpful rather than compulsory. Customers can activate access when it benefits them, recover securely when they forget details and continue shopping when a record needs review. Behind that simple experience, the retailer maintains clean identity links, defensible consent records and clear operational ownership. The key point to remember is that successful post-migration automation is measured by continuity: customers retain useful relationships with the retailer while the new platform gains safer, cleaner and more reliable account data. |
|||||||||||||||||||||||||||
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.