Commerce CensusContactRequest access

Home / Solutions / Catalog enrichment

Fill the gaps in your own catalogue

Most internal catalogues are missing identifiers, attributes or images on a meaningful share of rows. That gap blocks marketplace listing, agent feeds and every comparison you might want to run.

Your rowsInputGTIN + attributesOutputLow matches flaggedHonesty

Catalog enrichment

Match, then enrich

Bulk match maps your rows to canonical products; the product record then supplies verified identifiers, normalised attributes, taxonomy and media.

Catalog enrichment

Refusing to guess is a feature

Rows below the trust threshold come back flagged rather than filled. A confidently wrong GTIN is more expensive than an empty field.

Endpoints that do this

Where it lands in the API.

POST /v1/match

Bulk match

Send up to 10,000 of your own rows and get canonical ids back, each with a method and a confidence — including the ones we refuse to guess at.

→ reference
GET /v1/products/{id}

Product

The canonical record: identity, attributes, taxonomy, media, and every variant.

→ reference
GET /v1/categories

Taxonomy

One taxonomy across every seller, so a query does not have to know that one calls it “Audio” and another “Headphones & Earbuds”.

→ reference

Questions

Common questions.

What match rate should we expect?

It depends entirely on what you send. Rows with a valid GTIN match essentially perfectly; brand-and-title rows depend on how distinctive the title is. Every row returns its own confidence, so you never have to take an aggregate on faith.