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 |
Rebuilding Real-Time Stock Counters on Ecommerce Category PagesWhen shoppers browse an online catalogue, stock information often determines whether they click through, add an item to their basket or leave the site. A category card that says “In stock” can feel reassuring, but a live quantity such as “7 available” gives customers a clearer view of what they can buy now. Rebuilding NCR’s real-time stock level counters requires more than adding a number to a product tile. The counter must reflect inventory from the retail management system, account for sales and holds, and update without making the page slow or unreliable. It also needs sensible fallback behaviour when stock data is delayed. For Australian retailers moving away from NCR Retail Online, the task usually forms part of a wider platform transition. Magento, WooCommerce and other commerce systems can support the feature, provided the data model, application programming interface (API) and front-end display are designed together. Establish The Inventory Source Of TruthStart by deciding which system owns the available quantity. A point-of-sale platform, warehouse management system or central inventory service may hold different numbers. The category page should not calculate stock from browser-side basket data or from a manually maintained spreadsheet. A practical approach is to expose an “available to sell” value through a dedicated inventory API. This number can subtract reserved units, damaged stock, pending transfers and safety buffers from the physical quantity. For example, a shop in Fitzroy may have ten mugs on the shelf, but only eight should appear online if two are reserved for click and collect. Use a consistent product identifier across every connected platform. Stock counters fail when the ecommerce product uses a style code, the point-of-sale system uses a barcode and the warehouse feed uses a supplier SKU without a reliable mapping layer. Store the identifier, location, sellable quantity and last synchronisation time together. Design A Reliable Stock Event FlowA real-time display normally depends on events rather than repeated full catalogue imports. When a sale is completed, an order is cancelled or a return is processed, the retail system can publish an inventory event. The inventory service then updates the relevant product record and informs the storefront. Webhooks are useful for rapid notifications, while scheduled reconciliation protects against missed events. A nightly or hourly comparison can identify differences between the commerce platform and the retail system. This is especially valuable during busy periods such as Boxing Day, when large order volumes may expose small synchronisation errors. Every event should be safe to process more than once. An event ID, timestamp and product identifier allow the service to ignore duplicates and apply updates in the correct sequence. Keep an audit trail so support staff can explain why a counter changed from “12 available” to “9 available” after several online orders. Choose A Clear Category Page DisplayA category page should show stock information close to the product title, price and purchase control. Useful labels include “In stock”, “Only 3 left”, “Available for delivery” and “Check store availability”. Avoid presenting a precise count when the source is stale or when the retailer deliberately uses stock bands. Stock bands can protect operational information while still creating useful urgency. A retailer might show “10+ available”, “Limited stock” and “Out of stock” rather than an exact figure. If precise quantities are part of the brand experience, display a timestamp or freshness rule behind the scenes and use a generic message when that rule expires. The interface must work on mobile devices, where Australian shoppers often compare products while commuting or travelling between suburbs. Keep the label readable in a compact card, provide accessible text for screen readers and avoid relying on colour alone. A red badge should be accompanied by words such as “Out of stock”. Prevent Overselling Across Sales ChannelsA counter can be accurate at the moment it loads and still become outdated seconds later. Another customer may purchase the final unit through a physical shop, marketplace listing or phone order. The basket and checkout process must therefore validate availability again before payment is accepted. Use a short reservation window when a shopper begins checkout. The reservation should reduce the available-to-sell quantity, expire automatically and return the unit if payment fails. This prevents multiple shoppers from being promised the same item while avoiding permanent stock locks caused by abandoned baskets. For stores offering click and collect, inventory may need to be split by location. A product available in Newcastle should not be presented as ready for collection in Perth. Category pages can show national availability first, then provide store-level information on the product page or through a location selector. Make The Integration Fast And Fault-TolerantDo not make every category page request wait for a slow retail database. Place an inventory service or cache between the storefront and the source system. The cache can return the latest known value in milliseconds, while background workers process updates and refresh records. Set clear behaviour for outages. If the last successful update was recent, the page may show the cached value with a quiet “stock updating” state. If the data is too old, replace the quantity with “Availability checking” rather than displaying a confident but inaccurate number. Checkout must use stricter validation than browsing pages. Implementation checks
Front-end checks
Test The Counter Against Australian Retail ConditionsAustralian operations often combine a central online warehouse with suburban stores, regional outlets and pop-up locations. Test inventory rules across those fulfilment paths rather than assuming a single national quantity. A customer in Adelaide may see a delivery promise from a warehouse, while a customer in Cairns may need a different dispatch estimate. Consider local delivery cut-offs, public holidays and extended distances between states. A product can be technically in stock but unavailable for next-day delivery to Western Australia or far north Queensland. Separate stock status from fulfilment promise so “available” does not imply an identical delivery experience everywhere. Use realistic test scenarios that mirror how people shop in Australia: browsing on a phone, collecting from a local shop, ordering during a long weekend and switching between delivery and pickup. Include Australian spelling and familiar wording such as “postcode”, “click and collect” and “dispatch”, rather than importing language that feels out of place. Accessibility and content testing also matter. If product descriptions, labels or announcements need audio support, a service such as accessible text tools can help teams review how interface copy is heard. The stock counter itself should remain concise and understandable when read aloud. Protect The Migration And Customer ExperienceBecause NCR Retail Online was discontinued, rebuilding its stock display may happen alongside a move to Magento, WooCommerce or a partner-supported solution. Treat the counter as a business-critical integration, not as a small visual feature to recreate after the migration is complete. Create a mapping document before importing products. It should connect legacy SKUs, new catalogue IDs, warehouse codes, store IDs and stock policies. Run the old and new calculations in parallel for a controlled period, compare differences and investigate exceptions before switching customers to the new storefront. Customer communication also needs coordination. Explain changes to availability wording, store pickup, delivery promises and account behaviour before launch. Guidance on migration notifications can help teams plan messages without overwhelming customers with technical detail. Keep a rollback path for the inventory integration. A feature flag can disable exact counters and show a safe availability message while the underlying service is repaired. This is preferable to exposing negative quantities, impossible promises or stock values that have not changed for days. Keep The Numbers Trustworthy After LaunchLaunch monitoring should measure more than page speed. Track the percentage of products with fresh inventory, the age of the oldest update, checkout oversell attempts and differences discovered during reconciliation. These indicators show whether the counter is useful in real trading conditions. Give merchandising and support teams a way to inspect a product’s stock history. When a customer says an item appeared available but could not be purchased, staff should be able to see the event sequence, reservation status and fulfilment location without searching through raw server logs. A well-built replacement should also support catalogue growth and seasonal peaks. It must handle bulk price changes, product variants, store closures and sudden demand without requiring a redesign. For retailers selling homewares, category content such as everyday dining products can then sit alongside dependable availability information. The essential principle is simple: show customers the freshest stock information the business can verify, make uncertainty visible when systems fall behind, and validate the final quantity before accepting payment. A real-time counter earns trust when every layer—from store shelf to category card—agrees on what can genuinely be sold. |
|||
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.