Rebuilding NCR Retail Online Matrix Variants in WooCommerce

NCR Retail Online was built to connect ecommerce activity with retail inventory and business management processes. Since the product has been discontinued, many Australian retailers are moving their catalogues, stock rules and online ordering workflows to platforms such as WooCommerce, often with help from NCR Counterpoint partners.

One of the hardest parts of that move is recreating matrix products. A matrix usually represents one product with several selectable dimensions, such as size, colour, width, material or pack quantity. WooCommerce can support the same structure through variable products and variations, but the catalogue must be designed carefully so that product data, stock and order updates remain reliable.

Understand how matrix products map to WooCommerce

In a legacy retail system, a matrix product commonly has a parent item and a grid of combinations. A clothing item might use size and colour, while footwear might use size and width. Each sellable combination can have its own barcode, price, cost, stock quantity and supplier code.

WooCommerce uses a variable product as the parent record and individual variations beneath it. Attributes define the available choices, while each variation represents a specific combination. For example, “Blue / Medium” is a variation rather than a separate product page.

This difference matters during migration. A matrix row should not be copied as ordinary text into a product description. It needs to become a structured variation with its own SKU, inventory settings and, where appropriate, image, weight, dimensions and sale price. If the old system allowed customers to buy a combination that has no direct WooCommerce variation, the checkout process may produce incorrect stock or pricing.

WooCommerce also distinguishes between global attributes and product-specific attributes. Global attributes are useful for consistent filters across a catalogue, such as colour or size. Custom attributes can suit unusual dimensions that apply to one product range. A consistent approach makes administration easier and improves search and navigation.

Audit the source catalogue before importing

Start with a full export from NCR Retail Online and any connected retail system. Include parent product names, matrix dimensions, child SKUs, barcodes, stock locations, prices, tax settings, images, descriptions and category assignments. Do not rely on a partial web catalogue export if the retail system contains the most accurate stock records.

Look for common data problems: duplicated SKUs, blank child codes, inconsistent spelling such as “Navy” and “navy”, dimensions stored in different orders, and products where the same barcode appears on multiple combinations. Also identify discontinued lines and products that should be archived rather than published in WooCommerce.

Australian retailers should check how stock is held across locations. A business with a shop in Melbourne, a warehouse in Sydney and a pop-up site in Brisbane may need a clear rule for whether WooCommerce displays total stock, warehouse stock or stock reserved for online orders. Shipping expectations also vary between metropolitan and regional customers, so availability and dispatch information should be realistic.

It is useful to document the process in advance. These migration lessons can help identify issues involving data quality, customer accounts, order history and integrations before the production import begins.

Design attributes and variation rules

Use attributes that describe genuine buying choices. Size, colour and width are usually appropriate; internal supplier classifications, old screen labels and temporary promotion codes generally are not. Keep customer-facing names consistent, including capitalisation, spelling and measurement formats.

Each attribute should have a controlled set of terms. Decide whether Australian shoppers will see “Colour” rather than “Color”, and use familiar values such as “Black”, “White” and “Blue”. For apparel, make the sizing system explicit, especially when products mix Australian, UK, US and European sizes.

Avoid creating every possible combination automatically when some combinations cannot be sold. If a jacket comes in four colours and six sizes but only 18 combinations exist, importing all 24 may create false purchasing options. WooCommerce should contain only valid variations, with unavailable combinations removed or clearly disabled.

Variation names should be understandable in the cart and order administration screens. A consistent format such as “Colour: Black, Size: 10” is easier to reconcile than a compact code with no visible explanation. The internal SKU can retain the original retail identifier, while the customer sees plain language.

Build products with reliable identifiers

Create the parent product first, then add its attributes and variations. Each child variation should receive a unique SKU. Where the legacy SKU is stable and meaningful, preserve it to simplify stock reconciliation, reporting and support. If new SKUs are required, keep a mapping file that records the old code, new code, barcode and parent product.

Set variation-level prices when combinations differ in price. A base product price is suitable only when every option costs the same. The same principle applies to weight, dimensions and shipping classes. A heavier pack size may need a different freight rule from the standard item.

Assign images strategically. A colour variation can display its own image, while size variations may share the parent image. Compress photographs before upload and use descriptive file names and alternative text. This is especially helpful for customers browsing on mobile connections, a common habit for Australian online shoppers.

Inventory configuration deserves careful attention. Enable stock management at variation level where each combination has separate availability. Use backorders only when the business has a clear replenishment process. If stock is synchronised with Counterpoint, a connector or integration must know whether it updates the parent product, child SKU or both.

Connect WooCommerce to retail operations

A WooCommerce catalogue is only successful when orders and inventory move accurately between systems. Establish which platform is authoritative for products, prices, stock, tax and order status. A two-way integration without defined ownership can cause one system to overwrite valid changes made in the other.

Map every variation using a stable identifier, preferably SKU or barcode. Product names are poor matching keys because they can change and may be duplicated. Test the mapping with products that have multiple colours, different prices and low or zero stock.

Tax configuration should be checked against Australian requirements. Most standard retail goods are subject to GST, while some products may have different treatment. The business should confirm its WooCommerce tax settings, invoice format and reporting process with its accountant, rather than assuming the old system’s values transfer correctly.

Order failures need an operational response. A failed synchronisation can leave stock available online after a shop sale or create an order that staff cannot fulfil. Keep a queue or log of failed jobs, record the last successful sync and define who investigates errors. This contingency guidance is especially relevant during the first weeks after launch.

Test the catalogue before switching customers

Use a staging site or restricted test environment to validate the rebuilt catalogue. Select every attribute combination, add products to the cart, change quantities and complete test orders using different payment and shipping methods. Confirm that the order contains the correct variation name, SKU, price and tax treatment.

Test stock in realistic situations. Sell the same variation through the website and a retail till, then check whether the integration reduces available stock correctly. Try a zero-stock item, a partially available matrix and a product with a backorder rule. Repeat tests after product updates, because an import or plugin update can unintentionally reset variation settings.

A staged launch is safer than importing everything at once. Begin with a representative group of products, including simple items and complex matrices. Compare WooCommerce against the source system for product counts, variation counts, stock totals and prices. Keep the old exports and mapping files available until orders, returns and customer support records have stabilised.

Practical checks for a controlled migration

• Preserve a unique SKU and barcode for every sellable variation.
• Standardise attribute names, measurement systems and customer-facing terms.
• Import only valid combinations rather than every theoretical matrix cell.
• Test stock, pricing, GST, shipping and order-status synchronisation.
• Keep a documented rollback and manual order process for integration failures.

Once the catalogue is live, monitor failed syncs, overselling, missing images, abandoned carts and customer confusion around sizing or colour choices. Review variation-level sales rather than looking only at parent product totals, since popular combinations can sell out while slower options remain available.

The essential principle is to rebuild the matrix as structured retail data, not as a visual imitation of the old grid. A well-mapped WooCommerce variable product gives each combination a dependable identity, accurate stock and clear customer presentation. That foundation is what allows an Australian retailer to move away from NCR Retail Online without losing control of its catalogue or daily operations.