Every bad record in your catalogue was let in by someone in a hurry.
Not by accident, and not by a broken import. By a person who had a vendor going live on Friday, a submission missing thirty-one attributes, and a choice between the standard and the deadline. They chose the deadline, as anyone would.
- vendor
- Northvale Supply Co · onboarding
- sku
- NV-8841
- title
- premium quality kettle 1.7L BEST SELLER
- category
- Home
- gtin
- not supplied
- attributes
- not supplied
- images
- not supplied
- verdict
- not supplied
Category attributes required · electric kettles
- Vertical
- Multi-vendor
- Specimen
- NV-8841
- Stage
- Vendor onboarding
- Policy
- Exception granted
- Completeness
- 3 / 34
"BEST SELLER" in a title
Promotional language your own listing policy prohibits, submitted by a vendor who has never read it. It will be live by Friday because nobody has time to send it back.
A GTIN that fails its check digit
Twelve digits where there should be thirteen. It will pass a text field and fail every downstream system that tries to use it.
"Home" is not a category
It is the top of a tree. Without a leaf node, no attribute schema applies, so nothing can be required and nothing can be validated.
- vendor
- Northvale Supply Co · onboarding
- sku
- NV-8841
- title
- premium quality kettle 1.7L BEST SELLER
- category
- Home
- gtin
- not supplied
- attributes
- not supplied
- images
- not supplied
- verdict
- not supplied
Category attributes required · electric kettles
3 of 34 attributes · an invalid GTIN · a policy breach in the title · admitted because the alternative was a delay
3
Attributes the vendor supplied in their submission.
34
Attributes your own category schema requires.
Speed against standard, and the third option.
Every retailer picks one of the first two and lives with the consequence. The third is only available if enrichment happens at intake.
Onboard quickly, fix later.
The default at every retailer, because commercial pressure is real and immediate while data debt is diffuse and deferred. Vendors go live on time and the catalogue absorbs whatever they sent.
Fast — days
Good. Nobody is blocked
Whatever the vendor happened to supply
Degrades quietly as the catalogue grows
Scheduled, deprioritised, never happens
A catalogue nobody can query, built one exception at a time
Six ways a multi-vendor catalogue degrades.
The Friday exception
A vendor must be live before a promotion. The data gate is waived for one supplier, then for the next, and within a quarter the exception is the process.
Category-level dumping
Vendors submit against a top-level category because a leaf requires attributes they lack. Everything lands in a bucket where no schema applies.
Duplicate products
Three vendors submit the same manufacturer item with different titles and no valid GTIN. The catalogue now has three products that are one product.
Invalid identifiers
GTINs that fail their check digit pass a text field and break every downstream integration that assumes they are real.
Unenforced content policy
Promotional language, competitor references and unsubstantiated claims arrive from vendors who have never read your policy, and are checked by nobody at volume.
Imagery below threshold
480-pixel watermarked images accepted at onboarding, then surfaced in a grid that expects 2000. Conversion falls and it is attributed to the product.
The merchandiser granting the exception is doing their job. The vendor submitting three attributes genuinely does not hold the other thirty-one in structured form — though they almost certainly hold them in a PDF. Treating this as a discipline problem is why data quality programmes at retailers fail. It is a supply problem, and it is solvable at intake.
Run it in shadow before it blocks anything.
No retailer should put a new gate in front of vendor onboarding on trust. Run it beside the existing process and compare.
Intake baseline
We measure what your last ninety days of vendor submissions actually contained — attribute completeness by category, invalid identifiers, and how many exceptions were granted.
An export of recent vendor submissions · no integration
Gate in shadow
The enrichment gate runs alongside your existing onboarding without blocking anything, so you can compare what it would have produced against what you admitted.
Read access to the submission queue
Enrich on intake
New submissions are resolved from vendor documents at the point of onboarding. Vendors receive named gaps rather than rejection codes.
Your category attribute schemas, if they are documented
Backfill the existing catalogue
The same resolution runs against what is already listed, prioritised by traffic rather than by age.
Nothing — this is the debt that stops growing
What did you admit last quarter?
Send ninety days of vendor submissions. We will show you attribute completeness by category, how many identifiers were invalid, and — for the same submissions — what the gate would have resolved from documents those vendors already sent you.
90 days of submissions · Shadow mode · Nothing blocked · 10 working days