Search Results

The first question on Re-checking orders already with a carrier only cancels a slow carrier if there is a genuine alternative ready to take over. That check has two independent halves — whether your own fleet could take it, and whether another Third-Party carr...

Every order is ultimately resolved using one — or a combination — of three mechanisms. Mechanism When it's used PG Mode (FIFO) You have enough own drivers to cover pending orders Google OR-Tools There are more pending orders than own drivers, so routes need pl...

After the own solver and the Third-Party attempt have each had their one shot at an order, some orders may still be unassigned. Rather than leaving them for the next cycle straight away, the dispatcher makes one more attempt — per store, at the end of the same...

Drivers are ranked by three things: their current status, their type, and how close they are to the store. By status Status Description Idle Has zero orders currently assigned — fully available Waiting Has orders assigned, but none have left the store yet On T...

This page only applies if your account has Priority Customers (Platinum) evaluation enabled. It is not part of the core flow — it runs as an extra layer on top of it, only for stores where it's switched on, and only when there are Platinum orders to consider. ...

Before every assignment attempt, the dispatcher checks whether an order already assigned to one driver should instead go to a different one — but only on driver priority, never on how urgent or important the order itself is. When a reassignment is allowed Situ...

The dispatcher runs on a schedule you define per store, or per group of stores. Scheduling and assignment behaviour are configured together, in the same plan. How the automatic cycle works Each plan defines how often the dispatcher should run for a group of st...

Beyond the scheduling plan, several other parts of the product hold settings that directly affect dispatcher decisions. This page lists them by where you'd actually go to change them, and only includes settings you can edit. For the scheduling plan itself, see...

A one-page summary of the rules that come up most often. Each links to the page that explains it in full. Rule Behaviour Orders already out for delivery Never revalidated, never reassigned — only used to estimate when the driver returns Orders still waiting to...

These are intentional design limits, not faults. Knowing them keeps expectations realistic and saves time when something looks wrong but isn't. No proactive rebalancing The dispatcher never moves a regular order out of a driver's route just to make room for a ...

The full path a store's orders take in a single cycle, pulling together everything in this chapter. One cycle, one store Fetch orders and drivers for this store. Orders already sitting with a Third-Party carrier from an earlier cycle are re-examined here — see...

If something looks wrong — an order assigned to the "wrong" driver, delayed, or stuck unassigned — the fastest way to get it resolved is to report it with the right information the first time. Screenshots alone, especially of unrelated screens, rarely help. Sp...

Why did an order suddenly get reassigned to a different driver? A driver with better priority became available — for example an idle driver at the store, or an internal driver where before only an external one was free. See When an order changes driver for the...

You need: Pause / resume delivery — held by admin, hub_manager, dispatcher_manager and branch_manager. Viewing the status only needs store read access. Pausing delivery stops a store taking new delivery orders for a set time, without closing the store or t...

You need: Delivery zones — view to browse, Delivery zones — edit to change anything. Held by admin, dispatcher_manager and polygon_manager. A zone is a delivery area with a map polygon and a set of rules deciding which drivers and carriers serve it. Zones a...

You need: Third-party — view to browse, Third-party — edit to change. Held by admin, dispatcher_manager and third_party_manager. Per-store carrier settings are also reachable by hub_manager. Carrier configuration exists at two levels, and knowing which one...

You need: Store config — view to browse, Store config — edit to change. Held by admin, hub_manager, dispatcher_manager and branch_manager. Each store carries its own dispatcher settings, separate from the scheduling plan that governs when the dispatcher ru...

You need: the view or edit permission for whatever the backup contains — not a separate backup permission. A zones backup needs delivery-zone access; a carrier backup needs third-party access; an employee backup needs employee access. Every time you export con...