Start with the product question
A product locator is useful when a visitor knows what they want but does not know which nearby retailer carries it. Decide whether the first choice should be a product, a format, a pack size or a use case. That choice should shape the filters and the wording on the page.
Keep product data consistent
Use the same product names and category values across every location. If one retailer uses three spellings for the same product, visitors will miss results and your filters will feel unreliable.
- Use one filter value for each product or range
- Separate product availability from retailer type
- Add a direct retailer or product link when it exists
- Keep discontinued products out of the public data
- Review a few common product searches after each import
Design the result around a decision
A result should show the product match, retailer name, distance and the action that follows. Use a buy or website action for online stockists, and directions or phone for a physical retailer. Do not make visitors open a map marker just to learn whether the location carries the product.
Test useful and impossible searches
Try a popular product, a product with only one retailer and a term that should return no results. The empty state should suggest another product, a wider search or an online option instead of leaving the visitor at a dead end.
Build from a working example
Use the where-to-buy guide to structure the data, then review the custom filters feature and live examples before publishing.