Your upload "worked" — but the fitment came back rejected.
You ran a File Exchange or bulk template upload, the report said the listing processed, and then you saw it: error 21917122, "Compatibilities not valid." The item itself may even be live — but the fitment rows you spent hours building got silently dropped. No compatibility table, no Year/Make/Model filter, no "fits your vehicle" badge. From a buyer's side, the part now looks like it fits nothing.
This is one of the more confusing errors eBay returns, because it is a row-level rejection wrapped inside what looks like a successful upload. The listing record is fine. The problem is that one or more of your compatibility (fitment) lines did not match an entry in eBay's vehicle catalog, so eBay refused them rather than guess. The fix is almost never "try again" — it is correcting the specific values eBay could not resolve.
Below is what 21917122 actually means, the concrete reasons it fires, and a row-by-row way to clear it. If you want the deeper background on why eBay drops fitment without telling you, our companion guide on why eBay parts listings get no views covers how missing fitment quietly pulls a listing out of search.
Quick read
21917122 is not a formatting error in the classic sense — your CSV is parsing fine. It is a catalog-match error. eBay received your fitment rows, tried to map each one to a known vehicle in its system, and rejected the ones it could not match.
What "Compatibilities not valid" actually means.
eBay does not store your fitment as free text. Every compatibility row you submit has to resolve to a real vehicle record in eBay's catalog — its Master Vehicle List for the site you are listing on. When a row cannot be matched, eBay returns 21917122 and discards that row instead of publishing fitment it cannot verify.
Two ideas explain almost every instance of this error: exact-match resolution and action metadata. Understand those two and the error stops being mysterious.
Exact-match resolution
eBay's catalog is a controlled vocabulary. A 2014 Honda Accord EX-L is a specific record with specific Year, Make, Model, Trim, and Engine values. If your row says "Honda Accord 2014 EX L 3.5" but eBay's record reads "Honda / Accord / 2014 / EX-L / 3.5L V6," the values do not resolve and the row is rejected. eBay generally will not fuzzy-match "Chevy" to "Chevrolet," "F150" to "F-150," or "2.0 Turbo" to a fuller engine descriptor — it expects the catalog's own tokens.
Action metadata (Add / Delete)
File Exchange compatibility rows carry an action — typically an Add or Delete instruction tied to a specific listing. If that metadata is stale — for example, you reuse an old template that points a Delete at a compatibility that no longer exists, or an Add at a listing that has been ended — eBay cannot apply the instruction and reports the compatibilities as not valid. This is why a file that uploaded cleanly last month can fail today: the listing it references has changed underneath it.
Concept 01
Catalog, not free text
Fitment must point at a real record in eBay's Master Vehicle List. "Close enough" values are rejected, not auto-corrected.
Concept 02
Row-level rejection
One bad row does not fail the whole listing — it fails that row. The listing can publish with its good fitment and silently lose the rest.
The real causes, ranked by how often they bite.
Almost every 21917122 traces back to one of these. Work down the list against the rows in your file and you will usually find the culprit in the first two.
Cause 01
Non-exact YMM values
Abbreviations and spelling that do not match the catalog: "Chevy" instead of "Chevrolet," "Mercedes" instead of "Mercedes-Benz," "F150" instead of "F-150," a trim written "EX L" instead of "EX-L." Any one of these can break the match.
Cause 02
Engine / Trim mismatch
The Year, Make, and Model resolve, but the Engine or Trim string does not exist for that vehicle in eBay's catalog — e.g. a "2.0L Turbo" written in a format eBay never lists, or a trim that belongs to a different model year.
Cause 03
Stale action metadata
A reused template carries Add/Delete instructions pointing at listings or compatibilities that have since changed or ended. eBay can't apply the action and flags the compatibilities as invalid.
Cause 04
K-Type vs Master Vehicle List
Fitment exported from a European K-Type (TecDoc) source does not line up with eBay US's Master Vehicle List. The vehicle is real, but the identifier and naming scheme come from a different catalog than the one your site uses.
Cause 05
Vehicle not in the catalog
Brand-new model years, low-volume trims, and some commercial or imported vehicles may have no entry yet on your eBay site. With no record to match, the row is rejected.
Cause 06
Wrong column / header mapping
Year, Make, Model, Trim, and Engine landing in the wrong File Exchange columns — so eBay reads a trim where it expects an engine — produces values that can never resolve.
The error is not "your data is malformed." It is "your data does not match a vehicle in eBay's catalog."
The K-Type case deserves a flag because it is so easy to miss. K-Type numbers come from the European TecDoc standard and underpin a lot of imported catalog data. eBay's US site resolves fitment against its own Master Vehicle List, which follows the ACES-style Year/Make/Model/Trim/Engine model — not K-Type. If your supplier feed is K-Type-native, the vehicles are correct but expressed in the wrong vocabulary, and 21917122 is the result. Our ACES and PIES guide explains the standard eBay's catalog is built on.
How to fix it, row by row.
The goal is to make every compatibility row resolve to a real catalog vehicle, and to make sure your action metadata points at listings that actually exist. Here is the order that clears it fastest.
01
Read the report, not the upload status
- Open the File Exchange result report and find the rows flagged 21917122 — the top-level status can still say the listing processed.
- Note the exact item or SKU and the specific Year/Make/Model values on each rejected row.
- Treat each flagged row as its own problem; do not assume the whole file is wrong.
02
Normalize Make, Model, and Trim to catalog spelling
- Expand abbreviations: Chevy to Chevrolet, VW to Volkswagen, Mercedes to Mercedes-Benz.
- Match punctuation and spacing exactly: F-150, EX-L, 4Runner — the way eBay lists them.
- When unsure of the exact token, look the vehicle up in eBay's own compatibility picker on a live listing and copy its wording verbatim.
03
Verify Engine and Trim exist for that exact year
- A trim or engine can be valid for one model year and absent the next — confirm it against the specific year, not the model in general.
- Drop the Engine/Trim qualifier and test with just Year/Make/Model if you only need broad fitment; a coarser match that resolves beats a precise one that rejects.
- Watch for engine formats eBay never uses, like a raw '2.0T' where the catalog expects a fuller descriptor.
04
Rebuild action metadata from a clean template
- Stop reusing old compatibility files that carry Add/Delete instructions tied to past listings.
- Start from eBay's current File Exchange template for your category so the action and reference columns are fresh.
- If you are revising a live listing, pull its current compatibilities first, then add or delete against that real state.
05
Translate K-Type data before you upload
- If your source feed is K-Type / TecDoc, map each vehicle to its eBay Master Vehicle List equivalent before building the row.
- Do not submit raw K-Type identifiers into a US File Exchange compatibility upload — they will not resolve.
- Keep a reusable crosswalk so the same vehicles map consistently on every future file.
06
Re-upload only the corrected rows and re-check
- Submit the fixed compatibility rows, then open the new report and confirm 21917122 is gone for each one.
- Load the live listing and verify the compatibility table renders and the Year/Make/Model filter is populated.
- Spot-check one vehicle in eBay's 'fits your vehicle' lookup to confirm buyers will actually see it.
Caveat
eBay limits how many vehicles a single listing's compatibility list can hold (its published guidance has cited a ceiling in the low thousands). If a row is rejected near that ceiling, trim redundant or overlapping entries rather than chasing a catalog match that is not the real problem. Always treat eBay's published limits and catalog rules as the source of truth — they change.
The durable fix: catalog-matched fitment before upload.
Fixing 21917122 after the fact is row-by-row cleanup. The better outcome is never submitting a row that cannot resolve in the first place — because the fitment was matched to eBay's catalog vocabulary before it ever reached File Exchange.
That is the difference between guessing at vehicle strings and resolving them against a verified relationship graph. When every Year/Make/Model/Trim/Engine on a part is already aligned to a real catalog record, the upload doesn't get silently trimmed — the compatibility table renders complete, and buyers actually find the part. This is the premise behind GridX Connect's eBay fitment data and bulk auto-parts listing workflow.
Catalog-matched, not guessed
Vehicle-to-part relationships resolved to real records, so fitment rows match eBay's catalog instead of getting rejected.
Right the first time
Fitment is verified before it reaches File Exchange — fewer rows bounced back as 'compatibilities not valid.'
Coverage that resolves
Part-to-vehicle coverage broad enough that most YMM values map cleanly to a catalog entry on upload.
None of this removes your responsibility to read the report and sanity-check a live listing — eBay's catalog is the final authority, and brand-new vehicles will always lead the data. But moving the match upstream means the bulk of your 21917122 errors disappear before they happen, instead of becoming a cleanup task after every upload. For more on bulk-upload mechanics and common questions, see the FAQ.
Stop fixing fitment rejections one row at a time.
Match your fitment to eBay's catalog before you upload, so 21917122 never fires. First fifty SKUs free — no credit card.