Storefront widgets
Collection list
The post-search landing surface.
Where a shopper lands after picking a vehicle: the collections you sell for that vehicle, in your order, with your imagery.
Why it exists#
Sending a shopper straight from "2019 F-150" into a grid of 4,000 parts is a worse experience than asking one more question. The list page is that question — wheels, brakes, suspension, lighting, protection — and it is also where you get to merchandise.
Mapped collections#
Under Storefront → Collections you choose which collections appear here — typically your top-level categories:
- Add
- by handle or numeric ID
- Reorder
- by drag — the order shoppers see
- Image
- upload one or fall back to Shopify's collection image
- Toggle active
- hide seasonal collections without deleting the mapping
Mapping affects this page only. The fitment-aware grid still renders on every collection in your store, mapped or not.
Placement#
Add the block to the /collections (collection list) template. That is where the hero's blank redirect sends shoppers, so the two work together out of the box.
Settings#
- Heading, which can include the vehicle: "Shop for your {vehicle}"
- Layout variant: cards or compact tiles
- Columns per breakpoint
- Whether to show a per-collection count of fitting products
"312 parts fit your F-150" converts better than a bare "Suspension". It costs one extra query per tile, which is cheap — but on a list of twenty collections it adds up. Map the collections that matter and leave the long tail off this page.
When no vehicle is selected#
The block renders the same collections without counts, and shows the vehicle selector above them. A shopper who arrives from a Google result rather than your homepage still gets a sensible page.
Support is answered by the people who wrote this code — not a ticket queue.