Three different things get lumped into one complaint: an order that was never going to be fast because of who is actually fulfilling it, a leg of the trip that just hasn't been scanned in a while, and a genuine delay the order page has not caught up with yet. They call for different responses, and telling them apart starts with checking who is actually shipping the box.
Who is shipping it matters as much as what the tracking page shows.
The promised date on an Amazon order is only as good as the entity behind it. An item sold and shipped by Amazon itself draws on Amazon's own fulfillment network and the delivery-estimate tools built around it. An item sold by a third-party seller carries that seller's own dispatch time and their own choice of carrier — the Amazon order page still shows an estimate, but it is only as accurate as what that seller told the platform, not something Amazon's own operations can independently guarantee.
Before assuming anything is wrong, check the listing's own fulfillment line. A "Ships from and sold by Amazon.com" order and a third-party order that merely uses Amazon's checkout are not running on the same clock, even when both show the exact same delivery date format.
An order can sit without a visible scan for a day or more while still arriving on time. That gap is common enough on the last-mile leg that it has its own explanation on this site: our page on which shipping company uses the TBA tracking prefix covers why an Amazon Logistics tracking number often shows sparse or missing scans on a carrier's own site — the number belongs to Amazon's own delivery network, not USPS, UPS or FedEx, and it does not get scanned on the same schedule those carriers use.
Silence on tracking is not the same fact as a delay. Amazon's own order page status, and its own email if one arrives, are the more reliable signal than a gap in scan history alone.
The order page's own "Arriving" status is a forward-looking label attached to whatever date the estimate currently shows — it updates automatically when the estimate itself moves, which is why it can keep saying "Arriving" through a genuine slip without reading as an error message. That is a different design from a carrier's own tracking page, where a status usually only changes on an actual scan.
Read "Arriving" as a live estimate rather than a confirmation, in either direction: it is not proof nothing is wrong, and a day without a status change is not proof something is. The reliable signal is whether the date itself has moved and whether it keeps moving forward on each check.
Some Amazon orders, particularly heavier or oversized items and some third-party listings, travel on USPS, UPS or FedEx rather than Amazon's own delivery network. Once that is the case, the diagnosis is no longer Amazon-specific. Our general page on why a package is delayed covers the seven ordinary carrier-side causes behind a stalled shipment — weather, a missed connection, an address exception and the rest — none of which have anything to do with which platform sold the item.
Amazon publishes no page describing what its order-page statuses mean or how its delivery estimate is calculated, and its retail help center blocks automated reading — the same wall recorded on this site's guide to the TBA tracking prefix. So the three causes above are described from how the order page and carrier tracking behave, not quoted from Amazon wording, and no figure on this page is Amazon's. Check your own order's status screen for anything more precise.
Usually one of a small set of causes: the item is fulfilled by a third-party seller rather than Amazon itself, it is moving through Amazon's own last-mile network rather than a carrier with public tracking that updates on the same schedule, or a genuine delay has occurred that the order page has not caught up with yet. Checking which of the three applies, in that order, is faster than assuming the worst from a stale-looking tracking page.
Because the estimate is a model, not a guarantee, and it depends on which entity is actually fulfilling the order. A listing sold by a third-party seller carries that seller's own dispatch time and carrier choice, which Amazon's own delivery estimate tools cannot see any better than the buyer can.
That the order is still in motion toward the date shown next to it, not that anything is wrong. It is a status on Amazon's own order page and is not the same as a tracking scan on a carrier's own site — an Amazon Logistics leg in particular can go a day or more without a visible update while still on schedule.
Because not every leg of an Amazon delivery is scanned as often as a traditional carrier package. Our page on which shipping company uses the TBA tracking prefix covers why an Amazon Logistics number often shows sparse scans on usps.com or ups.com — a different problem from a genuinely delayed order.
Once the estimated date has clearly passed with no update, or once Amazon's own email has told you a delay occurred. If the parcel was instead handed to USPS, UPS or FedEx rather than Amazon's own network, our general page on a delayed package covers the seven ordinary carrier-side causes, none of which are specific to Amazon.