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

Replicating Counterpoint Reorder Alerts in WooCommerce

How to Replicate NCR Counterpoint’s Inventory Reorder Point Alerts in WooCommerce comes down to reproducing the purchasing decision behind each notification, rather than simply copying a low-stock badge. That means connecting live sellable inventory to demand, supplier lead time and a safety buffer, then presenting the result in a format store or warehouse staff can use.

NCR Retail Online has been discontinued, and Australian retailers moving to alternative storefronts need to rebuild familiar operational workflows around WooCommerce. A well-designed alert can prevent a popular product from disappearing online without creating false urgency or emergency freight.

Translating Counterpoint rules into stock decisions

Start with the business rule rather than an inherited threshold. A practical formula is reorder point = forecast daily unit demand × replenishment lead time + safety stock. Compare that value with inventory position: sellable stock on hand plus confirmed inbound units, minus units reserved, allocated or otherwise committed. When inventory position reaches the reorder point, the system should create an alert. It should not confuse that trigger with the recommended order quantity.

Demand belongs at SKU and stocking-location level. A rolling average over the previous eight to twelve weeks gives the connector a stable baseline, but promotions, seasonal demand and one-off bulk orders should be identified so they do not distort normal velocity. Variable products need rules for each variation, not just the parent product, otherwise a common size can be obscured by slow-moving colours.

Keep the reorder point, safety stock, lead time, demand window, supplier, pack size, minimum order quantity and target stock as configurable fields. Recommended order quantity is separate: calculate the gap to target stock, then adjust for supplier cartons. This lets a buyer approve an alert while a larger order remains subject to budget controls.

Connecting Counterpoint, WooCommerce and suppliers

The integration needs an explicit source of truth. Some Australian retailers keep Counterpoint for purchasing and accounting while WooCommerce becomes the storefront; others move both catalogue and stock to a new system. Whichever model applies, the connector must define who owns the on-hand figure, who owns reservations, which system records inbound purchase orders and which one triggers the alert. That prevents two valid-looking quantities from conflicting.

For a parallel example of moving away from NCR, the Magento migration guide sets out a sensible order for catalogue, customer and stock migration. The same principle applies to WooCommerce: preserve identifiers, validate the first stock balance, then move live synchronisation rather than copying a database and switching it on at once. Each SKU should retain a stable mapping so orders, adjustments and historical reports still reconcile.

Use WooCommerce webhooks for order events and a scheduled API pull for reconciliation. Counterpoint or a warehouse system can push sales, receipts and transfers into WooCommerce, while WooCommerce sends confirmed orders back. Make updates idempotent, so replaying an order or adjustment does not reduce stock twice. A nightly SKU comparison can expose missed webhooks, manual changes in the wrong system and unmapped products.

Scheduling checks and delivering actionable alerts

A dedicated connector plugin can calculate the rules every fifteen to sixty minutes, or immediately after a relevant stock event. The scheduler should be idempotent and protected by a lock, because overlapping checks can otherwise send the same alert twice. WordPress cron depends on site traffic, so a busy trading day and a quiet Sunday night may behave differently; an external scheduler provides more predictable timing for unattended stores.

Set WordPress and notification time zones carefully. Sydney and Melbourne shift with daylight saving, Brisbane remains on Brisbane time, and Perth operates on Perth time. A UTC cron job can still be correct if calculations are timezone-aware, but a display labelled “9:00 am” should mean the buyer’s local time. Include the alert timestamp and store location.

Each notification should contain enough information to order stock without opening another screen. It should identify the product and SKU, show the trigger, include current inventory position and the assumed lead time, and state the recommended quantity. If the connection to a supplier portal is not part of the workflow, the alert should link to a purchase-order draft rather than imply that an order has been placed.

After leaving NCR, retailers often rebuild campaign flows at the same time; this email marketing migration guide explains how to carry consent records and campaign activity into the new platform. Reorder notices should remain operational messages, while campaigns about sales and new products need separate consent, branding and unsubscribe controls. That separation avoids an urgent stock warning disappearing into a marketing newsletter.

Practical workflows for Australian retail teams

Australian shopping habits make shared inventory especially important. A shopper in Sydney may order for click-and-collect from a nearby store, while a customer in Brisbane may expect delivery from a warehouse or a local franchise. The online listing, physical shelf and allocated web stock must therefore agree. When a store reserves the final unit, WooCommerce should remove it from sellable availability immediately, including across channels connected to the same ledger.

A useful reorder alert should present a compact purchasing brief:

  • Product name, variant, SKU and stock location.
  • Sellable stock, reserved units, inbound stock and current inventory position.
  • Reorder point, forecast daily demand, safety stock and supplier lead time.
  • Recommended order quantity, pack size, supplier and order-by time.

Operational rules keep the notifications proportionate:

  • Trigger only when projected stock at the next delivery is at or below the reorder point.
  • Suppress repeats for a defined cooldown, but reopen the alert if a purchase order is cancelled or delayed.
  • Escalate an overdue delivery or a lead-time increase to the buyer responsible for the account.
  • Route each alert by supplier, business unit or store, rather than sending every item to one general inbox.

The market also includes independent retailers, franchise networks and businesses serving regional areas. Long-distance freight can extend a nominal two-day supply lead time, while an Adelaide order may involve a different cut-off from Melbourne. Keep those lead times visible in the calculation. Prices and margin reports should remain in Australian dollars and account for GST-inclusive pricing, but the reorder calculation should continue to use physical units; tax treatment and stock demand are separate concerns.

Testing accuracy, security and compliance

Begin with a test catalogue containing simple products, variations, partial shipments and products with no recent sales. Replay known sales and purchase orders, then compare inventory position, reorder point and alert timing with the intended Counterpoint logic. Include cancelled orders, returns, supplier backorders, demand spikes and simultaneous checkout in two stores. Record each decision so finance and buying teams can explain why an order was suggested.

Treat the connector as a privileged application. Store API credentials outside the public site, encrypt them at rest, rotate them regularly and give each integration only the permissions it needs. Validate webhook signatures, reject malformed payloads, sanitise imported fields and log changes without recording customer payment details. Backups and a rollback procedure are essential before a production stock cutover, because an incorrect quantity can affect every connected sales channel.

Teams that lack in-house connector engineering can assess external help for the migration and alert build, including WooCommerce migration support. The engagement should still have an Australian retail owner who understands supplier lead times, store allocations and the difference between a forecast warning and an approval to order. A configurable rule set and clear handover notes matter more than a hard-coded plug-in.

Australian privacy and consumer rules also belong in the design. Where the Privacy Act 1988 and Australian Privacy Principles apply, collect only necessary contact data, restrict access and explain how it is handled. Commercial email must follow the Spam Act 2003, including identification and a working unsubscribe mechanism. Under the Australian Consumer Law, stock claims and delivery promises must match actual fulfilment capacity, so an alert should not encourage an unavailable item to be presented as available.

The standard to sustain

A reliable system forms a loop: capture transactions, reconcile inventory, calculate the reorder point, notify the right buyer, record the decision and learn from stockouts or overstock. Measures such as stockout rate, emergency freight cost, supplier lead-time accuracy and false-positive alerts show whether the rules remain useful. Reviewing those measures after promotions, warehouse changes and seasonal shifts keeps the calculations tied to actual trading conditions.

The standard to remember is simple: replicate the purchasing decision, not just the notification. When WooCommerce inventory, demand and supplier timing agree, an alert gives the business a clear reason to reorder and a much better chance of keeping its products available without overcommitting cash to stock.

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.