A pre-alert is often treated as a simple “shipment on the way” email. In B2B logistics, however, its real value is the data and document package that enables the destination team to prepare before cargo arrives. If the sender attaches only a transport document—or fails to identify drafts, finals and missing items—the destination may still be unable to prepare customs clearance, review origin preference, obtain permits or arrange warehouse and delivery capacity. This article sets out the core pre-alert documents, mode-specific additions for ocean, air, road and rail, special-cargo records and the consistency checks required before release.

Operational compilation | Updated: 20 July 2026 | Scope: Pre-alerts in international freight forwarding

QUICK FACTS

No universal fixed pack

Content depends on mode, lane, cargo, service scope and the SOP agreed between origin and destination.

Core set

Shipment identification/routing data and a transport document or transport data; commercial shipments normally add a Commercial Invoice and Packing List, together with document status and a pending list.

Cargo and regulatory additions

Origin, permits, quarantine certificates, SDS/DGD, fumigation, insurance or temperature instructions where applicable.

Not an Arrival Notice

The origin forwarder usually sends the pre-alert; the carrier or destination agent generally issues the Arrival Notice closer to arrival.

SCOPE

This article covers ocean, air, road, rail and multimodal import/export shipments and is intended for shippers, consignees, buyers, suppliers, freight forwarders, customs brokers and destination agents.

Here, a pre-alert means an advance operational package of shipment data and documents. It is an operational term, not a separately defined customs document under Vietnam’s Customs Law, and should not be confused with the statutory customs dossier, an electronic manifest filing, PLACI/ACI data submission or a carrier’s Arrival Notice.

TERMS

Term	Meaning	Key distinction
Pre-alert	Advance notice with documents/data enabling the destination to prepare customs, document review, release and inland planning.	Designed under the shipment SOP; there is no single universal list.
Arrival Notice	Carrier or destination notice commonly showing ETA, voyage/flight, arrival location and charges.	Issued closer to arrival and does not replace the origin pre-alert.
Manifest	A cargo/waybill dataset used by carriers, agents and authorities under applicable rules.	A manifest is a separate operational/legal dataset; a copy or consol manifest may be attached to a pre-alert.
Shipping Instruction – SI	Shipper’s instruction used by the carrier/forwarder to prepare the transport document.	SI is source data; the issued waybill is an output requiring verification.
Document Status	Draft, Final, Pending, Original to follow, Telex/Surrendered or Amended.	Tells the destination which document can be used and which is not yet final.

CORE PRE-ALERT DOCUMENT PACKAGE

Document/data	Typical status	Required content	Pre-release control
Pre-alert cover sheet/email	Core management item	Shipment reference, lane, ETD/ETA, carrier, booking/waybill, contacts, attachment list and pending items.	Use the shipment reference in the subject and identify Draft/Final plus due dates.
Transport document	Core	MBL/HBL, MAWB/HAWB, CMR or rail waybill as applicable.	Match parties, packages, weight, description and origin/destination points.
Commercial Invoice	Usually core for commercial goods	Seller/buyer, invoice details, goods, quantity, unit/total value, currency and Incoterms.	Prefer the final version; if only a draft is available, state its status, owner and final-update time.
Packing List	Usually core for packaged cargo	Packages, packaging, net/gross weight, dimensions/CBM, marks and SKU allocation.	Reconcile package count and weight with the waybill and booking; mark “not applicable” where the shipment type does not generate a Packing List.
Routing/schedule information	Core	Vessel/flight, voyage/flight number, ETD, ETA, transshipment and departure status.	State the source, update time and location to which the ETA refers.
Release/original status	Core for ocean	Original B/L, Sea Waybill, Telex Release/Surrendered, original count and document holder.	Do not mark “telex released” until carrier confirmation is available.
Pending document list	Core control item	Origin, permits, certificates, originals or amendments still outstanding.	Name the owner, due date, risk and contingency if the document arrives late.

Principle: A useful pre-alert does more than attach files. It lets the destination understand document status, the next milestone and the owner of every outstanding action. The table does not make every document mandatory for every shipment; non-commercial, document, bulk or specially scoped shipments may require a different pack.

MODE-SPECIFIC ADDITIONS

