Product
WySync Fitment is a Shopify app and a theme extension. The app indexes your catalog and resolves fitment; the extension puts nine widgets on your storefront. They share one piece of state — the shopper's vehicle — so nothing ever contradicts anything else. It does not care what you sell, only that it fits some vehicles and not others.
Your products come out of Shopify through a GraphQL bulk operation — titles, variants, prices, inventory, collections and metafields. Nothing is copied into a WySync product table; Shopify stays the source of truth.
Every fitment source you've connected is merged into one set of vehicle IDs per SKU. Tags are parsed, CSV and Sheets rows are expanded across year ranges, metafield specs are canonicalised, editor overlays are applied last.
The resolved documents land in a per-shop Typesense index with Redis in front. Storefront widgets query that index through a signed app proxy — never Shopify, never our database.
The index carries whatever attributes your products have, in five typed families — spec_num_*, spec_int_*, spec_str_*, spec_strs_*, spec_bool_*. Blade length, pad compound, rotor thickness, hitch class, bed length and attachment type behave exactly like diameter, offset and bolt pattern do. Nothing about the engine is wheel-shaped.
Bolt pattern, offset, hub bore, diameter and load rating — the hardest fitment in the aftermarket, and the one we started with.
Lift and lowering kits, coilovers, control arms, leaf packs. Fitment by platform, often by trim and drivetrain.
Rotors, pads, big brake kits, axles, differentials. Front/rear position matters as much as the vehicle does.
Bars, pods, fog kits, harnesses, tail lights. Direct-fit SKUs that live or die on the year range.
Intakes, cat-backs, headers, tuners. Fitment is often engine-specific inside one model.
Tonneau covers, bull bars, fender flares, floor liners, roof racks, mud flaps.
Hitches, wiring harnesses, brake controllers, ball mounts.
Wipers, filters, belts, bulbs — high-volume parts nobody wants to return.
Homepage
Year / Make / Model / Submodel above the fold. Submitting routes the shopper into a catalog already filtered to their vehicle — whatever you sell for it.
How to set it upEvery page
The selected vehicle follows the shopper across the store, collapsing to a compact pill on mobile. Change or clear in one tap.
How to set it upHeader or sticky
Multiple vehicles per shopper — the daily driver, the work truck, the project car. Syncs to the customer account when they're logged in.
How to set it upCollections
Replaces the native product grid with a Typesense-backed one: fitment filtering, your own metafield facets, price and stock filters, four sorts.
How to set it upPost-search
The landing surface after a vehicle is picked. Shows only the collections you mapped, with your imagery and order.
How to set it upSearch
Replaces native Shopify search: keyword relevance, autocomplete, SKU-to-product redirect, and vehicles detected inside plain-text queries.
How to set it upProduct page
A plain-language verdict for the shopper's vehicle — fits, does not fit, or unconfirmed — with your copy and your escape hatch.
How to set it up| Years | Make | Model |
|---|---|---|
| 2015–2026 | Ford | F-150 |
| 2019–2026 | Ford | Ranger |
| 2018–2026 | Ford | Expedition |
| 2007–2021 | Lincoln | Navigator |
Product page
The full compatibility list for a SKU — every vehicle it fits, year-ranged and grouped, from your mappings and spec matching combined.
How to set it upCart & checkout
Re-checks every line against the active vehicle before checkout, and can hard-gate the checkout button when something no longer fits.
How to set it upSEO
Indexable pages for every vehicle you carry — "2019 Ford F-150 parts" — generated on a schedule from real published collections.
How to set it upSources merge as a union. If any connected source confirms a SKU fits a vehicle, it fits — so you can start with the tags already on your products and add a supplier feed later without re-doing anything.
fits_2018_2024-ford-f-150
SKU, years, make, model, submodel, note
Polled on a schedule, no re-upload
Per-product specs already in your catalog
16 supplier adapters in the registry
Spec matching · wheels & tires only
Supplier data is never perfect. The fitment editor sits on top of your sources as an overlay: add a vehicle a feed missed, exclude one it wrongly claims, flag a SKU universal, or attach a note that shows on the product page ("requires trimming", "not with factory tow package"). Your edits survive every reindex — they are applied after the sources merge, not baked into them.
"Chevy" and "Chevrolet" are the same make; "F150" and "F-150" are the same model; "5x114.3" and "5x4.5″" are the same bolt pattern. Physics ships in code, vocabulary is a per-shop synonym list you can read and edit — no black box deciding your catalog is wrong.
This add-on is category-specific and we'd rather be blunt about it: it covers wheels and tires. For those, the engine switches from "look up a mapping" to "judge the specs" — canonicalised bolt pattern, diameter and width envelope, offset range, hub bore, and exact tire sizes against factory, guaranteed and aggressive tiers. Every other category keeps using the sources you connect, which is what most of this app is.
Everything is inside Shopify admin, in Polaris, with no separate login. Seven sections, each doing one job.
Searches, vehicles, zero-result queries, fitment coverage and index health.
Sources and the editor — connect, upload, poll, override.
Widget install status with deep links into the theme editor, mapped collections, vehicle pages.
Facets, ranking weights, normalization rules and synonyms.
Job history, manual reindex, per-product failures with reasons.
Copy templates, no-data behaviour, billing and plan.
Direct line to the people who wrote the engine.
This site, linked from every page of the admin.
Next
Thirty-day trial on every plan. Setup and the theme install are included — we do them with you on a call.