Mapping Tax Categories from NCR to Magento Without Losing Exemptions

Moving from NCR Retail Online to Magento involves more than transferring product names, prices and stock quantities. Tax categories often contain the commercial logic that determines whether a customer pays GST, whether an item is GST-free, and how a tax invoice is produced. If those rules are flattened during migration, an apparently successful import can create incorrect checkout totals and reporting problems.

The safest approach is to treat the NCR export as a source of tax decisions rather than a list of labels. Each category should be matched to a clear Magento tax class, customer condition or product attribute, then tested against Australian GST requirements. This is especially important for retailers selling across multiple states, combining online orders with stores, or supporting trade customers with valid exemptions.

Identify What NCR Categories Actually Mean

Start by exporting every NCR product field connected with tax, including category names, tax flags, department codes, customer groups and any store-level overrides. The value “exempt”, for example, might refer to a GST-free product, a tax-exempt customer, a wholesale account, or an old internal code that no longer reflects current treatment. Keep the original field values in a migration archive before changing them.

The discontinued NCR Retail platform was designed to connect ecommerce activity with retail operations, so tax information may have been shared with inventory or point-of-sale processes. Review how the same SKU behaved in the online shop, at a physical checkout and on printed invoices. A retailer in Melbourne may have used one rule for ordinary consumer sales and another for approved trade accounts, even when both transactions involved the same product.

Create a data dictionary that explains each legacy code in plain language. Record its intended treatment, the evidence supporting that interpretation, and the Magento destination. This prevents a developer from guessing what codes such as “GSTX”, “ZERO” or “WHOLESALE” were meant to do.

Separate GST-Free Products From Exempt Customers

Australian GST treatment requires careful distinctions. GST-free supplies generally include specified categories such as many basic food products, some health-related supplies and exports, while other goods are taxable at the standard 10% rate. “Exempt” is often used informally by businesses, but the implementation must identify whether the exemption belongs to the product, the customer, the transaction or the delivery destination.

A tax-exempt customer should not automatically make every product GST-free. A registered organisation, reseller or government-related buyer may have a special arrangement, yet the seller still needs the correct documentation and accounting treatment. Magento should therefore use separate mechanisms for product tax classes and customer groups rather than assigning every zero-tax order to a single “exempt” category.

Consider common Australian scenarios such as a customer in Brisbane buying taxable kitchenware, a business in Sydney purchasing stock for resale, or an order shipped from Perth to an overseas destination. The GST result may differ even when the catalogue item is identical. Confirm the treatment with the business’s accountant and current Australian Taxation Office guidance before encoding a rule.

Build a Mapping Matrix Before Importing

A mapping matrix gives every NCR category one defined Magento destination. Useful columns include legacy category, SKU range, product description, GST status, customer group, shipping condition, Magento tax class, invoice wording and test case. Include a reason for each mapping, rather than relying on a simple old-to-new label conversion.

For instance, taxable general merchandise can map to a standard Australian GST class, while qualifying GST-free goods map to a separate class. A legacy “no tax” value should be held for review until its meaning is established. Products such as kitchen accessories demonstrate why descriptions matter: a broad department name may contain items with different treatments, packaging or intended uses.

Use SKU-level exceptions sparingly. If an entire product family shares the same statutory treatment, a category rule is easier to maintain. If a category mixes taxable and GST-free goods, split the source data before migration. Every manual exception should have an owner and an audit note, because future catalogue updates can otherwise overwrite it.

Configure Magento for Australian Checkout Rules

In Magento, create tax zones and rates for the locations the business actually serves, then associate them with product tax classes and customer tax classes. Australia-wide consumer sales will usually need an Australian GST rate, while exports, special supplies and other exceptions require separate logic. Customer groups can support trade pricing or approved accounts, but they should not replace product classification.

Set catalogue prices and display settings deliberately. Decide whether prices are stored or shown inclusive of GST, and ensure product pages, cart totals, checkout, credit notes and invoices use the same convention. Australian shoppers generally expect a clear final price in Australian dollars, particularly on mobile purchases and click-and-collect orders from stores in Sydney, Adelaide or the Gold Coast.

Check shipping tax separately from merchandise tax. Delivery charges can be affected by the tax status of the supply and the configuration of the carrier method. A rule that works for an in-store purchase may produce a different result when an order is split between warehouse fulfilment and store collection. Test postcode-based destinations, multiple shipping methods and mixed-tax carts.

Test Exemptions With Realistic Orders

Build a test suite from actual business patterns, not just one taxable product and one tax-free product. Include a mixed basket, a refund, a partial credit memo, a guest checkout, a logged-in trade customer, an Australian export order and an order with several delivery addresses. Compare Magento’s result with the approved NCR invoice and the expected accounting entry.

Pay special attention to rounding. Unit-level and row-level calculations can produce small differences when discounts, quantities and GST are combined. Test prices that end in common Australian retail values, such as $9.95 or $24.99, and check whether the tax total remains consistent between the product page, cart, payment gateway and invoice.

Search and catalogue behaviour also deserves attention during the transition. Guidance on preserving product search is relevant because a migrated SKU that loses its searchable attributes may be assigned the wrong tax class during manual correction. Confirm that redirects, filters, product identifiers and category assignments remain intact before staff begin reviewing tax exceptions.

Preserve Evidence and Monitor the First Orders

Retain the original NCR export, the mapping matrix, Magento configuration screenshots and approval notes in a controlled project folder. Keep a version history for tax rules so that a later change can be traced to a specific decision. This is useful when an accountant reviews BAS preparation or when staff need to explain why a product moved from taxable to GST-free treatment.

After launch, compare the first weeks of Magento orders with historical sales by category and customer group. Look for unusual spikes in zero-tax transactions, missing GST on shipping, inconsistent invoice totals or a fall in tax collected without a matching change in product mix. Reconcile ecommerce orders with payment settlements and the accounting system rather than relying solely on the Magento dashboard.

Assign responsibility for ongoing maintenance. New products need a tax decision before publication, customer exemptions should have an expiry or review process, and imported catalogue updates should not overwrite Magento tax classes without validation. A monthly exception report can highlight products with blank tax attributes, conflicting rules or orders where the expected rate was not applied.

A reliable migration leaves the original meaning visible while making the new configuration easier to manage. Map each NCR value to a documented Australian GST treatment, keep customer and product exemptions separate, and test the combinations that occur in real stores and online orders. The practical safeguard is simple: no product or customer should enter Magento without a named tax class, supporting rationale and a tested invoice result.