Deduplicate catalogue imports using identity rather than similar names

Two similar names can describe different products, while two different names can describe the same item. Define a product-identity rule before merging imported records.

Choose the strongest available reference

Use a stable SKU or product reference where one exists, then check whether it genuinely identifies the sellable item. Do not assume a supplier code is unique across every source.

Document the role of variant references separately. A size or colour combination may need its own identity even when it belongs to one parent product.

Separate exact matches from possible matches

An exact reference match can be handled differently from a fuzzy title match. Keep uncertain pairs in a review group instead of automatically collapsing them.

Compare material, dimensions, options and source before deciding. A newer product version may look similar while needing to remain distinct.

Decide what survives a merge

Specify which record supplies the title, images, price and category. Do not simply keep whichever row appeared last in a file.

Also consider links, reviews and order references. A catalogue clean-up should not silently break the identity used by another business record.

Test reruns before a full import

Ask how the tool handles an already imported record. A second upload might update, duplicate or reject it depending on the implementation.

Use a controlled sample to establish that behaviour. Keep the import result and the mapping rather than assuming a button labelled import is idempotent.

Reconcile the outcome

Count new, updated, held and rejected records separately. A lower row count after deduplication is not proof that every merge was correct.

Keep the original export untouched and maintain a reason for manual decisions. This guide does not claim a particular import capability in oBizee.

Use the catalogue and stock library to stabilise your product structure before moving data. Good identity rules reduce repeated cleanup more effectively than increasingly aggressive title matching.

Illustrative case to check

Two rows share “Sunflower keychain,” but one is a single item and the other is a pack of five. A title-only merge would destroy a meaningful difference. Compare the selling unit and stable reference before merging. Keep a possible-match queue for ambiguous rows instead of raising the matching threshold until they disappear.