For partners

Bring AI optimisation to your customers from your own system

Your customers manage jobs, customers and billing in your ERP, FSM or TMS. Allocator handles what's usually still manual work in the main system — routes, schedules and replanning the day when something changes. Integrate once, and every one of your customers gets optimisation without switching systems.

Allocator already works with these systems

Optimisation you don't have to build yourself

Route and schedule optimisation is a product of its own. The engine has to weigh time windows, skills, vehicle capacity, shift rules and contract terms all at once, and produce a new plan in seconds when someone calls in sick at 6:54am. As a partner, you get this ready-made alongside your own product, and can keep your focus on your core offering.

  • An answer to your customers' question

    When a customer asks "can the system plan routes?", the answer is yes. In a competitive tender, that's often the deciding feature.

  • No competition with your core product

    Allocator doesn't replace the main system. Jobs, customers and billing stay in your system.

  • Stickier customer relationships

    Once optimisation is connected to the main system, the integration makes the whole setup harder to replace.

  • Joint go-to-market

    We bring up our integration partners in our own sales conversations, and tell customers which main systems Allocator already works with.

Two ways to connect your system to Allocator

  • One-way

    Tasks and resources go from your system to Allocator. Nothing comes back.

    Planning happens in Allocator, and field workers use Allocator's mobile app. It's the lighter build.

  • Two-way

    Tasks and resources go from your system to Allocator. Schedules and job statuses come back.

    Two-way keeps everything in sync between Allocator and your business. Field workers can use Allocator's app or something else.

Who builds it is up to you

Allocator's REST API and webhooks are documented.

  • Our team
  • Your developers
  • A third party

What your customers get once optimisation is connected to the main system

Our customers' average results are 31% less driving, 18% more billable hours and half the time spent planning. Integration also removes double entry — a new job is created in the main system, moves into Allocator's plan, and shows up on the worker's phone without anyone copying it by hand. Once the job is done, the completion and the hours flow back to the main system for billing. In practice, your customer's supervisor no longer builds tomorrow by hand every evening. Sick leave and cancellations are handled in five minutes, and all the data still lives in one system.

−31% driving
+18% billable hours
−50% time spent planning
AI frees up time for our supervisors. That time goes into improving the customer experience, which makes the whole installation operation more efficient. Our installers save time too, in the kilometres they no longer drive.
Timo Kyllönen Head of Installation, EcoUp

From the first conversation to your first shared customer

  1. Discovery call

    We go through your system's data model and customer base.

  2. Choosing the integration

    Choosing the integration type and building it in a test environment.

  3. Pilot

    A pilot with one shared customer.

  4. Launch

    Your logo on our site, and joint marketing.

Tell us about your system

Give us a short description of your product and your customers, and we'll get back to you soon.

This form doesn't submit anywhere yet. Press "Send" and your answers open as a pre-filled email instead.

Integration options in detail

Allocator brings route and schedule optimisation into your ERP, FSM or TMS. Ready-made connectors exist for AVUX, Likeit, Admicom, Allteq, Reslink and Abacus; any other system connects through Allocator's documented REST API and webhooks, one-way or two-way.

One-way integration

Tasks and resources move from your system into Allocator, and nothing comes back. Planning happens entirely in Allocator, and field workers use Allocator's mobile app. A customer's own app can't be used, because it would get its schedule through your system, which receives nothing back. It's the lighter build, but not a first step toward two-way. If your customers need the results back in your system, build two-way.

Two-way integration

Tasks and resources move into Allocator, and schedules and job statuses come back to your system. Your system keeps running the whole business, from inventory and company-wide operations to work-time reporting, while Allocator only handles the mobile workers. Field workers can keep their current mobile app or use Allocator's. A two-way ERP integration is a separate project without a fixed timeline, because it usually depends on the ERP provider.

REST API and webhooks

Either option can be built by our team, by your own developers or by a third party. Allocator's REST API and webhooks are documented. Jobs go in through the API, optimised plans come out, and webhooks can push plan changes back to your systems in real time.