Courier Stuck in Transit: When to Wait, When to Chase, and When It Counts as Lost
The tracking hasn't moved since Friday night and the buyer is asking. Most silent parcels are fine. Some aren't. The difference is how long the silence has lasted in which status, and that can be counted.
Quick Answer
A shipment is "stuck in transit" when no new scan has arrived for longer than normal. Up to a day in transit is routine. After two silent days ShipSeth escalates it to the courier; after seven days in transit, or five after pickup with no hub scan, it is treated as lost and claimed within 15 days of expected delivery.
What does "stuck in transit" actually mean?
It means the courier has your parcel and hasn't scanned it anywhere new for a while. That is all it means.
Tracking is a list of scans, and a scan only happens when someone points a gun at a barcode. Between hubs, parcels travel inside sealed bags. The bag gets scanned when it leaves Surat and when it reaches the Ahmedabad hub; your parcel inside it does not. So a kurti set going from Surat to Lucknow can show "Bag received, Ahmedabad hub" on Friday night and nothing until "Reached Lucknow" on Monday, while it was on a truck the whole weekend.
The question is never "is it moving?" You can't see that. The useful question is narrower: how long has it been quiet, in which status, against what is normal for that status?
How long is too long without a tracking update?
It depends on the status. A parcel can sit quietly In Transit for a day without anyone worrying, but a day on Out for Delivery means the run was never closed.
These are the hours ShipSeth's own tracking system uses. Silence is counted from the last courier scan (or from the moment the shipment entered its current status, if that is later). When a shipment crosses a line, a case opens for the operations team and climbs in priority at each step after it.
| Status | Normal | Watch | Chase | Escalate | Suspected lost |
|---|---|---|---|---|---|
| Picked Up | Under 12 hours | 12 h | 24 h | 48 h | 120 h (5 days) |
| In Transit | Under 24 hours | 24 h | 48 h | 72 h | 168 h (7 days) |
| Out for Delivery | Same day | 12 h | 24 h | 48 h | n/a |
| NDR action sent, no re-attempt | Under 24 hours | 24 h | 48 h | 72 h | n/a |
Two more rules run alongside the clock. A shipment that passes the courier's confirmed delivery date without being delivered is flagged on its own, even if the scans look fresh, and at three days late it moves up to escalation. And Out for Delivery never reaches "suspected lost" on silence alone: a rider who doesn't close the run is chased as a courier problem, not written off.
Before pickup and on the return leg the hours are different. A missed pickup is covered in the pickup and cut-off guide, and a return that stops moving has its own checker in the RTO guide.
Is my shipment stuck? Check it here
Enter the status, the time of the last scan and the expected delivery date from the order. The check counts the silent hours against the table above and tells you what to do now, when the next step kicks in, and the last day to claim if it never turns up.
Silent for
61 h (2.6 days)
Verdict
Chase it
Last day to claim if lost
Wed, 11 Nov, 2026
15 days from the expected delivery date
Most a claim pays
₹1850
Lesser of invoice value or ₹5,000
Two days of silence in transit. ShipSeth's desk escalates it to the courier for a status. If the buyer is asking, tell them it is being traced, not that it is "on the way".
Next step on the clock: Escalate at Mon, 26 Oct, 9:40 pm if no scan comes first.
Subject: Shipment not moving, AWB [AWB] AWB: [AWB] Courier: [courier] Current status: In Transit Last scan: Bag received, Ahmedabad hub, 2026-10-23 21:40 No scan since: 61 h (2.6 days) Expected delivery date: 2026-10-27 Invoice value: ₹1850 Please ask the courier for a trace from the last hub and a new delivery date. If they cannot locate it, please raise a lost-shipment claim.
The check runs in your browser. The hours are the ones ShipSeth's tracking desk works to today and may be tuned; the 15-day window and ₹5,000 cap come from the refund policy and terms. The three examples are made up to show how the check reads, not real ShipSeth cases.
Why do parcels stop getting scanned?
Usually because nothing scannable happened, not because something went wrong. The table lists the causes in rough order of how often a silent parcel turns out to be one of them. Which cause is likely depends on the leg: a parcel quiet in Picked Up is still in your city, while one quiet in In Transit is somewhere on the line-haul. The first, middle and last mile leg finder maps each status to its leg.
| Cause | What the tracking looks like | What to do |
|---|---|---|
| Parcel is inside a sealed bag | Last scan at an origin or transit hub, then a jump straight to the destination city | Nothing. Wait one more day on long lanes. |
| Waiting for the next truck or flight slot | Same hub for a day, often over a Sunday or a holiday | Wait, but note the hub. Two days is the point to ask. |
| A hub skipped the scan | Silence, then a scan two hubs further on | Nothing; it resolves itself. You only learn this afterwards. |
| Misrouted to the wrong hub | A scan in a city that is not on the way | Write to support the day you see it, with the scan text. |
| Label torn or unreadable | Long silence at one hub, no movement at all | Support asks the courier to search the hub's exception shelf. |
| B2B freight held for paperwork | LTL consignment stopped at a hub or checkpost | Check the e-way bill and the LR copies travelling with the goods. |
| Lost or damaged in handling | Silence that never ends | Lost-shipment claim through support, within 15 days of expected delivery. |
Remote pincodes add their own quiet days. A courier that reaches an ODA pincode through a partner, or runs that route only a few days a week, will show a parcel sitting at the last proper delivery centre while it waits for the van. If the delivery pincode was ODA on the courier you booked, add a day or two to your patience before chasing. You can see the ODA flag per courier on Track & Check.
What does ShipSeth do when a shipment goes quiet?
It watches every live shipment against those hours and opens a case for its operations team when one crosses a line, without waiting for you to notice.
Couriers push most scans to ShipSeth as they happen. When one doesn't, the system asks the courier for the latest tracking itself: about once an hour while a parcel is in transit, and every 15 minutes once it is out for delivery. Every in-flight shipment is then re-checked every 15 minutes against the silence hours. That second part matters because silence raises no alert on its own. A parcel that stops getting scans sends nobody a message; something has to notice the absence.
When a case opens, the playbook for a silent parcel is short: look at the courier's own tracking for anything that hasn't reached us, escalate to the courier for a status, and if it is still silent at the top of the ladder, raise a lost claim. A shipment showing a different status in ShipSeth from the courier's portal is handled as a data problem and corrected, so what you see on the order stays honest.
On the order itself you see two things worth reading. Under the status, Last scan shows how long ago the courier last scanned it. Next to it, Expected delivery carries a tag: Courier confirmed when the date came from the courier, Estimated when ShipSeth worked it out from the lane. An estimated date that has passed is a softer signal than a courier-confirmed one. Where each date comes from, and why the estimate can read a day early, is in what EDD means in courier.
When should I write to support, and what should I send?
Write once the check says "Chase it", or earlier if you have seen a scan in the wrong city. Send the AWB, the courier, the last scan as it appears, and the expected delivery date.
- Open the shipment in Orders. Switch the scan history to all scans so you see every event, not just the status changes.
- Copy the last scan exactly. "Bag received, Ahmedabad hub, 23 Oct 9:40 pm" lets the courier find the bag. "It's stuck" doesn't.
- Send it by email if a claim is likely. WhatsApp is fine for a quick chase. Once the parcel is past "Escalate", use email so the invoice copy and the thread are in one place. The contact page has both.
- Answer the buyer with what you know. "It is being traced with the courier, I'll update you by Wednesday" holds better than a guessed delivery date.
- Mark the claim date. Fifteen days from the expected delivery date. Past that, a lost claim is out of time even if the courier admits the loss.
Keep the signed pickup manifest for the day the parcel left. If the first hub never scanned it, that sheet is the only proof the courier took it from you.
Can I cancel or reship a shipment that is stuck?
You can't cancel it from the dashboard once it has been picked up. You can always reship, and sometimes you should.
Cancellation in ShipSeth works only until the courier marks the shipment Out for Pickup; after that the parcel is physically in the network and the courier has to deal with it. For a stuck parcel, the options run through support: keep tracing, send it back to origin, or move to a lost claim.
Reshipping is a business call. Take the Ludhiana example in the check: a ₹7,400 carton of hosiery, picked up on a Monday, no hub scan by Saturday. That buyer is a distributor with shelves to fill, and a claim pays at most ₹5,000 of the ₹7,400 without insurance. Reship now and let the claim run behind it. For a ₹640 order to a first-time COD buyer in Pune, wait for the courier's answer; there is no money of yours at risk on a COD parcel that hasn't been delivered.
If you reship and the first parcel turns up later, it will either reach the buyer or come back to you as an RTO. Tell support you've reshipped and keep both AWBs on the same email thread, so nobody chases a parcel that has already been replaced.
What if it is B2B freight that has stopped moving?
Chase the LR, not the box. On LTL freight the consignment travels and is tracked as one lorry receipt, with a master AWB over the individual carton AWBs.
Freight goes quiet for reasons parcels don't. Trucks wait at a hub until there is enough load for the next lane, and a consignment can be held for paperwork. If the goods are worth more than the e-way bill limit, check the e-way bill was generated and is still within its validity for the distance; the e-way bill guide shows how validity is counted. Check that the LR copies are travelling with the goods; the lorry receipt guide explains which copy goes where.
A lost or short consignment pays out under the risk you chose at booking. The owner's risk vs carrier's risk guide shows what each one actually pays.
Silent parcels get noticed
Book Through ShipSeth and Let the Tracking Desk Watch the Gaps
Free to register, no monthly fee. Compare live courier rates before you book, pay per shipment from a prepaid wallet, and see the last scan on every order.