Your India Post tracking has not updated. What that usually means.
A parcel with no new scan for two days is almost always fine, and the reason is in how scanning works rather than in where the parcel is. Here is the timeline that is normal, and the four cases that are not.
This is the single most common thing people search for about India Post tracking, and the answer is usually the same: nothing has gone wrong. The confusion comes from an assumption the tracking page never corrects — that tracking reports where a parcel *is*.
It does not. It reports where a parcel *was scanned*.
A scan is an event, not a position
A parcel is scanned when it changes hands: booked in at a counter, bagged for a sorting hub, received at the next one, given to a postman. Between those moments it is in a sack on a train, and a sack on a train generates no events.
So a parcel crossing the country can go a day or two with nothing at all on its trail while moving perfectly normally, and a parcel that has been scanned four times today may not have travelled at all. The number of scans tells you how many times it changed hands, not how far it has come.
The timeline that is normal
- Nothing at all for a few hours after booking. A booking is made online; the first scan happens when the parcel is physically handed in at a post office. If the sender booked it this morning and has not been to the counter yet, there is nothing to show.
- One to two days between scans in long-distance transit. Longer across a weekend, and longer again over a public holiday — the network keeps moving on those days but far less is booked in or handed over.
- A quiet stretch in the middle of a long lane. The gap between leaving one sorting hub and arriving at the next is the longest silence on most trails, and it is the one people notice.
The four cases that are worth acting on
Everything else is waiting. These are not:
- No scan at all for six working days if you are waiting for the parcel, or four working days if you sent it. The sender's route is shorter because India Post's case needs the booking record, which only they have.
- Sitting at the destination delivery office for more than a working day or two. Once a parcel reaches the post office responsible for the destination pincode it should go out with a postman quickly. When it does not, the usual cause is an address or phone number the postman cannot work with.
- A delivery attempt recorded that nobody at the address knows about. Confirm the address and the phone number with the sender before the next attempt, because the attempts are finite and the parcel goes back afterwards.
- "Returning to sender" at any point. That is not a delay, it is a decision — the parcel is going back and no amount of waiting changes it.
What not to do
Do not re-enter the number repeatedly. Tracking is not a live feed being withheld from you; the page shows every scan India Post has, and refreshing produces a scan no sooner.
Do not assume a number that returns nothing is a lost parcel. Far more often it is a parcel that has not been handed in yet, or a digit misread off the label. An India Post article number carries a check digit, so a mistyped one is detectable — if our tracking page says the number is not valid, read it off the label again rather than retrying it.
If you do need to raise it
The sender is the route, whoever you are. India Post opens a case against the booking record, and the booking record belongs to whoever paid for the parcel. A recipient contacting a post office without it will usually be sent back to the sender anyway, a day later.
If you booked through Daakly, raise it with us: we hold the record and the full trail, and we open the case on your behalf.
Services
- Business Parcel — The lower-cost parcel lane, at contractual rates.
- Speed Post — India Post’s fastest lane, at contractual rates.
Main pages
Daakly is operated by Yahatech Solutions Private Limited, 51/D Goyal Complex, Opp. Ashima Tower, Bodakdev, Ahmedabad, Gujarat 380054, India. Email team@daakly.com.
Daakly on Instagram
This site needs JavaScript. A plain-text summary for machines is at /llms.txt.