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 |
Serialised inventory tracking for high-value items in WooCommerceRecreating NCR’s serialized inventory tracking for high-value items in WooCommerce is primarily an inventory-data problem, not a cosmetic product-page feature. Each valuable unit needs an identity, location and status that stay aligned with its order, while the catalogue SKU continues to represent the sellable product. Get that separation right, and staff can sell scarce stock without accidentally promising the same serialised item twice. Australian operations add practical complications: customers expect GST-inclusive prices in Australian dollars, deliveries span metropolitan and rural postcodes, and shoppers may choose click-and-collect from a Sydney or Melbourne store. The replacement should model stock by branch and serial number, expose only safe information to customers, and retain a defensible history from allocation to delivery. It should also integrate with WooCommerce, ERP or point-of-sale systems rather than leave valuable inventory stranded in a spreadsheet. Why NCR-style serial identity mattersA catalogue such as NCR’s kitchen cookware catalogue demonstrates why catalogue data and unit data must remain separate. A pan is described by model, size and finish, while an individually numbered premium piece also needs a one-of-one identity. Product variants can organise options such as diameter or colour, but they should not be forced to impersonate serial-number tracking. Serialisation is appropriate where loss or substitution changes value: a camera, collectible watch, signed limited edition, high-end appliance or numbered cookware set. Batch and lot numbers are better for consumables or multiple units sharing a production run. Assigning every cotton chef jacket a serial would create false precision and slow fulfilment without improving control. Each serialised unit should follow explicit lifecycle states, including available, reserved, allocated, dispatched, sold, returned, quarantined and written off. Every transition needs a timestamp, responsible user and source so that discrepancies can be investigated without relying on memory. This creates the chain of custody that NCR-style inventory management was intended to support. A practical data model for serialised stockWooCommerce can remain the customer-facing catalogue and checkout, but the unit ledger needs clear ownership. A dedicated table or carefully vetted extension should connect each serial record to the product and variation, branch, condition, acquisition value, timestamp and current status. Aggregate product stock should be derived from eligible units rather than maintained independently. The core records to retain are:
Those records only protect value when writes are coordinated. A database transaction or equivalent locking mechanism must prevent two checkout sessions from reserving the same physical unit. The controls that prevent duplicate sales are:
The source of truth must also be agreed. Counterpoint or an ERP may remain authoritative for stock, while WooCommerce maintains a synchronised view for the storefront. Whichever system leads, exceptions should create an alert instead of silently correcting themselves. Manual adjustments should be reserved for authorised staff and always include a reason. Storefront, fulfilment and security controlsThe storefront should display reliable product availability without publishing every serial number. A serial can reveal a valuable item’s identity, location or previous ownership, so customers should generally receive it only through a restricted order document, dispatch notification or post-sale account page. Limited stock may show an availability count, but the underlying unit identifiers should remain hidden from search engines and ordinary customer accounts. Fulfilment needs a controlled handoff between systems. Staff should select an eligible serial, scan or enter it against the order and trigger the relevant state change in one operation. Click-and-collect orders should add branch and identity verification, while shipped orders can record the carrier, tracking reference and despatch timestamp. Returns should reactivate a unit only after inspection, with quarantine available for damaged or suspect stock. Security also depends on disciplined integrations and access. API credentials should have the minimum permissions required, administrative actions should be protected by strong authentication, and backups should cover both WooCommerce and the serial ledger. For a specialist external review, teams can ask AyudagPlus WooCommerce specialists to assess whether the proposed extension handles reservations, multi-location stock and migration requirements rather than merely adding a serial field to the product database. Australian fulfilment and location decisionsStore availability is a hierarchy, not a single yes-or-no value. WooCommerce may know that a serial exists somewhere in Australia without knowing which customer can collect it. Postcode and state data can narrow the search, but the final allocation must use the fulfilment address selected for that order. The trade-offs outlined in geolocation API limitations matter because browser geolocation may be coarse, denied or based on a nearby network rather than the delivery location. Australian fulfilment should account for major metropolitan hubs such as Sydney, Melbourne, Brisbane and Perth, along with long-distance shipments to regional and remote areas. GST-inclusive AUD pricing should remain consistent across the catalogue, while shipping rules can still reflect distance, insurance and carrier requirements. Service copy can sound more natural by using “collection” instead of “warehouse pickup” and by giving a definite ready date; a conversational “no worries” can soften the message, but it must not replace operational detail. NCR’s chef apparel catalogue offers a useful counterexample to indiscriminate serialisation. Size and colour create ordinary product variants, whereas a rare signed or numbered garment may require an individual serial record. A standard chef jacket should use SKU-level stock and should never consume a serial-number record. This distinction keeps the ledger focused on items whose individual identity genuinely affects value. For valuable dispatches, carrier selection becomes part of the inventory control process. Australia Post tracking, signature capture, suitable insurance and tamper-evident packaging can support the handover record without exposing the serial on the exterior label. Where local collection is chosen, staff should verify the order holder and record the physical release of the unit. A controlled migration and launch planThe useful warnings in NCR migration pitfalls apply to businesses moving away from NCR Retail Online, including stores selecting Magento or WooCommerce through NCR Counterpoint partners. Catalogue migration is only part of the job: historical purchases, open orders, customer records, payment mappings and stock balances also need an identified owner and a documented destination. The data migration should proceed through repeatable stages covering extraction, cleansing, transformation, trial loading and reconciliation. Product identifiers must map cleanly to Counterpoint and WooCommerce, while serial values must be imported once without duplication. A SKU should never be reused as a serial number, and a legacy “available” quantity must not create phantom units when the physical count cannot support it. Before production, test the complete lifecycle rather than only the checkout path. A useful test set includes simultaneous reservations, an expired basket, a cancelled order, a return, a quarantined unit and a dispatch webhook received twice. Support staff also need a clear procedure for locating a serial’s current state, adjusting it and explaining any discrepancy to a customer or auditor. The immediate implementation step is to create one pilot SKU, attach three uniquely numbered units, and complete a paid order, a cancellation and a return before any production catalogue is imported. |
|||
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.