Mode	Typical additions	Purpose	Control note
Ocean FCL	Booking confirmation, MBL/HBL, VGM/weight data, container-seal list and release status.	Manifest preparation, container control, D/O and haulage planning.	VGM is normally an origin operational item; send where the SOP requires destination reconciliation.
Ocean LCL	HBL/MBL, consolidation manifest, CFS/warehouse data, marks and HBL breakdown.	Deconsolidation, manifest and CFS receipt planning.	Do not confuse an internal consol manifest with an authority-filed manifest.
Air freight	MAWB/HAWB, flight data, e-AWB/e-HWB information, security status/CSD and handling details where applicable.	Acceptance, customs, warehouse allocation and special-cargo handling.	IATA operational guidance indicates that e-AWB/e-HWB data, truck/ETA information and security-screening needs should be received in advance, where available, before cargo is accepted into the carrier domain.
Road	CMR, vehicle/driver data, border ETA, seal, permits and transloading list.	Border coordination, declaration and handover control.	Vehicle data may change; include the version and update timestamp.
Rail	Rail waybill, wagon/container list, stations, train number and border-interchange data.	Transfer, station receipt and border planning.	Reconcile container and seal numbers across all records.
Multimodal	Documents for each leg, multimodal transport document, handover records and milestone plan.	Shows responsibility at each transfer point.	Do not use one generic ETA without defining the final milestone.

SPECIAL-CARGO AND REGULATORY ADDITIONS

Cargo/situation	Possible documents	Data to lock
Dangerous goods	DGD, SDS/MSDS, packing certificate, approvals/exemptions and emergency contact.	UN number, proper shipping name, class, packing group, quantity and packaging.
Lithium batteries	SDS, UN38.3 test summary, DGD where required, PI/section and packing/label statements.	Battery type, whether packed with/in equipment and capacity limits.
Cold-chain/pharma	Temperature instruction, packing validation, logger list, cold-chain SOP and permits.	Temperature range, excursion tolerance, logger location and escalation contact.
Food, plants and animals	Health, phytosanitary or veterinary certificates, quarantine, origin, fumigation and specifications.	Issuer, lot, manufacture/expiry dates and scientific name where required.
Wood packaging	ISPM 15 marks or other treatment evidence; a fumigation certificate/packing declaration only where required by the market, carrier or customer.	Package marks, material, treatment method and destination-country requirements.
Preferential origin	C/O or origin statement, through-transport evidence, third-party invoice documents.	Form, criterion, HS, description, quantity, date and route.
Licensed/controlled goods	Import permit, inspection registration, conformity/product file, test report and model list.	Entity, model, quantity, intended use and validity period.
Insured cargo	Insurance certificate/policy, insured value, survey instruction and claim contact.	Coverage, exclusions and loss-notification timeline.

DATA CONSISTENCY MATRIX

Data field	Documents to compare	Common error	Control
Shipper/Consignee/Notify	Waybill, Invoice, PO/contract and C/O.	Abbreviations, obsolete address, missing tax ID or wrong notify.	Use controlled master-party data.
Goods description	Invoice, Packing List, waybill, catalogue and permit.	Generic waybill description or permit/model mismatch.	Align commercial and required technical descriptions.
Packages/weight/CBM	Packing List, waybill, booking, VGM/warehouse receipt.	Net/gross confusion or pallet/carton mismatch.	Select one final source and state the measurement basis.
HS/origin	Invoice, C/O, permit and reference declaration.	Different HS across records or confusion between commercial and preferential origin.	Mark HS “for reference” where destination classification is not final.
ETD/ETA/location	Booking, carrier tracking and flight/vessel schedule.	Port ETA read as warehouse ETA or stale transshipment data.	State location, time zone, source and timestamp.
Release status	Carrier confirmation and B/L release evidence.	Forwarder announces release before carrier completion.	Use “Confirmed” only with evidence.
Document version	All files.	Destination uses an obsolete draft.	Use ShipmentRef_DocType_Version_Date_Status naming.

WHO SENDS IT, WHO RECEIVES IT AND WHEN?

Role	Responsibility	Expected output
Supplier/Shipper	Provide commercial, technical and regulatory source documents.	Correct final commercial/technical records.
Origin forwarder	Compile transport data, waybills, routing, departure status and issue the pre-alert.	Cover sheet, attachments, pending list and escalation contacts.
Destination agent/forwarder	Check completeness, raise discrepancies and prepare arrival/customs/inland work.	Acknowledgement and deficiency list.
Customs broker	Review declaration fields and product-control requirements.	Correction list, regulatory file and declaration timeline.
Consignee/Buyer	Confirm legal entity, permits, charge instructions and receiving plan.	Approval or destination instruction.

