Skip to content

Troubleshooting ​

Solutions to the most common issues merchants run into with BRIX: Store Locator & Maps.


The floating Find a Store button doesn't appear ​

Possible causes:

  • The app embed hasn't been turned on in your theme editor.
  • The change was made but not saved.

Solutions:

  1. Open your theme editor's App embeds panel and confirm BRIX: Store Locator & Maps is on.
  2. Click Save in the theme editor - toggling without saving doesn't activate it.
  3. See Installation.

A location doesn't appear on the storefront ​

Possible causes:

  • The location's Status is Inactive.
  • No location has been added yet, or the app embed/block isn't live.

Solutions:

  1. Open the location and confirm its Status is Active - see Managing Locations.
  2. Confirm the app embed is turned on, or that the Store Locator block has been added to a page - see Storefront Widget Setup.

My CSV import has skipped or failed rows ​

Solutions:

  1. Download the import report and check each row's Reason.
  2. A Failed row usually means the Country column doesn't match a real country.
  3. A Skipped row usually means its Location ID matched an existing location while "Overwrite existing locations" was off - turn it on if you meant to update that row.
  4. See Bulk Import via CSV.

Address autocomplete or geocoding isn't working ​

Solutions:

  1. Type at least 3 characters and wait briefly for suggestions to appear.
  2. Very rural or newly built addresses may not exist in OpenStreetMap yet - you can still save a manually typed address and adjust the pin by hand.
  3. See Map Provider - OpenStreetMap and Adding & Editing a Location.

My custom CSS isn't taking effect ​

Solutions:

  1. Confirm you clicked Save on the Custom CSS page.
  2. Confirm you're viewing a page where the locator widget actually loads (your hosted locator page, or a page with the Store Locator block) - custom CSS doesn't apply theme-wide.
  3. See Custom CSS.

A translation isn't showing on the storefront ​

Solutions:

  1. Confirm you saved the translation, and that any {placeholder} tokens in the original text are still present in your translation.
  2. If a field is left blank for a language, it automatically falls back to your base language's text, then to the built-in English default - this is expected, not a bug.
  3. See Translations.

A location's public page isn't being indexed by search engines ​

Solutions:

  1. Confirm the location's Status is Active.
  2. Give it time - newly created pages can take a while to be crawled.
  3. Reference the app's sitemap from your theme's robots.txt, or submit it directly in your search console.
  4. See SEO Store Pages.

Still Need Help? ​

Use the Get Support link on the app's Dashboard, or contact support for anything not covered here.