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
  • Upfront: Starts at $2500**
  • Monthly: Starts at $495.00 plus hosting
Magento Most tightly integrated with Counterpoint and offers the most advanced features
CP Magento
  • Upfront: Starts at $2,500**
  • Monthly: Starts at $200.00 including hosting
Magento Integrated with Counterpoint and offers features similar to NRO
CP Shop
  • Upfront: Starts at $999**
  • Monthly: Starts at $125.00 plus hosting
Woo Commerce Catalog, Inventory, and Orders are integrated with Counterpoint

How to rebuild NCR’s automated order fulfilment notifications for staff

When NCR Retail Online was retired, the storefront was only one part of the work left behind. Staff also depended on automatic order alerts showing what had been paid, reserved, allocated, picked, packed and dispatched. Rebuilding those notifications gives employees a dependable view of fulfilment work instead of forcing them to check several systems throughout the day.

The former platform connected ecommerce sales with retail inventory and business management tools. Its retirement did not remove the need for those links; it changed how they must be maintained. The legacy NCR Retail Online site records the discontinuation and points customers toward migration options that include Magento and WooCommerce through NCR Counterpoint partners.

A sound replacement treats every customer order as a series of dated events. The storefront, point of sale, warehouse system and accounting platform can each publish those events, while a notification service decides which employee should see them and through which channel. This event-driven design is easier to support than a collection of brittle screen-scraping scripts.

For Australian teams, the rebuild must respect local trading conditions: Australian dollars and GST, courier cut-offs in Sydney, Melbourne and Brisbane, and the service promises attached to click-and-collect. Notifications should explain exceptions in plain language, preserve a timestamp and identify who owns the next action. That context prevents a generic alert from becoming a costly guessing game.

Why the old automated alerts need replacing

The original NCR Retail Online experience connected storefront orders to store and back-office processes in one NCR-centred environment. That reduced setup work, but it also meant staff alerts could inherit assumptions about a single database, a particular user model and one release cycle. Those assumptions rarely survive a move to Magento, WooCommerce or a specialist warehouse system.

A rebuild should preserve business outcomes rather than old screens: a paid order should reach the correct fulfilment queue, stock should be reserved once, and dispatch should update the customer record without generating another internal task. Treating the notification layer as a separate service creates room to change the commerce platform again without redesigning every employee alert.

Migration can proceed in controlled stages. Start with order creation, allocation and dispatch; add returns, click-and-collect exceptions and supplier backorders after the core route is stable. This keeps the first release small enough to test against real shifts while preserving a clear path from the discontinued NCR workflow to the replacement ecosystem.

Map the notification workflow before choosing tools

Begin with a role-by-role map of the fulfilment process. Identify who monitors incoming orders, who allocates stock, who picks and packs products, who creates shipping labels and who handles customer or courier exceptions. Record the point at which each task should appear, whether it requires acknowledgement and how quickly an unfinished task should escalate.

Legacy product pages can also become an accidental data source during this work. A category such as the stemware collection should be migrated with stable SKUs, barcodes, descriptions and product images rather than copied as unstructured text. Accurate product references help staff identify the correct item when checking a physical order.

For every event, document its trigger, eligible recipients, required information and acknowledgement rule. Include the order number, customer name, store or warehouse, items, stock position, payment state, fulfilment state and timestamp. Define what happens when data is missing, a webhook arrives twice or two employees acknowledge the same exception.

Turn order events into reliable staff alerts

Use an order-management or integration layer to publish normalised events such as order.paid, stock.reserved, pick.completed, parcel.dispatched and fulfilment.exception. Storefront applications should submit these events through webhooks or an API, with a queue absorbing temporary outages. A rules engine can then route each event to the appropriate dashboard, messaging channel, email or SMS notification.

Reliability depends on more than sending a message successfully. Give each event a unique identifier, record delivery attempts and make processing idempotent so retries cannot reserve stock twice or create duplicate pick lists. Monitor queue age, failed webhooks and unacknowledged exceptions. Automated staff notifications are useful only when the underlying order data remains complete and current.

The message itself should distinguish routine progress from work that is blocked. “Order 4821 has been allocated” is informative, while “Order 4821 cannot be fulfilled because SKU 3098 is below safety stock” should identify the available quantity, required quantity and responsible role. Consistent wording reduces interpretation time during busy trading periods.

Connect inventory, payments and delivery systems

Inventory synchronisation should support real-time reservations across stores, warehouses and the ecommerce platform. When a store confirms an allocation, the available-to-sell quantity should update in the storefront immediately, while an oversell should trigger an exception rather than a confirmed pickup promise. Barcode scanning can close the loop between the physical item and the digital order record.

Payment notifications need to distinguish authorised, captured, refunded and disputed transactions. Prices and tax fields should remain clear in Australian dollars, with GST treatment stored in a consistent format for accounting reconciliation. A staff alert should not tell employees to dispatch an order until the relevant payment state has passed the business’s fraud and credit checks.

Delivery integration should account for Australia Post and StarTrack collections, courier cut-offs and collection-point handovers. Time zones matter when stores in Brisbane, Sydney and Melbourne share a support queue, especially for same-day collection or late courier collection. For imported stock, alerts may also need to flag Australian Customs clearance or biosecurity holds, because those issues can delay availability even when payment is complete.

Role-based alerts and escalation rules

Apply least-privilege access so staff see only the orders and actions relevant to their location or function. When Magento is the replacement commerce platform, the role assignments described in the guide to Magento role-based access provide a practical starting point. Store employees should not need access to other stores’ customer details, financial reports or administrator settings.

Use a small core event set so staff receive meaningful signals rather than every technical callback:

  • Order paid and awaiting stock allocation
  • Reservation failed because the SKU is below safety stock
  • Pick-and-pack task ready for collection or courier
  • Dispatch exception, failed label or customer address issue

Match the delivery channel to urgency and task ownership:

  • Store dashboard for live queues and routine acknowledgements
  • Microsoft Teams or Slack for shift-level instructions
  • SMS or phone escalation for time-critical collection or courier failures
  • Email digest for non-urgent reconciliation and overdue summaries

Every alert should carry an owner, status, timestamp and direct action. Employees should be able to acknowledge, reassign or close a task without creating a parallel email chain. If no response arrives within the agreed service level, the rules engine should escalate the notification to a supervisor and preserve the previous attempts in the audit trail.

Test, launch and measure the new workflow

Test the notification path with representative orders, including multi-store fulfilment, partial stock, damaged goods, failed payments, address corrections and courier collection failures. Staff should verify that each event reaches the correct person, contains the required order data and updates when the underlying task changes. Test duplicate webhooks and temporary system outages to confirm that retries do not produce duplicate work.

Launch beside the existing process with a limited group of stores or a single fulfilment team. Compare order timestamps, allocation speed, picking accuracy and the number of manual status checks. Keep a rollback procedure for the integration layer and document how to reconcile orders that were mid-process during the changeover. Historical NCR-era rules should be archived so teams can identify their source when investigating an old alert.

Monitor notification delivery, acknowledgement times, unresolved exceptions and the proportion of orders completed without manual intervention. Business rules, support contacts and troubleshooting steps should live in a maintained staff knowledge base. The publishing layer can be handled separately from transaction processing; providers such as QLOUDPRESS web services are one option for creating staff documentation while operational data remains protected inside the commerce and fulfilment systems.

The practical takeaway is to launch one auditable notification path for paid, allocated, packed and dispatched orders, then expand it only after store staff can see, trust and act on every exception.

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.