City distribution software is built around the route rather than the consignment: what is loaded at the depot in the morning, the sequence of drops, the delivery windows each shop imposes, the crates and returnable packaging that have to come back, the unsold stock returning to the depot, collections made at the counter, and the reconciliation of the vehicle at the end of the day. With Pentoggle, a distribution operation can describe how its routes actually run and generate the starting application around it.
This is the daily movement that keeps retail supplied. FMCG distributors serving kirana stores, dairy and bakery routes running before dawn, beverage and water distribution, pharmaceutical distribution to chemists, and third-party operators running city delivery for brands. The vehicle leaves full and comes back with crates, returns and money.
Many distribution businesses already run Tally or a distributor management system for accounting, orders and stock. Those stay where they are. What is often still managed outside them is the route: what actually went on the vehicle, what got delivered, what came back and why.
Key takeaways
- The unit of work is the route-day, not the consignment. A vehicle, a driver and a helper are committed for a day, and the cost of that day is fixed while the number of successful drops is not.
- Failed drops are the main variable cost in the operation, and the reasons are usually structural rather than random: shop closed, no-entry hours, owner unavailable, payment not ready.
- Returnable packaging is a lending problem rather than a stock problem, and crates lost across a year usually exceed what anyone assumes.
- The reverse flow of unsold stock, expired goods and empties is genuine work with genuine cost, and it is almost never costed.
- A useful number is drops completed per vehicle per day against drops planned.
How a city distribution operation makes money
There are two versions of this business and they earn differently.
A distributor buys stock and sells to retailers, earning a margin on goods. Distribution is a cost of doing business rather than a revenue line, so every rupee saved on the route is margin retained.
A third-party distribution operator is paid to distribute somebody else's goods, on a rate per drop, per case, per route-day or a monthly contract. Here distribution is the revenue, and route efficiency is directly profit.
In both cases the cost structure is the same and it is dominated by the route-day. A vehicle, a driver and usually a helper are committed for the day. Diesel varies a little with distance. Everything else is fixed the moment the vehicle rolls out.
That produces an unusual economics. The marginal cost of one more drop on an existing route is very small. The cost of a drop that fails is very large, because it consumes the same time and travel as a successful one and returns nothing, and it frequently has to be repeated tomorrow, consuming the resource twice for one delivery.
The spreadsheet is often not the problem
A route sheet printed each morning and reconciled each evening is a working system for a few vehicles.
The trouble starts at identifiable points.
When failures have no reasons attached
Twenty-one delivered out of thirty. The route sheet records nine blanks. Whether those were closed shops, refused payment or a vehicle that ran out of time is not recorded, so nothing can be fixed.
When crates are counted occasionally
Empties go out and come back approximately. The shortfall appears at an annual count as a single number nobody can attribute to a route or a customer.
When routes are planned from memory
The sequence is what the driver has always done. Whether it is still right after eleven new outlets were added over two years is a question nobody has the information to ask.
When the reverse flow is invisible
Unsold stock, expiries and damaged goods come back on the vehicle. They are handled at the depot and absorbed, and no cost is ever attached to the return leg they occupied.
What city distribution software holds
Routes and outlets
Route definitions, the outlets on each, their sequence, delivery windows and access constraints.
Daily load
What was loaded onto each vehicle against the day's plan, by item and quantity.
Drop execution
Each drop with quantity delivered, time, and the outcome recorded at the shop.
Failure reasons
Why a drop did not happen, from a defined list, captured at the point of failure.
Crates and returnable packaging
Issued, expected back, currently outstanding by outlet, and condition on return.
Returns and reverse flow
Unsold stock, near-expiry, expired and damaged goods coming back, by outlet and reason.
Collections
Cash, cheque or digital payment taken at the counter against the invoice it settles.
Vehicle reconciliation
Loaded against delivered against returned, with money and crates squared off at day end.
The route-day is the unit
Everything about this operation follows from the fact that you are buying a day of a vehicle and a crew, not a delivery.
Once that is the frame, several things that look like separate problems turn out to be the same problem.
Route design. Outlets get added to routes as they are acquired and rarely removed when they close or move. Routes drift into inefficiency slowly and invisibly. A route that made sense with forty outlets makes less sense with fifty-eight, and nobody redraws it because there is no picture of what it currently looks like.
Sequencing. The order of drops determines how much of the day is spent driving rather than delivering. Drivers optimise from experience, which is usually decent and usually not current.
Delivery windows. Indian city distribution runs against real constraints that route planning has to respect. Some cities and local authorities restrict commercial-vehicle movement in particular areas or during particular hours. The applicable restrictions vary by location and should be built into the route rules for the areas you serve. Shops open and close at their own times, wholesale markets have their own rhythms, and some outlets will not accept goods during peak selling hours. A route that ignores these produces failed drops that were predictable.
Time exhaustion. The last few drops on a route are the ones that fail when anything earlier ran long. They fail for reasons that have nothing to do with those outlets, and they tend to be the same outlets every time, which quietly damages those customer relationships.
Holding the route-day as the unit means the plan, the execution and the reconciliation all sit in one record. Planned drops against completed drops, with the time each was made, is enough to see where the day went and which part of the route consistently runs out of time.
Crates and returns are the invisible half
Two flows run backwards through this operation and neither usually appears in any system.
Returnable packaging. Crates, trays, bottles, pallets and containers go out with goods and are supposed to come back. Some come back damaged. Some stay at outlets. Some are used by the outlet for their own purposes and are not returned at all. At an annual count the shortfall is a single large number written off centrally, at which point it cannot be attributed to a route, a driver or an outlet.
The correct treatment is a lending record rather than a stock record: issued to this outlet, expected back, currently outstanding, condition on return. The same structure applies as to shuttering and scaffolding in construction, and for the same reason, which is that recovery is straightforward while the relationship is active and nearly impossible once it is not. An outstanding position visible per outlet turns crate recovery into a conversation the driver can have tomorrow.
Returns of goods. Unsold stock, near-expiry, expired and damaged items come back on the same vehicle. Handling them consumes crew time at the outlet, space on the vehicle for the rest of the route, and processing at the depot. None of that is usually costed, so the true cost of serving an outlet with a high return rate is understated, sometimes substantially.
Recording returns by outlet and by reason produces the pattern. Returns concentrated at particular outlets may indicate over-supply relative to what that outlet actually sells, which is an ordering question. Returns concentrated on particular items across many outlets is a range question. Returns rising on a route is often a sign that stock is being pushed rather than sold.
Workflows this business depends on
- Route Planning and Optimization Software, for sequencing and route design.
- Delivery Management Software, for the operational picture across vehicles and days.
- Proof of Delivery Software, captured at the counter alongside collection.
- Fleet Management Software, for the vehicles running the routes.
- Warehouse Management Software, for the depot the routes load from.
- Cold Chain Logistics Software, for dairy, frozen and temperature-sensitive distribution.
Why distribution operations choose Pentoggle
Built around the route-day
Plan, load, execute and reconcile in one record, because that is how the cost is actually incurred.
Failure reasons captured at the door
A defined list recorded at the point of failure, so nine blank rows become nine specific problems with owners.
Crates tracked as lending
Issued, outstanding and returned by outlet, rather than counted once a year and written off.
Returns costed rather than absorbed
Reverse flow recorded by outlet and reason, so the true cost of serving an outlet is visible.
Sits around your accounting and DMS
Tally, a distributor management system or comparable software continues handling accounting, orders and stock. Pentoggle adds the route-level operational layer.
A useful number for city distribution
Drops completed per vehicle per day, against drops planned.
The cost of the day is committed when the vehicle leaves. The only variable that matters is how many productive drops that day produced, which makes this ratio the closest thing to a productivity measure the operation has.
Read the shortfall by reason rather than as a total. Nine missed drops caused by shop closures is a route-timing problem. Nine caused by running out of time is a sequencing or workload problem. Nine caused by payment not ready is a commercial problem belonging to the sales side. The total is identical in all three cases and the responses are completely different.
Track it per route as well as per vehicle, over weeks rather than days. A single bad day is weather or traffic. A route sitting consistently below the others has something structural in it, usually too many outlets, a difficult access window, or a sequence that was correct four years ago.
Ready to build software for your distribution operation?
The vehicle costs the same whether it makes thirty drops or twenty-one.
Nobody wrote down why the other nine did not happen.
Describe how your routes, drops and returns actually work to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.