Vehicle-fitment spare catalog
Fitment lived in a parts specialist’s head. We shipped a year / make / model / submodel selector in front of the spare-tire catalog.
The situation & problem
Kafina sells vehicle-specific spare tires. A generic grid would sell the wrong SKU.
The operational constraints
The vehicle must be selected before results. The catalog has to survive many makes without a 40-page brand directory as the only UX.
Architectural tradeoffs & what was refused
A store grid of “tire 1 / tire 2.” A PDF fitment chart next to an Add to cart button.
What I built & shipped
Fitment wizard, shop-by-make, product cards, and cart.
Architecture & stack
Commerce catalog with a fitment taxonomy in front of stock. Vehicle first, price second.
Result & measurable impact
The first question is the vehicle, not the price.
Next iterations & roadmap
Bind public “in stock” to the warehouse record so fitment results respect on-hand quantity.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell me where your current operational system or product is breaking.