Daily Bread Route Sales in Nepal: The 24-Hour Cycle from Oven to Cash

A bread route runs on a clock that no other trade shares. The product comes out of the oven at night, goes onto the van before sunrise, sits on shop shelves by breakfast and is worth much less the next morning. Every decision in the business, from how many loaves to load to which shop gets visited first, is a decision about time. This guide follows one bakery day from oven to cash, points out where money leaks at each hour, and shows how a Nepali bakery or bread distributor can run that cycle in gamitrack.

The bakery day, hour by hour

The exact times differ by town and by bakery, but most daily bread businesses in Nepal follow a pattern like this one.

Time (example)	What happens	What usually goes wrong
Night	Baking to the next day's plan	The plan is last week's guess, not this week's sales
Before sunrise	Loading vans and bikes	Load counted by eye; no record of what left
Early morning	First shops near homes, tea shops, canteens	Late start means the morning tea crowd buys elsewhere
Mid-morning	Remaining shops, schools and hostels	Driver skips far shops or spends too long at one
Late morning	Stale bread from yesterday collected	Returns taken without a count or reason
Afternoon	Van returns, cash handed over	Cash does not match sales; nobody knows why

The rest of this guide takes each of those stages in turn.

Night: bake to a number, not a habit

Most bakeries bake to standing orders: "twenty loaves daily for this shop, ten buns for that canteen". Standing orders are useful, but they go stale faster than the bread does. A shop that sold twenty loaves in winter may sell fourteen once school holidays start.

A simple rule keeps them honest. Every week, look at two numbers for each shop:

• Returns. If a shop sends back stale bread most days, its standing order is too high.
• Sold-out reports. If the driver keeps noting that the shop was empty before he arrived, the order is too low.

Change each standing order by a small step, then wait a week before changing it again. Large swings make it impossible to tell what worked.

Before sunrise: count what leaves

The load is where the day's money is decided. If nobody records what went onto the van, nobody can say later what should have come back.

In gamitrack, the bakery or depot is a branch and each bread, bun and bakery item is a SKU. The morning load is recorded as a stock movement out of the branch. Movements are append-only, so the record of what left at 5 am cannot quietly change at 3 pm. Prices come from the price list, so a shop on a special rate is still billed correctly.

Early morning: route order matters

A tea shop that wants bread at 6.30 is no use at 9.00. Build each van route in gamitrack as an ordered list of stops, with the early-trade shops first. The driver or salesperson starts the day in the app, which begins the GPS location trail, and each stop is checked against the shop's geofence with a photo as proof of the visit.

The manager does not have to ride along. The day's map in the admin console shows the actual path and the time spent at each stop. Visits that happen outside the geofence, are very short or have no photo are flagged for review. A daily integrity score gives a quick sense of which routes need a closer look, without checking every stop by hand.

Hill and outer-ring routes sometimes lose signal. The location trail is stored on the phone and synced when the signal returns, but orders, visits and payments need a connection, so drivers should save those as soon as they are back in coverage.

Mid-morning: orders, top-ups and institutions

At each stop the driver books what the shop takes, starting from the standing order and adding or removing loaves based on what is still on the shelf. The order is priced from the price list. If the shop's rate is set as a party override, it takes priority over the price for that type of shop and the default list.

Schools, hostels and canteens behave differently. Their orders are predictable during term and close to zero during holidays, and they usually pay on a statement rather than in cash. Treat them as their own parties with their own payment due days so their balances do not get mixed with walk-in cash.

If you have sub-agents who take bread to other areas, record their purchases as primary orders and their sales to shops as secondary orders. Their monthly stock report then shows expected against actual closing stock.

Late morning: returns with a reason

Stale returns are a normal cost of a daily product. The problem is not that returns exist; it is when they are not counted. A return that is not recorded hides two things: a standing order that is too high, and possibly a driver who is not handing back what he collected.

Record every return against the shop with a reason, such as stale, damaged or short-dated, and approve it into the branch with a credit note. After a month you have a return history by shop, which is the most useful number for adjusting tomorrow's bake.

Afternoon: close the van and the cash

Each route should end the day with a four-line tally:

1. Loaded (from the morning movement)
2. Delivered (from orders and deliveries)
3. Returned (from approved returns)
4. Cash and digital payments collected

Loaded minus delivered minus returned should equal what is physically left on the van. Delivered value minus what is on credit should equal what was collected. Differences are resolved the same afternoon, while the driver still remembers the day.

Payments are recorded against each shop as cash, eSewa, Khalti, Fonepay or bank transfer and allocated oldest-first, so the shop's statement shows exactly which bills are cleared. For shops that pay weekly, a weekly collection plan lists who should pay and compares it with what actually came in.

A worked morning on one route (hypothetical)

Suppose a bakery runs a route of 30 shops. On Monday the van leaves with 400 loaves. By the afternoon tally, 352 were delivered, 31 came back as stale from yesterday, and 17 are left on the van. Cash collected is short of the expected amount by the price of a few loaves.

The manager opens the return history and sees that three shops account for most of the stale bread, while two others reported being sold out before the van arrived. The route map shows that the van reached those two shops after 9 am. The fix is small: lower the three standing orders by a few loaves each, move the two sold-out shops earlier in the route, and check the cash gap with the driver against the payment records for each shop.

All numbers here are illustrative. The point is that each answer comes from a record, not from memory.

Numbers to watch

Measure	What it tells you	How often
Loaded vs delivered vs returned	Whether the van reconciles	Daily
Returns by shop	Standing orders that are too high	Weekly
Sold-out reports by shop	Standing orders that are too low	Weekly
Route start and finish times	Late starts and slow stops	Daily
Cash collected vs expected	Collection discipline	Daily
Institution balances	Statement customers paying late	Weekly

Your first 30 days

• Days 1 to 7. Enter every bread and bakery item as a SKU and record the morning load from the bakery branch each day.
• Days 8 to 14. Set up your two or three busiest routes with stops in delivery order. Drivers start the day in the app and photograph each stop.
• Days 15 to 21. Start recording every return with a reason, and run the four-line tally every afternoon.
• Days 22 to 30. Review returns and sold-out reports by shop and adjust standing orders in small steps.

A daily product gives daily feedback. If a change to the load or the route order works, you will see it within a week; if it does not, you can reverse it just as quickly.

Related reading: eggs and poultry products distribution, van sales cash reconciliation, handling damaged and expired returns and the bakery and confectionery industry page.

If you want to try this on your own routes, see the plans on our pricing page or contact us to talk it through.