By Maxxd · Published 21 September 2026
Two catalogues, two sets of IDs
Your website's fitment (if it's built properly) is keyed to K-Types — TecDoc's vehicle variant IDs, which is also what your reg-lookup provider returns when a customer types in a plate.
eBay Motors doesn't use K-Types. It has its own vehicle catalogue, and every vehicle in it has an ePID (eBay Product ID). When you add "parts compatibility" to a listing, you're attaching ePIDs. When a buyer sets their car in My Garage and filters results, eBay is matching ePIDs.
Both catalogues describe the same cars. They were built by different organisations, at different times, with different ideas about what counts as a distinct variant. That's the whole problem.
Where the two disagree
- Granularity. TecDoc will split a model by engine code and power output; eBay's UK catalogue often splits by engine size and trim name. One ePID can cover three K-Types. One K-Type can straddle two ePIDs.
- Naming. "Fiesta Mk7", "Fiesta VI", "Fiesta (CB1)" and "Fiesta 2008–2017" are the same car described four ways. Text matching between catalogues fails constantly.
- Date ranges. Facelift boundaries and model-year changes rarely land on the same dates in both catalogues.
- Coverage. eBay's catalogue is thinner on imports, low-volume variants and older cars. TecDoc is thinner on some grey imports and JDM models. Either way, some vehicles simply don't exist on one side.
- Change. Both catalogues are updated continuously. eBay merges, retires and corrects ePIDs. A mapping that was right last year has drifted.
The wrong fix: copying one channel into the other
The tempting shortcut is to export your eBay compatibility lists and import them to the website (or vice versa). It's quick and it's wrong. You import eBay's naming and granularity into a system that needs K-Types for reg lookup, so the website filter gets fuzzy. Or you push K-Type-derived model names to eBay, where they don't resolve to ePIDs and get silently dropped.
One channel's data structure can't be the master for the other. You need a translation layer.
The right fix: a maintained K-Type → ePID map
Keep one master fitment dataset keyed to K-Type. Build a separate mapping table — K-Type on one side, ePID(s) on the other — for every vehicle in your range. When you push compatibility to eBay, translate through the map. When eBay changes, update the map, not thousands of listings.
Building it
- List your vehicles. Every distinct K-Type in your master fitment. For a specialist seller that might be 300; for a general factor, tens of thousands.
- Pull eBay's catalogue for those makes and models. Via the eBay API (the Taxonomy and Catalog APIs expose compatibility properties and vehicle lists) or your listing tool's vehicle lookup.
- Match automatically where you safely can. Make, model, year range, engine size and fuel type give a confident match for most mainstream variants. Score each candidate; accept only high-confidence matches.
- Resolve the rest by hand. The awkward 10–20%: facelift boundaries, power variants, imports. This is skilled work and it's where most of the value is.
- Record one-to-many honestly. If one K-Type maps to two ePIDs, store both. If an ePID covers three K-Types, all three rows point to it. Don't flatten.
- Flag the unmappable. Vehicles that exist in one catalogue and not the other. You'll need to decide, per part, whether to list without compatibility or use eBay's nearest variant with a fitment note.
Maintaining it
- Re-validate the map on a schedule — quarterly for most sellers, monthly for large catalogues.
- Watch bulk-upload error reports. A sudden spike in "invalid compatibility" errors usually means eBay changed something.
- When you add a vehicle to the master, add its ePID mapping at the same time. Make it part of the process, not a clean-up job.
- Version the map. When a return comes in, you want to know what the mapping said at the time of listing.
What it fixes
With the map in place, a fitment edit happens once, in the master, and flows to the website, eBay and (via the same principle) Amazon and Google Shopping. Compatibility on eBay becomes complete rather than partial, so your listings appear for buyers filtering by vehicle. The website and eBay stop contradicting each other. And when something does come back as "doesn't fit", you can trace exactly which row was wrong — and fix it everywhere in one edit.
This is the core of our eBay compatibility service and it starts with the fitment data work. If you'd like to know how far apart your two channels currently are, the free fitment audit checks exactly that.