Product Thumbnail

LocateStore

Create a map of all your stores using Google Sheets

Spreadsheets
Website Builder
Maps

LocateStore turns a Google Sheet into a fast, mobile friendly store locator. Add your store address in a Google Sheet, and get an interactive map with search and filters. Easily embed on any website. No code, no API keys, and edits sync instantly. Built for multi location brands that want a simple “find a store near me” experience.

Top comment

Hi Product Hunt 👋

Shyjal here from Micro.company, maker of LocateStore.

While working with many businesses, we kept seeing the same issue: Building a store locator is still far more complicated than it should be.

Most teams already manage store locations in a spreadsheet. But to put those locations on a live map, they end up dealing with map API keys, custom development, agencies, long back and forth, and ongoing maintenance. All for something that should be simple. So we built LocateStore.

LocateStore lets you manage all your store locations in a Google Sheet. Store name, address, contact details, website, tags and more. From that single sheet, LocateStore automatically creates a clean, interactive, mobile friendly store locator with search and filters. Any update in the sheet reflects instantly on the live map.

No code. No API keys. No maintenance.

How it works is simple.
- Sign up to locatestore
- Add locations to a Google Sheet
- Copy-paste a small embed snippet into your site

That’s it, your store locator is live.

We built LocateStore to keep store locators simple, easy to understand, and fast to set up. It is designed to deliver a smooth “find a store near me” experience and is already powering 1000+ businesses.

Would love for you to check it out, try it, and share your feedback.

Comment highlights

Hello,

A great and very useful tool.
I have a few clarifying questions:

Is it possible to support multiple maps within a single account?

Is it possible to add custom fields (for example, store type, status, or opening hours)?

this is a brilliant idea. Looks like it only works of google sheets? How about a just a simple csv file?

I once spent three painful days trying to build a store‑locator UI for my parents’ business — wrestling with API keys, messy code, and endless tweaks, only for it to still look pretty awful in the end. Seeing LocateStore honestly made me laugh a little… this would’ve solved my entire headache in seconds. The convenience and speed here are exactly what I wish I had back then.

One question though, I’m curious about the subscription model. What’s the reasoning behind separating pricing by monthly visits and monthly searches? It would be great to understand how those metrics map to real usage patterns. As the product evolves, it might also be worth exploring additional value for the paid tier — things like analytics, custom branding, advanced filters, or integrations that help teams get even more out of their store locator.

Overall, this is a thoughtful and well‑executed tool. Congrats to your launching!

LocateStore sounds like such a clever and simple way to set up a store locator! I'm really curious if it can handle hundreds of locations smoothly without any lag on the map. Since it doesn't require API keys, I wonder how it manages the mapping data and if there are any extra costs for high traffic. Is the "instant sync" truly seamless even for mobile users, and can we customize the filters and map pins to match our brand's look? It would also be great to know if it supports international addresses just as easily as local ones!

This solves a very real ops problem. Spreadsheets are still the backbone of many multi-location setups, so building on top of Sheets makes a lot of sense.

Is this meant for businesses that have offline stores and want to show their locations on their website??

It's almost refreshing to see such a simple (at least in concept) product doing so well and receiving so much attention. It seems the AI-wrappers steal the show the majority of the time, but something like this is TRULY useful and can be used with certainty. Amazing.

Love the simplicity of the concept, going from a simple, accessible datastore to a embeddable web component. I honestly kind of want to use this just personally to create a map of my favorite places around town.

A lot of products in this category either focus on SEO (indexable location pages) or on a fast embedded widget. What tradeoffs did you make around SEO vs simplicity/performance, and how should a brand decide if LocateStore is the right fit for their goals?

Nice launch :), this feels very practical. Curious how people handle frequent or seasonal updates with it.

This is a really satisfying idea - “a Google Sheet becomes a store locator” is exactly how most small teams already work. The no-API-keys, no-maintenance promise is a huge win.

I’m curious how it behaves once it meets real-world data though. Addresses are often messy, duplicated, or half-filled - do you do any validation/cleanup, or is it strictly “whatever’s in the sheet”?

Also, if someone has a larger list (say, a few thousand locations), does the map stay snappy and readable? And can the embedded map be styled enough to feel on-brand, or is it intentionally minimal?

Congrats on the launch - this feels like one of those tools that saves you an entire weekend the first time you need it.

Hi PH community, 👋

Managing store locations shouldn’t require a developer. That’s why we built LocateStore to sync directly with Google Sheets.

Instead of showing customers a long, static list of addresses on your “Contact Us” page, LocateStore helps you add an interactive map that makes it easier to find nearby locations and can increase the chances of visitors actually walking into a store.

You can check out the live demo here:
👉 https://locatestore.com/demo

I’d love to hear your thoughts:

  • Do you prefer maps over lists when searching for a business?

  • Does an interactive locator influence your decision to visit a store?

Cheers,
Aslam from Micro.company

Turning a live Google Sheet into a locator gets tricky at scale: Sheets API quotas plus geocoding churn and 1k+ pins can tank TTI on mobile.

Best practice is to precompute and persist canonical lat,lng in the sheet, batch geocode server-side with caching, and ship a CDN cached JSON feed with marker clustering or viewport based loading.

What geocoder and maps stack are you using to keep it truly “no API keys,” and how do you handle address normalization plus rate limits when rows change frequently?