Skip to content
AspirecoStart
All answers

Ecommerce

How do you merge supplier feeds into one product catalogue?

The short answer

Read what each feed actually contains, map every supplier's fields and units onto one schema, and match products on identifiers such as SKUs before anything fuzzier. What cannot be matched with confidence goes to a person rather than being guessed.

Updated

Read each feed as it is

Suppliers send different columns, units and names for the same thing. Start by inventorying what each feed really holds — not what its documentation says — and how often it changes.

Normalise into one schema

Map each supplier's fields and units onto one set of definitions, so a product has one record instead of one per supplier. On Shopflooring, our own storefront, twenty-plus supplier price lists were normalised this way.

Match on identifiers first

Exact identifiers beat fuzzy matching: 2,257 supplier photos were matched to products on exact SKU. Fuzzy matches are suggestions for a person to confirm, never automatic merges.

Keep it running

Feeds change, so ingestion is a pipeline that reruns, not a one-off import. The result on Shopflooring is a catalogue of 118,651 rows, 117,873 of them live, with search usable across all of it — and it paid off again at replatform time, when over 23,000 old URLs could redirect straight to the same product.

Asked next

What if two suppliers sell the same product under different names?

Match on identifiers where they exist — a manufacturer part number or SKU — and treat name similarity as a suggestion for a person to confirm. Merging on names alone is how two different products end up as one.

How often should supplier feeds be re-imported?

As often as each supplier changes them, which differs by supplier. The point is that the import is a repeatable pipeline rather than a one-off job, so a price change arrives without someone re-keying it.