Lodged is not a state, it is a word
The conversation you are having with the forwarder is the same one that happens between a provider and a payer, or between a retailer and a carrier: one party reports the last thing they did, and the other hears it as the completion of the process. "The declaration is lodged" means a message was submitted. It says nothing about whether the authority accepted the message, whether it has been risk-assessed, whether anything has been queried, whether another agency has an interest in the goods, and whether release has been granted.
So the answer starts by decomposing that single word into a sequence of facts, each with an owner and a timestamp, and then asking which of them you can actually observe.
Roughly, and with the caveat that the mechanics differ substantially by jurisdiction, the sequence runs: the carrier reports the arrival of the goods, the declarant lodges a declaration, the authority accepts or rejects the message itself, the declaration is risk-assessed and either routed for a documentary check, selected for physical examination, or passed, duties and taxes are accounted for, any other government agency with an interest gives or withholds its clearance, release is granted, and finally the goods are physically collected from the terminal.
Release and collection are different events and the gap between them is where a great deal of cost hides.
Being able to speak that sequence is most of the answer, because it turns the question from "why is the box stuck" into "which of these nine facts do we have, and which is missing".
Why the broker is opaque, and what to require instead
The broker or forwarder is not being evasive by design. They are usually operating their own system whose interface to you is a person and an email, they hold a status model built for their own workflow, and they have no commercial incentive to expose the moment at which a clearance began to go badly. Meanwhile the authority's responses go to the declarant, not to you, which means the only party who sees the authority's actual messages is the one summarising them.
What you can require, and should require in the contract rather than ask for as a favour, is a small set of specific things. The declaration reference issued by the authority, because that is the identifier that ties your shipment to the process and it is what any subsequent conversation will be about. A status event each time the declaration's state changes, with the authority's own timestamp rather than the broker's. The category of any hold, which matters because a documentary query and a physical examination need entirely different responses from you. And the identity of the party who must act next, since a query addressed to the broker that only your product team can answer will sit unanswered while everyone assumes someone else has it.
Where a customs authority publishes an interface for declarants, and many do, the further step is to become or engage a declarant whose system you control, which converts the black box into your own state machine. That is a large decision with compliance consequences and it is the honest answer to a company for whom clearance delays are a material cost rather than an occasional nuisance.
The alternative, which is worth naming because it is common and cheap, is triangulation. The terminal or port community system usually publishes container status, so you can see whether a box has been discharged, whether it has been gated out, and often whether it is under a hold. The shipping line publishes its own milestones. Those two feeds will not tell you why clearance stalled, and they will tell you within hours that it has, which is enough to start asking.
The clock nobody owns is the one that costs money
The reason a two-day silence is worth an engineering response rather than a phone call is that charges are accruing on several meters at once, and they are owned by different parties.
The terminal charges storage for occupying its yard once a free period expires. The shipping line charges for its container being held beyond a free period, whether the box is sitting inside the terminal or has been taken away and not returned, and those are two distinct charge types with distinct free periods. Any of the free periods may have been negotiated in the freight contract and may differ from the default. Meanwhile the goods themselves may be perishable, seasonal, or promised to a customer on a date, and the commercial cost of missing that date is usually larger than all the charges combined.
The consequence for the design is that clearance state needs a cost dimension attached, not just a status. If your view of an import shows the date the container was discharged, the free periods that apply, and therefore the date on which charges begin, then a stalled clearance can be prioritised by money rather than by whoever shouted. That single derived field, days until charges begin, is often the most valuable thing a visibility build produces, and it is computed from data you already have.
It also determines where the escalation threshold sits. Waiting until charges start is too late; the threshold should be set so that a human is investigating with enough time to resolve a documentary query, which means it is derived from the free period minus the time it typically takes your own organisation to answer.
What actually causes the hold
Knowing the likely causes shapes what you instrument, because each has a different resolution path and a different owner.
A message-level rejection means the declaration itself was malformed or referenced something that does not exist, and it is the broker's to fix, usually within hours. A documentary query means the authority wants evidence: an invoice, a licence, a certificate, proof of an origin claim, or an explanation of a value. That is yours to answer, and the speed with which you can answer it is entirely a function of whether the documents are retrievable in one place or scattered across a shared drive, a supplier's mailbox and someone's laptop. A valuation query is a specific subtype worth calling out, because answering it requires somebody who understands how the declared value was derived, and that person is often in finance rather than in logistics.
Selection for physical examination is different in kind, because there is nothing to fix. The container must be moved to an inspection facility, opened, examined and restuffed, which takes days and costs money, and the only useful response is to notify everyone downstream immediately and revise the promise. Candidates who treat examination as something to be resolved rather than absorbed have not seen one.
Then there are holds that have nothing to do with customs at all: a health, plant health, safety or standards agency with its own interest in the goods, operating on its own timetable, sometimes requiring its own sampling. Those need modelling as separate clearances, because a shipment can be cleared by customs and still not releasable, and a status model with one clearance flag cannot express that.
Instrument the exception, because the exception is the workload
The design failure underneath this whole scenario is that import systems get built for the happy path, on the reasonable observation that most shipments clear without incident. The consequence is that all the effort lands where there is nothing to do, and the cases that consume the organisation's time are handled entirely by email.
The inversion worth arguing for is that the exception is the product. A clearance record with a state, a timestamp per state, a hold type, a named owner of the next action, an age, and a derived cost of delay is a modest amount of data and it changes how the team works. Add a queue ordered by cost of delay rather than by arrival, a place to attach the document that answered a query so that the answer is reusable next time the same product is queried, and a record of the resolution so that recurring causes become visible.
That last point is where the real return sits. The same product queried three times for the same reason is a master data problem masquerading as a logistics problem, and it will keep recurring until someone fixes the classification, the origin evidence or the invoice description. Without a recorded hold reason, nobody can see the pattern, and each occurrence looks like bad luck.
It is your name on the declaration
The final thing to get right, and the thing that most often surprises candidates, is where responsibility sits. The broker files on your behalf as your agent. The importer of record is legally responsible for the accuracy of the declaration, for the duty paid, and for the records behind it, and engaging a competent broker does not transfer that. An error made by a broker using data you supplied is your exposure, recoverable from you, retrospectively.
That reframes the visibility question as a control question. You are not chasing a status update for convenience, you are exercising oversight of a legal obligation someone is discharging on your behalf, and the record of what was declared, on what basis, with what supporting evidence, needs to be retrievable by you rather than by them, for as long as the relevant jurisdictions require. Retention periods vary, and confirming them per market is a better answer than assuming a number.
The broker's status is a summary of their workflow, not a view of the clearance. Insist on the declaration reference and a timestamped state per transition, attach the cost of delay to it, and the two-day silence becomes a queue entry with a deadline rather than a phone call.
© 2026 Preptima. Originally published at preptima.com (opens in a new tab).