A Store Locator displays stores on a map and allows website or app users to find the closest and more convenient store from them. It will also help you show related information such as address, business hours, contact details or any available amenities and services. We offer two different ways to embed a Store Locator on your app or website, the Woosmap Store Locator Widget or Woosmap Store Locator JS API. We will help you choose which is the best solution for your needs.
The Woosmap Store Locator Widget is a one-stop-shop to create a Store Locator based on Google Maps API (or Baidu Maps). It is the short cut to provide your users with a powerful store locator. To match your preferences and website’s graphic style, all the properties of your Store Locator Widget can be customised client side thanks to the
Natively responsive layout based on your window width breakpoint.
Labels support different languages.
Bunch of prebuilt features such as Autocomplete Search, Driving Direction, Distance Matrix,...
Fast to deploy and easy to maintain (source code of the widget is hosted by us)
Style is not fully customisable as you don't have access to CSS ClassNames and icons are inline svg.
Tracking users interaction with an analytics tools (Google Analytics for example), is limited to existing
HANDLED_EVENT properties list
Possible styles collision with your own styles.
Less flexibility for new features.
The side panel used to display detailed information for the nearby stores or a selected store is fully customizable. You might consider this option as an alternative to the Store Locator Widget without custom rendering as you’ll need familiarity with front-end development concepts.
Customize stores information rendering: set your own style and display desired information for both summary renderer (list of nearby stores) and detailed renderer (selected store) in the side panel. see how.
Greater ability to record how the user is using your Store Locator
Same pros than the Widget without custom renderer
A bit longer and timeconsuming development
Same cons than the Widget without custom renderer
Full control over UI/UX.
You could develop advanced behaviour by extending JS Classes using MVCObject (search for stores names for example).
More flexible to add new features as you remain owner of the source code.
Tracking user interaction limited only to your ideas and creativity.
Longer and more complex development (and therefore timeconsuming).
You'll need to host the integration source code on your side.
Maps providers updates could impact the stability in cases you directly instantiate their classes.
First of all, our Customer Care team is here to help you make the right choice and make sure the job is done right. So please don’t hesitate to reach out to us.
To decide which option is best for you (using the Widget or developing with the JS API), you could write a small decision matrix. There are some tips that may helps you:
Store Locator Widget
Store Locator Widget
Store Locator JS API
The implementation with the highest total value is the one to consider first. It really depends on what your priorities are. We’re always happy to help with code or other questions you might have! If you interested in sharing what would be your choice, feel free to contact us.
If you want to go further
Woosmap offers an easy embeddable Store Locator Widget. Our aim is to help you to integrate a powerf [...]
The Google Places API is a service that returns places predictions using HTTP requests. The service [...]