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

Real-time tax calculation for NCR and Avalara at checkout

Setting up NCR’s real-time tax calculation at checkout using Avalara turns tax from a back-office estimate into a priced order attribute. For Australian shoppers, the result should feel ordinary: GST-inclusive prices, a clear tax breakdown and no delay between the cart, payment authorisation and receipt. The same discipline applies when an order is collected in Sydney, delivered in Melbourne or fulfilled through a Brisbane click-and-collect counter.

NCR Retail Online has been discontinued, so new builds cannot assume it remains a supported destination. Existing estates need an owned bridge, while migrated storefronts generally run on Magento or WooCommerce through NCR Counterpoint partners. Avalara calculates tax when the cart is confirmed; the storefront, payment gateway and retail workflow still need clearly separated responsibilities.

A dependable setup starts with Australian tax rules, accurate product codes and a documented checkout sequence. Tax becomes transaction data rather than a number typed into an order template. The key decisions cover architecture, catalogue mapping, payment controls, privacy and launch testing, so a fast response does not come at the expense of correct invoices or reliable fulfilment.

Map the commerce, platform and tax responsibilities

Begin by naming the system of record for customers, products, orders and payments. For a migrated retailer, the storefront may be Magento or WooCommerce, with NCR Counterpoint handling relevant inventory or retail processes. Avalara should calculate and return tax; it should not become the authoritative store for product descriptions, customer accounts or fulfilment status. Capture these boundaries in an integration diagram.

Multi-currency adds another boundary. The multi-currency migration guidance discusses configuration after migration, and the same principle applies to tax: Avalara needs the sale currency, exchange treatment and Australian fulfilment evidence, while the storefront owns price display. Do not convert GST twice or assume an overseas visitor receives Australian GST without checking export conditions and supporting documents.

Define the sequence as address validation, tax calculation, total display, payment authorisation, order creation and result persistence. Tie the tax quote to the cart version so a changed address, quantity or discount cannot reuse an outdated amount. Assign an owner to each step and decide whether a service timeout blocks checkout or triggers a controlled fallback; a silent zero-tax order is never an acceptable default.

Encode Australian GST and clean product data

Australian GST is a federal 10% tax on most goods, not a state retail sales tax. Australian Consumer Law requires prices to be presented clearly, and shoppers commonly expect GST-inclusive pricing. Configure Avalara to extract GST from an inclusive total rather than add another 10%. For example, a $110 GST-inclusive line contains $10 GST; it is not $121 at checkout.

Tax codes must reflect the item sold, not its broad department name. Use clean catalogue records: the kitchen utensil catalogue demonstrates the descriptions, variants and SKU fields worth reviewing before mapping. Most ordinary kitchenware is standard-rated, while food, books, medical goods and other exceptions require different treatment. Have the catalogue and tax owners approve the mapping rather than asking developers to infer codes from titles.

Create distinct mappings for mixed-rate kits, promotional discounts and occasional exempt products. Document supporting evidence such as export declarations or exemption certificates, and prevent an item-level discount from changing tax treatment unintentionally. Regular catalogue reviews should identify obsolete SKUs, duplicated records and variants that no longer match the products held in inventory.

Calculate tax before payment and preserve the receipt

At checkout, send the validated destination, line items, quantities, prices, discounts and relevant exemption evidence to Avalara. Process the response before requesting payment authorisation. Return the tax amount and treatment message to the storefront, while preserving the detailed engine reference with the order. A fast calculation is useful only if the amount can be explained on the tax invoice.

Test carts that reflect local habits: one standard-rated item, a mixed basket, a promotion, click-and-collect and freight. Australians commonly use contactless cards and mobile wallets, so tax and receipt preparation must not add another customer step after the total is agreed. For click-and-collect, confirm the store and customer treatment rules for the supplying entity before quoting tax.

Bulky products raise additional questions. The furniture product catalogue shows the flat-pack, assembled and furniture inventory for which delivery arrangements need review. A seller-arranged delivery charge can form part of the consideration for a taxable supply, while a genuinely separate service is treated differently. Record freight, installation and discount treatment in the tax specification with Australian examples.

Persist the transaction reference, taxable amount, GST amount, rate or exemption basis, currency and calculation timestamp with the order. A receipt should distinguish tax included in the displayed total from tax added at checkout, and a GST invoice should show the seller’s ABN when registered. Refunds, cancellations and price adjustments need a matching credit or adjustment path, not a manual edit that leaves Avalara and the ledger disagreeing.

Secure tax data and test failure paths

Treat the tax integration as a sensitive data flow. Send only the address and transaction data needed for calculation, encrypt it in transit, rotate API credentials and redact personal information from routine logs. Under the Privacy Act 1988 and Australian Privacy Principles, purpose limitation and data minimisation matter when customer details pass through middleware or hosted checkout components.

Authentication is not customer identity. Fraud controls may separately assess a provider such as Hunter Biometrics, but biometric verification should not be bundled into the tax request or made a condition of routine payment. Where biometric information is used for automated verification or identification, assess its higher privacy sensitivity, obtain appropriate consent and offer a non-biometric alternative where feasible.

Before launch, test addresses in all six states and two territories, tax-inclusive and exclusive prices, GST-free and exempt lines, discounts, returns, refunds, zero-value baskets and failed calls. Include registered and unregistered sellers: the $75,000 GST registration threshold affects registration duties, but it does not remove the need to classify each line correctly. Compare Avalara output with expected invoices and accounting entries.

Launch with controlled evidence and clear ownership

Start with a limited catalogue and trading period, then widen it after orders, refunds and reconciliation agree. Monitor calculation latency, error rates, mismatched totals, manual overrides and differences between Avalara, the order and the general ledger. Give the tax owner, ecommerce lead and finance control a shared exception queue with a clear audit trail.

Keep checkout tax isolated from adjacent monetisation features. An external content monetisation guide illustrates local ad insertion around content; for a retailer, the lesson is that advertising code must not intercept the cart, change prices or receive tax data. Test third-party scripts with payment and tax traffic, and keep advertising consent separate from the information needed to produce a GST invoice.

Document the tax matrix, API mapping, supported cart scenarios, outage behaviour and reconciliation schedule. Assign owners for rule changes, Avalara maintenance, catalogue codes and legislative updates under the A New Tax System (Goods and Services Tax) Act 1999. Retain the supporting records required for tax evidence, generally for five years, and review the flow whenever a store, currency or sales channel changes.

The next concrete step is to run three sandbox baskets through the checkout API with Sydney, Melbourne and Brisbane delivery addresses, covering one taxable kitchen item, one basket mixing taxable and exempt goods, and one seller-arranged delivery charge, then reconcile every Avalara total with its order and invoice.

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.