How do you run deliveries across more than one site?
Treat each site as its own dispatch point with its own drivers and its own coverage area, and keep one view across all of them. The common failure is the opposite: one shared pool of drivers dispatched centrally, which produces couriers driving past one branch to collect from another.
Per site, not per group
Orders should be dispatched from the site that prepares them. That sounds obvious until an order taken centrally has to be routed, at which point the system needs to know which kitchen it belongs to before anyone can be assigned.
Drivers attached to a site should default to that site's work. Sharing capacity across sites is useful as an overflow, not as a default.
One view for the operator
Whoever is responsible for the group needs to see every site at once: what is late, where capacity is short, and which site is paying for network deliveries because it is under-staffed.
Per-site reporting matters more than group totals. A group average hides the one branch that is failing.
Scorto dispatches per site, with each site's own couriers assigned first and the freelance network as overflow, and reports per site as well as across them. Territories are enforced on the delivery address automatically, so an order outside a site's coverage does not silently get accepted.