Customs entry status is where an import entry stands in the clearance process: filed, accepted, under review, held for exam, released, or liquidated. A customs entry status request asks the broker or forwarder to report that state for a specific shipment, usually because a pickup is waiting on it.
These requests stack up wherever imports move. The importer wants to know if the shipment has cleared, the trucker cannot schedule pickup until release, and the ops desk pings the brokerage side for the same answer it was just asked. The state itself is structured data: it lives in the entry filing system and moves through a known sequence, which makes the lookup mechanical. What makes customs different from the rest of the queue is what sits next to the lookup: classification, valuation, and admissibility questions that read as conversational but are legal determinations with penalty exposure.
The frame to reject is the customs bot that answers everything. An AI that guesses an HTS code or opines on valuation is not doing support, it is practicing customs compliance without a license, and a wrong answer is not a bad ticket, it is duty exposure and penalties. The opposite failure is just as common: treating all customs email as untouchable and burying a purely mechanical status lookup in a licensed broker's queue. The line is not the word customs; it is lookup versus determination.
Status lookups vs customs determinations at a glance
| Dimension | Status lookup | Customs determination |
|---|---|---|
| The question | where does the entry stand | what is it, what is it worth, is it admissible |
| Source of the answer | entry status in the filing system | classification and valuation judgment |
| Consequence of error | a wrong update, correctable | duty exposure, penalties, compliance risk |
| Automation posture | automate end to end | human-gated, always |
Aide, the agentic AI platform for customer experience, draws that line in how the intent is scoped, not in a prompt. Entry-status requests are classified as their own intent and resolved from the systems of record, on the thread, with every lookup logged. HTS, valuation, and admissibility questions are recognized as different intents entirely and always route to the licensed team; the AI holds no permission to answer them, so it cannot drift into them under load. What stays gated and what automates across the rest of the freight queue is covered in [Aide for logistics and freight](/industries/logistics).
Frequently asked questions
- What do the customs entry statuses mean?
- An entry moves through a known sequence: filed with customs, accepted, possibly held for documentation or exam, then released, and eventually liquidated when duties are finalized. Released is the state most requesters care about, because it is what lets the cargo move.
- Why are HTS classification questions human-gated?
- Because classification is a legal determination, not a lookup. The code chosen sets the duty owed, and errors carry penalty exposure for the importer. A governed deployment scopes AI to reporting entry status and routes classification, valuation, and admissibility to licensed people.