Appearance
Store Locator Setup
Getting your locations live is three decisions and one data load. The field reference and the endpoint reference live elsewhere — this page is the order to do things in.
1. Decide what is a location and what is a hub
A hub is a physical inventory location: it holds stock, it fulfils orders, it has a delivery and pickup radius. A listed hub is the customer-facing profile the store locator shows.
They are separate records. Set up the hubs you fulfil from first (Profile → Hubs), because a listed hub can then point at one and inherit its room and POS integration in the storefront response.
A location you want shoppers to see but do not fulfil from — a partner dispensary, a stockist — needs a listed hub and no hub.
2. Load the locations
One at a time under Profile → Locations → Create Location, or as a CSV under Import. The CSV path geocodes each address through Google and shows you the rows it could not resolve before anything is written.
Both routes are covered step by step in Store Locator.
3. Make them visible to "nearest"
show_on_nearest gates whether a location appears in the nearest-store lookups a storefront calls at checkout. It defaults to false and neither the create form nor CSV import sets it, so this step is an API call — PUT /listed/hub/:listedHubId.
4. Have Batch set the search behaviour
How the locator searches — text only, driving distance or straight-line distance — plus the radius, the default page size and the country used to resolve a bare zip code, all come from the brand's siteConfiguration.listedHub master data. There is no admin screen for it; ask Batch to set it for your brand. The options are listed under Search configuration.
Next Steps
Related pages
- Store Locator — managing the locations themselves
- Finding a store — the shopper's side