Handling NCR Matrix size and colour variants in WooCommerce

NCR Retail Online connected web stores with retail inventory and business management systems, but the platform has been discontinued. Its NCR Counterpoint migration path led many Australian retailers toward WooCommerce, Magento or partner-hosted equivalents. The hardest records to move are often Matrix products: one base style crossed with size and colour choices to create multiple sellable versions. A direct copy can turn that relationship into dozens of unrelated listings, so the catalogue structure must be translated as carefully as the stock.

WooCommerce represents this hierarchy with a variable product. The parent holds shared content, while each variation stores its exact attribute combination, SKU, price, stock and fulfilment data. A variation such as Navy, size 10 should not inherit a generic colour label or accidentally reuse another variation’s SKU. Equally, a Matrix option with no separate price or stock should not become a variation merely because it appears in a dropdown.

Australian data adds another layer. A Matrix size code may represent an AU 10 shoe, an AU 10 dress or an internal warehouse code, while a retailer may also sell UK, US or EU labels. Sydney and Melbourne fulfilment centres can hold the same style in different colour curves, and prices need a clear AUD and GST treatment. Correct mapping at this stage prevents online orders from consuming store stock that has a different size, colour or tax treatment.

Stores still connected to NCR point-of-sale systems can use the legacy guidance on connect your new store to clarify which system owns products, stock and order status. The migration should be treated as a controlled catalogue and operations project rather than a bulk upload. Exporting, mapping, validating and reconciling a Matrix file is safer than sending it straight into a live WooCommerce site.

Map the Matrix catalogue before importing

The correct destination depends on what each Matrix record represents, not simply on how many options its title contains. Use the source structure to decide whether the WooCommerce record is a variable product, a grouped set of simple products or a parent that shares stock across its options.

Variable products suit a retail range in which colour and size alter what is physically sold. Grouped simple products make sense only when each option was already a separate catalogue entity with its own image, description and buying workflow. Keep shared copy on the parent, place variant-specific images on variations where possible, and give every sellable combination an intentional SKU.

Before generating variations, record invalid combinations explicitly. Navy might not exist in size 6, and a seasonal colour might have no remaining stock. These exclusions must be enforced in WooCommerce and the source system, not merely hidden in the storefront, or replenishment and reporting will drift apart.

Match Matrix records to WooCommerce structures

Decide which fields are genuine variation axes. Size and colour usually are, because they identify purchasable units. Fit, fabric or pack quantity also qualify when they change the SKU, barcode, price or stock. Descriptive phrases such as “new season” are normally metadata; turning every phrase in a Matrix title into an attribute creates unwieldy selectors and fragile imports.

Use custom product attributes for commercial ranges such as Colour and Size, then assign each variation one exact value from each attribute. “Any Size” and “Any Colour” are suitable parent values when every child has its own values. Keep spelling and capitalisation consistent—Black and black may look identical to shoppers but complicate filters, feed matching and automated updates.

For an Australian catalogue, keep the Matrix source code separate from the shopper-facing size. An internal code such as W10 might need to display as AU 10 or UK 9, depending on the footwear range. If the same style uses different size systems for different markets, maintain channel-specific feeds or separate products rather than mixing both labels in one variation set.

Clean attributes, SKUs and customer content

Build a master export before using WooCommerce’s CSV importer or REST API. It should contain the parent SKU, child SKU, attribute values, cost, selling price, stock, weight, dimensions, image references and barcode. Preserve the original identifiers, but validate them for uniqueness and remove duplicate rows. An import can recreate a broken hierarchy just as easily as a clean one.

Normalise case, trim spaces, standardise colour names and prevent descriptions from repeating every option in a long title. Product copy should remain readable when a shopper lands on the parent page. For substantial rewording or formatting, a separate preparation workflow using TXTify content tools can run before descriptions are placed in the master sheet.

Reconcile prices with Australian tax settings before launch. If WooCommerce prices are tax-inclusive, the imported selling price should already include the 10% GST; adding it again creates a compliance and margin problem. Also assign shipping classes using accurate packaged weight and dimensions, especially for bulky apparel or footwear, and retain EAN or UPC values for scanning.

Keep stock aligned across stores and warehouses

With NCR Retail Online discontinued, inventory automation still needs an owner. The legacy case for automated operations after NCR remains relevant to retailers that keep WooCommerce alongside a counterpoint or ERP environment. Automation should move changed stock, prices and order status reliably, rather than relying on someone to notice a spreadsheet update.

Choose a clear system of record. WooCommerce may own sales-only inventory, while a point-of-sale or ERP platform owns stock across channels. In that arrangement, send reservation, sale and cancellation events to the authoritative system and apply safety-stock buffers for each store. Define a fail-safe: if the connection drops, pause affected orders or display an explicit availability delay instead of confirming unverified stock.

Australian fulfilment often links a Sydney or Melbourne warehouse with physical shops, an online warehouse and couriers such as Australia Post. Store-specific stock pools and postcode-based rates matter because an item available in Melbourne cannot necessarily be collected from a Sydney shop. Publish realistic dispatch times for metropolitan, regional, rural and remote destinations, and prevent click-and-collect orders from consuming store stock before a transfer is confirmed.

Test the Australian customer journey and cut over

Test the full customer journey with every attribute combination, not just the default option. Select an out-of-stock colour, a size with low stock and a valid SKU; then check the basket, tax, shipping charge, discount, confirmation email and order handoff. Test barcode scanning in the warehouse and a refund in WooCommerce and the point-of-sale system to confirm both records agree.

Physical goods imported for an Australian launch also involve customs rather than only digital catalogue work. Goods valued at A$1,000 or less are generally treated as low-value consignments, with 10% GST collected on eligible sales, while customs, biosecurity and product compliance requirements can still apply. Keep commercial invoices, accurate commodity descriptions and the importer details ready for Australian Border Force, and confirm current thresholds before shipping.

Customer terms should explain sizing, delivery areas, returns and warranties in plain Australian English and comply with the Australian Consumer Law, which cannot be excluded by a store policy. Before cutover, reconcile variant counts, SKUs, stock and tax-inclusive prices between Matrix exports, WooCommerce and the counterpoint ledger; pilot a small range, then monitor failed imports and cancellation rates. The practical takeaway is to preserve the Matrix hierarchy as true WooCommerce variations, validate each sellable combination against the operational ledger, and only then release the range to customers.