Product Data for Spare & Wear Parts: Compatibility Without Wrong Buys
In the aftermarket one attribute outranks all others: does the part fit the vehicle? Where TecDoc and KBA numbers carry that link — and where the non-TecDoc longtail leaves it to you.
- ✓For spare and wear parts, fitment is the one critical attribute: a part fits the vehicle or it doesn't — a wrong link means a near-guaranteed return.
- ✓TecDoc (K-Type key) and KBA numbers are the backbone that links parts to vehicles for the big branded makers.
- ✓But no-name parts, accessories, tuning and small suppliers arrive outside TecDoc — Excel and PDF, often with no vehicle link.
- ✓Productbay keeps the TecDoc core structured and uses AI enrichment exactly where the standard stops: the non-TecDoc longtail.
In most retail sectors, a wrong attribute is a nuisance — a slightly off weight, a missing color. In spare and wear parts, one wrong attribute is a return. A brake disc, a timing belt, a wheel bearing: it fits the customer's vehicle, or it doesn't. There's no "close enough." That binary reality makes compatibility the single most important — and most expensive to get wrong — field in the whole catalog.
Product data for spare and wear parts revolves around one critical attribute: does the part fit the vehicle? Everything else — price, brand, image, description — matters, but nothing matters if the fitment is wrong. This is a focused sub-topic of the broader automotive and car-parts data challenge, where the vehicle-part relation, not the product record alone, is what has to be correct.
Why is compatibility the one attribute that decides everything?
The aftermarket is different from every other retail sector because the value of a part is defined by its relation to something outside itself — the vehicle. A part isn't just "a brake disc"; it's "a brake disc for these specific engine and model variants." Get that relation wrong and the consequences are immediate:
- Fitment is binary. The part physically fits or it doesn't. There's no partial credit for a diameter that's 2 mm off or a bolt pattern that's one hole short.
- A wrong link equals a return. A mismatched K-Type reference or KBA number range sends the customer a part that can't be installed — with return shipping, restocking and a lost customer attached.
- The link is fragile across variants. One model can have dozens of engine, year and equipment variants; a part may fit some and not others, and the data has to reflect exactly that.
- Customers search by their car, not by the part. If the vehicle-part link is missing or wrong, the part is effectively invisible in every fitment finder — no link, no sale.
So the job isn't only to normalize product records the way any multi-supplier catalog needs — it's to keep a correct, verifiable relation between each part and every vehicle it fits.
What does TecDoc cover — and where does it stop?
The aftermarket does have a backbone for exactly this problem: TecDoc. TecDoc is the industry data standard that links parts to vehicles through the K-Type key (and connects to KBA registration numbers on the vehicle side). For the big branded part makers, TecDoc delivers clean, structured, correctly linked records — it's genuinely the reason online parts trade works at all. But it's important to be honest about its edges:
| Data layer | What TecDoc delivers | Where it stops |
|---|---|---|
| Vehicle-part fitment | K-Type link to vehicles for listed branded parts | No link for parts not registered in TecDoc |
| Branded core makers | Clean, structured records for the big suppliers | No-name / private-label parts absent |
| Accessories & tuning | Partial, supplier-dependent | Much of the accessory longtail outside TecDoc |
| Sales content | Not the job of a technical standard | Descriptions, SEO text, benefit copy missing |
| Small / regional suppliers | Only if they publish to TecDoc | Most arrive as raw Excel or PDF |
In short: TecDoc covers the branded core and the fitment link for it extremely well. What it doesn't cover is the non-TecDoc share — no-name parts, accessories, tuning, consumables and small suppliers — plus the sales content no technical standard provides. That non-TecDoc longtail is where the manual work and the fitment risk concentrate.
How does Productbay keep fitment correct — including outside TecDoc?
The throughline is a three-step job, and for spare parts it has to protect the vehicle-part link at every stage — that's what Productbay is built for:
- Consolidate: import every source once — TecDoc export, supplier CSV, Excel, PDF datasheet, feed URL, FTP, API — and match by article number or EAN/GTIN so existing parts update and new ones are created. The TecDoc-linked core and the non-TecDoc suppliers land in one structured catalog.
- Enrich: AI parses attributes out of titles and PDF datasheets, normalizes dimensions and specs, assigns categories, writes descriptions, and attaches vehicle references where the source carries them — always with a review queue before a fitment relation publishes. This is where the non-TecDoc longtail finally becomes usable.
- Publish: two-way sync to Shopify and Shopware, ERP connections (Xentral, weclapp), and feed exports for Amazon, OTTO and Kaufland — carrying the vehicle-part link and the attributes each channel's fitment finder needs.
Crucially, Productbay starts where TecDoc ends. If TecDoc already feeds your branded core, great — Productbay complements it, keeps that structure clean, and takes over the non-TecDoc suppliers, the accessory and tuning longtail, and the sales content the standard never carried. For how technical standards map across sectors, see GDSN, ETIM and eCl@ss. Productbay is built for specialist retailers running multi-supplier, multi-channel parts catalogs — from mid-sized shops to large chains.