A sourced comparison
Handled Locator vs Bullseye Locations.
Bullseye Locations sells a dealer and store locator as part of a wider location-marketing platform: lead capture and routing to dealers, location landing pages, and integration with the systems a channel-sales team already runs.
AI answer engines name Bullseye Locations more often than any other product when asked about store locators, which is why this page exists. It is not, for most readers, a real choice between two similar things. Handled is an embeddable locator you configure yourself in an afternoon. Bullseye is a platform bought to run a dealer channel, and the parts of it that justify the difference are precisely the parts Handled does not have.
Handled wrote this page, and Handled is one of the two products on it. Treat it as a vendor comparison, not a review. Every figure in the other column is what that vendor published on its own site on the date below, and a vendor can change its pricing and features the day after we read them.
Bullseye Locations pages read on September 7, 2026. Check the current version before you buy either product.
We could not read bullseyelocations.com from our own checks on the date below; every request was refused. So this page publishes none of their prices, plan names or capability claims, and no cell below describes what Bullseye can or cannot do. Read their pricing page yourself. A comparison that invents the other column is worse than one that admits it is half a page, and this is the half we can stand behind.
Side by side, with nothing in the Bullseye Locations column we did not read on their site.
| Decision point | Handled Locator | Bullseye Locations |
|---|---|---|
| What you are buying | An embedded locator, and nothing else. One script tag on a site you already own, configured in a dashboard, with the visitor experience as the whole product. | A location-marketing platform, positioned around dealer and channel programmes rather than around the embed. Confirm the current scope with Bullseye. |
| How you buy it | Self-serve. Published prices from $19 a month, a 7-day trial with no card, and a card at the end of it. Nobody has to talk to us. | Bullseye publishes plan pricing on its own pricing page. We do not reproduce the figures here, because our checks could not read the page and a price we cannot source is not one we will print. |
| Generated location pages | Not built. Handled embeds into pages you already have and generates none of its own, so it adds no indexable pages to your site. If a page per location is the point of the purchase, we are the wrong product and say so on our features page. | Location landing pages are part of what Bullseye is known for. Ask them for the current specifics rather than taking our word for the category. |
| Lead capture and routing to dealers | Built, within limits worth reading. An optional enquiry form appears in the locator after a search, off until you turn it on. The visitor does not choose who receives it: the enquiry is routed to the dealer whose published postcode territory covers the address, then to the fallback location you set, then to the nearest. That dealer is emailed with the reason they were chosen, replies reach the customer, and they mark it handled from a link in the email with no login. Every enquiry is listed under Leads. What Handled does not do is deliver it anywhere else: no webhook fires, nothing is pushed to a CRM, and there is no dealer portal or pipeline beyond that one status link. | Lead management and routing are central to how Bullseye positions itself. Their own documentation is the place to check what it does. |
| Managed CRM or ERP synchronization | Not built. Handled emits no webhooks and runs no bidirectional sync. There is a REST Location API and a Query API with scoped keys, so a scheduled job in your own system can push and pull, but you write and run that job. | Integration with existing sales and marketing systems is part of the platform pitch. Scope it with them directly. |
| Locators per account | One. An account styles and serves a single locator, because the embed snippet carries an account id and no configuration id. If you need two different locators on one site, this is the wrong product today. | Multi-brand and multi-interface handling is something to ask about if you run several brands from one programme. |
| Map billing | You create your own Mapbox or Google Maps key. That provider meters and bills your map traffic directly, and Handled adds no margin to it. It is one extra setup step and it is the reason our sticker price is not the whole cost story either. | Not stated in anything we could read. Ask how map usage is priced, because at dealer-network traffic it is not a rounding error. |
| What Handled does have | 85+ widget settings, CSV and Google Sheets ingestion with change review, service areas, online stockists, featured locations, postcode dealer territories with an explicit publish step, an optional enquiry form routed to the territory owner, owner, admin and editor roles, a public REST and Query API, and a bundle under 100 KB gzipped. | Compare these against the equivalent parts of their locator rather than against the platform as a whole, which is a different purchase. |
Sources: Bullseye Locations, Bullseye Locations pricing. Figures are as published on Bullseye Locations’s own site and may change without notice. Handled figures come from the same constants our checkout charges against.
What we left out, and why.
A missing row is the honest outcome when a vendor has not published something. Filling it in from memory is how comparison pages become fiction, so these are named instead.
- Every Bullseye price, plan name and location limit. Their site refused our requests, so we quote none of them.
- Any claim that Bullseye does or does not have a given capability. We have not verified one, so we assert none.
- Third-party review-site figures for Bullseye. Aggregators go stale silently, and a price we did not read on the vendor's own page is not a price we will publish.
What Handled does not do.
The same list we publish on our own features page, unedited. If one of these decides your purchase, we would rather you found it here than three weeks into a trial.
A page per location
The locator is embedded in your site rather than generating indexable pages of its own.
Managed CRM or ERP synchronization
Handled does not currently maintain a live CRM or ERP connection, emit webhooks, or run automatic bidirectional synchronization. Use the REST and Query APIs from a scheduled job in your own system when you need one.
Scheduled banners and promotions
No rules engine for showing a message in a region during a date range.
More than one locator per account
One account styles and serves one locator. There is no per-page variant showing a filtered subset of your locations, because the embed snippet carries no configuration id.
Translated location details
The locator's own controls can be held in several languages and matched to each visitor. Your location data cannot: a store's name, description and custom fields are stored once and read the same to everyone. Platforms that do translate the data give each language its own copy of every location and its own locator, which is the gap above as much as this one.
County, state and drawn territory areas
A territory is a list of postcodes, which is how most dealer agreements are written anyway, and a service area is a radius the map draws. A county or a state cannot be picked by name in the dashboard: the rule can be stored and the engine resolves it, but there is no region picker to author one and no boundary data is loaded outside the United States, so a rule naming a British county or a Canadian region covers nothing. There is no drawing a shape on a map at all.
Leads delivered into your own systems
The locator can take an enquiry and route it to the dealer whose territory covers the address, email them, and list it under Leads. What it will not do is put that lead anywhere else: there is no webhook when one arrives, no CRM or ERP push, and no dealer login. A dealer works from the email and its one-enquiry status link, and your team works from the dashboard. There is no leads endpoint on the API either, so if the record has to live in the system your sales team already uses, this does not put it there.
Best for us
Choose Handled when
- You want a locator on a website, not a channel-marketing programme.
- Your dealer agreements are written in postcodes, and you want the map to respect them and an enquiry to reach the dealer who holds that ground, without buying a channel-marketing platform to get it.
- You want to buy it today at a published price without a demo call.
- Your locations are your own, or a dealer list you already maintain in a spreadsheet.
- You would rather pay your map provider directly than have map traffic priced into a platform fee.
Best for them
Choose Bullseye Locations when
- You need an indexable page per location. Handled does not generate them, and that alone can decide the purchase.
- The enquiry has to land in the CRM your sales team already works in. Handled captures and routes one to the owning dealer and keeps the record itself, but it pushes that record nowhere else.
- The locator has to stay in step with a CRM or ERP without you writing and running the job that does it.
- You run several brands or several locators from one programme, which Handled cannot do at all today.
- You want scheduled promotions or regional banners in the locator, which Handled has no rules engine for.
Try both against the same brief.
Load the same locations, filters, fields and brand direction into each product. The one your team can keep useful six months after launch is the right answer, and no table settles that.