> ## Content Index
> Fetch the complete content index at: https://human-business-works.ghost.io/llms.txt
> Use this file to discover other available public pages before exploring further.

# Why a Second Distribution Hub Rarely Doubles a Delivery Business's Capacity
- URL: https://human-business-works.ghost.io/second-distribution-hub-delivery-capacity/
- Published: 2026-10-30T15:00:00.000Z
- Updated: 2026-10-30T14:59:59.000Z
- Description: Opening a second hub feels like doubling a delivery business's reach, but route density economics mean the new territory often starts from near zero. Here's how to judge if it's worth it.
- Author: Human Business Works
- Tags: logistics, operations, delivery, scaling, growth

## The math founders skip

A regional courier operator running twenty vans out of one depot decides to open a second location forty miles away, in a market with real demand. On paper the move looks straightforward: double the depots, double the coverage area, and eventually double the revenue. The spreadsheet usually shows the lease, the new hires, and the fuel budget. It rarely shows what happens to the routes that already work.

Delivery businesses don't scale on square miles covered. They scale on stops per mile driven, which is a function of how tightly customers cluster around a depot. Industry research on last-mile delivery, including work from the University of Arkansas's Walton College supply chain research initiative, has long pointed to delivery density, the number of drop-offs achievable per mile of driving, as the dominant cost driver in courier and parcel economics. A single depot serving a well-mapped, densely packed territory can run trucks nearly full and routes nearly tight. A second depot, by definition, starts without that density. It has to build it customer by customer, block by block, often while the original hub is still absorbing the overhead of split management attention.

## Splitting the fleet splits the efficiency

The instinct behind a second hub is usually sound: demand is growing in an adjacent territory, and driving there from the existing depot eats too much time and fuel. The fix, opening closer to that demand, is directionally correct. The problem is what it does to the rest of the network.

When a fifteen-van fleet becomes two fleets of seven and eight, neither fleet has the route flexibility the combined fleet had. A driver who used to pick up slack from a nearby route now works in isolation, because the routes near the boundary of the two territories don't cleanly belong to either hub. Drivers on the edges spend more of their day driving between stops and less of it delivering. That unproductive driving time is functionally the same phenomenon the trucking industry calls empty miles, distance covered without generating revenue, and it tends to increase, not decrease, in the months after a second hub opens because both locations are still learning where their real boundary should sit.

This is the part operators consistently underestimate. Two half-full trucks don't equal one full truck. They equal two trucks burning fuel and driver hours to do work one vehicle could plausibly have done at higher density.

## Dispatch software doesn't know you have two depots

Most small and mid-sized delivery operators run dispatch and routing software that was configured, sometimes years earlier, around a single depot and a single service radius. The zone maps, the driver assignment logic, the customer database's default depot field, all of it assumes one point of origin.

Adding a second hub means someone has to go back into that system and rebuild the logic: which customers belong to which depot, how routes get split when an order falls near the boundary, how drivers get reassigned on days when one hub is short-staffed and the other has capacity. This is not a weekend project. It's ongoing configuration work, and until it's done well, dispatchers tend to fall back on manual overrides, phone calls, and spreadsheets on the side, which is exactly the kind of informal patchwork that automated dispatch was supposed to eliminate. Every manual override is a small tax on the day's efficiency, and it compounds across a growing driver count.

## Rebuilding density from zero

The hardest part of a second hub isn't the lease or the equipment. It's that the new location starts its delivery density curve over. The original depot likely took months or years to reach the point where routes were tight and vans ran close to full. The new hub doesn't inherit any of that. It has to sign customers, build a route map, and gradually pack stops closer together, the same slow process the original location went through, except now it's happening while the company is also paying rent, insurance, and staff for a location that isn't yet contributing proportional revenue.

This is the same trap that shows up when [regional banks rethink branch expansion](https://human-business-works.ghost.io/regional-banks-branch-expansion-strategy/): a new physical location carries fixed costs from day one, but the customer relationships and transaction volume that justify those costs take much longer to arrive. A delivery hub is no different. The rent starts on the first of the month. The route density that makes the hub worth having might take a year or two to materialize, if it materializes at all.

## A framework for judging the second hub

Before committing to a second location, operators can ask a narrower set of questions than the ones a real estate agent or growth consultant tends to pose.

First, is the new territory's demand dense enough on its own, meaning is there a customer base clustered tightly enough within a few miles of the proposed hub that routes could reach reasonable stop density within a defined window, typically six to twelve months, without relying on customers poached from the existing depot's edge?

Second, is the existing hub actually capacity-constrained, or is it geographically stretched? These are different problems with different fixes. A depot running full trucks on tight routes that simply can't reach a farther-out cluster of demand has a geography problem a second hub might solve. A depot with half-empty trucks driving long, sparse routes has a density problem that opening a second location will not fix and may make worse, because it splits an already thin customer base across two fixed-cost locations instead of concentrating effort on tightening the existing one.

Third, can the company's dispatch system and management bandwidth actually support two depots operating semi-independently, or will the second location function as an appendage that constantly needs oversight from the first? A hub that can't run its own daily dispatch decisions without the original location's manager weighing in isn't really a second hub. It's a remote outpost with its own rent bill.

The volume threshold that makes a second hub worthwhile isn't a company-wide revenue number. It's a local one: enough stop density in the new territory, reached fast enough, to offset the empty miles and dispatch friction the split will inevitably introduce. Operators who treat expansion as a geography problem, rather than a density problem, tend to find out the hard way that two depots can produce less combined efficiency than one ever did.

The question worth asking isn't whether a new market has enough total demand to support a hub. It's whether that demand sits close enough together to replace, quickly, the density the company is about to give up by splitting its fleet in half.