Cargo release is not gate-out
DCSA defines cargo release as the authorization that allows cargo to leave the container yard, typically granted by the carrier. It is often confused with gate-out, but gate-out is the physical event of the container passing the terminal gate. Cargo release is the legal and operational authorization that must exist before that physical event can occur.
The DCSA Industry Blueprint 2026.Q1 describes pre-release as a series of validations. The applicable Bill of Lading or Sea Waybill must be checked; where title transfer applies, the endorsement chain must be valid. For an eBL, surrender for delivery must be accepted, and third-party collection may require a Letter of Authority.
The right to take delivery is only one layer. Customs clearance, credit or payment clearance, mandatory references, local documentation and terminal approval may also be required. Once these conditions are satisfied, the carrier can authorize release and issue the operational instructions needed for the terminal, inland carrier or delivery party to execute collection.
Digitizing the bill of lading is not enough. An eBL can remove the paper original, but if surrender is not connected to the release system, customs data is re-keyed or the terminal still waits for email confirmation, the chain stops at the final step. Straight-through processing requires machine-readable delivery entitlement.
DCSA Bill of Lading 3.0 already covers surrender for delivery. Use case 12 allows the holder to request surrender to collect cargo; use case 13 requires the carrier to verify the request and identity before changing the document state to SURRENDERED FOR DELIVERY. This connects digital title to physical cargo, but not the entire release process.
APIs must connect delivery entitlement with release conditions
DCSA's 2026 Standards Roadmap identifies import cargo release as a new standardization project because no common API standard currently exists for the process. DCSA's end-to-end objective is for data handoffs to move from booking and transport documents through to import release without manual intervention at the junctions.
Arrival Notice is an important precursor already standardized by DCSA. Version 1.0, published in late 2025, replaces PDF-and-email workflows with machine-readable API data and gives consignees structured information needed before release and collection.
Cargo release, however, needs more than arrival information. A release workflow needs to know whether the transport document has been surrendered, customs has cleared the goods, freight and local charges have been settled or credit-approved, the consignee or representative is authorized, other holds remain, and the terminal is operationally ready. A single failed condition should keep the release on hold.
Identity is critical. Digital release is secure only when the system knows who is requesting delivery rights and on whose behalf. Shared passwords, forwarded PDFs and emailed delivery orders can be copied. API-based release therefore needs authentication, delegation, audit trails and revocation, with references bound to the correct shipment and equipment.
The industry also needs to avoid creating more portals. If every carrier operates a release portal, every terminal has an ePort and every forwarder re-enters the same data in a TMS, digitization merely replaces paper with screens. Standard APIs create value when status moves across carrier, terminal, forwarder and trucker systems while preserving permissions.
Cargo should move to a 'released' state only when six conditions are clear: the transport document is valid; surrender or endorsement is complete; the consignee or authorized representative is verified; customs clearance is available; freight and local charges are paid or credit-approved; and the terminal has no operational hold. The key is structured status exchange. If these checks still depend on emails, PDFs and manual re-entry, the eBL revolution stops immediately before the terminal gate.
Vietnam: eDO exists; interoperability is the next step
Vietnam has already digitized significant parts of cargo release. Saigon Newport has deployed ePort and electronic delivery-order functions across its ecosystem. Tan Cang-Cai Mep Thi Vai specifically highlights EPORT, EDO, online payment and electronic cargo delivery as core services that allow customers to perform import and delivery procedures remotely.
In June 2026, Saigon Newport's ePort instructed customers to check pickup sequence before dispatching trucks. That detail captures an important reality: authorization alone is not enough. Release must connect with yard sequencing, truck dispatch and gate execution so vehicles do not arrive before the unit is ready.
An eDO inside one ecosystem, however, is not yet end-to-end cargo release. Importers still interact with shipping lines, agents, customs, terminals, depots, forwarders and trucking companies. When each party uses a different identifier or status, staff continue downloading files, sending screenshots, forwarding emails and manually reconciling the shipment before a truck can be sent.
A stronger architecture should rely on common references. Bill of Lading number, shipment ID, container number, customs declaration, eDO reference and truck appointment should connect within one flow. When the carrier changes release status, the terminal should receive a machine-to-machine notification; when customs or payment status changes, the shipment should update without another person retyping the event.
Security must advance at the same time. The right to collect a container has real economic value; releasing it to the wrong party can cause loss even when upstream documents are genuine. Consignee, broker, forwarder and trucker identities therefore need MFA, time-limited delegation, audit logs and step-up verification for sensitive changes.
Ports and carriers should also measure more than whether an eDO was issued. Useful KPIs include time from final clearance to gate-out, release-error rates, holds caused by data mismatch, repeated manual data entry and the share of transactions completed straight-through. Those metrics reveal whether digital release actually reduces dwell time or simply moves paperwork online.
The final issue is standards. DCSA placed import cargo release on its 2026 roadmap precisely because container shipping still lacks a unified API standard for this last step. Vietnam has practical experience with ePort and eDO. The next stage does not require replacing those systems; it requires making them able to communicate in the same data language as carriers, forwarders and global standards.
The container-documentation revolution is not complete if title and delivery rights are digital but the terminal still needs a final email or manual confirmation before opening the gate. Cargo release is where digital trade must finally touch physical delivery.
When surrender, customs, payment, identity and terminal status are connected through APIs, release can move from a chain of fragmented confirmations to an auditable and executable data decision. This final step may look small, but it determines whether an eBL ultimately results in a container leaving the port faster.
