Vehicle taxonomy

Every shop gets the vehicle taxonomy free, on every plan, including during the trial. It is the cascade behind every Year → Make → Model → Submodel dropdown in the app.

What's in it#

About 65,000 vehicles

, each a unique year-make-model-submodel combination with a stable numeric ID.

Four levels only

YMMS. Not engine, not bed length, not drivetrain.

Shared and read-only

one taxonomy for all shops, refreshed on a schedule. You do not maintain a vehicle list.

Why four levels#

YMMS is the shape of the data WySync owns, and for most categories it is the right granularity — the submodel level is where trim-specific fitment usually lives.

Some categories genuinely need more dimensions: bed length for bed liners and tonneau covers, drivetrain for driveshafts, engine code for intakes and headers, cab configuration for running boards. Those are modelled inside the vendor adapter that carries them rather than by widening the core schema for everyone — and in the meantime the honest answer is a per-SKU editor note ("6.5ft bed only"). If a dimension is structural to your catalog, it is an Enterprise conversation, not a setting.

Submodel semantics#

The rule that catches people out:

A mapping with a blank submodel applies to every submodel of that year, make and model.

So 2019 Ford F-150 with no submodel covers XL, XLT, Lariat, King Ranch, Platinum, Limited and Raptor. That is usually what you want — and where it isn't (the Raptor's very different suspension and wheel geometry), map the submodels explicitly or exclude the exceptions in the editor.

Vehicle IDs#

Widgets pass a numeric vehicle_id, never the four strings. That is why a customer's saved garage stays valid, and why a link to a filtered collection keeps working when a make gets renamed upstream.

Resolve a YMMS combination to its ID through the storefront API:

GET /apps/wysync/api/ymms/resolve?year=2024&make=Ford&model=F-150&submodel=Lariat
→ { "vehicle_id": 36968, ... }

See the storefront API for the whole cascade.

Missing vehicles#

If a vehicle your customers drive isn't in the taxonomy, tell us. Additions flow from the upstream data pipeline, not from per-shop edits — which means a fix helps every shop, and means nobody can quietly invent a vehicle that doesn't exist.