This line shows up underneath an Exception heading, which is why it reads like bad news, and it almost never is. A parcel carrying it is sitting still on a schedule somebody chose: the person expecting it, the company that sent it, or a station working around an address that is shut. Nothing is missing, nothing is broken, and no money is owed. What matters is which of those three set the date, because only one of them can move it.
A requested date has an author. Find the author and you have found the only person who can change it.
FedEx keeps a short list of statuses on its tracking guide, and future delivery requested is not one of them. What sits on that list is Exception, a bucket whose published definition points at unavoidable circumstances of the extreme weather and customs variety. Those are events nobody chose. The specific reason prints beneath the heading, and on this one the reason contradicts the bucket it arrived in: somebody did choose.
| Status FedEx publishes | The wording behind it | What it tells you |
|---|---|---|
| Exception | The definition points at circumstances outside the network's control, naming extreme weather and customs delays as the examples. | The heading describes a class of events, not your parcel. The line under it is the message. |
| Delivery updated | “Due to a request or delay, we’ve updated the shipment’s estimated delivery date.” | A request is one of only two things FedEx names as moving an estimated date. Requests are the half people never expect. |
| Ready for pickup | “Your package was redirected to a nearby location because you placed a hold-at-location request. Your package is now ready to be picked up.” | When the request was a counter collection, the parcel stops showing exception wording and lands here instead. |
| We tried to deliver | “FedEx was unable to complete the delivery, resulting in a failed delivery attempt.” | A door nobody answered reads differently from a date somebody picked. Seeing this one instead means no request was made. |
The distinction decides who you contact. A weather exception belongs to nobody and clears when the network reopens. A requested date has an author, and the author is the only party who can undo it.
Working out which one did it takes a minute on the tracking page and saves an afternoon on the phone.
FedEx lets a residential recipient suspend deliveries across a date range of up to 14 days at no charge, and states that normal delivery resumes on the first business day after the end date. Only Express and Ground packages qualify for that hold. A redirect to a staffed location runs on a 7-day clock instead.
UPS publishes that a shipper may have restricted delivery changes for their shipments, which is why a recipient sometimes finds the change screen closed to them. Senders also book arrival dates deliberately for anything that needs a person standing there: appliances, perishables, equipment going to a site that opens on one particular day.
A closed business does push a delivery out. What it rarely produces is this wording, because the reattempt rule FedEx publishes is the following day rather than a scheduled pause. A date sitting several days out did not come from a locked door on its own; a person put it there.
The order to check them in is recipient, then sender, then address. Recipient holds are by far the most common, they are the easiest to confirm, and they are the only one of the three the person reading the tracking page can often fix themselves in under a minute.
Each carrier puts the controls in a different place and attaches a different limit to them. None of them lets a third party override a date that somebody else booked.
| Who set the date | Where it comes off | What the carrier publishes |
|---|---|---|
| A FedEx recipient holding deliveries | The same delivery account that created the hold | The suspension runs to the end date chosen, up to 14 days, and delivery resumes on the first business day after it. Express and Ground packages only. |
| A FedEx recipient wanting one specific day | A paid option inside the same account | The chosen date has to fall within 7 calendar days of the original delivery date. FedEx calls this a premium service and says prices vary based on location. |
| A UPS recipient | The UPS delivery change tool, signed in or as a guest | Fees may apply to all types of requests, and you are charged only when a request is completed. An intercept has to be requested before delivery happens. |
| A USPS resident holding mail | The hold request itself | A start date has to be filed by 3 AM Eastern on the day it begins, and the request can be lodged as much as 30 days ahead of it. |
| The sender, on any carrier | The sender's own account, nowhere else | UPS states outright that a shipper can restrict delivery changes on their shipments. No recipient-side action clears that, and the carrier's phone agents cannot see past it either. |
The last row is the one that catches people out. A buyer who cannot move their own delivery date is not being obstructed by the carrier. They are looking at a setting the person who bought the postage chose, and the fix is a message to that person rather than another hour in a queue.
A requested date is the cheapest thing that can happen to a parcel in transit, and it is worth saying so to a buyer before they say something else to a marketplace. The scan trail carries the whole argument: the original estimate, the line naming the request, and the new date. Three lines pasted into a reply end most of these conversations on the first message.
What deserves your attention is the far end of the pause rather than the pause itself. Every hold expires, and the expiry is where money starts moving, because an uncollected parcel goes back and the return trip rides on postage you have already spent. Those clocks differ by carrier and by product, and they live on their own pages here: the seven-day window at a FedEx counter, and the collection deadline that follows a USPS hold.
For a label bought through SMKlog we report the carrier's status as it arrives, this one included. We cannot lift a hold a recipient placed on their own carrier account, and we cannot pull a scheduled date forward, because neither control sits with the party that bought the postage. What we can do is price the next box before you tape it shut.
Nothing above is a promise about your parcel. It is what those three carriers had on their own pages on 2026-07-31, and the terms attached to a shipment are the ones in force on the day it moves.
The parcel is being held to a date somebody chose, rather than moving as fast as the network can move it. FedEx files the line under its Exception heading, which is why it looks like a fault, but the event underneath is a request. The published status closest to it is Delivery updated, which FedEx defines as an estimated date changed by a request or a delay.
Neither, in the ordinary case. Nothing has gone missing, and the first estimate was replaced rather than missed. The date worth watching is the new one on the tracking page, not the one quoted when the label was bought.
One of three parties. The recipient, through a carrier account that lets them hold or schedule their own deliveries; the sender, who may have booked an arrival date or blocked changes outright; or the delivery address, when a business is shut for a stretch. The scans before the line usually show which.
Only the party who set the date can move it. A recipient undoes their own hold in the account that created it. A sender restriction has to come off at the sender, so calling the carrier will not get you anywhere. FedEx also sells a paid option that pins a specific date within 7 calendar days of the original, and calls it a premium service whose prices vary based on location.
No. A claim is for a parcel that is missing or damaged, and this one is neither. The useful move is to note the new date and open the tracking page again on it.