Every bhatta that sells bricks runs on the challan: a numbered slip confirming what was loaded, for which customer, on which vehicle, on which date. It is signed at the point of loading and becomes the reference for everything downstream—what stock left, what the customer now owes, and what gets matched against payment later.
Most kilns have run this on a carbon-copy book for years, and the book itself is not the problem. The problem shows up in what happens to that slip after it leaves the loading point.
How the paper challan book works today
A pad of pre-numbered, carbon-copy slips is kept at the loading point. One copy travels with the vehicle and the customer, one stays in the book as the kiln's record. Numbering is sequential by the book itself, and the slip is later matched—usually at the end of the day or week—to the customer's order and running account.
Where it breaks down
- Matching happens later, not at the moment of dispatch. The customer's ledger is not actually updated until someone sits down and enters the challan against the account, which can lag the real dispatch by days.
- Numbering can duplicate across books. If more than one pad is in circulation, or a book is started out of sequence, two challans can end up sharing a number.
- The kiln copy can be damaged or misplaced before it is entered into the ledger, leaving a dispatch with no clean record on the kiln's side.
- Quantity recorded on the slip does not automatically reduce sellable stock—someone has to separately update the stock count, and that step can be skipped on a busy day.
- Reconciling a customer's account at month end means physically gathering every challan slip issued to them and adding it up by hand.
What actually changes with a digital challan
The moment of dispatch does not change much—someone still confirms quantity, vehicle and customer at the loading point. What changes is everything the slip triggers once it is created.
- A single, continuous numbering sequence, so two challans cannot accidentally share a number even if issued from different points.
- Stock reduces at the moment the challan is generated, not on a separate manual update later.
- The customer's running account updates the same moment—no separate ledger entry step, and no lag between dispatch and the account reflecting it.
- Any challan can be reprinted or reviewed later without depending on a physical copy surviving in good condition.
- A customer's full dispatch and dues history for a period can be pulled up directly, instead of gathering slips by hand.
Being honest about the trade-off
A digital challan still depends on someone recording the correct quantity at the point of loading—software cannot catch a miscount that was never entered accurately in the first place. The physical, signed proof of delivery a driver or customer holds is also still worth keeping in some form, at least during a transition period, since it is the documentary evidence both sides can point to on the spot.
The loading point also needs a device and, ideally, an internet connection at the time of dispatch. Kilns operating in areas with unreliable connectivity should have a plan for what happens when a challan needs to be generated offline.
A practical way to move over
- Keep a signed physical copy at the loading point during the transition, even once the digital challan is the authoritative record.
- Start with one vehicle or one route before switching all dispatch over, so any workflow issues surface on a small scale first.
- Check that stock and customer ledger updates are actually reflecting correctly for the first several challans before relying on the numbers unchecked.
- Train whoever loads the vehicle on the exact quantity-entry step—this is the one manual input the whole chain still depends on.