Route Optimization for Direct Store Delivery and Beverage Distribution: Why Distance is the Wrong Objective

Direct store delivery is treated as one category in almost every route optimization discussion. It is not. A truck delivering canned soda and a truck delivering potato chips face opposite physical constraints, operate under different legal restrictions on where they may go, and spend their day differently. Optimizing both with the same objective function produces a plan that is wrong in two directions at once. The soda truck reaches its legal weight limit with roughly three quarters of its cargo space empty. The chip truck fills its cargo space using roughly a fifth of its payload. A utilization dashboard measuring cubic feet reports the fully loaded, legally maxed beverage vehicle as mostly empty, and a planner acting on that number will try to add volume the axles cannot carry.

Beverage distribution adds a second constraint that has no equivalent in general logistics. In most of the United States, the territory a beer distributor may deliver into is a legal instrument filed with the state, granted brand by brand. Delivering across that line is not an inefficiency to be optimized away. It is grounds for losing the brand.

This piece covers what route optimization should actually mean for DSD and beverage distribution: load density, legal territory, service time and the return leg. It assumes you already have sales territory and journey planning in place, which is a separate discipline covered elsewhere.

Why DSD is two optimization problems wearing one name

The category exists for commercial reasons, not logistical ones. PepsiCo’s FY2025 annual report states that delivery to customer warehouses is “a less costly method of distribution than DSD,” and that DSD is retained because it “enables us to merchandise with maximum visibility and appeal” and suits products restocked often. One company runs both beverages and convenient foods through that system, which is precisely why a single DSD routing configuration cannot serve it.

The physical envelope is set by federal law. FHWA’s truck size and weight limits cap gross vehicle weight at 80,000 pounds, single axles at 20,000 pounds and tandem axles at 34,000 pounds, with a bridge formula in effect since 1975 governing weight against axle spacing. For beverage, these are binding operational constraints reached on ordinary routes, not theoretical ceilings.

The legal envelope is set by state beer franchise law. The Brewers Association’s beer franchise law summary, prepared by counsel to the association, notes that a majority of states have enacted full beer franchise laws, and that these commonly “mandate that sales territories be exclusive,” warning that wholesalers “may face substantial penalties for making deliveries outside their designated territory,” conduct that “may permit expedited termination by the brewer.” Across the 51 jurisdictions surveyed, exclusive-territory provisions appear in 40, territory designations must be filed with the state in 22, and 13 name out-of-territory sales as grounds for termination, several of them immediate.

Exclusive territory is not confined to alcohol. Coca-Cola Consolidated’s annual report describes distribution rights held under comprehensive beverage agreements in exclusive distribution territories across 14 states and the District of Columbia.

Meanwhile the distributor base has consolidated. NBWA’s industry fast facts record traditional beer distributors falling from 4,595 in 1980 to around 3,000 by 2020, against more than 20,000 licensed alcohol beverage wholesalers overall. Fewer operators cover larger areas, so the average distributor now runs more routes inside a territory map that remains legally fixed.

How to optimize a DSD and beverage route

1. Compute the vehicle’s critical density first

Critical density is payload divided by usable cargo volume. It is a single number that tells you which constraint binds for any product you carry.

Take a 26,000-pound GVWR straight truck with a 12,000-pound payload and 1,200 cubic feet of usable cargo space. Critical density is 10 pounds per cubic foot. Anything denser weighs out. Anything lighter cubes out.

The span from chips to glass bottles is 36 times. That range inside one distribution category is the reason a single routing configuration underperforms across it. Figures here are illustrative, and every operator should run this calculation on their own vehicle specifications and case dimensions.

2. Treat load composition as a decision, not an output

Loaded alone, 545 cases of canned soda hit the 12,000-pound payload while occupying 273 cubic feet, or 23% of the cube. Glass bottles are worse: 300 cases reach the weight limit at 12% of cube. Full kegs reach it at 14%. Chips are the mirror image, filling the cube at 22% of payload.

