Store Locator for Magento

None of those. The locator embeds into a CMS Page or Page Builder block as a single line of HTML, similar to dropping in a YouTube embed. No composer require, no bin/magento module:enable, no third-party namespace registered in your Magento codebase. The store locator software lives on Storepoint's infrastructure, your Magento install stays untouched.

All three, same snippet. The locator is hosted, so PHP versions, MySQL versions, deployment topology (on-prem vs Cloud), and whether you're running 2.4.x or migrating to 2.5 don't change the integration. One embed serves your entire Magento estate including multi-store and multi-website setups.

Sign up at app.storepoint.co/dashboard, add your locations or import them, copy the snippet from the Embed sidebar. In Magento admin, edit a CMS Page or drag a Page Builder HTML widget, paste, save. Buyers get search by city or postcode, filters for product, brand, dealer type, or anything else you want to tag, autocomplete, GPS auto-detect, and one-tap directions. 200 pins on Starter, 2,000 on Pro, 10,000 on Business with marker clustering.

Yes. Storepoint runs outside your Magento codebase, so deploy commands and mode switches between developer and production leave it untouched. Magento's RequireJS map, static asset compilation, and generated/ directory cleanup all stay focused on your own modules. The embed renders the same way before and after every deploy.

No. Locations, settings, brand styles, search analytics, and Spotlight territory rules all live on Storepoint's infrastructure, leaving your Magento database unchanged. If you ever remove the locator, deleting the embed line is the entire cleanup. The database keeps its current schema, with no migration scripts required.

All of them. Storepoint is plain HTML and JavaScript loaded from our CDN, so Hyvä's no-Knockout architecture, Luma's RequireJS layer, and PWA Studio or Vue Storefront headless setups all render the locator the same way. We've matched designs for Hyvä-themed stores, custom Luma builds, and React-based headless storefronts.

Use Spotlight (Business plan). Draw a polygon or radius for each territory directly on the dashboard map, then attach a "show only these dealers" rule. Customers searching within the territory see only the authorized dealers for that region, regardless of which locations are technically closest. Same setup handles franchise catchment areas, exclusive distributor regions, and authorized service zones for B2B Magento stores.

Yes, through Priority Sorting (Pro plan and above). Tag your premium dealers ("premium-partner") and authorized distributors ("certified-dealer"), then create rules that boost them to the top of results within a distance limit. A typical manufacturer setup: Premium Partners boosted within 50 miles, Certified Dealers boosted within 25 miles, everyone else by distance. Combine with Spotlight for full B2B dealer-network control.

Clustering, geocoding, and search run on Storepoint's infrastructure, not your Magento server. So whether you display 10 stores or 10,000 dealers, TTFB and storefront rendering stay unaffected. Magento's full page cache and Varnish layer cache the static page; the locator hydrates after the page is interactive without invalidating any cache entries.

Yes. Beyond what's covered above, Storepoint includes filters with multiple filter groups (filter by product, service, certification, brand, or anything else you want to tag), Custom Fields for per-location buttons (Book Now, Buy Online, View Menu, social links), custom map markers and themes (different markers by location type, product, or service), keyword search, GPS geolocation, opening hours with live open and closed status, multilingual labels, search analytics, territory rules, Google Sheets and CSV sync, full custom CSS for designers, and developer APIs. On Magento specifically, that includes Hyvä, Luma, headless PWA Studio storefronts, and Adobe Commerce B2B configurations. If you have a specific feature in mind for your use case, it's likely already built in. Explore all features . Don't see what you need? Email [email protected] and we'll help you find a path with what's built, or work with you to add what's missing.