1Start from a clear scenario

In the technical Route Builder examples we always start from a concrete case: a single store with its own fleet, a group of stores in one Zone, or a delivery company serving many brands. Each case leads to a different combination of plan (Semi-Auto or Auto), route capacity and waiting windows.

2Tune the waiting windows

There are settings that control how long the engine waits before it “locks in” a route for a driver. Short waiting windows keep orders moving fast but usually mean fewer stops per route. Longer windows give the system time to group nearby orders into the same route (bundling), at the cost of needing closer monitoring so that delays and SLA breaches do not increase.

3Choose route capacity wisely

One of the most important knobs is the upper limit on how many orders you allow in the same route and –in the Auto plan– any per‑driver limit. In fast‑food style operations, starting with 2–3 orders per route usually gives couriers enough visibility without overloading them.

4Semi-Auto or Auto for peak?

The case studies typically recommend the Semi-Auto plan when you have a shift manager who wants to approve proposals, and Auto when volume and scale require full automation with clear SLAs. In both cases you get full auditability: you can see which couriers were considered for each route, which one was finally chosen and how the delivery progressed.

5Experiment in simulation first

Before changing live settings, run simulations with your own numbers (stores, drivers, SLAs) and see how routes, delays and load distribution change. This makes shifting to a new peak‑hour setup much more predictable.