HELP CENTRE
Getting a straight answer out of it
MapLogics takes an address and tells you who covers it and what should happen next. This page covers the ideas, the setup, and what to do when an answer surprises you. If you are calling the API, the API reference has the request and response shapes, every reason code and every error.
The six words that matter
Everything else is built from these. They are worth five minutes now because every screen and every answer uses them.
- Location
- A place you work from. A branch, a depot, a franchisee. Locations are who does the work, not where the work is.
- Territory
- A shape on the map, usually assigned to a location. Territories are where the work is. One address can fall inside several.
- Layer
- A group of territories that belong together, such as sales areas or service areas. Layers let one address be in a sales territory and a service territory at once without the two competing.
- Service
- Something you offer. A territory can cover an address for plumbing and not for HVAC, which is why the answer depends on what was asked.
- Rule
- A condition that changes the answer. Exclude a postcode, prefer one branch over another, refuse work outside opening hours. Rules run in order and each one says why it fired.
- Configuration version
- A snapshot of every territory, rule and assignment, frozen at the moment you publish it. Nothing you edit affects live answers until you publish, and a published version never changes afterwards.
Setting it up
The order matters. Each step needs the one before it, and the whole thing takes about twenty minutes for a first territory.
- Add your locations. Branches, depots, the people who do the work. You can type them in or import a spreadsheet. Each one needs an address so it can be placed on the map.
- Add the services you offer. Even if there is only one. Answers are per service, so this is what lets you cover an address for one thing and not another.
- Draw or import territories. Draw on the map, build one from a radius around a location, or import postcodes, counties and states. Assign each to a location.
- Add rules, if you need them. Most people start with none. Add one when the map alone gives the wrong answer, and only then.
- Test before you publish. Check a list of addresses you already know the answers for. This is the step people skip and regret.
- Publish. Until you do, nothing you have built affects a live answer. After you do, the version is frozen and you can roll back to it.
When the answer is not what you expected
Every answer carries a reason code that says which step decided it. Find the code in the response, or in Activity, and start here.
NO_TERRITORY_COVERS_POINT no coverage No territory covers this address. Extend a boundary or add one to cover it.
ALL_CANDIDATES_INELIGIBLE unserviceable A territory covers this address, but no assigned location can perform the requested service. Check the capabilities on those locations.
EXCLUDED_BY_RULE unserviceable Every candidate was removed by an exclusion rule.
EQUAL_PRIORITY_OVERLAP ambiguous Two or more territories are equally eligible and nothing breaks the tie. Set an explicit priority, or narrow one boundary.
ADDRESS_NOT_FOUND invalid input No geocoder could place this address. Check it for typos, or send a coordinate instead.
ADDRESS_TOO_IMPRECISE invalid input This address could only be placed to a postal code or region, which is not precise enough to route: a boundary can run through it. Add a street number, or send a coordinate.
The API reference lists every code, including the ones you will only see if something is wrong on our side.
Limits
What each plan holds. These are the numbers the product enforces, not a guide: the day one of them changes, this table changes with it or the build fails.
| Plan | Territories | Locations | Checkers | Requests a second |
|---|---|---|---|---|
| Trial | 25 | 50 | 1 | 5 |
| Starter | 100 | 250 | 3 | 10 |
| Growth | 500 | 1,000 | 10 | 30 |
| Network | 2,000 | 5,000 | 25 | 45 |
| Enterprise | 5,000 | 20,000 | 50 | 60 |
There is no monthly cap on decisions on any plan. The requests-a-second figure is a burst limit that protects the service; going over it returns a rate-limit response rather than a bill.
Still stuck
Email hello@maplogics.com with the request id from the response, or the address and service you were checking. The request id lets us see exactly which territories were considered and which rule decided, which is usually a two-minute answer instead of a two-day one.