Use case11 min read

How to build a where to buy page that retailers thank you for

The where-to-buy page for brands sold through retailers: the data model, the filters, online sellers alongside physical ones, and how the search data feeds your next wholesale pitch.

In short

A where to buy page lets a visitor type their postcode and see which shops near them carry your product, with an online option for everyone else. It exists because brands that sell through retailers cannot answer the most commercial question a visitor has, where can I get this, with a checkout button alone.

Building one is a store locator with three differences: the locations are shops you do not own, the filters describe which of your products each shop carries, and online sellers appear alongside physical ones so nobody hits a dead end.

Done properly it does a second job: every search on it is demand data. Searches in towns where you have no stockist are a map of where your sales team should pitch next, which is information a brand cannot buy anywhere else.

Lumen Optical website showing its stockist locator with search, filters, result cards and a map
The Lumen Optical stockist locator on a phone

Who needs one, and why a checkout button is not it

If your product sits on other people's shelves, supermarkets, pharmacies, bike shops, garden centres, your website has a gap: the visitor who wants the product today, near them, in their hands. A buy online button answers a different question. The where to buy page answers this one, and it is usually the highest-intent page on a brand site because everyone on it has already decided to purchase.

It also does quiet diplomatic work. Retailers notice which brands send them customers. A page that routes visitors into your stockists is evidence you bring to a wholesale conversation, and brands with strong where to buy pages get asked for less margin than brands that only compete with their own retailers online. A CPG brand like Coca-Cola sending traffic to Walmart or HEB, or a food brand like KIND pointing shoppers at Whole Foods, is exactly the signal a buyer notices at the next line review.

The four things that make it different from a shop finder

Mechanically it is a store locator, and our general setup guide covers the embed itself. The differences are in the data and the journey.

  • The locations are not yours. You do not control their hours or their stock, so the page should promise what you can keep: who carries the product line, not live shelf counts.
  • Filters describe your products, not their services. A visitor wants the shop that carries the flavour or model they are after, so each stockist row needs a column for the lines it stocks.
  • Online sellers belong on the page. A visitor with no stockist within fifty miles is not a lost sale, they are an online order. An online options tab alongside the map keeps them.
  • The link target matters. Each result should point at the retailer's page for YOUR product where one exists, not their homepage. A visitor dropped on a homepage starts a search they may finish with a competitor.

Build it in five steps

The sequence assumes a hosted locator; the platform-specific paste points are in the any-website guide.

  1. List your stockists as one row per shop: stable name, address, phone, website, and one column per product line they carry. For a retailer with many branches, one row per branch, because the visitor cares about the branch near them, not the chain.
  2. Add your online sellers, your own webshop and any marketplaces, flagged so they appear under an online tab rather than on the map.
  3. Import, then fix what the report flags: failed geocodes and duplicates are cheapest to correct now.
  4. Turn the product-line columns into filters, and set each result's link to the retailer's product page for your brand where one exists.
  5. Embed on a page named the way people say it, Where to buy, test the phone layout, and put it in the main navigation. Packaging and ads should point at this URL.

Keeping stockist data true without owning it

The hard part of a where to buy page is not building it, it is week twelve, when a stockist has dropped your line and their entry still promises visitors your product. Wrong data here embarrasses you in someone else's shop.

Two habits keep it honest. First, connect the page to a Google Sheet your sales team already maintains, so the person who signs a new stockist or loses one edits a row and the page follows, with no website access needed. Second, prune on a schedule: a quarterly pass through the list asking is this still true costs an hour and is the entire maintenance burden.

Resist the temptation to promise stock levels. Retail inventory feeds are expensive to integrate, wrong within hours, and answer a question the visitor did not ask. Carries this line is a promise you can keep; three units on shelf B is not.

What belongs on a stockist's result card

Each card answers one question: is this shop worth my trip? For stockists the answer has different parts than for your own shops. The name and address identify it; the product-line chips say whether your thing is there; the phone number lets a cautious visitor confirm before driving; and the directions link does the actual job. A website link earns its place only when it points somewhere useful, which for a stockist means their page for your brand.