Mix them and both constraints can be satisfied at once. For this vehicle, 448 cases of soda plus 610 cases of chips consumes exactly 100% of payload and 100% of volume, for 1,058 cases in total against 545 for the all-soda load. That is 94% more cases on the same trip, and it comes from load composition rather than from routing.

The mix that saturates both constraints is fixed by physics, and real demand will not match it. So the practical question becomes which constraint you prefer to waste on a given day, and that is a planning decision that should be made explicitly rather than discovered at the loading dock.

3. Model the territory map as a hard legal boundary, per brand

Standard route optimization practice treats territories as economic objects to be rebalanced as demand shifts. In beer distribution, that practice produces unlawful plans.

Territory rights are granted by each brewer, so a distributor carrying dozens of brands holds dozens of territory maps that do not share boundaries. Two retailers on the same street can be inside the territory for one brand and outside it for another. A route serving both is legitimate for part of its manifest and a termination event for the rest.

The consequence for planning is specific. Territory boundaries must be enforced at the order-to-vehicle assignment level and keyed to the brand or supplier on the line item, not applied as a single geofence around a depot. Re-sectorization, the usual answer to falling drop density, is available only inside a brand’s own territory.

4. Optimize the clock, not the odometer

A beverage DSD stop is a merchandising visit. The driver rotates stock, restocks coolers, builds or resets displays, handles out-of-code product and completes paperwork. Service time is long, variable and driven by store conditions rather than by order size.

On a route with 15 stops at 25 minutes of service and 8 minutes of driving between them, service consumes 375 of 495 minutes, or 76% of the clock. Cutting drive time by 15% shortens the route by 18 minutes, which is 3.6%. On a parcel route where driving is 57% of the clock, the same 15% improvement returns 8.6%, well over twice as much.

This does not mean routing is unimportant. It means distance minimization is the wrong objective. The levers that matter are accurate per-store service time estimates, sequencing against store receiving and merchandising windows, and balancing routes so no vehicle exceeds the driver’s available hours once realistic service time is loaded in.

5. Plan the return leg as its own capacity problem

Beverage routes carry returnables back: kegs, returnable glass, plastic crates, pallets, and out-of-code or damaged stock. The weight profile changes completely while the volume profile does not.

A full half-barrel keg runs 72.7 pounds per cubic foot, 7.3 times critical density. Empty, it runs 13.6, only 1.4 times critical. So the same vehicle that could carry 75 full kegs can carry 400 empty ones, roughly 5.3 times as many, and it is still weight-bound rather than cube-bound because kegs stay dense even empty.

That asymmetry has a clear planning implication: collection capacity vastly exceeds delivery capacity on the same asset, so dedicated empties-collection trips are almost never justified on capacity grounds. Where they persist it is usually because the return volume is not modeled on the outbound plan and the empties accumulate until someone schedules a sweep.

6. Sequence the load against the delivery sequence

Weight distribution is an axle compliance issue, not only a total payload issue. Federal limits apply per axle as well as gross, so a load that is legal in total can be illegal in distribution, and it can move into non-compliance as the route progresses and product leaves from one end of the box. On a weight-bound vehicle carrying dense product, load sequencing and axle loading must be planned together with stop sequence.

Where the archetypes diverge

Reporting cube utilization on a beverage fleet will understate performance by a factor of four or more, and every capacity decision taken on that number will be wrong in the same direction.

Five criteria for evaluating route optimization for beverage DSD

1. Does it constrain on weight and axle loading, not just volume? Ask whether the engine enforces payload and per-axle limits simultaneously and whether it reports weight utilization alongside cube. A platform that models a single capacity number cannot plan a dense load.

2. Can it enforce territory rules per brand or supplier at line-item level? Not a depot geofence. The rule needs to attach to the product and the account pair, because a legal delivery for one brand can be a violation for another to the same store.

3. Does it estimate service time per store from history rather than applying a flat allowance? On a route where service is three quarters of the clock, a flat service assumption is the largest single source of plan error.

4. Does it treat returnable collection as a task on the outbound plan? Empties need volume, weight and time on the same trip, with the collection quantity forecast per account rather than discovered on arrival.

