Delivery order release is the authorization that lets import cargo leave a terminal's or carrier's custody: the forwarder or NVOCC issues a delivery order naming who may pick up the freight, and releasing it clears the trucker to collect the container. Until the release happens, the cargo does not move.
In an import operation these threads run hot. Truckers ask when the DO will be released so they can schedule pickup, importers push because every idle day at the pier risks demurrage once free time runs out, and the release itself waits on preconditions: freight charges settled, the original bill of lading surrendered or a telex release on file, customs clearance complete. The ops desk fields the same two questions all day, has it released and what is blocking it, while the actual release is a deliberate act with real preconditions behind it.
The pitch to reject is full automation for its own sake: if the AI can see the preconditions are met, let it release. Releasing cargo to the wrong party is not a mis-sent email; it is misdelivery of goods someone else holds title to, and there is no recall once the container is on a chassis. An action with that blast radius should never execute silently, however confident the model is. This is the difference between automating conversation and automating custody.
Answering about a release vs executing a release at a glance
| Dimension | Answering about a release | Executing a release |
|---|---|---|
| What it changes | nothing: it reports state | custody of the cargo |
| Reversibility | fully reversible | effectively none once the freight is picked up |
| Preconditions | none | charges settled, OBL surrendered or telex release, customs cleared |
| Automation posture | automate end to end | human-approved blocking gate, every time |
Aide, the agentic AI platform for customer experience, is built for exactly this split. It answers the status side instantly: which preconditions are met, what is still blocking, when free time ends, all read from the systems of record and logged. The release itself is different: in Aide's ASOPs it is a blocking gate, meaning the AI can assemble the release-ready picture and stage the action, but a named human approves before anything releases cargo. That is what governed automation means when an action transfers custody. The full map of freight's hard gates and what automates around them is in Aide for logistics and freight.
Frequently asked questions
- What has to happen before a delivery order is released?
- Typically three things: freight and accessorial charges are settled, the original bill of lading is surrendered or a telex or express release is on file, and customs has cleared the entry. Terminals may add their own requirements before honoring the DO.
- Can delivery order release be automated?
- The questions around it can: status, blockers, and free-time timing are lookups an AI resolves end to end. The release action itself should stay behind human approval, because it transfers custody of the cargo and cannot be reversed once the freight is gone.