There is no universal statutory deadline for the operational pre-alert email/package itself. Timing should be defined in the SOP/SLA and allow discrepancies to be resolved before customs, arrival and free-time milestones. Separate advance-cargo, manifest or security filings may have statutory deadlines, so the pre-alert must be issued early enough not to miss them.

PRE-ALERT ISSUE PROCESS

Lock the shipment reference and scope

Define mode, service, lane, Incoterms, consol/direct status and recipients.

Collect the core set

Obtain the waybill/transport data, routing and release data; for commercial cargo add the Invoice and Packing List; flag non-final or non-applicable documents.

Add lane/cargo records

Review DG, batteries, food, quarantine, origin, permits, insurance and destination requirements.

Cross-check data

Compare parties, goods, packages, weight, value, HS, origin, container/seal and ETA.

Issue under version control

Use a standard subject, cover sheet, file naming and Draft/Final/Pending labels.

Obtain acknowledgement

Destination confirms receipt and discrepancies; every amendment is logged.

Close the shipment file

Add final documents, Arrival Notice, D/O, declaration and POD after arrival.

COMMON FAILURES

Sending only the B/L or AWB: where commercial or regulatory records are needed, destination may lack the Invoice, Packing List, permits or certificates required to prepare the shipment.
No Draft/Final label: an obsolete file is used for manifest or customs.
Late origin document without warning: no time remains for review or correction.
Confusing pre-alert and Arrival Notice: document review starts only when the carrier announces arrival.
Mixing internal and statutory manifests: users assume a consol file has been officially filed.
No release-status control: cargo arrives but release documentation is incomplete.
No naming convention: version history and audit trail are lost.
Over-sharing: unnecessary commercial data increases confidentiality risk and hides critical documents.

OFFICIAL AND INDUSTRY SOURCES

Source	Reference point	Use in this article
IATA – Air Cargo Handling	Before carrier acceptance, e-AWB/e-HWB data, truck/ETA information and security-screening needs should be supplied in advance where available.	Supports advance-data practices in air cargo operations.
IATA – e-freight/e-AWB	Customs, transport, commercial and special-cargo document groups and high-quality electronic data.	Provides a framework for air pre-alert design.
Maersk – Important Shipping Documents	Invoice, Packing List, declaration, B/L/Sea Waybill and certificates varying by cargo and lane.	Shows that shipment document requirements are shipment-specific.
Maersk – Arrival Notice	Carrier-issued notice with ETA, location and shipment details used for release planning.	Distinguishes Arrival Notice from origin pre-alert.
FedEx Vietnam – Ancillary Services	Pre-alert/reporting described as customizable to customer requirements.	Supports the operational, scope-based nature of a pre-alert.
Vietnam Consolidated Customs Law 54/VBHN-VPQH (2026)	Vietnam customs procedure and dossier framework.	A pre-alert does not replace statutory customs filing obligations.

IATA Air Cargo Handling IATA e-freight Maersk Documents Maersk Arrival Notice FedEx Pre-alert Service Vietnam Customs Law

FAQ

1. Must every pre-alert include a Certificate of Origin?

No. Include it where preference or an origin requirement is relevant. A draft may be sent with a clear status and update deadline.

2. Can a draft B/L be included?

Yes, provided it is unmistakably marked Draft. The final B/L must be issued as an amendment and the old version must not remain the working copy.

3. Does the pre-alert replace the manifest?

No. It may carry manifest data, but statutory manifest filing must follow the applicable system, party and deadline.

4. Is the Arrival Notice part of the original pre-alert?

Usually not. It is commonly issued at destination closer to arrival and may later be added to the shipment record.

5. How early should the pre-alert be sent?

There is no single global rule. It must allow enough time for advance filing, document review, permits and discrepancy correction before arrival.

6. Who is responsible for incorrect data?

Responsibility depends on the data source, legal role and service contract. The shipper controls source data; the forwarder must compile and transmit within scope; destination reviews and raises discrepancies under the SOP. Destination review does not automatically transfer legal responsibility away from the data provider or declarant.

7. Should all commercial emails be forwarded?

No. Share only data needed for transport, customs and control, using access restrictions or secure channels for sensitive information.

APPLICATION NOTE: The document list in this article is an operational framework, not a fixed legal dossier. The final pre-alert must be set by mode, lane, Incoterms, cargo, carrier requirements, origin/destination rules, service scope and the parties’ SOP.

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B

MACHINERY

HOUSEHOLD GOODS

COSMETICS – PERSONAL CARE

ELECTRICAL – ELECTRONICS – IT EQUIPMENT

F&B – FOOD & BEVERAGE