Step 01
In-transit register populated
On dispatch, the in-transit register opens with vehicle, expected receipt date, distance, courier (Delhivery, Bluedart, Shiprocket).
Inventory Management | Goods in Transit
In-transit, visible. Loss-in-transit, accounted.
Goods between branches sit in the in-transit register with vehicle, distance and ETA. Receipt closes the loop. Variance posts to the loss-in-transit GL with reason capture. Period-end reconciliation surfaces aged in-transit positions.
How it works
From dispatch to receipt, with the variance closed.
Step 02
ETA tracked
Where the courier API is connected, ETA updates live. Where not, the dispatcher updates manually. Aged in-transit (past ETA) surfaces on a dashboard.
Step 03
Receipt closes the loop
Quantity received closes the in-transit position. Variance flagged. Photos and damage notes captured at receipt.
Step 04
Loss-in-transit GL posts
Variance posts to the loss-in-transit GL with reason code. ITC reversal under Section 17(5) where applicable. Insurance claim workflow triggered for damage above threshold.
What the system does
Capability, input, output.
| Capability | Input | Output |
|---|---|---|
| In-transit register | Dispatch event | Open in-transit position with metadata |
| Courier ETA tracking | Delhivery / Bluedart / Shiprocket API | Live ETA on dashboard |
| Receipt closure | Receipt quantity confirmation | In-transit closed; variance flagged |
| Loss-in-transit GL | Variance + reason code | GL posted; ITC reversal where applicable |
| Insurance claim trigger | Damage above threshold | Claim workflow initiated |
-
In-transit register
- Input
- Dispatch event
- Output
- Open in-transit position with metadata
-
Courier ETA tracking
- Input
- Delhivery / Bluedart / Shiprocket API
- Output
- Live ETA on dashboard
-
Receipt closure
- Input
- Receipt quantity confirmation
- Output
- In-transit closed; variance flagged
-
Loss-in-transit GL
- Input
- Variance + reason code
- Output
- GL posted; ITC reversal where applicable
-
Insurance claim trigger
- Input
- Damage above threshold
- Output
- Claim workflow initiated
Compliance + integrations
In-transit, accounted properly.
Aged in-transit positions are an audit finding when not reconciled. The register surfaces them at period-end. Loss-in-transit posts with the reason captured. ITC implications addressed at the source.
Regulations we work within
-
Section 17(5), CGST Act
ITC reversal on loss / damage in transit.
-
AS-2 / Ind-AS 2
In-transit stock reflected in inventory valuation.
Connects to
- Delhivery Live ETA + delivery confirmation
- Bluedart Live ETA
- Shiprocket Multi-courier aggregation
Goods in Transit FAQ
What buyers ask.
How are aged in-transit positions handled at period-end?
In-transit positions older than the configured threshold (typically 14 to 30 days) surface on the period-close checklist. The team confirms whether the goods are genuinely in transit (long-distance shipment) or lost. Lost positions write off; genuine in-transit roll forward with a tracking note.
Insurance claims for damaged goods. How does the workflow run?
Damage at receipt above the configured threshold triggers an insurance claim workflow. Photos, bill of lading and damage notes attach. The claim form drafts for the insurance partner. The recoverable amount sits in the insurance-claim-receivable GL until settled.
Can we hold ITC on goods in transit?
Yes. ITC on goods in transit is held until receipt confirmation per Section 16. Where the goods are lost in transit, the ITC reverses under Section 17(5). The reversal posts automatically when the loss-in-transit GL fires.
Connect one courier integration. See live ETAs.
Free trial, one courier API. Last week of dispatches lights up with live ETA. Aged positions surface on the dashboard. Loss-in-transit GL fires on confirmation.