Troubleshooting
Fixes for the most common Nearby issues — the widget not appearing, a blank map, a missing location, or stock that looks wrong.
Most issues come down to the theme block, a location's address, or inventory still syncing. Work through the relevant section below, then email nearby@harbourlabs.app if it persists.
The widget doesn't appear on the product page
- Confirm the Nearby block is added to your Product template in the theme customiser and saved (see Getting started).
- Check you're looking at the live theme, not a preview of a different theme.
- The widget only shows locations that have the product in stock. If no location has stock, there's nothing to show — try a product you know is stocked in more than one place.
The map is blank or grey
- The map needs Starter or Growth; on Free the widget is compact (list-only) by design.
- If you switched the provider to Google Maps (Growth), make sure a valid Google Maps API key is set under Settings and that the key allows your storefront domain.
- A custom style.json URL must be a reachable MapLibre style; revert to a preset to confirm.
A store is missing from the widget
- Check the store's address is complete enough to geocode — a store without a resolvable address can't be placed on the map.
- Confirm the store is within your plan's location limit (Free 3, Starter 25, Growth unlimited). Locations beyond the limit are hidden on the storefront.
- Make sure the mapped Shopify location actually holds stock of the product.
Stock looks wrong
- Nearby reads inventory from Shopify and updates via webhooks. Right after install, the first sync may still be running — give it a few minutes.
- If a location shows "low" unexpectedly, check its low-stock threshold and stock buffer under Stores.
- If it's still off after syncing, editing the product or its inventory in Shopify will re-trigger a sync.
"Open now" is wrong
- Confirm the store's opening hours are set, and that they reflect the store's local time.
Still stuck?
Email nearby@harbourlabs.app with your shop domain and the product page you're seeing the problem on.
Was this helpful?