Magento 2 Store Locator with Map

Key Features

Google Maps JavaScript API store directory with custom markers, clustering and branded info windows

Nearest-store search by typed address or HTML5 browser geolocation, sorted by real driving/straight-line distance

Dedicated branch entity with its own DB table, repository and service contracts (StoreRepositoryInterface) — not CMS blocks

Per-store opening hours, phone, email, amenities and 'available for in-store pickup' flag

One-click driving directions deep-linked to Google Maps / Apple Maps from each result

Admin grid + form built on Magento UI Components, protected by dedicated ACL resources

Automatic geocoding of admin-entered addresses via cron job + event observer (no manual lat/long)

REST and GraphQL endpoints so PWA Studio, mobile apps and headless front ends can query locations

Store / website scope-aware configuration via Stores > Configuration (System config + di.xml)

Multi-store and multi-language friendly, with translatable labels and per-store-view content

SEO-friendly locator landing page with schema.org LocalBusiness structured data per branch

Upgrade-safe implementation using plugins (interceptors) and di.xml preferences — no core edits

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Magento 2.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

This is a build-to-order Magento 2 extension, not an instant Adobe Commerce Marketplace download. ECOSIRE designs, builds, installs and supports the Store Locator with Map module directly on your Magento Open Source or Adobe Commerce instance — tuned to your theme, your store hierarchy and your fulfillment workflow.

The extension ships as a proper module under app/code/Ecosire/StoreLocator, registered through registration.php and module.xml. Branch records are a first-class entity with its own database table, repository and service contracts (StoreRepositoryInterface), so your data stays queryable, exportable and API-addressable rather than locked in a CMS block. A dedicated admin grid and form (UI Components, secured by granular ACL resources) lets staff manage locations, geo-coordinates, opening hours, contact details, amenities and per-store pickup flags.

On the storefront, customers search by typed address or browser geolocation; results are sorted by real distance and plotted on an interactive Google Maps JavaScript API map with info windows and one-click driving directions. The same data is exposed over REST and GraphQL so your PWA, mobile app, or headless front end can consume it. Geocoding runs through a cron job and an event observer, so addresses entered in admin are resolved to coordinates without manual lat/long lookups.

Because every Magento install is different, we adapt the build with plugins (interceptors) and di.xml preferences instead of core hacks — keeping the module upgrade-safe. We install it on your staging environment first, run setup:upgrade / setup:di:compile, validate, then promote to production. You get the full source, no encryption, no per-domain license server. Pricing is a one-time build fee of $199; ongoing support and updates are available as described below.

What you get

Custom Ecosire_StoreLocator module source (app/code), fully readable and unencrypted

Installation on your staging then production Magento Open Source / Adobe Commerce instance

Declarative schema (db_schema.xml) and data/upgrade scripts for the branch table

Admin management UI with ACL roles configured for your store team

Google Maps API key wiring plus guidance on key restriction and billing setup

REST + GraphQL endpoint documentation and example queries for your front end

Theme integration of the storefront locator page matching your current design

Post-deployment validation report (setup:upgrade, di:compile, smoke tests) and a short admin handover guide

Who this is for

Multi-location retail brand

A retailer with 10–200 physical stores that wants online shoppers to find their nearest branch, check its hours and amenities, and get directions — driving footfall from the website.

Franchise operator

A franchise group needing each franchisee's branch managed under store-scoped permissions, with consistent map presentation and per-location contact and pickup data across the network.

BOPIS / omnichannel merchant

An omnichannel store on Magento that surfaces per-branch in-store pickup availability so customers can confirm a nearby location stocks pickup before they travel or order.

How Magento 2 Store Locator with Map Compares

Criterion	ECOSIRE	Custom Build	Competitor
Built specifically for your store hierarchy, theme and pickup workflow	Included	Included	Not included
Installed and validated on your environment by the vendor	Included	Partial support	Not included
Branch data as a true entity with REST + GraphQL service contracts	Included	Partial support	Partial support
Per-store in-store pickup availability flag	Included	Partial support	Partial support
Available out-of-the-box with no engagement	Not included	Not included	Included
Full unencrypted source with no per-domain license server	Included	Included	Partial support
Upgrade-safe (plugins / di.xml, no core edits)	Included	Partial support	Partial support
Ongoing support and Magento version-compatibility updates	Included	Partial support	Partial support

Frequently Asked Questions about Magento 2 Store Locator with Map

Is this an instant download from the Adobe Commerce Marketplace?

No. This is a build-to-order extension. ECOSIRE builds the Ecosire_StoreLocator module for your specific Magento Open Source or Adobe Commerce install, then installs and configures it for you. There is no Marketplace download link — you receive the full module source and a working deployment on your environment.

How long does delivery take?

Typical lead time is 5–10 business days from the moment we have access to your staging environment, your branch data and a Google Maps API key. Simpler single-store-view builds land sooner; heavy theme or PWA/GraphQL integration can extend it. We confirm a firm timeline in writing before starting.

Do you provide ongoing support and updates?

Yes. The build fee covers a warranty period for defect fixes after handover. Beyond that, we offer optional support and maintenance — Magento version-compatibility updates, Google Maps API changes, and enhancements — on a retainer or per-request basis. Because you own the unencrypted source, you are never locked to us.

Will it work on both Magento Open Source and Adobe Commerce?

Yes. The module targets standard Magento 2 framework APIs (service contracts, di.xml, UI Components, GraphQL), so it runs on both Magento Open Source and Adobe Commerce. We tailor scope-aware config and any Commerce-only touches (such as additional ACL granularity) to your edition during the build.

Does it require Google Maps API billing, and is it upgrade-safe?

It uses the Google Maps JavaScript API plus Geocoding, which require your own Google Cloud API key with billing enabled; we help you restrict the key by domain and IP. The module itself is upgrade-safe — it uses plugins (interceptors) and di.xml preferences with no core-file edits, so it survives Magento minor and patch upgrades.