Fitment data
Vendor integrations
Supplier feeds and what each adapter needs.
Vendor integrations pull fitment straight from a supplier, so the mapping arrives with the catalog rather than as a file someone remembers to export.
How it works#
Sixteen suppliers are in the adapter registry. An integration is connected with your credentials — you already have an account with the supplier; we do not resell their data and we never see it for any shop but yours.
- Ask us to enable the supplier Fitment data → Sources → Vendors lists the registry. Adapters ship per merchant signup, so tell us which of your suppliers you want and we'll turn it on for your shop.
- Enter your credentials Usually an API key or an FTP account issued by the supplier. Stored encrypted, used only for your shop's sync.
- Match on SKU or MPN Most suppliers key on their own part number; the adapter maps it to your SKU, or to an MPN metafield if your SKUs are internal.
- Sync The first sync is full; later ones are incremental on the supplier's own cadence.
Plan limits#
| Plan | Vendor integrations |
|---|---|
| Starter | 2 |
| Growth | 5 |
| Pro | All 16 standard adapters |
| Enterprise | Unlimited — including adapters we build for suppliers not in the registry |
That last row is the real Enterprise feature. If your best supplier has no API and mails you a fixed-width file — or an ACES XML export nobody else will touch — we will write the adapter for it as part of the plan.
What an adapter can and cannot do#
It can bring product-to-vehicle mappings, and often notes, positions (front/rear, left/right) and supplier part numbers — for whatever categories that supplier carries.
It cannot fix a supplier whose data is wrong. WySync's rule is firm here: the pipeline carries what the source says. Integrity checks report anomalies — a value that contradicts every other row for that platform, a measurement of 0 — but nothing is silently corrected, because a number we invented is one nobody can audit. Corrections go in the editor, where they are visible and attributable.
Reading the sync report#
Every sync records rows received, rows matched to your catalog, rows skipped, and why. The number worth watching is matched: a sync that receives 80,000 rows and matches 300 is a SKU-mapping problem, not a data problem.
When two vendor feeds disagree about one SKU, the union means the wider claim wins — the SKU will show as fitting the superset. If one supplier is reliably wrong for a platform, exclude those vehicles in the editor rather than disconnecting a feed you otherwise need.
Support is answered by the people who wrote this code — not a ticket queue.