Handled Local → Handled Locator
Handled Locator is the store locator product made by Handled Local.
It is built for brands and multi-location businesses that want a searchable locator on the website they already own, without turning every location update into a development ticket.
Why it exists
The map is only useful when the surrounding work is manageable.
Publishing a locator is not just placing pins. The recurring work is cleaning a spreadsheet, preserving hours and categories, making search useful, matching the website and keeping the installation stable as the location list changes.
Handled Locator keeps those jobs in one product: location management, visitor search, brand controls, a responsive embed, analytics and documentation written around the task being completed.
What it is
A hosted locator that lives on your own website.
Handled Locator is store locator software for brands, dealer networks, stockists and multi-location businesses. A location can be a storefront with a pin, a service area with a radius the map draws, or an online stockist shown in its own tab. Locations come in by hand, from a reviewed CSV import, from a synced Google Sheet, Airtable table, Webflow collection or HubSpot list, or through the API. It installs on Shopify, WordPress, Squarespace, Webflow, Wix and any page that accepts HTML. Plans start at $19 a month after a 7-day trial that needs no card.
One line of script on your page
The locator is a single custom element that renders in a shadow root, so it cannot collide with the website's CSS. It stays under 100 KB gzipped, loads after the page rather than blocking it, and has been verified on a third-party origin in Chromium, Firefox and WebKit.
Settings live in the dashboard, not the snippet
85+ settings cover search, results, filters, hours, maps, markers, layout, links and formatting. Change one and the live locator picks it up; nobody touches the embed again after pasting it.
Your map key, your map bill
The map is drawn with a Mapbox or Google Maps key from the customer's own account. That provider meters and bills map traffic directly, and Handled adds no margin to it. The subscription pays for the locator, location capacity and team seats.
Visitors are not tracked
The locator sets no cookies on visitors, does not track them across sites and builds no profile. Browser events it dispatches for a site's own analytics leave out what the visitor typed, their coordinates and any contact details.
Credentials are stored as hashes
API keys and AI assistant connections are kept as one-way hashes rather than usable credentials, so a copy of the database is not a working key to anyone's locator. Servers and the database are in the United States.
Operable by people, code and assistants
The same account can be run from the dashboard, from the Location API and webhooks, or from Claude and ChatGPT through an MCP server. Configuration changes made through an assistant are proposed with the exact differences first, and every version can be restored.
How we work on it
A few working rules, and what they mean for you.
- Prefer undo to confirmation.
- Deleting a location offers an undo instead of an are-you-sure dialog, and every configuration version is kept. A confirmation charges every customer a click to protect the few who did not mean it.
- Say what a control cannot do.
- Each feature page states its boundary, and the features page lists what is not built. A claim the product cannot keep is either made true or removed.
- Numbers come from the product.
- Prices, location capacities, seats and the trial length quoted across this site are read from the same plan definitions the product enforces, so a page cannot quietly go stale when a plan changes.
- Name competitors carefully or not at all.
- Comparison pages date every competitor cell, link the vendor's own pages as sources, and say so when a vendor's site did not answer a question rather than guessing.
How the product is presented
Evidence before adjectives.
A young product has to make it easy to check what is real. These are operating choices, not a claim that every possible locator feature already exists.
- Pricing, location capacities and team seats are public.
- Feature pages connect claims to real product captures and task documentation.
- The features page names 5 important capabilities that are not built yet.
- Live examples use invented brands and sample data rather than presenting concepts as customers.
- Customers can export their location data instead of relying on lock-in.
- Sales, support, feature and privacy questions all reach hello@handledlocal.com.
Who makes it
Handled Local, at handledlocal.com.
Handled Locator is made and operated by Handled Local, which can also help with the surrounding website, design and implementation work at handledlocal.com. The same team configures the done-for-you brand match included with active paid plans, answers support at hello@handledlocal.com, and publishes the documentation and the developer reference for everything described on this page.
A real question should reach a real person.
Ask about setup, pricing, a missing feature or what Handled stores. The reply comes from Handled Local rather than an anonymous software marketplace profile.
Contact Handled Local