WySync Fitment Data add-on

The add-on switches the engine from look up a mapping to judge the specs. It costs $150/month on top of any plan, including Starter.

What you get#

65,000 vehicles

the same YMMS taxonomy every shop gets, now with dimensions attached.

Wheel spec envelopes

for each vehicle: bolt pattern, hub bore, and acceptable diameter, width and offset ranges.

1.2 million tire sizes

with the data's own factory, guaranteed and aggressive tiers.

Query-time matching

evaluated per request across search, collections, the product verdict, the fits endpoint and the fitment table.

How a wheel is judged#

For the shopper's vehicle and one product's specs, in order:

1. Bolt pattern Canonicalised on both sides, then compared exactly. A mismatch is a definite does not fit — this is the one property with no tolerance.
2. Hub bore The wheel's bore must be greater than or equal to the vehicle's hub. Larger is fine with a centring ring; smaller cannot physically seat.
3. Diameter and width Must sit inside the vehicle's envelope.
4. Offset Inside the envelope is a stock fit. Outside it but within tolerance is an aggressive fit — mountable, with the stance and the rubbing that implies.
5. Verdict Stock, aftermarket, aggressive, or does not fit.

Tires are matched on exact size against the vehicle's factory, guaranteed and aggressive size lists, which is why a plus-sizing shopper gets a different tier rather than a flat no.

Honest negatives#

This is the part that changes a storefront. Without spec data, a product with no mapping can only ever be unconfirmed — the engine cannot prove a negative. With the add-on, when the specs positively rule a fit out, the shopper is told does not fit, and the collection grid can filter it away.

The engine only asserts a negative when it can actually judge: it needs the vehicle's envelope and enough of the product's specs. A product missing its bolt pattern stays unconfirmed rather than being guessed at.

Turning it on#

The add-on is an entitlement on your shop, not an integration. There are no credentials, nothing to sync, and no file to maintain — which is also why it cannot be "connected" like a vendor. Ask us to enable it and it takes effect immediately; matching is at query time, so no reindex is needed.

Where it stops#

• It judges wheels and tires, and nothing else. Lift kits, brake kits, lighting and accessories still need mappings from your own sources.
• It needs your products to carry specs. Garbage or missing metafields produce unconfirmed verdicts, not magic.
• It is fitment intelligence, not a product catalog. If you need the products themselves — brands, inventory, MAP — that is the separate data subscription.