Storefront widgets
YMMS hero
The homepage vehicle picker and where it routes.
The front door. Four dropdowns — Year, Make, Model, Submodel — that cascade, and a button that sends the shopper into a catalog already filtered to their vehicle.
Behaviour#
Each dropdown loads only values that exist below the one above it, so a shopper can never build a vehicle that doesn't exist. Options come from the taxonomy through the app proxy and are cached, so the second visitor of the day gets them instantly.
Submodel is optional by default: a shopper who stops at model gets fitment for every submodel of that model. Make it required in the block settings if your catalog's fitment genuinely varies by trim.
On submit the vehicle becomes the active vehicle and the shopper is routed to the block's redirect URL. Leave it blank and they go to /collections, which is where the collection list belongs.
Placement#
Homepage, above the fold. It is a section block: theme editor → Add section → Apps → WySync YMMS hero. It also works on a landing page template if you run vehicle-specific campaigns.
Horizon constrains section content to a centre column. The hero includes the override that lets it run edge-to-edge inside any section width, so you don't need a custom section wrapper.
Settings#
- Heading and helper copy
- "Find parts for your vehicle" is the default; use your own voice.
- Button label
- "Shop my vehicle", "Find parts that fit", "Shop my F-150" — whatever your customers say.
- Layout variant
- stacked, inline, or card. Inline suits a slim band under a banner; card suits a hero image background.
- Background style
- transparent, surface, or image, with an overlay control.
- Accent colour
- defaults to your theme's accent.
- Redirect URL
- blank is
/collections. - Require submodel
- off by default.
- Remember last vehicle
- pre-fills the dropdowns for a returning shopper.
Why it converts#
The hero is the only widget most first-time visitors will see, so two things matter more than the styling: it must be above the fold on mobile, and the button label must promise the outcome ("Shop my F-150") rather than the mechanism ("Search"). Both are settings, both are worth testing.
Adding the block twice is supported and occasionally useful (top and bottom of a long homepage). They share the same vehicle state, so filling in either one updates both.
Support is answered by the people who wrote this code — not a ticket queue.