Create a delivery challan to accompany goods being shipped, separate from the sale invoice.
A delivery challan is the document that travels with the goods themselves, confirming what is being shipped, in what quantity, and to whom - distinct from an invoice, which is about billing, or a purchase order, which is about placing the original order. Many businesses issue goods against a challan first and invoice separately afterwards, particularly when a shipment needs to be inspected, approved, or partially accepted before final billing is settled, or when goods are sent on approval, on consignment, or for job work rather than an outright sale.
This generator uses the same familiar line-item structure as the rest of the toolkit - description, quantity, and an optional rate - but the emphasis is on what is physically moving, not on collecting payment. You can leave rates blank entirely for a pure goods-movement challan, or include them for your own reference even though the challan itself isn't a demand for payment. A dedicated delivery address field, separate from the general 'to' address, helps when goods are shipped to a site or warehouse that differs from the client's billing address.
Because challans are frequently checked against the actual goods on arrival, keeping the description and quantity fields precise - down to the unit of measure where relevant - saves considerable back-and-forth if a receiving clerk needs to verify the shipment matches the paperwork. The challan number is also commonly referenced later when the corresponding invoice is eventually raised, so keeping a consistent numbering scheme between challans and invoices makes reconciliation much easier for both your own accounts team and the client's.
As with every tool here, none of your shipment details, client addresses or product information are ever transmitted to a server - the whole document is generated and calculated inside your browser. Once complete, print the challan to send along with the physical shipment, or download it as an HTML file to email ahead of dispatch so the receiving party knows what to expect. Getting this document right is a small but meaningful part of keeping goods-in-transit disputes to a minimum.
It's also worth training whoever handles dispatch to fill in the challan consistently every time a shipment leaves, rather than treating it as optional paperwork only for larger orders, since even small shipments benefit from a clear written record if a dispute ever arises about what was actually sent. A well-kept sequence of challans over time also becomes a useful internal record of dispatch volume and frequency, which can be handy when reviewing logistics costs or negotiating with a shipping partner. Ultimately, a consistent challan process is one of the simplest ways a growing business can avoid the kind of he-said-she-said disputes that arise when goods go missing or arrive short, since the paperwork trail speaks for itself regardless of who is asking.
Many businesses find it useful to keep a simple monthly count of challans issued as a quick proxy for shipment volume, which can feed into broader logistics or inventory planning conversations without needing a separate tracking system just for this purpose.
A delivery challan accompanies goods in transit and confirms what was shipped; an invoice is the request for payment for those goods. Some businesses issue both together, others issue the challan first and invoice later once goods are accepted.
Not necessarily - many challans list only description and quantity. Prices are optional here and can be left blank if the challan is purely for goods-movement tracking.
Yes, challans are commonly used for goods sent for job work, on approval, or on a returnable basis, since no sale has technically occurred yet.
Yes, everything is generated locally in your browser with nothing uploaded to a server.