What fitment does for an automotive listing
Compatibility is the difference between a parts listing and a product listing. With it, a buyer enters a registration or picks a vehicle and gets a straight answer; without it, they are asked to interpret a part number and most of them leave.
It also unlocks the vehicle filters on search results. A listing with no compatibility is excluded from every vehicle-narrowed search, which is how most parts buyers shop.
Sources of fitment data — and their limits
Fitment quality is a data problem before it is a listing problem. These are the realistic sources, in descending order of reliability.
| Source | Reliability | Limitation |
|---|---|---|
| Manufacturer application data | High | Format differs per brand |
| Licensed catalogue dataset | High | Licence and coverage scope |
| Client's verified existing fitment | Good | Only covers current range |
| Supplier free-text 'fits' notes | Low | Model only, no engine or years |
| Copied from other listings | Unusable | Propagates other sellers' errors |
Getting the precision right
Most wrong-fit returns come from fitment that is technically true at model level and wrong at variant level. The fields below are what separate a safe fitment record from an optimistic one.
- Make, model and submodel or trim.
- Engine code or capacity and power output, not just fuel type.
- Production year range with correct start and end.
- Body style and drive type where the part differs.
- Placement — front/rear, left/right, driven/non-driven axle.
- Notes for restrictions such as chassis number breaks or brake system variants.
Loading compatibility in bulk
Fitment is uploaded as rows attached to a SKU: one row per vehicle variant. That structure multiplies fast, so it has to be produced by rule rather than by hand and validated before it reaches the account.
Vehicles that do not exist in the marketplace's own vehicle catalogue are rejected, so source vehicle names have to be matched against that catalogue first — this is where most large fitment uploads fail.
- Normalise vehicle naming to the marketplace's vehicle catalogue.
- Deduplicate overlapping year ranges for the same variant.
- Batch uploads so an error report is readable and re-runnable.
- Keep a per-SKU record of what was applied, for return disputes.
- Re-run fitment when the range changes rather than patching listings.
Having fitment built and imported for you
CPL PRO is a done-for-you automotive eBay listing and catalogue service — not software, SaaS, an AI tool or a self-service platform. We work from client-supplied or properly licensed fitment data, build the compatibility records, and import the agreed products into your own eBay account.
Typical delivery is 3–5 working days after a 1–2 working day planning stage confirmed in writing. FTP stock feeds and price update runs are quoted as project extras.
Frequently asked questions
What is eBay parts compatibility?
It is the structured list of vehicles a part fits, attached to the listing. It powers the 'check if this fits your vehicle' panel and lets buyers filter by registration, make, model, engine and year.
Where does fitment data come from?
From the parts manufacturer's own application data, from a licensed catalogue dataset, or from the client's existing verified fitment. It should never be assembled from guesswork or scraped listings — wrong fitment causes returns and account defects.
How precise does fitment need to be?
Down to engine and production year range, not just make and model. Two cars with the same badge and different engines frequently take different discs, pads or filters, and buyers hold the listing responsible when it fits the badge but not the car.
How many compatibility rows does a catalogue produce?
A single part can fit hundreds of vehicle variants, so mid-size catalogues routinely produce hundreds of thousands of compatibility rows. This is why fitment is handled in validated batches rather than one spreadsheet.