Live store locator examples

A preserves brand's stockist page

Bramble & Co

Bramble answers the where-to-buy question for a brand sold through other people's shops. The two filters are product truths, flavour and store type, because a visitor wants the shop that carries the flavour they are after, not a generic list. Nearby locations and an online options tab sit side by side, so a visitor with no stockist in range becomes an online order instead of a lost sale.

The dark green and cream palette runs through the widget: result cards, filter chips and cluster markers all take the brand's colours, which is what makes the locator read as part of the site rather than a bolted-on map. Clustering matters here because stockist lists are long, and forty pins without clusters is noise.

A bakery's own shops, styled hard

Fornaio

Fornaio shows how far the design settings stretch: logo-shaped map pins, a red search band matching the brand's header, serif result typography, and a warm map style in place of provider-default colours. It is deliberately the loudest example, because the question it answers is whether a locator can carry a strong identity without custom code.

Structurally it is the simplest data model here, a handful of company-owned shops with hours and phone numbers, which is the starting point most businesses actually have. The filters sit directly under the search bar so narrowing happens before scrolling, a small ordering decision that matters most at phone width.

A dealer network with accreditation

Northwind Cycles

Northwind is the dealer-locator shape: the locations are independent bike shops, so each card leads with what the visitor needs to trust it, an authorised dealer badge, and what they need to choose it, service centre and bike fitting capability chips. The filters mirror those fields, splitting the buyer looking for a test ride from the owner needing a repair.

Every branch is its own entry with its own phone number and hours. That is the modelling rule dealer pages most often get wrong, and this example exists partly to show what per-branch data looks like when it is done properly.

Service areas instead of shopfronts

Rivet Plumbing

Rivet answers a different question: not where is the shop but do you come to me. A plumber has no premises worth visiting, so the map draws coverage radii around bases rather than pins to walk to, and the result card's primary action is the phone call, not directions.

Who actually comes out is decided by zip code, the way a trade dispatches crews. The map draws each crew's zip codes from Census boundaries, and typing a zip on a crew's list makes that crew the only answer. Try 75034 for the Frisco crew, then 75024 in Plano, a gap on the map: the locator says it is not covered and offers the nearest crews.

This shape fits any at-home trade, cleaners, installers, mobile mechanics, and it demonstrates that the same widget handles a geometry other locators cannot: the honest answer to a service-area search is a boundary, not a distance.

Classes in hired halls, not shops

Rollo

Rollo runs puppy classes in church halls, which is a different problem from finding a shop: the venue is incidental and what a visitor is choosing is a course. So the filter is one captioned row of courses, each chip showing how many halls run it, and every card says which course that hall teaches.

It is also the gallery’s loudest consumer brand: one saturated coral on an off-white ground, pill corners everywhere, a serif name over a humanist sans. Nothing else here tested whether the widget survives a colour used at that volume, and the map pins are the brand mark itself rather than a drawn icon, because a filled circle is what stays legible at pin size.