5. Can it plan mixed-density loads deliberately? The engine should be able to compose a load that saturates both constraints where demand allows, and to tell the planner which constraint is being left slack when it cannot.

What this looks like in enterprise deployments

A global FMCG manufacturer operating across ten Asian countries with more than 1,000 distributors and 5,000 riders reached 3X ROI while saving over 12,000 trips a month and optimizing more than $4 billion of orders across 1.8 million retail outlets. Trips saved rather than miles saved is the correct headline for a distribution model where each trip carries a fixed cost in driver hours and vehicle availability.

Across Locus FMCG and CPG deployments the recurring pattern is roughly 15% lower freight cost, 20% fewer vehicles required, 84% less planning time and 95% SLA attainment. The vehicle count reduction is the one that matters on a weight-bound fleet, because on a dense product you cannot buy throughput by filling empty cube.

Cost pressure makes the load density question more valuable than it was. ATRI’s operational cost analysis put the industry-average cost to operate a truck at $2.336 per mile in 2025, up 3.4%, with tolls up 13.2% and repair and maintenance up 8.6%. Repair and maintenance is a line item that dense loads drive directly, since a vehicle running at full payload every day wears differently from one running at a fifth of it.

Four mistakes that keep beverage DSD routes expensive

Reporting cube utilization on a weight-bound fleet. A legally full beverage truck shows as 77% to 88% empty. Every capacity conclusion drawn from that number points the wrong way.

Optimizing distance on a route where service time is 76% of the clock. The savings are real but small, and pursuing them can lengthen the route if sequencing drifts away from store merchandising windows.

Treating territory as a soft constraint. In beer, out-of-territory delivery is grounds for termination in 13 of the jurisdictions surveyed, several without notice. An optimizer permitted to rebalance across brand territories will eventually produce a plan that costs a brand.

Leaving returnables off the outbound plan. Empties are forecastable per account. When they are not planned, they accumulate and get collected on dedicated trips that the vehicle’s own spare capacity made unnecessary.

Why Locus fits beverage and DSD route optimization

Locus is an agentic transportation management system, and the relevant capability here is constraint fidelity rather than raw solver speed. The Fireworks routing engine plans against more than 250 real-world operating rules, which is the layer that carries weight and volume capacity together, per-axle and vehicle class restrictions, store receiving and merchandising windows, shelf-life and temperature requirements, driver hours, load sequencing tied to warehouse picking, and returnable collection modeled as tasks on the same trip rather than as a separate reverse workflow.

Route planning across these deployments delivers up to 34% fewer miles, 25% higher drop density and 28% fewer trips through order consolidation, with fleet utilization up to 90%. On a dense-product fleet, the trip reduction and the utilization figure are the ones to watch, since miles are the smaller share of a beverage route’s cost structure.

Territory enforcement is worth being precise about. Locus models territory and journey plans, including permanent journey and dispatch plans, and applies constraints at order and account level rather than only at depot level. Whether a given deployment enforces brand-specific legal territories correctly depends on how the brand and supplier attributes are mapped during implementation, and that mapping should be a named requirement in any beverage rollout rather than an assumption. Locus does not provide legal advice on franchise compliance, and the territory definitions themselves have to come from the distributor’s filed agreements.

Allocation runs across owned fleet, contracted transporters and a network of more than 1,000 carriers, decided per shipment against live cost and serviceability. For distributors running mixed captive and contracted capacity across a legally bounded territory, that keeps the outsourcing decision at route level.

One boundary: Locus is not a telematics platform and does not provide ELD logging, dashcams, vehicle diagnostics or onboard weight sensing. Axle load compliance depends on accurate case master data and, where available, telematics or scale integration. The platform plans the load; verifying it on the vehicle is a separate system.

Locus supports more than 360 enterprise customers across 30-plus countries, with over 1.5 billion deliveries optimized and more than $320 million in documented client logistics savings, and has been recognized by Gartner for seven consecutive years. Beverage, FMCG and retail customers include Heineken, Nestlé, Unilever, Mars and Makro, the last of which scaled from 500 to 4,000 trucks with 24% higher fleet efficiency and 66% less planning time.