Moving Product Variants Safely Beyond NCR Retail Online

When leaving NCR Retail Online, product variants deserve more attention than a simple export and import. A shirt in three colours, a wine glass sold in different pack sizes, or a coffee machine with several finishes may appear as one product to shoppers but consist of multiple inventory records, prices, barcodes and images behind the scenes. If those relationships are mishandled, stock levels can drift and orders may arrive with the wrong option.

The safest approach is to treat the migration as a catalogue data project. Before moving to Magento, WooCommerce or another platform supported by an NCR Counterpoint partner, establish a clean variant structure, preserve identifiers, and test the customer journey from product page to fulfilment. Australian pricing, GST, delivery zones and local product conventions should be included in that process rather than added afterwards.

Audit the catalogue before exporting

Begin with a complete inventory of products, options and stock records in NCR Retail Online. Separate genuine variations from unrelated products that merely share a name or description. For example, a 250 ml tumbler and a six-pack of 250 ml tumblers might be separate sellable items, while “blue”, “red” and “clear” may be options under one drinkware product.

Record each item’s product name, parent product, SKU, barcode, cost, retail price, tax setting, stock quantity, images, dimensions and supplier reference. Include discontinued, hidden and out-of-stock products in the audit so that old URLs and historical orders are not accidentally disconnected. A catalogue spreadsheet can expose duplicate SKUs, blank attributes and inconsistent spelling before those errors reach the new store.

The NCR Retail Online site announced the product’s discontinuation, so merchants should also identify which data will remain accessible and which must be exported through their implementation partner. Keep an untouched copy of every export, along with the date and source system, before making corrections.

Choose a variant model that matches the products

A new ecommerce platform may use different terminology from NCR Retail Online. One system may call a parent record a configurable product, while another uses a variable product with child variations. The labels matter less than the underlying structure: one shopper-facing product should connect clearly to each purchasable combination of attributes.

Use attributes for choices that define a sellable version, such as colour, size, material, capacity or pack quantity. Each combination should have its own SKU and, where applicable, barcode and inventory quantity. A wine glass available in clear and smoke finishes should have two child records if those finishes are stocked and sold independently. A description such as “available in several colours” is not enough when the warehouse needs separate stock control.

Avoid creating variants for information that does not affect the purchase or fulfilment process. Care instructions, country of origin and warranty length usually belong in product content or custom fields. Too many options can make filtering difficult, slow down imports and create confusing product pages.

Preserve identifiers and stock relationships

SKU design should be predictable before migration. A format such as MUG-350-WHT can communicate product, capacity and colour, but the exact pattern should fit existing warehouse and point-of-sale procedures. Do not reuse a SKU for a different item simply because the old product has been discontinued. Historical orders, returns and stock movements may depend on that identifier.

Barcodes require similar care. A barcode should identify one physical sellable unit, not a parent product with several different versions. If a case and an individual item have different barcodes, model them as separate products or as a properly configured pack relationship. Check that leading zeroes survive CSV exports, since spreadsheet software can remove them and leave an apparently valid but unusable number.

Inventory synchronisation also needs a deliberate mapping. Decide whether the new store receives stock from Counterpoint, a warehouse system, or another source of truth. Test purchases, refunds, cancellations and manual stock adjustments in a staging environment. A product with five blue units and two red units should produce the same quantities in the online shop, back office and physical store after each test transaction.

Adapt Australian pricing and fulfilment details

Australian customers generally expect prices to be shown in Australian dollars and, for consumer retail, to include GST where applicable. Confirm how the new platform stores tax-inclusive prices and how it displays GST on invoices, receipts and checkout pages. A migration that imports a $55 shelf price as $55 before tax can create an immediate margin and compliance problem.

Review dimensions, weights and capacities in metric units. Local shoppers may compare a 750 ml bottle, a 12-pack or a 42 cm appliance without converting measurements. If the catalogue contains imported imperial values, standardise the display while retaining accurate shipping data. Product variants should also carry the correct shipping weight when a larger pack or heavier material changes the delivery charge.

Delivery rules need an Australian postcode test matrix. Include metropolitan Sydney, Melbourne, Brisbane, Adelaide and Perth, as well as regional locations and a PO Box if your carrier supports one. Remote and rural surcharges, Tasmania, the Northern Territory and Western Australia can expose errors that remain invisible when testing only an inner-city address. Australia Post and courier services may also apply different rules to bulky or alcohol-related goods.

Rebuild product pages for clear selection

A correct database structure can still fail if shoppers cannot understand the options. Show the parent product name with concise attribute labels, such as “Colour”, “Capacity” and “Pack size”. Use consistent spelling across filters, variant selectors and search results. Australian English conventions should be applied throughout, including terms such as “colour” and “favourite” where relevant to the brand.

Give each important variant a suitable image when appearance changes between options. A shopper selecting smoke glassware should see smoke glassware, rather than the default clear image. For products sold in packs, state the number of units prominently and distinguish “one item” from “set of six”. A useful reference for organising merchandising language is this drinkware range, where product categories and use cases can inform clearer naming.

Check accessibility as part of the rebuild. Variant controls should work with a keyboard, have readable labels and remain usable on a mobile screen. Do not communicate colour through a swatch alone; include the written colour name. If a selected option is unavailable, explain whether it is temporarily out of stock, discontinued or available for back-order rather than silently allowing an incomplete order.

Test migration, redirects and ongoing operations

Run a sample migration before importing the full catalogue. Choose products with one option, several options, multiple images, sale pricing, low stock, no stock and unusual characters in the name. Compare the old and new product pages, then place test orders for every significant combination. Confirm that the chosen SKU appears in the order, invoice, fulfilment screen and stock adjustment.

Test search, filters, category pages, feeds and promotions as well. A parent product may import successfully while its children remain invisible to search engines or excluded from a Google Merchant feed. Check that variant URLs, canonical tags and redirects preserve valuable traffic. Products in food and entertaining categories, such as those represented by this food and wine collection, may have seasonal demand, so broken links during a busy period can carry a real sales cost.

Compare totals between systems after the test orders: available stock, allocated stock, revenue, GST, discounts and shipping charges. Keep a written exception log for records that need manual correction. Once the new store is live, freeze catalogue edits briefly or use a controlled change process so that updates are not made in the old and new systems at the same time.

A well-planned transition also documents who owns variant maintenance. Staff should know how to add a new colour, retire a discontinued size, update a pack quantity and correct an image without breaking the parent-child relationship. Schedule regular checks for duplicate SKUs, missing barcodes, negative stock and options with no inventory.

Product variants are the link between what shoppers select and what the business actually fulfils. Preserve that link by auditing the old catalogue, giving every sellable combination a stable identity, applying Australian tax and delivery rules, and testing real order paths before launch. The key point to remember is simple: every option that changes price, stock or fulfilment must be represented as a clear, traceable variant in the new platform.