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

Counterpoint kit and bundle logic for ecommerce plugins

Setting Up Counterpoint’s Kit and Bundle Product Logic in a Standard Ecommerce Plugin starts with a key distinction: the ecommerce catalogue describes what customers may buy, while inventory records determine what each sale consumes. A bundle is more than a parent product with selectable options; it is a controlled relationship between sellable goods, component quantities and stock locations.

Kits commonly behave like recipes: the parent item has little or no stock, and each sale consumes defined quantities of component SKUs. Bundles may retain component identities while being priced and displayed as one offer. The plugin must reproduce the exact Counterpoint tenant rules rather than assume these labels always mean the same thing.

Since NCR Retail Online has been discontinued, retailers face a migration boundary rather than a routine feature update. Product, order and customer data must be preserved while the new commerce platform is connected to a supported Counterpoint environment. NCR Counterpoint partner implementations commonly use Magento or WooCommerce, making data portability and clean stock reconciliation central to the transition.

A dependable rollout consequently needs three foundations: a canonical product map, controlled stock movements and observable order processing. Security belongs in the same design because API credentials, pricing rules and fulfilment actions carry operational and financial consequences.

Why bundles need a deliberate data model

Build the model around what happens when an order is paid, cancelled, refunded or partially fulfilled. For each bundle definition, decide whether the parent is a stockable SKU, a virtual recipe or a sales-only grouping. Also decide whether component stock is deducted at order placement, reservation, pick or dispatch. Those answers determine behaviour during peak demand and returns.

Keep the storefront product separate from its inventory recipe. The ecommerce record should expose the offer and customer-facing price, while a bundle-component mapping identifies each Counterpoint item code, required quantity, unit of measure and tax treatment. Order lines should snapshot this relationship so later catalogue changes do not rewrite settled sales.

The NCR post-discontinuation data guide explains the sales-data implications of the closure. Historical orders still need accessible references, while new products and stock movements need an operational master. Preserve stable IDs in a migration map so a historic bundle can be understood without letting discontinued-platform fields overwrite live Counterpoint records.

Map Counterpoint products before installation

Start with a controlled extract rather than importing every historical field. Required attributes usually include parent SKU, component SKU, quantity, unit, warehouse code, active status, barcode, cost, tax category and price basis. In the plugin, create a bundle-definition record for each offer, populate its component rows and link that definition to the storefront SKU.

Resolve unit conversions before they reach checkout. A case, inner and single unit need explicit conversion rules, and each component quantity must be whole-unit friendly or rounded under an agreed policy. Import validation should reject missing parents, circular relationships, negative quantities and duplicate component lines instead of silently repairing them.

Run the mapping against representative products before bulk loading: a two-item gift set, a multi-item kit, a bundle with substitutions and a product available in several warehouses. Record which details are authoritative in Counterpoint and which the web store may edit. This prevents a second catalogue from becoming a conflicting source of truth.

Connect inventory without two sources of truth

Choose one system as the stock authority. In a typical design, Counterpoint owns component availability and the plugin executes each approved inventory command through authenticated API calls. Order creation should validate availability, reserve the required quantities, place the components against the order and record a transaction identifier.

A short comparison makes the operating trade-offs visible:

Approach Strength Main limitation Appropriate use
Native ecommerce bundles Quick to sell and simple for customers Counterpoint component and stock rules often remain outside the plugin Simple fixed bundles with limited ERP complexity
Counterpoint-aware plugin Reusable mappings, component availability and controlled inventory events Each Counterpoint tenant still needs rule validation and reconciliation Mixed catalogues and standard WooCommerce or Magento integrations
Bespoke connector Full control over pricing, allocation and exceptions Highest build, testing and maintenance cost Highly unusual workflows or several legacy systems

Order processing must be idempotent regardless of the chosen approach. A repeated webhook should not deduct the same component twice, while cancellation or refund must reverse only the quantity actually consumed. Failed events need a visible exception queue, an operator reference and a safe retry path.

Control pricing, promotions and Australian GST

Price the offer from an agreed base: the current component total, a manually approved bundle price or a promotional reduction. Apply discounts in a deterministic order and round once at the published price point. For Australian shoppers, display prices in AUD and show whether they include the 10% GST. A catalogue promotion, bundle discount and cart discount should not stack unless that behaviour is deliberate.

Tax treatment needs the same precision. Components can carry different tax categories even when the bundle is sold as one line, so the plugin needs a documented rule for mixed baskets and tax-inclusive component prices. Australian invoices should identify the supplier ABN and show GST correctly. If components are imported, distinguish the store price from customs, duties and import GST so customers are not surprised at delivery.

Protect stock across multiple warehouses

Multi-warehouse bundles need allocation rules before launch. Define whether a Sydney order uses the nearest stocked component, the warehouse with the best complete set or a customer-selected pickup location. Partial availability should not be presented as available unless every required component can be supplied together.

NCR’s multi-warehouse inventory guidance describes a practical way to assess location, transfer and stock visibility after the transition. Treat location codes as a controlled mapping rather than relying on store names, and decide how virtual warehouses, quarantined stock and reserved quantities are handled.

Local delivery realities make this material. Australia Post serviceability, Australian postcodes and state or territory rules affect bundled shipping options, while remote-area surcharges can change the final cost. Warehouses serving Melbourne, Brisbane, Perth and Adelaide may have different carrier cutoffs, so a bundle can be in stock yet not dispatchable as a complete order on the promised day.

Validate fulfilment and prepare for launch

Test the complete journey with local orders, not just product pages. Place test orders for standard Australian postcodes, a New South Wales suburb, a regional Victorian address and an eligible click-and-collect customer in Brisbane. Confirm that one component can be picked from a different location, partial fulfilment is blocked or clearly controlled, and dispatch notifications retain the bundle’s component trace.

Perishable and regulated combinations need their own scenarios. The NCR food and wine examples are useful for testing categories where freshness, age restrictions or substitutions affect fulfilment. A gift hamper must record its replacement policy, and a bottle cannot be treated as an unrestricted component merely because its parent bundle has a simple SKU.

A disciplined launch checklist should cover the following areas:

  • Reconcile every parent SKU, component SKU, quantity and warehouse code against the Counterpoint source.
  • Test standard fulfilment, partial fulfilment, cancellation, return, refund and component substitution paths.
  • Snapshot bundle price, discount, tax treatment and cost at the time the order is accepted.
  • Simulate interrupted webhooks, duplicate events, unavailable components and a failed component deduction.
  • Verify allocation between warehouses, customer pickup locations, stock transfers and reserved inventory.
  • Monitor exception queues, reconciliation reports, access logs and inventory variances after each release.

Run these checks with a realistic catalogue and several concurrent test orders. A single successful checkout does not prove that reservations, refunds and partial picks remain accurate under pressure.

The operating standard worth remembering

Operational safeguards determine whether the design survives ordinary retail pressure. Use least-privilege API credentials, signed webhooks, role-based access and an audit trail for price, stock and refund changes. Keep payment-card data outside the plugin. For high-value orders, additional identity checks may be justified, provided biometric checkout options are assessed against the Privacy Act 1988, Australian Privacy Principles, explicit consent, retention limits and non-biometric alternatives.

The durable rule is simple: Counterpoint remains authoritative for component availability and consumption, the ecommerce platform owns the customer-facing offer and order record, and every transformation between them is observable and reversible. That arrangement keeps kits saleable without surrendering stock control, pricing accuracy or auditability as the catalogue grows.

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.