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 |
Replicating NCR’s Automatic Tax Class Assignment in MagentoMoving from NCR Retail Online to Magento involves more than transferring products, customers and orders. Tax behaviour must also be rebuilt so that each item receives the correct GST treatment when it is added to a cart, sold to a particular customer or shipped to an Australian address. NCR’s former platform connected ecommerce activity with retail inventory and business management processes. Its discontinuation means merchants must now reproduce important automation through Magento configuration, structured product data and, where necessary, a small customisation or a suitable extension. The central task is to map product types to Magento tax classes. A simple product, configurable product, bundle or virtual item may need a different rule depending on whether it is standard-rated, GST-free or subject to a special commercial treatment. Australian stores also need to account for local pricing expectations. Consumers in Sydney, Melbourne and other major cities commonly see shelf and online prices advertised as GST-inclusive, while the Australian Taxation Office requires tax invoices to present GST information clearly in applicable transactions. Define The Tax Outcomes Before Building RulesBegin with a catalogue review rather than immediately editing Magento settings. Export the NCR product catalogue and add columns for SKU, product type, category, tax treatment, selling price basis and any exception that sales staff currently apply manually. For most Australian retail goods, the destination tax class will be “Taxable Goods” with a 10% GST rate. A separate “GST-Free” class is useful for products that qualify under Australian rules, such as some basic food, certain medical products and specific educational items. Do not assume that every grocery or health-related product is GST-free; eligibility depends on the item and its use. Keep “Zero Tax” for genuinely out-of-scope or non-taxable situations rather than using it as a general workaround. GST-free sales and sales with no applicable tax can have different reporting implications, so the source system’s labels should be checked against accounting records and ATO guidance. Before closing the old platform, preserve the tax-related fields and historical order data. The explanation of NCR data retention is useful when deciding which exports, invoices and product attributes should remain accessible after decommissioning. Create A Small, Clear Class StructureMagento tax classes are applied through tax rules that combine a product tax class, a customer tax class and a tax rate. A practical Australian setup normally starts with three product classes: Taxable Goods, GST-Free Goods and Zero Tax or Out of Scope. Avoid creating a separate tax class for every department unless the legal treatment truly differs. “Shoes,” “homewares” and “cosmetics” can usually share the taxable class. Excessive classes make imports harder to maintain and increase the risk that a new product receives an obsolete or contradictory rate. Create the classes in Magento under Stores, Tax Rules and Product Tax Classes, then configure the Australian GST rate as 10%. Set the relevant country to Australia and define the postcode or region scope required by the business. A national retailer may use one standard rate, while a store with international sales will need additional destination rules. Customer tax classes should also reflect the operating model. Retail customers may use the standard class, while wholesale accounts can have a separate class if their invoicing and exemption process requires it. An ABN alone does not automatically make every wholesale sale GST-free, so the customer classification must be based on the actual transaction and business advice. Map Product Types To Tax ClassesReplicating NCR’s automatic tax class assignment by product type is easiest when “product type” means a controlled attribute, not a loose category name. Add a dedicated product attribute such as Values can be limited to For a straightforward catalogue, an import process can read the source value and assign the corresponding Magento product tax class. For example, a product marked Configurable products require special care. The parent product may be visible in search results, but the selected child SKU usually determines the purchasable item and price. Assigning a class only to the parent can produce inconsistent cart calculations, so each taxable simple variation should be checked independently. Bundles and grouped products need a deliberate policy. If components have different GST treatments, the tax outcome may need to be calculated at component level rather than inherited from the displayed parent. Test the result in the cart and on the invoice rather than relying solely on the product page. Choose Automation That Matches Catalogue ComplexityA small catalogue can use Magento’s native bulk attribute update or a carefully prepared CSV import. This is often safer than adding custom code when the tax mapping is stable and products change infrequently. The import should preserve SKU integrity, use controlled values and produce an error report for unmapped products. A larger retailer may need an integration service, scheduled feed or custom module. The logic should use a priority order: an approved SKU exception first, a validated product attribute second, and a default taxable class only as a monitored fallback. Silent defaults can conceal GST errors when new products arrive from a point-of-sale or enterprise resource planning system. Custom observers, plugins or import processors should be kept narrow. They can assign a product tax class when a product is created or updated, but they should not alter historical orders. Existing invoices must retain the tax calculated at the time of purchase, even if a product’s current classification later changes. For stores selling through multiple channels, maintain the mapping in one authoritative source. A spreadsheet, middleware table or product information management system can hold the rule, while Magento receives the resulting class. This avoids one department changing a class in Magento while another changes it in the inventory system. Configure Magento’s Price And Checkout BehaviourAustralian consumers generally expect the advertised retail price to include GST. In Magento, set catalog price and display settings deliberately so the product page, cart, checkout, order confirmation and invoice show consistent amounts. A mismatch between an inclusive product price and an exclusive checkout total can quickly damage trust. Review settings for catalog prices, shipping prices, shopping cart display and sales documents. If the business operates B2B and B2C channels, determine whether separate customer groups need different display conventions. A wholesale portal may show net prices, but the tax calculation and invoice still need to be accurate. Shipping deserves its own test. Freight may be taxable, GST-free or supplied under a particular carrier arrangement depending on the transaction. Configure shipping tax class separately rather than assuming the product’s class will provide the right result. Use Australian addresses from Perth, Brisbane, Adelaide and regional areas during testing. Check postcode handling, state selection, discount allocation, mixed carts and orders containing both taxable and GST-free items. A discount should reduce the taxable base correctly, and a mixed cart should display a transparent GST total. Validate Migration And Staff WorkflowsCreate a test matrix before the live switch. Include a standard taxable item, a GST-free item, a mixed cart, a configurable product, a bundle, a virtual product, a discounted order, a shipping charge and a wholesale customer account. Compare Magento results with known NCR orders and the accounting system, checking line totals, GST amounts, grand totals and invoice presentation. Test refunds and partial credit memos as well, because tax errors often appear when only the original sale path has been reviewed. Staff need to understand where the class comes from and what to do when a product is unclassified. Magento admin training can support a transition programme covering catalogue edits, import errors, order review and escalation procedures. Useful operational checks include:
Protect Product Data And Customer TrustTax automation depends on clean product data. Duplicate SKUs, inconsistent category names and free-text descriptions make it difficult to identify exceptions. Normalise attributes during migration and retain the source value in a separate field for audit purposes. Search visibility also matters when products move between platforms. Correct titles, descriptions, structured attributes and canonical URLs help customers find the right item, while accurate product metadata reduces manual corrections after launch. The guide on migration SEO data provides relevant context for protecting catalogue quality during the changeover. Do not expose internal tax codes in customer-facing copy unless they are required on a document. Shoppers need a clear price and tax explanation, not an internal classification system. At the same time, administrators and finance staff should be able to trace why a SKU was assigned to a particular class. For retailers promoting products across Instagram, email and marketplace listings, keep destination links and product information consistent. A multi-destination bio link can direct campaigns to the correct Magento storefront, but every linked landing page should display the same price and GST treatment as checkout. Maintain The Rules After LaunchTax classification is a business process rather than a one-time migration task. Assign an owner for product tax decisions, an owner for Magento implementation and an owner for accounting reconciliation. New products should pass through the same review before publication. Schedule periodic audits around catalogue changes, promotional seasons and legislative updates. Australian GST guidance can change, and a product that was previously treated as standard-rated may require review when its composition, packaging or intended use changes. A concise rule register should record the class, qualifying conditions, effective date, approving person and affected SKUs. This supports staff training and makes future platform changes less disruptive. The dependable pattern is simple: keep the legal decision in structured product data, map it to a small Magento tax-class set, test every product format and reconcile the output against accounting records. That approach recreates NCR-style automation while giving an Australian retailer a clear, auditable method for maintaining GST accuracy. |
|||
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.