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 | |||||||||||||||||||||||||
Setting Up Low-Stock Email Alerts After Migrating Off NCR Retail OnlineWhen NCR pulled the plug on NCR Retail Online, plenty of Australian store owners suddenly found themselves without the safety nets they'd been relying on for years. One of the quietly important ones was the email notice that pinged across the shop whenever a popular item looked like running out. Replicating that workflow on a new stack takes a little planning, but it pays for itself the first time you catch a stock gap before a weekend rush in Brisbane or a Saturday arvo trade at your Sydney flagship. The migration path most retailers now follow involves plugging into Counterpoint through accredited partners and rebuilding the storefront on either Magento or WooCommerce. That move opens up far more flexible notification logic than the legacy platform ever offered, but only if you know which settings to find and how to wire them to the right mailbox. Done well, low-stock alerts become a daily rhythm your floor staff actually look forward to reading instead of another alert they mute. Why Stock Threshold Alerts Still MatterA missed reorder has always been expensive, but in a market the size of Australia the ripple effects are larger than they look. A café in Perth that runs out of beans can usually phone a neighbour. A multi-store apparel brand stretched between Adelaide and the Gold Coast cannot. The shipping distances alone mean a two-day gap easily becomes four, which is enough to lose a customer to a competitor whose website still shows the size in stock. Beyond the obvious lost sale, there are subtler costs. A shopper who clicks through to "out of stock" on a high-margin item rarely returns the next day. Marketing spend on Google and Meta gets attributed to a dead product page. Your returns queue grows because customers panic-buy elsewhere. None of that needs to happen if your team gets a heads-up the moment inventory crosses a defined threshold for an SKU they actually care about. There is also a seasonal layer that Australian operators understand instinctively. The run-up to Christmas, Boxing Day sales in late December, and the late-January back-to-school push all create demand spikes that don't line up neatly with automated reorder cycles. Alerts that fire at the right threshold let buyers respond in hours rather than discovering the problem during a Monday morning stocktake. Picking the Right Platform for Your AlertsWooCommerce and Magento both handle inventory notifications out of the box, but the depth differs considerably. WooCommerce relies on extensions such as Stock Notify or follow-ons from developers on the WordPress plugin directory. Magento Commerce and Adobe Commerce ship native low-stock email rules that you can tune through the admin panel. If your business runs with Counterpoint as the system of record, the alert rules often live in Counterpoint itself, with the storefront just receiving the resulting event. The choice hinges less on feature lists and more on who is maintaining the stack day to day. A solo founder running a boutique label from a home office in Hobart will find WooCommerce easier to keep current. A retailer processing more than a few thousand orders a week will appreciate the heavier workflow tooling in Magento. Either way, build the integration in a controlled way before it touches real customer data — using staging environments to mimic the Counterpoint handshake is the safest path. Configuring Threshold Rules for Each ChannelOnce the new platform is live, the threshold configuration is where most teams either get this brilliantly right or embarrassingly wrong. The simplest approach sets a single low-stock number that applies to every SKU. It is fast to roll out and it works for stores with consistent product lines, such as a uniform supplier shipping to schools across Victoria and NSW. The smarter approach is per-product and per-store thresholds. A boutique item turning over once a quarter needs a lower trigger than a best-selling basic. A flagship store in Westfield Sydney will want different limits than a satellite counter in regional WA where the next restock plane only flies twice a week. Build a small rule library first — fast movers, slow movers, made-to-order items, consignment stock — then layer thresholds on top rather than trying to guess values SKU by SKU. Also consider lead time when you pick the numbers. If a supplier in Melbourne takes five business days to fulfill an order and freight to Broome adds another three, the alert cannot fire when stock hits five. It needs to fire when stock dips to whatever level lets you reorder and still arrive before you sell out. That maths is basic but it is the most common reason teams report "we get alerts but still run out." Wiring Email Delivery ProperlyAn alert nobody receives might as well not exist. Both Magento and WooCommerce depend on a sending service, and using the default PHP mail function is a recipe for messages landing in spam folders or vanishing entirely. Configure SMTP through a dedicated transactional provider such as Postmark, SendGrid, or Mailgun, and authenticate the sending domain with SPF, DKIM, and DMARC records so Australian recipients see clean headers. For retailers who want the alerts to feel like internal communication rather than a system message, set the From name to something a shop manager recognises — "Stock Watch" or "Shop Floor Alerts" works well. Bounce handling matters too: if an alert goes to a buyer who has left the business, the system should suppress that address after a couple of soft bounces rather than continuing to flag the same product every six hours. This is also the moment to decide who gets the alerts. Head office buyers, store managers, floor staff, and the ecommerce lead may all need different slices of the same data. Most platforms support recipient roles, and Counterpoint can push notifications to distribution lists rather than individuals, which keeps the list maintainable when staff change over. Keeping the Alert Templates UsefulOut-of-the-box templates tend to read like error messages: dry, repetitive, easy to ignore. Invest an hour in customising the subject line, the opening line, and the action you want the recipient to take. A subject such as "Heads up: 3 units of [SKU] left at Sydney CBD" is more likely to be opened than "Low stock alert – product 4782." Add a brief note that makes sense to your team. Some Australian retailers include the local store nickname, the buyer's initials, or a short link to the purchase order screen in Counterpoint. Embedding a personalize it touch turns a system notification into something your staff actively forward to each other when an item is genuinely at risk. Remember the content has to fit on a phone screen. Buyers are often walking the floor, scanning a barcode, or driving between locations when the alert lands. Keep the body to a SKU, a location, the current on-hand figure, and a single clear action. Anything longer and your team will start skimming it the same way they ignore push notifications from shopping apps. Testing the Workflow Before It Goes LiveSkip the test phase and you will discover your problems the hard way — usually during a public holiday weekend when nothing can be fixed quickly. Push a known low-stock state through the new platform in a controlled environment first, confirm that the email arrives at every recipient role, and confirm that reordering the item actually clears the alert once the new purchase order is logged. Test more than happy paths. What happens when stock hits zero? When a SKU is hidden from the storefront but still tracked in inventory? When the same item crosses the threshold at two stores at the same time? Each of these edge cases tends to surface in the first month after migration, and they are far easier to fix during the build than during a code freeze. Pair this with broader work on fulfilment automation so that when an alert fires, the downstream ordering process is equally robust.
The patterns that survive a busy trading quarter in Australia are simple ones: alerts go to the right people, thresholds reflect real lead times, and templates respect the fact that the reader is often on a phone in a stockroom. Keep those three at the centre of your rebuild and the rest of the configuration becomes straightforward. The migration is a chance to tidy up a process you may have been patching for years, and a well-tuned alert system is the kind of small improvement that quietly pays back every week of the year. |
||||||||||||||||||||||||||||
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.