Five reasons a consignment gets stopped that have nothing to do with the goods

A detained consignment is rarely a quality problem or a customs problem. It is almost always a documentation problem, and the documentation was almost always correct when it left your gate. Something changed on the road, or something was never generated at all because a threshold was measured against the wrong number.

Here are the five that account for most of it, in rough order of how often they happen.

1. The e-way bill expired while the truck was parked

Validity runs off distance, not calendar convenience: broadly one day per 200 km for regular cargo, with part distances rounding up, and the clock starts when the transport details are first entered. A 900 km run is five days. Five days is generous — until the truck sits two nights at a transporter’s hub waiting for a full load, and the driver delivers on day six.

Extension is possible, but only in a narrow window around expiry — a few hours either side, not next week — and it has to be done by the transporter or the generator, from the portal. A bill that lapsed on Tuesday cannot be revived on Thursday.

The fix is not a longer validity. It is knowing which of your live consignments expire in the next 24 hours, every morning, without anybody asking.

2. Part B does not describe the truck it is stapled to

The e-way bill names a vehicle. The moment the goods move to a different vehicle — a breakdown, a transhipment at a hub, a last-mile change from a trailer to a tempo — Part B has to be updated before the new vehicle moves. In practice the transporter knows and your plant does not, so nobody updates it.

This is the one that most often turns into a penalty rather than a warning, because on paper it looks like the same document being used for a different movement.

3. Nobody generated one, because the value was measured wrong

The requirement bites above a consignment value of ₹50,000, and consignment value means the value on the document including tax — not your ex-works price, and not the line total before freight and other charges. A ₹46,000 invoice with tax on it is over the line. Plenty of dispatch clerks have looked at the taxable value, decided they were under, and been right about the wrong number.

Two more traps in the same family:

• Movements that are not sales still need one. Material going to a job worker, goods sent for exhibition or on approval, a line rejection going back to the vendor, stock transferred between your own plants. These move on a delivery challan rather than an invoice, and the challan does not exempt them.
• Some inter-state movements need one regardless of value, job work being the common case for manufacturers. “It is only ₹12,000 of tooling” is not a defence.

4. Generation was blocked, and the reason was in the accounts department

If returns have not been filed for two consecutive tax periods, e-way bill generation against that GSTIN gets blocked — for you as a supplier, and for anybody trying to generate one against you as a recipient. The dispatch team finds out at 6pm on a Saturday, and the person who can fix it is a filing, not a phone call.

Worth knowing because it is the only item on this list where the shop floor cannot solve its own problem. If dispatch is suddenly failing for everything rather than one consignment, stop debugging the consignment.

5. The three documents do not agree with each other

Invoice, delivery challan and e-way bill get raised at different moments, sometimes by different people, sometimes in different systems. Then a line is short-shipped and only the challan gets corrected. Or the description on the invoice is the customer’s part name and the description on the e-way bill is your internal one, and an officer reading both cannot tell they are the same item.

The specific mismatches that draw attention: quantity, taxable value, HSN, and the consignee’s address and GSTIN. The specific absence that draws attention: a movement that is not a supply travelling without a delivery challan at all.

What to do about it

None of the five is difficult to prevent, and all five are difficult to remember. That is the actual problem — they are prevented by a routine, not by a rule.

• Raise all three documents from one record, so they cannot disagree by construction. A challan typed fresh from an invoice is a chance to introduce a difference.
• Put expiring e-way bills on a screen somebody looks at in the morning, alongside vehicles still in transit past their expected delivery date.
• Compute consignment value inclusive of tax and other charges, automatically, and block dispatch above the threshold without a bill rather than warning about it.
• Give the transporter a way to update Part B that does not require them to call your accounts department.

What MANUPRIME does about it

Dispatch, the packing list, the challan, the e-way bill and the invoice come off one document chain, so quantity and value are the same number in all of them rather than four typed copies of it. The dispatch screen carries vehicle and transporter details and the documents each consignment is travelling on, and the transport documents are raised through your own GSP connector.

The dispatch module is one of the screens we walk through — ask for a demo.