Sugar and Salt Wholesale in Nepal: Truckloads, Thin Margins and the Credit Book

Sugar and salt are products every household buys and every shop stocks. That makes the trade look easy, and it is not. Your sugar is the same as the next wholesaler's sugar, and the margin per sack is thin. The only lasting advantages are having stock when others do not, delivering when you said you would, quoting the same price to everyone and keeping a credit book that does not quietly swallow your working capital. This guide is built around the two places where those advantages are won or lost: the order desk, where you decide whether to say yes, and the truck, where goods and money leave the godown.

How the trade is structured

Wholesalers buy in bulk from importers, mills or larger stockists and hold stock in godowns. Sugar mostly moves in sacks; salt moves in sacks and in retail packs. Buyers range from sub-wholesalers buying by the truck to small shops taking a few sacks, plus sweet makers, bakeries, hotels and canteens with steady demand.

Buyer	Typical order	Terms	What goes wrong
Sub-wholesaler	Part or full truck	Longer credit	One large late payer blocks your own supplier payment
Town retailer	A few sacks or cartons, weekly	Short credit	Small balances pile up unnoticed
Sweet shop or bakery	Regular, rising before festivals	Monthly account	Festival orders on credit, paid long after
Institution	Scheduled	Per agreement	Slow approval, slow payment

Demand is steady for salt and seasonal for sugar: Dashain, Tihar and the wedding season lift sweet-making, and the monsoon brings damp godowns and closed roads. Prices can move suddenly, which makes consistent quoting harder and more important.

At the order desk: four checks before you say yes

Most losses in this trade begin with a "yes" given too fast on the phone. Before confirming an order, the desk should be able to answer four questions in under a minute.

1. Is the stock actually there? Each godown is a branch in gamitrack with its own balance. Every receipt, dispatch, transfer, return and adjustment is an append-only movement, so the balance is the sum of what really happened, not someone's estimate. If it says 120 sacks at Godown B, you can promise against that.

2. What does this buyer already owe, and how old is it? Open the party ledger statement and aging. A buyer with a large balance more than 30 days old should hear "we will send it once the old bill is settled", not "yes".

3. What is the right price? Prices come from lists: an override for that buyer if there is one, then the list for their party type (sub-wholesaler, retailer, bakery), then the default. Whoever answers the phone quotes the same price, because the system applies it.

4. Can it go on the planned truck? Each product carries its weight in kg, so the order weight is known before it is accepted onto a route.

Officers in the field book orders in the mobile app with exactly the same pricing; the office books phone orders. VAT applies only to taxable lines, and invoices are numbered per fiscal year in IRD format. Check the current IRD rules for how your products are treated.

A truckload, worked through

Here is one hypothetical delivery day, with illustrative numbers.

Suppose you have eight orders for a route toward three nearby bazaars, totalling a little under the truck's capacity by weight. One order, from a retailer whose old balance has been overdue for some weeks, is on hold until a payment arrives. The other seven are confirmed against Godown A's stock.

1. Dispatch. The seven orders are dispatched. Dispatch is all-or-nothing per order, so no order sits half-complete in the records. Due days for each invoice are fixed from today's dispatch date.
2. Loading. The truck is loaded in reverse route order. Two sacks are found torn at loading; they are recorded as damage straight away instead of being quietly left behind.
3. Delivery. At each stop the delivery person sees the amount due, location and directions on the driver tab, and marks delivery with GPS, a photo and the receiver's name. A delivery marked far from the buyer's location is flagged.
4. Collection. Three buyers pay on delivery, one by cash, one by Fonepay and one by cheque. Each payment is recorded against the oldest open invoice.
5. Back at the godown. The day's dispatches, the two damaged sacks and the collected payments are all in the system before the truck is parked. Nothing needs to be rebuilt from memory tomorrow.

The held order goes out on the next truck once its buyer pays. These details are invented to show the routine, not a real result.

Sacks, damp and the monthly count

Sugar draws moisture and sacks tear. Salt absorbs moisture and cakes. In the monsoon both get worse. If damage is not recorded when it happens, it appears months later as a "shortage" nobody can explain.

Godown checklist

• Stack on pallets or a raised base, away from walls that take on damp.
• Inspect the stacks weekly in the monsoon.
• Record every torn, wet or short-weight sack as a damage movement with a reason, in the same week.
• Count each godown on a fixed day each month and compare with the system balance.
• Explain every difference before the next count.

Low-stock levels per SKU and godown give you the reorder warning before the shelf, or a sub-wholesaler, runs dry. Transfers between godowns are recorded as movements so both balances stay correct.

The credit book

Because the margin per sack is thin, a single large buyer paying late can force you to pay your own supplier late. The credit book needs a weekly routine, not a monthly panic.

Rule	Why it matters
Every buyer has a limit and terms	One account cannot consume all working capital
Due date fixed from dispatch	No arguments about when the clock started
Weekly aging review	Overdue balances are raised while they are small
Weekly collection plan per officer	Collection becomes a list, not a memory
Advances kept on the ledger	Pre-payments are applied to the next invoice automatically

Weekly collection plans in gamitrack show planned collections against actual, per officer, so you know by Friday which balances moved and which did not.

Covering retail properly

Small retailers ordering a few sacks every week are the steady base of a sugar and salt business, and they are the first to be forgotten when one salesperson holds the routes in his head.

Build retail routes with ordered stops. Officers start the day with GPS, each visit is checked against the shop's geofence and recorded with a photo, and each ends with an order, a no-order reason or a note that the shop has closed. Visits outside the geofence, too short or without a photo are flagged for the manager, and the location trail and daily integrity score give an overview without phone calls. If sub-wholesalers resell your goods to these shops, use via-dealers mode and monthly dealer stock reports to compare expected and actual closing stock.

The owner's five questions each month

1. Which five buyers have the largest overdue balances, and what is the plan for each?
2. Which routes grew and which shrank, by weight?
3. What was the damage and shortage record by godown?
4. Did every phone and field quote follow the price list?
5. How did collections compare with the weekly plans?

Your first 30 days

• Week 1: set up each godown as a branch, sugar and salt SKUs by sack and pack size with kg weights, and opening stock.
• Week 2: enter your largest buyers with opening balances, limits and price lists.
• Week 3: run all orders through the four desk checks and record every delivery with proof.
• Week 4: first weekly collection plans and first fixed-day godown count.

Related reading

For a similar bulk, credit-heavy trade, see edible oil distribution in Nepal. For credit, read collecting payments on time, and for festivals, Dashain and Tihar stock planning. Industry page: FMCG and packaged food.

Next step

Start with one godown and your ten largest buyers, and watch stock and aging for four weeks. Compare plans and start a free trial on the pricing page, or contact us.