Distribution

Optimise delivery and document the cold chain.

Routes optimised with Google OR-Tools on vehicle capacity and delivery windows. Driver app with proof of delivery. A transport temperature record per delivery leg, exportable for inspection (Spain: ATP transport evidence, RD 237/2000).

See distribution in demoSee pricing →

What does the optimiser decide, and what does it only record?

It builds routes against two hard limits: what fits in the van and when each stop can receive. Temperature is not one of them. The driver app collects proof of delivery, and each leg carries its own temperature record — evidence you export for an inspection, not a rule the solver enforces.

Calculates the optimal route respecting delivery windows and van capacity. Each leg carries its own temperature record, and the compliance documentation generates itself, per jurisdiction.

What does this cost today?

  1. Routes by eye every dayThe distribution lead plans in Excel. One extra shop = 30 minutes of manual replanning.
  2. Cold chain unloggedDid it go above 4°C? Your driver thinks not. Inspection wants to see the log. You don't have it.
  3. Delivery without proofCustomer says they didn't receive. Your driver says they did. No photo, no signature. You lose the dispute.

Before / After

And what changes on an ordinary Monday?

Manual planning vs. automatic VRP.

TodayWith BakeWise
30 min daily planning routes in Excel.Optimal route computed in 30 seconds.
Nobody logs temperature during transit.Temperature logged automatically by the driver app.
Delivery disputes without proof.Photo + signature + PIN on every delivery.

Which numbers can you check?

  • 25%

    km reduction

  • 1

    temperature record per delivery leg

  • 3

    Proof types

  • 30s

    VRP computation

What is underneath?

  1. Google OR-Tools VRPVRP solver with delivery windows and vehicle capacity as constraints.
  2. Driver app (PWA)Offline proof-of-delivery, syncs when coverage returns.
  3. Transport temperature evidenceEvery leg carries its temperature log — sensor or manual — traceable to the batch and exportable to an inspector. The route itself is optimised on capacity and time windows; temperature is evidence the delivery carries, not a constraint the optimiser enforces.
  4. Cold-chain breach rankingPrioritizes alerts when a route repeatedly breaks cold chain. Group.

What else gets asked before deciding?

  • How many delivery points does it optimize?

    Up to 50 per route, 200 per fleet. For larger networks, hierarchical pre-clustering. Google OR-Tools.

  • How is the cold chain documented for an ATP inspection?

    With a temperature log per delivery leg (IoT sensor or manual entry in the driver app), out-of-range alerts, per-batch and per-route traceability and exportable reports. The transport rule in Spain is the ATP (RD 237/2000, amended by RD 402/2021); RD 1021/2022 governs retail display temperatures, not transport.

  • What if the driver loses coverage?

    App works fully offline. Saves proof of delivery locally and syncs when coverage returns. No delivery lost.

  • What proof types are supported?

    Photo (mandatory by product type), receiver digital signature, numeric PIN sent to customer via SMS/email.

  • Does it work with 2 vans or do I need 10?

    From 1 van. VRP remains useful for optimal sequence + windows. Optimization savings kick in at 4+ delivery points.

See distribution in demo

See distribution in demo