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 | ||||||||||||||||||||||||||||||
Recreating NCR bundle pricing in MagentoNCR Retail Online connected online stores with retail inventory and business management systems, helping retailers automate operations, synchronise stock and sell across channels. The platform has since been discontinued, and NCR directed customers toward alternatives such as Magento and WooCommerce through NCR Counterpoint partners. For many Australian merchants, preserving a familiar basket presentation matters as much as preserving the ledger total. The practical task of recreating NCR’s Product Bundle Pricing with Discounted Components in Magento is to reproduce the component lines, sale prices and discount presentation while keeping the checkout total trustworthy. Australian shoppers expect prices in Australian dollars, usually with GST included, and compare offers through Catch, marketplaces and services such as Afterpay and Humm. A recreation must therefore handle local tax display, delivery options and promotion rules without a price that changes at checkout. Capture the NCR pricing behaviourA bundle should be documented as a pricing agreement before it is coded. For each parent SKU, record the child SKU, quantity, normal component price, discounted component price, discount label, bundle total and allocation method. This avoids treating an apparent saving as a vague bundle-level markdown. A typical example might contain two drink glasses normally sold at $49 each and four coasters at $10, discounted to $44.50 and $10 respectively. The customer sees two component lines totalling $129, while a promotion record explains why the two glasses carry a saving. Exact labels and calculations should be checked against NCR exports, not assumed. Build acceptance cases from real baskets: one component, multiple quantities, fixed and percentage discounts, a free component and a cancelled order. Capture item lines, tax, delivery, payment and refund views so finance, sales and warehouse teams agree on the required behaviour. Model components and catalogue dataKeep the parent as a Magento bundle product and import each component as a simple or configurable child with its own SKU, quantity, tax class and stock mapping. Add custom attributes for the source price, permitted promotional price, price-effective timestamp and bundle allocation rule rather than overwriting the regular catalogue price. Counterpoint data needs a controlled mapping layer because identifiers, tax flags and decimal precision must survive migration. A $10 component must not become $10.99 through rounding, and a zero-priced component must remain distinguishable from an unavailable one. Store the source promotion identifier and import status so finance can reconcile every line. Inventory then becomes an integration concern rather than a one-off import. The legacy explanation of inventory webhooks remains useful for the event-driven pattern, but a Magento implementation also needs authenticated requests, retries, duplicate-event handling and reservation rules. Update child availability before a parent bundle can be bought, and release reserved stock when a quote expires. Select a Magento pricing approachMagento’s native bundle type is a sound catalogue foundation, yet it is not a guaranteed match for NCR’s component-level discount display. Fixed bundle pricing and built-in savings views can represent simple kits, although complex allocations, independent child discounts and precise promotional labels may need additional logic. A hybrid usually works best: retain native bundles for selection and fulfilment, add a focused pricing extension for discounted component lines, and reserve cart price rules for promotions such as a coupon across the whole basket. All calculations must run server-side against the quote, with the same rounded values rendered in the cart, order summary, invoice and credit note. Before choosing that path, test whether the business truly requires line-level discounts. If the only goal is a lower total, a native bundle plus a cart price rule is cheaper to maintain. If customers and staff depend on the old discounted-component breakdown, a custom renderer backed by authoritative server-side pricing is the safer match. Compare the implementation optionsFour routes can recreate the shopping and accounting outcome, but they differ in control, effort and reporting accuracy.
A native bundle is appropriate when every child shares the same promotion treatment. Cart rules help with a coupon, but may not communicate the old breakdown or allocate a fixed saving exactly. The custom extension route provides stronger control, yet adds obligations around upgrades, tax rounding, refunds and regression testing. For a faithful recreation, use the custom extension only where native behaviour falls short. A hybrid of native product setup, catalogue attributes, cart rules and targeted pricing code usually contains both cost and complexity. Document which engine owns each value so shoppers, finance and ERP processes never calculate three different totals. Apply Australian tax and checkout rulesGST is 10% in Australia, and many consumer-facing prices are shown tax-inclusive. Magento commonly stores catalogue prices before tax and then applies display settings, so the extension must use the final tax-inclusive component values consistently. The sum shown for the parent must equal the sum of its displayed children plus any shipping, less discounts; otherwise shoppers will notice the mismatch immediately. Rounding needs a defined order. Apply taxes and promotions to the amount Magento actually charges, allocate a fixed bundle discount across eligible components, then place the final rounding remainder on one designated line. Test GST-inclusive invoices, refunds, gift cards, shipping charges and cancellation fees with a fixed example from each store’s tax settings. Returns also affect the component model. The former NCR guidance on a unified return policy illustrates why online and store returns need shared rules. Decide whether returning one damaged child triggers a full bundle refund, whether discounts are recalculated, and how store credit is allocated before launch. Australian Consumer Law requirements remain the baseline, regardless of the ecommerce platform. Synchronise inventory and operationsStock control must follow the components because the parent SKU usually has no physical stock of its own. A homeware set such as everyday drinkware can contain several colours or sizes, and each child needs a live quantity, safety threshold and warehouse location. Prevent overselling by checking all required children together during checkout and reserving them when the order is placed. Australian geography adds fulfilment choices that retailers must reflect carefully. A warehouse near Brisbane, Melbourne or Sydney may serve eastern capitals quickly, while regional and remote deliveries can take longer or cost more. Integrations with Australia Post, CouriersPlease and regional carriers should use the same stock deductions and order events, including an arvo cut-off for same-day dispatch. Security should cover both the storefront and its back-office connections. Give ERP, payment and carrier integrations separate credentials, rotate keys, apply least privilege and log every price or stock change. Webhook endpoints need replay protection and monitoring, while customer data should be minimised and handled under current Australian privacy obligations and PCI DSS requirements. Validate the migration and retain the core outcomeRun a parallel catalogue check before switching channels. Import parent and child SKUs into a staging Magento store, compare totals with Counterpoint, then test single and multi-component purchases through payment, cancellation, partial return and full refund paths. Reconcile discounts, GST, delivery charges, stock movements and the final ledger export rather than relying on visual cart comparisons. Make operational ownership explicit. Merchandisers should approve promotional prices, finance should approve rounding and refunds, and warehouse staff should confirm component-to-item mapping. For role administration and staff records, HR software for retailers offers a useful model for separating purchasing, merchandising and fulfilment permissions. Brief teams using plain language, including an arvo handover for daily stock checks and no surprises when a bundle is unavailable. The outcome to remember is not merely a lower Magento price. It is one authoritative calculation that displays discounted components, totals correctly under Australian tax rules, reserves the right stock and remains auditable from basket to refund. Preserve that chain of decisions, and the replacement platform can serve customers without erasing the pricing logic NCR retailers already used. |
|||||||||||||||||||||||||||||||||
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.