Skip to main content

Maps not showing all your stores?

Are you missing some stores on your map even though they are loaded in the back end?

Updated over 2 weeks ago

It might be the "Number of Stores in List" setting..

The setting “Number of Stores in List” is used to limit the output of the list of stores on the map display. However if you want to be able to see all stores you should likely set the limit to the total number of stores you have uploaded.

📌 Note:
If you're using the “No limit” option in the search dropdown, please ensure that the “Number of Stores in List” value is set greater than or equal to the total number of locations in your database. Otherwise, some locations may not be loaded or shown on the map.

1. List Sorting Field

  • If this option is set to "Priority", which means the app will sort and return stores based on their priority value (as configured in the store data).

  • If you want to display the nearest stores based on a specific address, you’ll need to set this field to "By Distance" - this is the default option. If you set the option to "By Distance" and it returns nearby stores for the address entered "123 Address Way, FL 12345, USA" (example address).

  • If this option is set to "Store Title Alphabetically" then the stores will sort by the name/title of the store.

2. Number of Stores in List

  • This field controls how many stores are pre-loaded into the map list, regardless of filtering or searching.

  • For example if set to 150 (you can choose any number up to the total number of stores) , the app will only consider the first 150 stores (after sorting) when you perform a location-based search — even if "No limit" is selected for the distance.

  • So when you search using a specific address, the system filters within this list of 150 stores. This explains why some nearby stores may not show up — if they are outside the initial 150 .

3. Maximum Stores Loaded

  • This defines the maximum number of stores the app will load into the map list on initial page load.

  • It acts as a performance safeguard — if too many stores (e.g., over 5000) are loaded and appended into the Webpage (DOM) at once, it can negatively impact website performance due to excessive HTML rendering.

  • This setting does not affect search accuracy directly, but rather controls the size of the initial dataset being appended.


✅ Summary

If your goal is to return all nearby stores for an address like "123 ADDRESS Way", make sure these two configs are set:

  1. List Sorting FieldBy Distance

  2. Number of Stores in List → large enough to cover all stores (e.g., 5000 to include full dataset)

Did this answer your question?