A shipping delay is any order that misses its promised date. The causes are boringly consistent. Slow warehouse handover, a carrier sitting on a parcel, a customs hold, a weather event, or a bad address. The problem is rarely that a delay happened. It is that the customer found out before you did and opened a ticket. The fix is to catch the delay first and say something useful. This guide walks through the common causes and what to do about each one.
What counts as a shipping delay (and what does not)
A delay is an order that misses the date you promised. That definition matters, because the promise is the baseline. If you never showed a date, the customer sets their own expectation, and you fail against a number you never agreed to.
So a "delay" is measured against your estimated delivery date, not against a vague hope. An order arriving on day five is not late if you promised five days. It is late if you promised two.
What does not count is normal transit time. A parcel moving through the network on schedule is not delayed just because it is not delivered yet. The trigger is a missed milestone, not an impatient customer. Getting this line right keeps you from chasing false alarms.
Cause 1: slow warehouse handover time
The first delay often happens before the carrier ever touches the parcel. Handover time is the gap between an order being placed and the parcel actually leaving the warehouse. When that gap stretches, you lose days no carrier can win back.
This is the delay most brands miss, because it hides inside their own operation. The tracking page still says "processing," so nobody flags it. Meanwhile the promised date is quietly slipping.
The fix is to measure handover time as its own number and watch it. If orders routinely sit for two days before shipping, that is not a carrier problem. It is a warehouse throughput problem, and it is yours to fix or renegotiate with your 3PL.
Cause 2: carrier stalls and exceptions
Once the carrier has the parcel, a new set of delays begins. A parcel can sit at a facility, get misrouted, or throw an exception scan that stops its progress. These are the delays you see on the tracking page as a status that stops moving.
The hard part is noticing. A parcel that has not scanned in three days is a problem, but nothing actively tells you that. Silence on a tracking page reads the same as normal transit until it is too late.
Here is how the common carrier events break down.
| Event | What it usually means | What to do |
|---|---|---|
| No scan for days | Parcel stalled or lost in a facility | Flag it, open a trace with the carrier |
| Exception scan | Delivery blocked (address, damage, hold) | Read the reason, act on it |
| Misroute | Parcel sent to the wrong hub | Watch for recovery, warn the customer |
| Return to sender | Delivery failed repeatedly | Contact the customer before it ships back |
The pattern across all of these is the same. A carrier tracking status either stops or turns into an exception, and you want to catch that the moment it happens.
Cause 3: customs holds on cross-border orders
Cross-border orders add a delay type domestic orders never see. A parcel can clear the warehouse and the carrier on time and still sit at a border for days waiting on customs.
Customs holds happen for real reasons. Missing or wrong paperwork, a duties question, or a random inspection. The parcel is not lost. It is parked, and neither you nor the customer can rush it.
What you can do is set the expectation up front and watch the customs milestone. If a parcel enters customs and does not clear within the normal window for that lane, treat it as a delay and message the customer. Cross-border transparency is worth more than a domestic apology, because the customer already expected uncertainty.
Cause 4: bad addresses and failed delivery attempts
The last common cause is the simplest. A wrong or incomplete address, or a delivery attempt that fails because nobody is home. The parcel moved fine right up until the doorstep.
These delays are frustrating because they feel preventable, and often they are. An address that fails validation at checkout will fail again at delivery. A parcel that needs a signature and gets no answer bounces back into the network.
The fix splits in two. Catch bad addresses early, ideally before the label prints. And when a delivery attempt fails, tell the customer immediately with a clear next step, because a fast reschedule beats a parcel drifting toward return to sender.
Turning a delay into a proactive message before the ticket
Here is the shift that changes everything. The delay itself is rarely the real damage. The damage is the customer discovering it first and opening a ticket, or worse, a chargeback.
Flip the order. If you detect the missed milestone before the customer does, you get to control the message. A short, honest note that says "your order is running a day behind, here is the new date" turns a complaint into a moment of trust.
This only works if detection is automatic. A human cannot watch every parcel for a stalled scan. A scan that flags delays across all your orders can, and that scan is the trigger for the message. Proactive beats reactive every time, and it is the core idea behind proactive shipping notifications.
How Pango fits: delay scans that trigger proactive notifications
Pango is one adaptive layer over your orders, carriers, warehouses, and returns. It is not a WMS or a 3PL. On delays, it does one specific thing well. It runs a delay scan as a trigger.
The scan reads normalized status data across your carriers. Pango maps the 10 to 115 different labels carriers report into one clean set, and scrapes tracking data where a carrier's API is poor. When an order misses a milestone, the scan catches it and fires a branded, proactive notification to the customer before they have to ask. That is live today, along with returns and exchanges and analytics across your orders.
Anything beyond the standard triggers, like a custom rule specific to one lane or one carrier, is build-to-fit. It gets built to match your policies rather than forced into a fixed template. If WISMO tickets are the symptom you are chasing, start with our explainer on what WISMO is. For the full platform view, see the transportation management system (TMS) product page.
A simple delay-response playbook
You do not need a complex system to respond well. You need a repeatable order of operations.
First, detect the missed milestone automatically, not by hand. Second, message the customer before they message you, with the new date and a plain explanation. Third, give them one clear action if there is one, like confirming an address or rescheduling.
Then close the loop internally. Log why the delay happened so you can see patterns. If handover time keeps causing delays, fix the warehouse step. If one carrier keeps stalling, that shows up in your analytics and gives you the case to change carriers. The playbook is short on purpose, because a short one gets used.
