A package stuck in customs is almost never randomly stuck. Customs holds have causes, the causes are boringly consistent, and most of them are the sender's to fix. Waiting harder does not clear a parcel that is missing a commercial invoice.
Here is why parcels actually stall at borders, who has to act for each cause, and how stores make customs invisible for the next thousand parcels.
The real reasons packages get stuck
- Unpaid duties or import VAT. The most common cause for shoppers. The parcel shipped DDU/DAP, so the carrier is waiting for the customer to pay duties plus a handling fee before releasing it. The parcel is not "stuck", it is held for payment.
- Missing or vague paperwork. No commercial invoice, a description like "gift" or "merchandise", a missing HS code. Customs cannot classify what it cannot read.
- Valuation queries. The declared value looks wrong (too low is the classic), so customs asks questions. Undervaluing to dodge duties is what turns a two-day hold into a seizure risk.
- Restricted or inspected goods. Batteries, cosmetics, food supplements and anything organic draw extra checks in many countries.
- Random inspection or backlog. A real but overused explanation. Peak season and strikes create genuine queues, but if your parcels stall repeatedly, the cause is in the first four.
The status usually reads "held by customs", "clearance event" (DHL's wording), "customs clearance" (Bring into Norway), or a generic delivery exception.
Who has to act
The customer acts when duties are due on a DDU shipment: pay the carrier's import invoice and the parcel moves, usually same day. Nothing else the customer does speeds up customs.
The store acts on everything else: supplying the missing invoice, correcting the HS code or value, answering the valuation query. The carrier's broker handles the conversation, but the data comes from you.
Nobody needs to act during genuine inspection queues. One to three days of customs silence on a cross-border parcel is normal. It becomes a problem when the status repeats for a week or explicitly asks for documents or payment.
How long is normal?
Routine clearance: hours to two days. Payment holds: as long as the customer takes to pay, plus a return-to-sender deadline (commonly one to three weeks). Document problems: however long the sender takes to respond, which is why the stores that answer broker emails in hours have "fast customs" and everyone else has stories.
How stores make customs boring
- Ship DDP on lanes that matter. Duties collected at checkout, cleared before arrival, no payment hold and no surprise fee. The trade-offs per lane are covered in DDP vs DDU.
- Send complete data on every label. Real product descriptions, correct HS codes, honest values, recipient phone number. This is a carrier integration quality question: the data flows from your catalog to the customs declaration automatically or someone retypes it badly.
- Use the schemes built for parcels. IOSS for low-value EU imports, VOEC for Norway. They exist to pre-clear exactly the parcels that otherwise queue. Background in our ecommerce tariffs guide.
- Message the customer at the customs scan. A held parcel with an honest explanation ("customs is processing your parcel, no action needed" or "the carrier will contact you about import fees") produces no ticket. Silence produces a WISMO ticket and a one-star delivery review.
In Pango, the customs scan is a trigger like any other: the customer gets the right message for the cause, repeated holds on a lane flag the data problem behind them, and a returned-by-customs parcel opens the returns flow automatically.
The bottom line
Packages stall at borders for payment, paperwork and valuation, in that order, and the sender controls two of the three. Ship DDP where it counts, put real data on every declaration, and message the customer at the customs scan. Pango automates all three across 100+ carriers. See the post-purchase operations platform and book a demo.
