Fixing Duplicate NCR Products in WooCommerce

Moving a catalogue from NCR Retail Online or NCR Counterpoint into WooCommerce can create a messy shopfront. A product may appear twice, variations can be detached from their parent item, and stock quantities may stop matching the figures held in the retail system. These problems often become visible only after the import has finished.

Duplicate products usually come from repeated imports, inconsistent identifiers, or a mismatch between the way NCR stores an item and the way WooCommerce recognises it. Product name, SKU, barcode, variation code, and database ID can all play different roles, so matching by title alone is rarely reliable.

Australian retailers also need to watch local catalogue details. GST-inclusive prices, Australian postcodes, Australia Post delivery zones, AUD formatting, and click-and-collect stock can expose errors quickly. A duplicate product with the wrong tax setting may produce incorrect prices at checkout, while a duplicate with a separate stock record can oversell popular items.

The safest approach is to pause automatic synchronisation, preserve the original data, identify the cause, and then clean the catalogue using a consistent key. A controlled repair is much safer than deleting products at random, particularly when existing orders, images, reviews, and search rankings are attached to the records.

Identify What WooCommerce Considers a Duplicate

Start by exporting the WooCommerce product list, including product IDs, SKUs, parent IDs, variation IDs, names, slugs, stock status, and inventory quantities. Sort the file by SKU and then by product name. Exact SKU matches are strong evidence that two records represent the same item, while similar names require further checking.

A duplicate may be a complete copy, a product with the same SKU but a different ID, or a variable product imported as several simple products. For example, a shirt called “Harbour Blue” might exist once as a variable product with size variations and again as separate small, medium, and large products. Those records look related but need different treatment.

Check the public shop as well as the dashboard. Search for the item name, SKU, and product slug, then inspect category pages, internal search results, and the basket. A product appearing twice in a collection page is a visible duplicate, but two records with one hidden as a draft can still interfere with stock updates later.

Keep a copy of the original NCR export and the current WordPress database before making changes. If the store operates across Sydney, Melbourne, or regional Queensland, schedule the work outside the busiest ordering period and temporarily stop catalogue imports. A short pause is preferable to creating another batch of conflicting records.

Find the Import Rule That Created the Copies

Repeated imports are a common cause. Some migration tools create a new WooCommerce product whenever an incoming row lacks the original WordPress product ID. If the import is run twice, the second pass may create another set of products rather than updating the first set. A failed import can have the same effect if it reached the database before reporting an error.

Review the importer settings for fields such as “update existing products”, “match by SKU”, “use external ID”, and “create new items when no match exists”. The best matching field is normally a stable NCR item code or SKU that remains unchanged between exports. Product names and slugs are poor primary keys because spelling, punctuation, and marketing descriptions can change.

Variations need special attention. A variation SKU should be unique across the entire WooCommerce site, not merely within one parent product. If NCR uses a style code plus colour and size, map that complete combination into the variation SKU. Avoid importing a parent SKU into every child variation, since WooCommerce may then treat several legitimate options as the same stock item.

Images can reveal a mapping error too. If unrelated products share the same gallery, the import may have matched attachments by filename instead of product ID. A listing such as everyday drinkware example illustrates why a descriptive title is not enough to identify a unique catalogue record; the underlying item code should control the match.

Clean the Catalogue Without Losing Sales Data

After identifying the duplicates, choose one record as the keeper. Usually this is the product with the correct SKU, complete description, accurate price, usable images, and links to reviews or previous orders. Check which record has the correct parent-child relationships before removing anything. The product ID alone does not indicate which record is best.

For simple duplicates, merge useful content into the keeper, then place the unwanted product in the bin rather than permanently deleting it immediately. For variable products, move or recreate the valid variations under one parent and confirm each option in the front end. Never delete a parent product until its children, images, and stock records have been reviewed.

Existing orders generally retain a snapshot of product information, but extensions may reference the current product ID for reporting, subscriptions, bundles, or loyalty features. Check recent orders, abandoned carts, coupons, product feeds, and marketplace connections before permanent deletion. A redirect from an old product URL to the keeper can also protect search traffic and saved customer links.

Where a duplicate has already received orders, preserve its history and consider hiding it from the catalogue instead of deleting it. This can be appropriate when the record is needed for reporting or an integration still references it. The correct choice depends on the connected systems, so test the effect in a staging copy before applying it to the live store.

Reconcile Stock, Prices, and Australian Tax Settings

Once the catalogue is consolidated, compare WooCommerce quantities with the authoritative NCR or Counterpoint stock file. Include products held in shops, warehouses, lay-by allocations, damaged stock, and items reserved for click and collect. A duplicate may have split ten units into two records showing five each, making the total look correct while each sales channel sees the wrong number.

Pay close attention to products sold by pack, metre, kilogram, or individual unit. NCR may store a case quantity while WooCommerce sells one item, or the reverse. Confirm decimal quantities, backorders, low-stock thresholds, and warehouse locations before enabling synchronisation again. A retailer in Perth may also need to check that delivery promises are not being calculated from stock held on the east coast.

Prices should be reconciled in Australian dollars and checked for GST treatment. If the catalogue stores GST-inclusive prices, configure the import so WooCommerce does not add GST a second time. Test a standard item, a sale item, and a shipping charge with an Australian billing address. Compare the result against the retailer’s accounting system, including rounding at the line and order level.

Run test purchases using a New South Wales address, a Victorian postcode, and a remote or regional address. Verify tax, shipping, inventory reduction, invoice details, and confirmation emails. Local shoppers expect clear delivery estimates, and an incorrect duplicate can make an item appear available for same-day pickup when it is actually sitting in another store.

Validate the Store Before Restarting Automation

Use a staging site to run a small import containing a simple product, a variable product, a discontinued item, and an item with existing stock. Run the same file twice and confirm that the second pass updates records rather than creating new ones. This repeat-import test is one of the quickest ways to prove that the matching rule works.

Inspect the product count before and after the test, then search for repeated SKUs, repeated barcodes, identical slugs, and unexpected draft products. Review parent and variation relationships, category assignments, images, prices, stock quantities, and visibility. A CSV comparison or database report can help find records that are not obvious from the WordPress dashboard.

Re-enable the NCR connection or scheduled import gradually. Start with a limited category or a small group of products, then compare the result with the source system. Monitor stock updates, failed rows, API logs, and webhooks for at least one complete trading cycle. Keep the old export and database backup until orders and reports have been checked.

Order history deserves its own validation because migration work is broader than catalogue repair. The guidance on order migration is useful when checking invoices, customer records, and historical references alongside products. This matters for Australian GST records, returns, warranty claims, and end-of-financial-year reporting.

Duplicate product issues after importing NCR data into WooCommerce are usually symptoms of an unreliable matching process rather than a WooCommerce display fault. The durable fix is to establish one stable product key, map variations correctly, reconcile stock and GST, and test repeated imports before automation resumes.

A clean catalogue should leave one dependable record for each sellable item, with clear ownership of price, stock, images, orders, and customer-facing URLs. Preserve historical data where integrations need it, remove only confirmed duplicates, and remember that the SKU or external item code—not a similar product name—should be the source of truth.