Avoiding Duplicate SKUs When Importing NCR’s Catalog into WooCommerce

Moving a catalogue from NCR Retail Online into WooCommerce can look like a straightforward export-and-import job. In practice, product identifiers often carry years of retail history: old supplier codes, seasonal variants, archived items, and manually created records may sit beside current stock. If those values are imported without checking, WooCommerce can create duplicate products or attach stock to the wrong listing.

The risk is particularly serious for Australian retailers where online orders may draw from the same inventory as a physical shop. A customer in Parramatta, Geelong, or regional Queensland expects the website to show accurate availability, while staff need the point-of-sale system and ecommerce store to agree. A repeated SKU can undermine both stock control and fulfilment.

NCR Retail Online has been discontinued, so businesses transitioning to platforms such as WooCommerce through NCR Counterpoint partners need a careful migration process. The NCR Retail Online site can still provide useful background about the former platform, but the practical work now involves extracting, cleaning, mapping, and validating the catalogue before it reaches the new store.

A reliable migration treats each SKU as a permanent business identifier rather than a piece of display text. Product names can change, prices can be updated, and categories can be reorganised. The SKU should remain unique, consistent, and traceable from the source catalogue through WooCommerce, warehouse workflows, and the final customer order.

Audit The Source Catalogue Before Exporting

Start by creating a full inventory of the NCR catalogue, including active, discontinued, hidden, and out-of-stock products. Export the product ID, SKU, name, parent or variation relationship, barcode, supplier code, category, and stock quantity. Do not restrict the export to products currently visible online, because archived records may contain identifiers that are still assigned to new merchandise.

Sort the data by SKU and inspect repeated values. Look for differences in capitalisation, spaces, hyphens, slashes, and leading zeroes. For example, ABC-104, abc104, and ABC 104 might represent the same item, while 00127 and 127 may be different codes in a supplier’s system. Decide which rules apply before changing any value.

A useful audit also checks blank identifiers. Assigning a temporary value such as TEMP-0001 may be safer than allowing WooCommerce to receive an empty SKU, but temporary codes must be recorded and replaced with approved identifiers before the product is published. Keep the original NCR value in a separate migration column so every change remains reversible.

Define A Single SKU Policy

Create a written format for new and existing SKUs. A retailer might use a short brand prefix, product family, size code, and colour code, such as BRD-TSH-BLU-M. The exact pattern matters less than applying it consistently. Avoid putting changing information such as price, season, or warehouse location into the identifier, since those details can become obsolete.

Decide whether variations receive their own SKUs. In WooCommerce, a shirt parent product may have separate child variations for size and colour. Each sellable variation should normally carry its own unique SKU if it is stocked, picked, returned, or replenished separately. The parent product can have a separate catalogue reference or remain without a stock-tracking SKU, depending on the retailer’s operating model.

Australian businesses should also separate SKU logic from local tax and pricing data. GST-inclusive prices, Australian dollar rounding, and sale pricing belong in product fields rather than identifiers. This keeps a product’s code stable when prices change during an end-of-financial-year promotion or a Boxing Day sale.

Clean Parent Products And Variations

Duplicate records often arise when a flat NCR export loses the relationship between a parent product and its variations. A product such as a men’s polo may appear once per size and colour, with repeated descriptions and incomplete option data. Before importing, identify the common parent and convert the option values into structured attributes such as Size and Colour.

Category names can also cause confusion. Map source departments to a controlled WooCommerce taxonomy rather than allowing every spelling variation to create a new category. For example, “Menswear”, “Men’s”, and “Men” should resolve to one agreed category. A curated men’s catalogue example illustrates why product grouping and variant presentation need to be considered separately from the SKU itself.

Check that each variation has a distinct combination of attributes and a distinct identifier. Two records with the same SKU but different sizes are still a conflict if each can be purchased separately. Conversely, two records that describe the same physical item should generally be merged rather than given new codes simply to make the import pass.

Use A Staged Import And Duplicate Checks

Never load the cleaned catalogue directly into a live WooCommerce shop. First, duplicate the store or create a staging environment, then import a small sample containing simple products, variable products, discontinued items, and products with missing images. Review how the importer handles existing product IDs, SKUs, stock quantities, categories, and variations.

Before each import, run a database-level or spreadsheet-level uniqueness check. In a spreadsheet, normalise values with trimmed spaces and consistent capitalisation, then count each normalised SKU. In WooCommerce, confirm that the chosen import tool matches products by SKU or a stable source ID rather than by product name. Names such as “Classic Tee” are too easily reused.

Test unusual catalogue entries as well. A small media or entertainment retailer might have a product called “Live TV package”, while a fashion retailer may carry the same base item in several colours. A live TV product example can help illustrate why a descriptive title should never be used as the primary matching key. The SKU must identify the sellable record independently of its marketing name.

Preserve Mapping Data And Import Safely

Maintain a migration map with the original NCR product ID, original SKU, approved WooCommerce SKU, product type, variation ID, and import status. Include a reason for every changed identifier, such as “removed trailing space”, “merged duplicate”, or “assigned variation code”. This file becomes valuable when a staff member searches an old invoice or when a supplier refers to a legacy code.

Large exports and product images should be transferred through a controlled process, especially when several people or an external partner are involved. Use restricted access, encrypted storage, and expiring links rather than sending sensitive files through an open public share. Guidance on secure downloadable links is relevant when exchanging catalogue exports, image folders, or customer-related migration data.

Import products in logical batches and record the result of each batch. Stop if the number of created products is higher than expected, if variations become standalone products, or if stock is assigned to the wrong parent. Do not repeatedly re-run an uncertain import, because some tools may create another set of products instead of updating the first set.

Validate Stock, Orders, And Customer-Facing Data

After importing, search WooCommerce for every known duplicate pattern: exact SKU matches, case-only differences, whitespace differences, and matching barcodes. Check parent products and variations separately. A clean count should show one sellable record per approved SKU, with no hidden duplicate carrying stock in the background.

Place test orders for several products and confirm the SKU shown on the order, packing slip, invoice, stock adjustment, and fulfilment export. This matters for Australian shipping workflows, where an order may move from a shop in Melbourne to Australia Post, a courier network, or a local click-and-collect counter. Verify that suburb, postcode, GST, shipping zones, and stock deductions behave as expected.

Review product pages on mobile and desktop, particularly for variation-heavy items. A gifts retailer may present a couples collection such as these couples gift products, where similar titles can make two distinct items appear interchangeable. Each option should show the correct image, price, availability, and SKU behind the scenes.

Keep the old-to-new mapping after launch and restrict who can edit SKUs. New products should pass through the same naming and uniqueness rules, with a scheduled report checking for blanks, duplicates, and unexpected changes. A short reconciliation after the first week can reveal issues that a staging test missed, such as stock updates arriving from an integrated retail system at the same time as an online order.

A controlled migration turns a catalogue transfer into a traceable data project. Audit the source, establish the identifier policy, model variations correctly, test in stages, and verify the result through real orders. For the next step, export the complete NCR catalogue and run a duplicate report on its normalised SKU column before preparing any WooCommerce import.