Ask DHL to name the last completed clearance event and the queue that owns the next one. “Documents received” is not the same as “accepted by customs,” and “awaiting clearance” does not say whether a customer action exists. Request the submission timestamp, rejection reason if any, and written storage or return consequence for this waybill. That record prevents the shipper, importer and broker from each assuming another party has already answered.
← Full guide: DHL Shipment Held in Customs (Find the Exact Blocker)
Separate a broker task from an authority wait
Ask DHL to name the last completed clearance event and the queue that owns the next one.
Start here
Ask DHL to name the last completed clearance event and the queue that owns the next one. “Documents received” is not the same as “accepted by customs,” and “awaiting clearance” does not say whether a customer action exists. Request the submission timestamp, rejection reason if any, and written storage or return consequence for this waybill. That record prevents the shipper, importer and broker from each assuming.
What applies to this exact problem
Check these first
- Ask DHL to name the last completed clearance event and the queue that owns the next one.
- Request the submission timestamp, rejection reason if any, and written storage or return consequence for this waybill.
Fix it in this order
- Ask DHL to name the last completed clearance event and the queue that owns the next one.
- Request the submission timestamp, rejection reason if any, and written storage or return consequence for this waybill.
Evidence to keep
- Tracking history — keep it with the evidence for “Separate a broker task from an authority wait”.
- Order/invoice and shipping label — keep it with the evidence for “Separate a broker task from an authority wait”.
- Photos/proof of delivery or missing-item evidence — keep it with the evidence for “Separate a broker task from an authority wait”.
- Carrier/seller case number — keep it with the evidence for “Separate a broker task from an authority wait”.
Do not make it harder
- Opening many duplicate carrier cases For “Separate a broker task from an authority wait”, that can hide whether the underlying issue is actually resolved.
- Discarding packaging before a damage/loss claim For “Separate a broker task from an authority wait”, that can hide whether the underlying issue is actually resolved.
- Assuming “delivered” proves possession For “Separate a broker task from an authority wait”, that can hide whether the underlying issue is actually resolved.
How you know it is fixed
- You can reproduce the charged or projected amount from documented inputs for “Separate a broker task from an authority wait”.
- Any unexplained difference has a written explanation or correction for “Separate a broker task from an authority wait”.
If this still isn't resolved
- Seller marketplace support State the unresolved issue explicitly: “Separate a broker task from an authority wait”.
- Carrier trace/claim process State the unresolved issue explicitly: “Separate a broker task from an authority wait”.
- Payment dispute/consumer route where the seller or carrier fails to resolve an eligible case State the unresolved issue explicitly: “Separate a broker task from an authority wait”.
Parent-guide references
These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.
Need the complete context?
This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.