Ingest and reconcile
Catch duplicates before they become commercial inconsistencies
Fuse compares identifiers and mapped fields, surfaces the records that describe the same product, explains the proposed match and keeps the source trail.
The situation today
What goes wrong today
The same product arrives twice under different references. It comes from two suppliers, from two historical catalogues, from an ERP and a PIM that were never aligned, from a migration, or from two brands inside the same group. Two records mean two prices, two stock figures and two descriptions, and the shop publishes whichever one it read last. The customer sees the difference before anyone internally does.
The mechanism
How it runs in Fuse
Fuse compares the fields you map: SKU, EAN or GTIN, manufacturer reference, brand, model, dimensions and technical characteristics. Duplicates surface when the same business key appears twice, or when those fields contradict each other on one record. Fuse proposes the match, shows which source contributed which value, and leaves the decision to a person in the Inbox. Once merged, the record keeps the trace of every source it came from, so the merge stays auditable.
- reference sourced from Fuse master validated
- gtin sourced from Supplier A validated
- price sourced from ERP extract validated
- colour sourced from Colour reference validated
- locales sourced from Translation step validated
Identity is the business key you map: GTIN first on variants, SKU as fallback, product family from the product code or parent SKU. Fuse does not decide that two rows are the same product because their titles or spellings look alike.
What changes
What you get
-
One record per product
One price, one availability figure and one description, whatever the source count.
-
Fewer commercial inconsistencies
The gaps that customers and marketplaces notice — price differences, contradictory stock — stop being structural.
-
A smaller active catalogue
Superseded records stop competing with the live one, so the team always works on the current version.
-
A base for the golden record
Identity resolved once, then reused by every downstream system instead of re-argued per project.
Indicators to track
How to measure it
- Duplicates detected
-
candidate pairs surfaced per import
- Duplicates merged
-
merges confirmed in the Inbox
Detected and merged are different numbers on purpose: a person confirms the merge.
- Active records
-
count before and after deduplication
- Conflicts resolved between sources
-
field-level conflicts closed per week
Next
Related use cases
-
Product golden record
Fuse reconciles ERP, PIM, supplier and team data, applies the priorities you set, and produces a traceable record every system can read.
-
Supplier onboarding
Fuse reads the file or the API, infers its structure, proposes the mapping to your model and flags blocking errors before they reach the ERP, the PIM or the shop.
Name the product that exists three times
We import the sources it arrives from and walk you through the duplicates Fuse proposes, with the identifiers behind every match.