WHAT IS AN ARRIVAL NOTICE? INFORMATION TO CHECK WHEN RECEIVING A NOTICE OF ARRIVAL
An Arrival Notice is commonly issued when an import shipment is approaching or has reached the destination port or place. Many importers look only at the ETA and immediately pass the notice to customs operations. However, discrepancies in bill of lading numbers, discharge port, place of delivery, container data, cargo-release status or destination charges can delay the entire pickup plan. An Arrival Notice is not a Delivery Order and does not replace the bill of lading, manifest or customs documents. Its operational value is to create a control point before arrival so the importer can lock shipment data, prepare funds, documents, trucks and warehouse capacity, and correct discrepancies before storage, demurrage, detention or missed delivery windows arise.
QUICK FACTS
An Arrival Notice is issued by the carrier, NVOCC or destination agent to advise that cargo is approaching/has arrived and to indicate the next import steps.
It does not itself grant cargo pickup rights. A Delivery Order or cargo release is issued only after the carrier’s release conditions are satisfied.
Fields, issue timing and whether charges are shown depend on the carrier, country, trade lane and service type.
Lock the B/L number, consignee/notify party, vessel/voyage, ETA, POD/place of delivery, container/seal, packages/weight, free time and release status.
SCOPE OF APPLICATION
This article primarily covers ocean-import FCL/LCL shipments and Arrival Notices issued by shipping lines, NVOCCs or destination agents. Air, road and rail arrival notifications may use different names and formats; similar control principles apply, but the ocean-shipping document should not be copied mechanically to other modes.
KEY TERMS
| Term | Meaning | Operational role |
|---|---|---|
| Arrival Notice / Notice of Arrival | A notification that cargo is due to arrive or has arrived. | Triggers data review, document preparation, payment and pickup planning. |
| ETA / ATA | Estimated time of arrival / actual time of arrival. | ETA supports planning and may change; ATA records the actual event. |
| POL / POD | Port of Loading / Port of Discharge. | Locks the correct port routing. In other documents, POD may also mean Proof of Delivery, so the context must be checked. |
| Place of Delivery | The final named delivery place under the bill of lading or contract of carriage. | Defines the carrier’s transport scope and is not automatically the same as the Port of Discharge. |
| Cargo Release | Carrier document-control status permitting delivery. | May depend on B/L status, settlement of charges, pickup authorisation and local carrier/terminal procedures. |
| Delivery Order – D/O | Delivery instruction or order. | Used to collect cargo; it is distinct from the Arrival Notice. |
| Free Time / Last Free Day | Agreed free period / final free day under applicable conditions. | Controls exposure to demurrage, detention, storage or similar charges. |
| Collect Charges | Charges payable at destination. | Must be reconciled to invoices and the rate agreement; not every AN displays charges. |
NATURE AND OPERATING MECHANISM
The carrier, NVOCC or destination agent generates an Arrival Notice from bill of lading data, vessel schedules, import systems and relevant filing data. It is generally delivered to the consignee, notify party or a registered portal recipient. It should not be treated as an instruction to collect cargo immediately. The recipient should perform three control layers:
- Shipment identity: B/L, booking, container, seal, package count, weight and cargo description.
- Operational milestones: ETA/ATA, discharge port, terminal/CFS, place of delivery, free time and pickup plan.
- Release conditions: B/L status, charges, eDO/D/O requirements, authorisation, customs and specialised controls.
OOCL Vietnam states that Arrival Notices are generally sent 1–2 days before vessel arrival, while other carriers and trades may use different timing. No single issue deadline should therefore be treated as universal.
ARRIVAL NOTICE VS PRE-ALERT, MANIFEST AND DELIVERY ORDER
| Document/data | Typical issuer/transmitter | Timing | Primary purpose | Allows pickup? |
|---|---|---|---|---|
| Pre-alert | Origin office, forwarder or overseas agent. | During transit or before arrival. | Transfers shipment documents/data so the destination team can prepare. | No. |
| Manifest | Carrier/NVOCC files to the competent system/authority. | According to legal and port/customs cut-offs. | Declares cargo and transport data. | No. |
| Arrival Notice | Carrier/NVOCC/destination agent. | Before or around arrival, depending on process. | Advises arrival and the next import steps. | No. |
| Invoice | Carrier/agent/service provider. | Before or after the AN depending on the system. | Requests payment of charges. | Not by itself. |
| D/O / eDO / Cargo Release | Carrier, NVOCC or delivery agent. | After release conditions are met. | Instructs terminal/CFS to deliver cargo. | Yes, within the granted scope and validity. |
INFORMATION TO CHECK ON AN ARRIVAL NOTICE
| Data group | Fields to check | Reconcile with | Risk if wrong | Action |
|---|---|---|---|---|
| Identity | MBL/HBL, booking or shipment reference. | B/L, pre-alert, carriage contract. | Wrong shipment, missing file or payment to the wrong reference. | Stop and request confirmation/correction. |
| Parties | Shipper, consignee, notify party, company details and recipient email. | B/L, contract and authorisation. | Missed notifications or release/authorisation issues. | Lock the correct legal entity and contact. |
| Routing | Vessel, voyage, POL, POD, transshipment and place of delivery. | B/L and carrier tracking. | Wrong port/terminal, truck or declaration location. | Update the timeline and handling location. |
| Time | ETA, ATA if shown, issue date and expected discharge. | Latest tracking/schedule. | Using an outdated ETA and missing operational windows. | Continue monitoring; ETA is not absolute. |
| Container | Container no., seal no., size/type, FCL/LCL and quantity. | B/L, packing list, pre-alert and EIR if available. | Missing container, seal discrepancy or wrong truck/equipment. | Reconcile container by container. |
| Cargo | Packages, gross weight, volume, description and marks. | Invoice, packing list, B/L and manifest data. | Wrong customs data, vehicle plan or specialised controls. | Resolve before declaration/pickup. |
| Pickup point | Terminal, CY, CFS, depot, contact and opening hours. | Carrier/terminal import instructions. | Truck goes to the wrong location or lacks required release. | Confirm location and gate requirements. |
| Release | B/L type, surrender/OBL status, cargo release and D/O/eDO requirements. | Carrier portal and original document set. | Cargo arrives but cannot be released. | Close each release condition. |
| Charges | Freight collect, local charges, D/O fee, deposit or invoice reference if shown. | Invoice, quotation, Incoterms and contract. | Underpayment, overpayment or scope dispute. | Use the invoice as the payment basis. |
| Free time | Free days, last free day and demurrage/detention/storage references if shown. | Tariff, agreement and import portal. | Charges from relying on unconfirmed dates. | Obtain current carrier confirmation. |
| Special cargo | Reefer setpoint, DG reference, OOG handling, customs hold or inspection note. | Booking, DG declaration, reefer instructions and approvals. | Temperature, permit or equipment failure. | Escalate to the specialist owner immediately. |
DOCUMENTS AND DATA TO RECONCILE
| Document/data | Prepared/issued by | Used to verify | Fields that must align |
|---|---|---|---|
| Bill of Lading / Sea Waybill | Carrier or NVOCC. | Shipment identity, parties, routing and documentary release. | B/L no., consignee/notify, POD, place of delivery and cargo/container data. |
| Commercial Invoice (where applicable) | Seller. | Commercial value, product name and delivery terms. | Entities, description, currency, Incoterms and invoice number. |
| Packing List (where applicable) | Seller/packer. | Packages, weight, volume, marks and container allocation. | Package count, gross/net weight, CBM and container mapping. |
| Pre-alert (if available) | Forwarder/origin agent. | Expected data before the AN is issued. | B/L versions, ETA, contacts and attachments. |
| Carrier tracking/import portal | Carrier. | Latest schedule, movements, AN, invoice and release. | ETA/ATA, terminal, release and free-time data where available. |
| Manifest/customs draft | Declarant. | Pre-declaration consistency. | Description, quantity, weight, B/L, port and parties. |
| Booking/rate confirmation | Contracting party. | Rate scope, free time, haulage and special conditions. | Prepaid/collect, POD, place of delivery and service mode. |
| Permits/specialised documents | Importer/issuing authority. | Eligibility for regulated goods. | Goods, model, quantity, importer and validity. |
CHECKS BY CARGO AND DELIVERY TYPE
| Shipment group | Priority information | Additional control |
|---|---|---|
| FCL consumer goods/machinery | Container, seal, size/type, terminal, free time, D/O and empty return depot. | Truck capacity, pickup schedule, empty return plan and release status. |
| LCL cargo | HBL, related MBL, CFS, stripping date and delivery hours. | Vessel ETA is not the cargo-ready date; wait for CFS readiness. |
| Reefer/food | Reefer container, setpoint, terminal, plug status and inspections. | Cold-chain, quarantine and pickup timing after release. |
| DG/chemicals | UN No., class, packing group when applicable, DG approval and terminal handling. | Use carrier-approved data and verify dangerous-goods gate restrictions. |
| OOG/project cargo | Dimensions, weight, equipment, handling and lifting requirements. | Lock crane, low-bed, permits and pickup gate; obtain drawings separately. |
| Door delivery/carrier haulage | Place of delivery, delivery address, appointment and contact. | POD is not necessarily the final delivery point; verify inland scope. |
| Merchant haulage | Terminal/CY, D/O, release, appointment and driver requirements. | Importer controls truck, gate and empty-return execution. |
ARRIVAL NOTICE HANDLING PROCESS
| Step | Input | Action | Output |
|---|---|---|---|
| 1. Authenticate source | Email/portal/AN PDF. | Check domain, carrier account and B/L; avoid spoofed links/files. | Validated AN. |
| 2. Reconcile shipment | AN + B/L + pre-alert. | Lock parties, routing, container/cargo and pickup point. | Discrepancy log. |
| 3. Update timeline | ETA/ATA, terminal/CFS and free time. | Set customs, payment, D/O, truck and warehouse milestones. | Pickup plan. |
| 4. Close release conditions | B/L status, invoice, eDO/D/O and authorisation. | Check portal or delivery agent requirements. | Open-action list. |
| 5. Close customs file | Invoice, PL, B/L, permits and C/O if any. | Resolve inconsistencies before final declaration. | Customs-ready file. |
| 6. Close transport/warehouse | Container/cargo data, terminal and appointment. | Select truck, lifting equipment and warehouse slot. | Executable delivery plan. |
| 7. Monitor changes | Carrier tracking and advisories. | Update ETA/ATA, terminal, holds, free time and release. | Current plan version. |
| 8. Retain evidence | AN versions, emails, screenshots, invoices and D/O. | Store by shipment and timestamp. | Audit trail for reconciliation/claims. |
RESPONSIBILITY MATRIX
| Party | Primary responsibility | Do not assume |
|---|---|---|
| Carrier/NVOCC/agent | Issue the AN from system data and provide import/release information within service scope. | The AN always contains final charges, final free time or proof cargo is ready. |
| Consignee/importer | Validate data, prepare documents/fees/permits, clear customs and arrange pickup. | Receiving the AN completes the importer’s obligations. |
| Notify party/destination forwarder | Receive, coordinate and escalate discrepancies under authority. | Forwarding the email transfers all importer liability. |
| Customs broker | Review declaration data and file under authorisation. | It may amend the B/L, manifest or AN on behalf of the carrier. |
| Trucker/warehouse | Collect/deliver under valid release, appointment and safety rules. | The AN can replace a D/O or terminal instructions. |
RISKS AND COMMON ERRORS
| Error | Cause | Impact | Control |
|---|---|---|---|
| Checking ETA only | Terminal, place of delivery and release are ignored. | Wrong truck timing or location. | Use the full data matrix. |
| Treating AN as D/O | Document functions are confused. | Truck is denied cargo. | Dispatch only after valid release/D/O. |
| Using AN as invoice | Charges may be absent or preliminary. | Underpayment or wrong payment. | Reconcile to invoice/account statement. |
| Not reconciling HBL/MBL | Party and B/L differences are missed. | Release, manifest or customs issues. | Cross-check identifiers. |
| Using old ETA | Tracking is not monitored. | Missed revised schedule. | Assign a milestone owner. |
| Ignoring free time | Relying on verbal/unconfirmed data. | Demurrage, detention or storage. | Obtain current carrier confirmation. |
| Ignoring special cargo | AN may not show all DG/reefer/OOG conditions. | Refusal, damage or equipment shortage. | Reconcile booking approvals. |
| Overwriting versions | Revised AN replaces earlier evidence. | Weak fee/timeline/claim audit. | Store each version by timestamp. |
REFERENCES AND OFFICIAL SOURCES
There is no single worldwide Arrival Notice template. Use the latest import instructions of the issuing carrier/agent and the official data for the specific shipment. The sources below were reviewed on 21 July 2026.
| Source | Use | Caution |
|---|---|---|
| Maersk – Arrival Notices and Spot Shipping | Explains the purpose, typical information and access process for Arrival Notices. | Carrier guidance; timing and fields vary by market and shipment. |
| OOCL Vietnam – Import Procedures | Provides a current Vietnam reference for Arrival Notice timing and eDO release procedures. | OOCL Vietnam currently states ANs are generally sent 1–2 days before vessel arrival; recheck the live page. |
| Hapag-Lloyd – Import Overview | Provides routing, Arrival Notice, B/L, container, cargo, release and redelivery information. | Displayed data depends on account rights and the shipment. |
| Maersk Vietnam – Imports | Provides Vietnam import, Arrival Notice, free-time and cargo-release information. | Tariffs and conditions may change by effective date and contract of carriage. |
| Hapag-Lloyd Vietnam – Import FAQ | Provides local practical conditions for Delivery Order/container release. | An Arrival Notice alone does not prove that release conditions have been completed. |
FAQ
Is an Arrival Notice a mandatory customs document?
Not automatically. It is mainly an operational carrier/agent document; the customs file depends on the customs regime and applicable law.
Does receiving an AN mean the cargo has arrived?
Not necessarily. It may be issued before ETA. Check ETA, ATA and container movement.
Can an AN replace a Delivery Order?
No. The AN advises arrival; D/O/eDO or cargo release authorises delivery when conditions are met.
Why are charges missing from the AN?
Some carriers issue charges through a separate invoice or finance portal. Use the invoice/account statement for payment.
Is the ETA on the AN guaranteed?
Usually not. ETA can change due to schedule, port, weather or operating factors.
Who should review the AN?
The importer/consignee owns the final control; a forwarder or broker may execute under authority.
What additional checks apply to LCL?
Check the CFS, stripping/cargo-ready date, HBL release, warehouse charges and delivery hours, not only vessel ETA.
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