Dispatch and delivery software for e-commerce with its own fleet

We prove we're better, or we refund everything. And you keep the solution.

How

We measure it with an A/B experiment in your live operation, against what you use today, with the metric, method and duration agreed before we start.

  • Tailored to your deliveries
  • Integrated with your shop, OMS and WMS
  • Dedicated instance in the EU
FIG. 1 — Your solution, tailoredon top of what you already have
01 / Sound familiar?

You promise a time slot at checkout. Your deliveries have to keep that promise, order by order.

  • 1.1

    The slot your customer sees doesn't always match your delivery capacity.

    And when it doesn't, the delays, calls and complaints follow.

  • 1.2

    During sales and campaigns, volume multiplies.

    Yet orders are still assigned as if it were any old Tuesday.

  • 1.3

    The last mile eats into your order margin.

    And nobody knows for sure which decisions make it more expensive.

  • 1.4

    Nobody can prove how much a change improves things.

    A before/after comparison can't separate the improvement from everything else that changed: campaigns, season, staff.

02 / Tailored

Built around your deliveries. Not the other way round.

We don't ask you to change how you sell or deliver to fit a piece of software. We start from your operation and build the solution on top of it.

Specification · your solutiondefined in the first meetings
Fleet
Yours, in-house or mixedEmployed drivers, freelancers or a mix, with their capacities and shifts.
Delivery slots
The ones your shop offersWith their cut-off times and priorities.
Rules
Your operation'sNot those of a generic template.
Systems
The ones you already haveOnline shop, OMS, WMS and ERP. No migration.
Driver app
Yours, extendedIf you already have one, we add what's needed. If not, you use ours.
Success metric
The one you chooseAgreed before the experiment.
Instance
Yours aloneIsolated, in the EU. We run it.
03 / The solution

Three pieces, one solution, tailored to your deliveries.

We run it for you on an instance that is yours alone. You don't maintain any infrastructure.

  1. Piece 1 / 3

    The decision engine

    Decides in real time which driver takes which order and in what sequence, taking the promised slot into account, and measures how much it improves on your previous solution.

  2. Piece 2 / 3

    The operations console

    Your deliveries, live: manual dispatch, overriding an assignment with a reason, escalation and an explanation of every decision.

  3. Piece 3 / 3

    The driver app

    Receive and accept jobs, mark pickup and delivery, share location and capture proof of delivery. Already have an app? We extend it.

Console — “why this driver?”, with every decision explained and logged.
Driver app — ours, or yours, extended.

Integrates with what you already have.
No forced migration.

  • Online shop
  • OMS
  • WMS
  • ERP
04 / How we work

Four steps. The last one is our risk, not yours.

  1. Step 1

    Meetings and requirements

    We get to know your deliveries: fleet, slots, zones, campaigns and systems.

  2. Step 2

    We build it to measure

    The solution, adapted to your operation and integrated with your shop and your systems.

  3. Step 3

    A/B experiment

    In your live operation, against your current solution. Metric, method and duration agreed up front.

  4. Step 4

    No improvement, full refund

    Onboarding and licences. And you keep the solution.

05 / Measurement

A before/after proves nothing. An experiment does.

Between before and after, volume, campaigns, staff and customers all change. That's why we alternate your current solution (A) and Pontro (B) in the same operation, on the same days, and compare the metric we've agreed with you.

B · Pontro
A · today
08:0011:0014:0017:0020:00

Example: time blocks within a single day are randomly split between A and B. The same conditions for both.

Before / after

  • Different periods, different conditions
  • The vendor chooses the baseline
  • Impossible to isolate its effect from everything else

A/B experiment

  • A and B in the same operation, on the same days
  • Metric, method and duration in writing, before we start
  • Results your team can audit
06 / Pricing

A model with a single incentive.

We send you a proposal after the first meeting: it depends on your operation.

Onboarding
A fixed fee for building your solution and integrating it with your shop and your systems.
Licence per order delivered
You pay for the orders the solution delivers. If your sales stand still, so do we.
If we don't prove an improvement
If the agreed experiment doesn't prove we're better than your current solution, we refund onboarding and licences, and you keep the solution.

We only win if you win.

07 / Team and trust

Who's behind it, and where your data lives.

Founded by the engineers who built Glovo's dispatching system.

We know what it takes to make decisions every minute while the streets keep changing and the customer is waiting. Now we do it around your deliveries.

Dedicated instance
Isolated from every other customer.
Data in the EU
In our dedicated cloud, within the European Union.
GDPR
Processing compliant with the GDPR, by contract.
Perpetual licence
If our company disappears, the solution remains yours.
08 / FAQ

What people ask us before the first meeting.

How is the improvement measured?

With an A/B experiment in your live operation: your current solution and Pontro alternate in the same operation, on the same days. The metric, method and duration are agreed in writing before we start.

Which metrics do you use?

The ones that matter to your business, chosen with you: for example deliveries within the promised slot, cost per order, orders per driver hour or late-delivery complaints. We set one primary metric before we start.

Do I have to replace my online shop, OMS or WMS?

No. We integrate with your online shop and with the systems you already have. We don't force you to migrate.

Does it work with employed and freelance drivers at the same time?

Yes. The solution is built on your fleet as it is: in-house, freelance or mixed, with their capacities and shifts.

How long does it take?

It depends on your operation and your integrations. After the first meeting we give you a firm timeline to the start of the experiment.

Where is my data?

In your dedicated instance, in the EU and isolated from other customers, in line with the GDPR. And if Pontro were to disappear, you hold a perpetual licence to the solution.

What exactly is refunded if you don't prove the improvement?

The onboarding and every licence fee paid. And you keep the solution, with a perpetual licence.

Do you have real dispatching experience?

Yes. Founded by the engineers who built Glovo's dispatching system. Right now we are designing and implementing the dispatching system of a last-mile delivery company.

Let's talk.

A first conversation to understand your deliveries and tell you whether we can prove an improvement. If we can't, we'll tell you.

Tell us who you are and what your operation looks like. We'll reply by email.

Orders per day or fleet size