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 |
Preserving NCR Customer-Specific Catalog Pricing After Switching PlatformsWith NCR Retail Online discontinued, retailers and distributors are moving to replacement platforms such as Magento or WooCommerce, commonly through NCR Counterpoint partners. The software change may be straightforward; preserving the commercial value of every price is harder. A catalogue that looked simple in NCR may contain negotiated customer rates, contract dates, quantity breaks, promotional overrides and warehouse-specific rules. Those differences matter when products sell across Sydney and Melbourne, where buying teams expect account-level pricing and quick fulfilment, and when freight reaches Brisbane or Perth. A migration that displays the correct product but the wrong customer price can damage margins, trigger account disputes and expose sensitive terms to people who should not see them. The safest approach treats pricing as governed business data rather than storefront display fields. It starts with a complete rule inventory, translates each rule into the target platform, reconciles outputs and retains a rollback path. Australian tax settings, privacy obligations and import costs must be included in that design from the beginning. Build a complete pricing rule inventoryBegin with a price-to-customer matrix, not just a product export. For each active SKU, record the list price, customer-specific price, currency, effective dates, minimum quantities, promotional status, tax treatment and approving user. Include inactive contracts and recent history so future renewals do not inherit stale values. A straight SKU count can hide the harder data. Auditing current inventory helps confirm that products, stock locations and catalogue records are complete, but pricing also needs identifiers for customer accounts, customer groups, price lists and legacy contracts. In Australia, make A$ the explicit transaction currency and record whether each price includes GST. A 10% GST-inclusive trade price cannot be compared with an ex-GST rate by dividing one figure by another. Preserve the original tax basis, rounding rule and tax code, and retain billing-account information where it affects customer documentation. Translate rules into the replacement platformMagento or Adobe Commerce usually offers greater scope for complex catalogue, promotion and customer-group logic, while WooCommerce may suit a simpler catalogue but often needs a reliable price-list extension. The choice should follow the complexity of the pricing estate, not the feature count on a sales page. Adapt the criteria for replacement features to include contracts, margin controls, ERP integration and Australian tax requirements. Represent each NCR rule in a platform-neutral model before importing it. A rule such as “Customer A receives 18% off list from 1 July for 12 units or more” should become named conditions, effective dates and a defined result, with the original wording attached. Keep the NCR customer ID as a migration key; email addresses should not be the only way records are joined. Document price precedence explicitly. Decide whether contract, customer-group, quantity-break, promotional or loyalty pricing wins when two rules overlap. Verify how the selected WooCommerce extension resolves conflicts, and test tax, currency and promotion layers separately so a cart-level discount cannot overwrite a negotiated base price. Design reconciliation, staging and security controlsMake one source authoritative during cutover. For many NCR Counterpoint deployments, that means a controlled price table or master-data feed supplying the ecommerce platform, with scheduled updates and an audit trail. A one-time import is enough only if prices genuinely change once; negotiated contracts and promotional calendars usually require a repeatable update process. Use a non-production environment to compare source and target records. A practical staging option may sit behind a temporary hostname, and this Gandi hosting walkthrough shows a rapid application-deployment pattern that can be adapted for that purpose. Keep customer and pricing data encrypted, limit administrator access and test latency for teams in Sydney and Melbourne. Assess hosting location and privacy commitments against the Australian Privacy Principles rather than assuming any overseas host is suitable. Keep landed cost separate from catalogue price. Australian Customs and Border Service rules for GST, duty and low-value imported goods can affect the cost of overseas stock, but those charges should not silently change a customer’s agreed AUD price. Store freight, duty, tax treatment and margin calculations as distinct fields, then apply them through a documented pricing rule. Use a pricing continuity checklistBefore deleting NCR environments, preserve exports, field definitions, rule approvals and training material. If walkthroughs were saved as AVI files, playing legacy AVI files makes those recordings accessible during validation. Build the handover record around questions a new operator must be able to answer without access to the old system. Apply these controls before approving the migrated catalogue:
Each completed check should have supporting evidence, including query results, reconciliation reports and approval records. Assign an owner to exceptions rather than burying unresolved differences in a general migration issue list. Launch with controlled pricing validationBegin with a limited-traffic launch and compare live orders against NCR or Counterpoint records for each active customer group. Monitor gross margin, discount depth, tax calculation and the number of prices falling outside expected ranges. A price that is technically present but materially wrong still needs to be treated as a failed migration. Give account managers and customer-service teams a concise reference showing where customer prices now live, how exceptions are approved and which team can authorise corrections. Notify business customers before any change to payment terms or invoicing basis, particularly where GST-inclusive pricing forms part of an existing agreement. Retain the legacy export, rule dictionary and rollback instructions for the agreed support period. Track every price exception to closure and feed recurring pricing problems back into the rule catalogue rather than recreating manual overrides indefinitely. The practical takeaway is to treat each customer price as a governed data asset with an owner, a test case and a documented fallback, ensuring the platform changes without changing what Australian customers are entitled to pay. |
|||
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.