WHAT IS A DELIVERY ORDER? IMPORT CARGO RELEASE PROCESS
A Delivery Order (D/O) is an operational release instruction issued after the carrier, agent or NVOCC verifies cargo entitlement and the applicable release conditions. It does not itself create, transfer or replace the right to receive cargo under the transport document. Importers often receive an Arrival Notice and assume that paying a “D/O fee” is enough to move the cargo. In practice, the carrier or NVOCC must verify the lawful consignee, bill-of-lading status, manifest, financial position and any release holds. The importer must then arrange the port or warehouse transaction order, customs release, service payments and trucking. A machinery or components shipment may therefore remain in the yard even though the D/O has been issued. This article explains the legal and operational nature of a D/O, the required data, FCL/LCL workflows and the controls needed to collect cargo under the correct authority, at the correct location and within the available time.
Operational compilation: 21 July 2026 · Scope: inbound FCL/LCL sea cargo
QUICK FACTS
The carrier or NVOCC authorises cargo/container delivery within the stated scope after the applicable release conditions are satisfied; the D/O itself does not create a new title or entitlement.
The entitlement to receive cargo still comes from the original bill, sea waybill, telex/surrender release or another valid transport document.
A D/O alone cannot gate cargo out where customs supervision, port orders, service payments or operational holds remain outstanding.
FCL involves container release, terminal orders, trucking and empty return; LCL involves CFS/warehouse release, tally and package collection.
SCOPE OF APPLICATION
This article covers inbound sea freight in Vietnam, with emphasis on machinery, equipment, industrial components and carton/pallet cargo moving as FCL or LCL. It is intended for importers, procurement, logistics, documentation, finance, customs brokers and inland transport teams.
Limitation: terminology, documentation, release channels, D/O validity, fees and ePort procedures differ by carrier, NVOCC, agent, terminal, ICD, CFS and shipment. Local instructions, tariffs and transport contracts remain controlling.
TERMS AND DEFINITIONS
| Term | Meaning | Operational role |
|---|---|---|
| Delivery Order – D/O | A delivery/release instruction issued by a carrier, agent, NVOCC or another entitled release party after the conditions for cargo delivery are met. | Allows the terminal/CFS or connected system to recognise delivery authority; it may be paper, PDF, code or system data. |
| eDO – Electronic Delivery Order | The electronic form of the D/O or cargo-release data transmitted through a portal, email or system integration. | Paperless format does not remove the need to check scope, validity, named location, empty return and authorised party. |
| OBL – Original Bill of Lading | An original bill may be issued to order, bearer or named consignee; transferability and lawful entitlement depend on its form. | The carrier may require presentation, endorsement or surrender of the original(s) specified by the bill terms and local instructions; after delivery, remaining originals no longer carry collection value. |
| Sea Waybill – SWB | A non-negotiable sea transport document. | The named consignee may be released under local verification without presenting an OBL. |
| Telex/Surrender Release | Origin-side confirmation that the OBL has been surrendered and destination release may be processed. | A scan of an OBL is not enough; the release status must exist in the carrier/NVOCC system. |
| Arrival Notice | An arrival notification covering ETA, voyage, location, charges and pickup preparation. | Starts the preparation process but does not itself confer delivery authority. |
| Container/Cargo Release | A status or instruction permitting delivery of a container or cargo within a defined scope. | May be linked to a D/O, but labels and scope differ by system. |
| Port transaction order / ePort order / eEIO–eEIR | A transaction or handover record issued by a terminal/port system after service registration and payment; labels may include ePort order, eEIO, eEIR or a port-specific term. | It is not the carrier D/O; it is the next execution layer for terminal operations. |
NATURE AND OPERATING MECHANISM
1. Where does the D/O sit in the entitlement chain?
The bill of lading or other transport document identifies the lawful consignee and the basis for controlling the cargo. The carrier/NVOCC then checks the document, manifest, accounts and shipment status before issuing the D/O or eDO. The terminal or CFS uses the resulting release data to execute delivery.
2. Why can there be more than one release layer?
For a direct MBL shipment, the consignee normally deals with the ocean carrier or its agent. Where an HBL–MBL structure exists, the NVOCC/forwarder must resolve the master-level entitlement and then issue a house-level release. The importer should not assume it must physically collect two D/Os; it should verify which release is used by the terminal/CFS and whether the master hold has been cleared.
3. How is the D/O different from customs and port orders?
The D/O addresses delivery authority under the transport contract. A terminal/ePort transaction order addresses the physical port operation; status labels are not uniform across ports. The declaration and customs-supervision status address regulatory release. These layers interact but do not replace one another.
HOW D/O DIFFERS FROM B/L, ARRIVAL NOTICE, CUSTOMS AND PORT ORDERS
| Document/status | Issuer/controller | Primary purpose | Enough to collect cargo? | Critical checks |
|---|---|---|---|---|
| B/L or SWB | Carrier/NVOCC | Evidence of carriage and basis for identifying the lawful consignee. | No; destination release is still required. | Consignee, B/L number, document type, endorsement/surrender status. |
| Arrival Notice | Carrier/agent/NVOCC | Arrival, location, ETA, charges and collection instructions. | No. | Voyage, POD, terminal/CFS, containers, free time and D/O contact. |
| D/O or eDO | Carrier/agent/NVOCC | Authorises delivery of cargo/container within the stated scope. | Not necessarily; customs and terminal/CFS execution remain. | B/L, container/packages, location, validity, authorised party and empty return. |
| Customs declaration/supervision status | Customs and connected systems | Regulatory declaration and permission to move cargo out of customs supervision. | Does not replace the D/O. | Bill, container, location, clearance/release and holds. |
| Terminal/ePort transaction order | Terminal/ICD/CFS | Registers the transaction, vehicle, services and operational delivery. | Execution layer, subject to all other releases. | eDO number, B/L, container, truck/driver, QR/OTP, services and validity. |
| EIR/delivery record | Terminal/depot/CFS | Records condition and handover time for the container/cargo. | Evidence during/after collection. | Container, seal, damage, time in/out, packages and acknowledgement. |
DOCUMENTS AND CONDITIONS BEFORE REQUESTING RELEASE
| Condition group | Required data/documents | Prepared/confirmed by | Lock before D/O request |
|---|---|---|---|
| Entitlement | Properly endorsed OBL, SWB or telex/surrender confirmation; authority letter where an agent acts. | Consignee, shipper, bank where relevant, carrier/NVOCC. | Legal entity, tax identity, lawful consignee and release type must align. |
| Transport data | Arrival Notice, MBL/HBL, container/seal, voyage, POD and place of delivery. | Carrier/NVOCC/forwarder. | No unresolved consignee, bill, container or manifest error that blocks release. |
| Transport accounts | Debit note/invoice, prepaid/collect charges and any older outstanding balances under the applicable policy. | Carrier/NVOCC and importer finance. | Correct bank account and payment reference; proof and posting confirmation retained. |
| Shipment status | Manifest filed to the level required by the carrier and relevant authority, or the carrier’s required system status is achieved; cargo is available and no legal/commercial hold remains. | Carrier/NVOCC/agent. | Do not infer from ETA; request actual release status. |
| Authority and access | Letter of authority, portal account, digital signature/OTP where required. | Importer or authorised representative. | User is authorised for the correct B/L and legal entity. |
| Pickup plan | Terminal/CFS, FCL/LCL mode, truck, receiving warehouse and empty-return depot. | Logistics, trucking and warehouse. | D/O remains valid for planned collection; truck and appointment meet requirements. |
FCL, LCL AND HBL–MBL RELEASE STRUCTURES
| Shipment structure | Typical release party | Actions after D/O | Specific risk |
|---|---|---|---|
| Direct FCL under MBL | Ocean carrier or carrier agent. | Create port/ePort order, check customs, select container, pay terminal services, dispatch truck, obtain EIR and return empty. | Confusing D/O expiry with free time; missing container release; wrong empty depot. |
| FCL under HBL–MBL | NVOCC/forwarder issues the house release after master release is addressed. | Confirm which release the terminal uses, complete the terminal order and collect the container. | House D/O issued while master hold remains; HBL/MBL consignee mismatch. |
| LCL under HBL | NVOCC/forwarder/CFS agent. | Obtain warehouse/CFS release, pay handling/storage, book package pickup and perform tally. | Devanning incomplete, package/marking mismatch and warehouse fees outside the D/O. |
| Carrier haulage/door delivery | Carrier may combine D/O with inland delivery instructions. | Provide address, slot, contact, unloading conditions and confirm proof of delivery. | Container release mistaken for a confirmed delivery appointment. |
IMPORT DELIVERY ORDER PROCESS
| Step | Input and action | Output/control decision |
|---|---|---|
| 1. Review Arrival Notice | Check B/L, consignee, voyage, terminal/CFS, ETA/ATA, containers/packages, local charges and D/O instructions. | Exception list and timeline before storage exposure increases. |
| 2. Identify document level | Lock MBL/HBL, carrier/NVOCC, OBL/SWB/telex type and lawful consignee. | Correct release party and no missing master layer. |
| 3. Complete release basis | Present/endorse OBL or obtain SWB/telex confirmation; prepare authority and identity records. | Transport document is eligible for release. |
| 4. Reconcile and pay | Validate debit/invoice scope, references and tax invoice; pay and submit proof where required. | Financial hold cleared in the issuer system. |
| 5. Request D/O/eDO | Use the relevant portal, email or counter; select containers or delivery method if requested. | D/O/eDO or cargo/container-release confirmation with reference and validity. |
| 6. Validate the release | Check B/L, containers/packages, location, consignee/agent, expiry, empty depot and special holds. | Usable release; corrections completed before terminal registration. |
| 7. Register terminal/CFS transaction | Create the transaction order in the relevant ePort, terminal or CFS system; select services and vehicle, pay charges, and verify customs and appointment status. | Gate/warehouse order and pickup slot. |
| 8. Collect and close | Check container–seal/EIR or package–tally; record shortage/damage; deliver, return empty and reconcile invoices. | Handover evidence, actual timestamps, claim file and audit trail. |
RISKS AND COMMON ERRORS
| Error | Cause | Impact | Control |
|---|---|---|---|
| Arrival Notice received but bill type not locked | OBL, SWB and telex basis not confirmed. | D/O cannot be issued even after charges are paid. | Confirm the release basis with origin before ETA. |
| Only the HBL is checked | NVOCC shipment still has a master-level hold. | House D/O cannot be used by the terminal. | Require confirmation of master cargo release. |
| Consignee/legal entity/authority mismatch | B/L, manifest, portal and authority documents differ. | Release refusal or document amendment. | Freeze legal name, tax ID, address and representative before B/L issuance. |
| Payment posted with wrong reference | Consolidated transfer or incorrect invoice/B/L reference. | Financial hold, storage and demurrage exposure. | Use exact reference and retain proof plus posting confirmation. |
| D/O issued but no terminal order | D/O confused with eEIO/gate transaction order. | Truck arrives but cannot transact. | Separate carrier-release and terminal-execution controls. |
| Expired D/O or wrong empty depot | Validity/empty instruction not checked. | Extension, depot change, detention or extra trucking. | Lock pickup/return timeline and follow official depot updates. |
| Customs cleared but transport release missing | Declaration assumed to replace D/O. | Carrier/CFS continues to hold cargo. | Track customs release and transport release in parallel. |
| No condition record at handover | EIR/tally checked only after departure. | Weak evidence for shortage, damage or seal dispute. | Photograph and annotate EIR/tally at the handover point. |
LEGAL BASIS AND REFERENCE SOURCES
| Source | Issuer/operator | Operational relevance |
|---|---|---|
| Vietnam Maritime Code – Consolidated Text 101/VBHN-VPQH | Office of the National Assembly; 26 Aug 2025 | Article 148 defines transport-document types and the evidentiary value of bills/sea waybills; Article 162 governs bill transfer and identifies the lawful consignee by bill form; Article 166 requires delivery to the lawful consignee holding a valid transport document. Article 167 addresses delayed or uncollected cargo. |
| Hapag-Lloyd Vietnam – Import FAQ | Carrier local guidance | Local release requirements for SWB/telex/OBL, documents, outstanding balances and payment. |
| MSC Vietnam – Import E-Portal | Carrier local information | Consignee registration, debit note, invoicing, payment and eDO issuance; MSC also uses eDO for container release and empty return. |
| Maersk – Import Delivery Order | Carrier system guidance | Vietnam import guidance lists EDO-request prerequisites including transport-document status, manifest status and prepaid/collect payment; the current portal and shipment-specific criteria remain controlling. |
| Port of Hai Phong – ePort guide | Port operator | Distinguishes carrier DO/eDO from the transaction order generated by the port ePort system and describes DO/eDO declaration, payment, vehicle data and electronic handover instructions. |
| Saigon Newport – eDO | Port operator | Describes electronic data exchange replacing the conventional paper delivery order within the port ecosystem. |
| Circular 39/2018/TT-BTC and Circular 121/2025/TT-BTC | Ministry of Finance; current customs-procedure framework | Used to verify customs-dossier components by regime and applicable date. A D/O should not be assumed to be a universal filing document for every import declaration. |
FAQ
1. Is a D/O always a mandatory document in the import customs dossier?
A D/O is primarily an operational carrier/NVOCC release document. It is not a universal mandatory component of every ordinary import customs dossier; however, customs or supervision authorities may require related data or evidence depending on the regime, inspection status and circumstances.
2. Can the D/O be obtained before vessel arrival?
Some carriers allow early processing after documents and payments are complete. Early issuance does not mean the cargo has been discharged or is available.
3. Is a scanned original bill enough for telex release?
No. Telex/surrender release is a carrier/NVOCC system status following origin-side surrender. A scan alone does not create release authority.
4. Does the D/O fee cover all import pickup charges?
Do not assume so. Other items may include local charges, THC, storage, CFS handling, terminal services, reefer power and other tariff items.
5. Does D/O expiry equal the end of free time?
No. D/O validity and free time/Last Free Day are separate mechanisms. Extending the D/O does not automatically extend demurrage, detention or storage.
6. Does an LCL consignee return the empty container?
Normally the consignee collects packages from the CFS and does not return the consolidated container. The warehouse release and purchased service remain controlling.
7. D/O and customs clearance are complete but cargo cannot be collected—what should be checked?
Check cargo availability, customs-supervision status, terminal/CFS holds, port charges, appointment, container release, inspection/quarantine holds, transaction order and truck/driver authorisation.
Tiếng Việt
中文 (中国)
NEED TO REVIEW IMPORT PROCEDURES OR A SHIPPING PLAN?
Send us the product name, shipping route, current dossier, or implementation request in advance so we can suggest a suitable approach that is practical, focused, and aligned with your shipment.
Import procedure for cream-filled wafers: HS code, tax, food safety, C/O and E2E workflow
Gate Valve Export Guide: Markets, HS, Origin, Documents and Process
Industrial Router Export Guide: Markets, HS, Licensing, Origin and E2E Workflow
Exporting Butterfly Valves from Vietnam: Markets, HS 8481, Origin, Pressure Compliance and Transport
Laser Cutting Machine Export Procedure: HS, Dual-Use Screening, Origin and Shipping
Blade server export procedure: markets, HS, origin, dual-use screening and logistics
Exporting Gateways from Vietnam: Markets, HS 8517.62.21, Origin and Compliance
Mini PC export procedure: markets, HS, origin, dual-use, FCC/IMDA/OFCA and logistics
Exporting Industrial PCs from Vietnam: Markets, HS, Origin, Compliance and Transport
SERVER RACK EXPORT GUIDE: MARKETS, HS, ORIGIN, COMPLIANCE AND SHIPPING
Exporting Tower Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting PoE Switches from Vietnam: Markets, HS, Origin, Compliance and Transport
Desktop PC export guide: markets, HS code, origin and shipping
Exporting Edge Servers from Vietnam: Markets, HS, Origin and E2E Workflow
Exporting Load Balancers from Vietnam: Markets, HS, Origin, Compliance and E2E Workflow