Hours deserve a deliberate decision rather than a default. They are the most-checked field on any result card, but these are another business's hours, and a wrong open-until claim sends someone to a locked door with your brand on the journey. Show them where your team can genuinely keep them current, through the same Sheet the stockist list lives in; omit them where you cannot, because no answer beats a wrong one.

Watch two numbers once it is live: searches that end in a directions or phone tap, which is the page doing its job, and searches that return nothing, which is the next section.

The search data is a market map, read it

Every search on a where to buy page is a person declaring purchase intent at a postcode. In aggregate that is distribution intelligence: the towns where searches happen and no stockist exists are, precisely, the places your product has demand and no supply.

Treat that list as the input to your next wholesale round. A pitch that opens with forty people a month search for us in your town and we send them elsewhere is a different conversation from a cold call. This is also the honest reason to prefer a locator with search analytics over a static map: the map serves visitors, the analytics serve the sales team.

Mistakes that show up in real pages

In rough order of how often they appear.

  • Linking results to retailer homepages instead of product pages, which hands the visitor a second search to finish.
  • No online path, so the visitor with no nearby stockist leaves instead of ordering.
  • One pin per chain instead of per branch, which makes a national retailer look like one shop in one city.
  • Stale stockists that no longer carry the line, discovered by a customer who drove there.
  • Burying the page. If the packaging, the ads and the navigation do not point at it, the highest-intent page on the site gets the least traffic on the site.
  • Skipping the phone test, when packaging QR codes and social ads make this the most phone-heavy page a brand runs.

Where Handled Locator fits

Handled Locator ships the pieces this page needs as first-class features: stockist imports from CSV or a synced Google Sheet, product-line filters, an online options tab for web sellers, per-result links you control, and search analytics that show the searches with no nearby result. Styling covers 85+ settings so the page reads as your brand, and the map runs on your own Google or Mapbox key at provider cost.

Plans start at $19 a month for 200 stockists and reach 10,000 on the top plan, which covers a retailer network with many branches. The stockist guide goes deeper on the data model, and the live examples include stockist setups like the one pictured above. The stockist locator overview is the shorter version of this page if you want the pitch rather than the how-to.

Frequently asked questions

What is a where to buy page?

A page on a brand's website where visitors enter a town or postcode and see the nearby shops that carry the brand's products, usually with filters for product line and an online option for visitors with no stockist nearby. It is a store locator whose locations are retailers rather than the brand's own shops.

What is the difference between a where to buy page and a store locator?

The mechanics are the same; the data is not. A store locator lists locations you own and can promise things about. A where to buy page lists other people's shops, so it promises what the brand controls, which shops carry which lines, and adds online sellers so no visitor dead-ends.

Should the page link to the retailer's homepage or product page?

Product page, wherever one exists for your brand. A homepage link hands the visitor a second search inside the retailer's site, and some finish it with a competitor. Use the deepest stable link the retailer offers.

Should I show live stock availability?

Almost never. Inventory integrations are costly, wrong within hours, and answer a question visitors did not ask. Carries this product line is a promise you can keep indefinitely; live shelf counts are not. The exception is high-value goods where a wasted trip is severe, and even then a call this shop button beats a stale number.

How do I keep stockist information up to date?

Put the list where the people who know live: a synced Google Sheet the sales team edits beats a website-admin bottleneck. Then prune quarterly. The failure mode is not missing a new stockist, it is keeping a dead one, because a customer finds that mistake in person.

Can a where to buy page help me get into more shops?

Yes, twice over. The page itself is evidence in wholesale conversations that you send retailers traffic. And its search data shows where people looked for you and found nobody, which is a ranked list of towns for your next distribution push.

Where should the where to buy button live?

Main navigation, product pages, and the back of packaging via QR. The page only earns its keep when the moments of intent, seeing the product in an ad, holding it at a friend's house, can reach it in one step.