ISF 10+2, AMS, ENS and ACI: Advance Cargo Filing Rules for Shipments from China (2026) | Baton Logistics
News
News

ISF 10+2, AMS, ENS and ACI: Advance Cargo Filing Rules for Shipments from China (2026)

Nov 18,2026

Freight documentation desk with advance cargo filing forms, container booking printouts and a customs handbook

Quick answer: Before an ocean container is loaded onto a vessel bound for the US, EU, Canada or several other destinations, customs authorities require cargo data to be transmitted in advance of loading — not at arrival. In the US this is the ISF 10+2 rule: the importer (or its agent, usually the freight forwarder or customs broker) files 10 data elements, and the carrier files 2, generally no later than 24 hours before the cargo is laden aboard the vessel. The EU equivalent is the ENS (Entry Summary Declaration) under the Union Customs Code and ICS2; Canada uses ACI eManifest; the US carrier-side manifest is AMS. The exact deadline, data set, filing party and enforcement practice differ by destination. Do not assume a DDP booking transfers filing responsibility away from the importer of record — and always verify the current rules with the destination authority or a licensed broker, because filing windows, ICS2 release scope and penalty schedules change.

Key takeaways

  • Advance cargo filing is a pre-loading obligation. Missing it can stop a container being loaded, trigger a "do not load" message, or cause a hold and penalties at destination — long before normal customs clearance begins.
  • ISF (importer side) and AMS (carrier side) are different filings with different responsible parties. Confusing them is the most common reason a China–US shipment is filed late or incomplete.
  • The "10" in 10+2 belongs to the importer; the "+2" (vessel stow plan and container status messages) belongs to the carrier. A forwarder can file the 10 on the importer's behalf, but the legal responsibility sits with the importer of record.
  • The EU's ENS under ICS2, Canada's ACI eManifest, and destination-specific schemes such as Egypt's ACI / ACID number are separate regimes. One filing does not satisfy another.
  • Accurate HTS classification, manufacturer/supplier identity, country of origin and container stuffing location feed the advance filing. Errors here are a frequent cause of both pre-loading holds and destination clearance problems.
  • Under DDP/DAP terms, agree in writing who files, who supplies the data, and who carries the penalty risk. Commercial terms do not automatically reassign statutory filing duties.
  • Penalties and enforcement are set by each authority and change over time; treat any figure as indicative and confirm current guidance before relying on it.

The regimes at a glance

This is a planning comparison, not legal advice. Deadlines and data sets are the commonly cited baseline rules for ocean container cargo; confirm current requirements for your lane.

RegimeDestinationCommon nameTypically filed byTypical timingCore purpose
ISF 10+2United StatesImporter Security FilingImporter of record, or its agent (forwarder / broker)Generally no later than 24 hours before ladingSecurity risk assessment before loading
AMSUnited StatesAutomated Manifest System (carrier manifest)Ocean carrier / NVOCCBefore lading; carrier-sideCarrier manifest and "+2" elements
ENS / ICS2European UnionEntry Summary DeclarationCarrier, or in some cases the forwarder / filerGenerally at least 24 hours before loading for ocean containersEU safety & security pre-arrival screening
ACI eManifestCanadaAdvance Commercial InformationCarrier / forwarder per CBSA rulesAdvance of loading / arrival by modeCBSA pre-arrival risk assessment
ACI / ACIDEgyptAdvance Cargo Information registrationImporter / exporter via the national platformBefore shipment; ACID must appear on documentsPre-registration of shipment data
Other national schemesVariouse.g. advance manifest / pre-arrival declarationsVariesVariesLocal security screening

How to read this: the acronyms are not synonyms, and they are not interchangeable. A shipment from Shenzhen to Los Angeles involves both ISF and AMS. A shipment to Rotterdam involves ENS, not ISF. A shipment to Egypt involves the ACID workflow, which is a registration step that must be reflected on the bill of lading and other documents.

ISF 10+2 explained

The US Importer Security Filing rule is often called "10+2" because of its structure:

The 10 importer-side elements (filed by the importer of record or its agent):

#Data elementTypical source of truth
1Seller name and addressCommercial invoice / supplier master data
2Buyer name and addressSales contract / purchase order
3Importer of record number / FTZ applicant identificationImporter's CBP-assigned number
4Consignee number(s)Delivery party details
5Manufacturer (or supplier) name and addressFactory information — often the weakest link
6Ship-to partyFinal delivery location, especially for FBA / 3PL
7Country of originOrigin determination, not just port of loading
8HTSUS number (commonly at 6-digit level for ISF)Product classification
9Container stuffing locationWhere the container was physically packed
10Consolidator / stuffer name and addressWarehouse or consolidator details

The +2 carrier-side elements: the vessel stow plan and container status messages. These are the carrier's obligation, not the importer's.

Two practical consequences follow. First, the importer's 10 elements depend on data that often sits with a Chinese factory or a consolidation warehouse — manufacturer name, stuffing location, consolidator — so a forwarder needs that information before the filing window closes, not after the container is gated in. Second, the HTS number used for ISF should be consistent with the classification used on the entry; a mismatch is a classic trigger for a hold or a request for clarification.

Filer responsibility: who actually does what

ScenarioWho normally files the importer-side dataWho carries the legal responsibilityWhat must be agreed in writing
Importer has its own US brokerThe brokerImporter of recordData hand-off timing and accuracy
DDP shipment arranged by a China forwarderForwarder's US agent / broker on the importer's behalfStill the importer of record (or the party contractually assuming it)Who supplies IOR number, who pays penalties, who corrects a rejected filing
Amazon FBA inboundForwarder or designated brokerImporter of record (often the seller)Ship-to party and FBA warehouse details must be correct
NVOCC issuing a House B/LNVOCC may file master/house-level dataDepends on the filing role and contractHouse vs master data consistency

The critical point: Incoterms describe cost and risk allocation between buyer and seller; they do not, by themselves, change who is the importer of record or who is legally answerable for a security filing. Under DDP the seller may arrange and pay for the filing, but the destination authority still looks to the importer of record. Put the allocation of filing duties, data supply and penalty risk into the sales contract or the forwarder's service agreement rather than assuming the trade term covers it.

Deadlines and the "24 hours" rule

For ocean container cargo, the commonly cited US baseline is that ISF must be filed no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. Several elements may be updated later under flexible provisions, but relying on that flexibility is poor practice: the practical cut-off is usually earlier, because the forwarder needs the complete data set, a valid importer number and an accepted transmission before load.

Operationally, work backwards from the vessel's planned loading window at the Chinese port:

MilestoneWhy it matters
Booking confirmedETD and vessel identified; filing clock starts to matter
Cargo details finalised (cartons, weights, CBM, HS code)Feeds HTS, origin, ship-to and stuffing data
Factory / supplier identity and stuffing location confirmedElements 5, 9 and 10 — frequently missing
Consolidation / container stuffing completedStuffing location and consolidator become fixed
Advance filing transmitted and acceptedA rejection must be corrected before loading
Container gated in and loadedToo late to file if nothing was transmitted
Destination arrival and entry filingSeparate customs clearance step; not a substitute for ISF

For the EU, ENS under the Union Customs Code / ICS2 follows the same "before loading" logic for ocean containers, with the data set and filer depending on the ICS2 release scope and the transport scenario. Because ICS2 has been rolled out in phases, confirm which release and which data set apply to your lane at the time of booking.

What a mistake costs

Penalty schedules are set by each authority and change; the figures commonly cited in industry guidance for ISF violations are in the thousands of US dollars per violation, with higher exposure for repeated or uncorrected non-compliance. Treat any specific number as illustrative and verify current CBP guidance rather than quoting it in a contract.

The real cost is usually operational, not the fine:

  1. "Do not load" / loading hold — the container misses the vessel and waits for the next sailing.
  2. Rolled cargo and missed season — a one-week slip can miss a retail launch or Amazon inbound appointment.
  3. Destination hold or exam — inconsistent data attracts inspection, adding demurrage, detention and storage.
  4. FBA appointment failure — a delayed container can invalidate an inbound appointment window.
  5. Contractual disputes — when the sales contract never said who bears filing penalties, buyer and seller argue after the fact.

These downstream costs are why advance filing belongs in the booking checklist rather than in a post-departure cleanup.

Decision framework

Work through these questions for every China-origin ocean booking.

StepQuestionAction if the answer is unclear
1What is the destination customs regime (ISF / ENS / ACI / other)?Confirm with the forwarder before booking; do not assume the last lane's rules apply
2Who is the importer of record, and is their number valid?Resolve before data transmission; a wrong IOR number means a rejected filing
3Who files the importer-side data, and through which broker?Name the filing party in writing
4Are manufacturer, stuffing location and consolidator known?Collect from the factory / warehouse before the cut-off
5Is the HTS / commodity code consistent across ISF, invoice and entry?Pre-classify and document the decision
6Does the shipment go to an FBA warehouse or third-party DC?Verify ship-to party and consignee data
7Is the trade term DDP/DAP?Add explicit clauses on filing duty, data supply and penalty allocation
8Is there a destination-specific registration (e.g. Egypt ACID)?Complete it before B/L issuance; the number must appear on documents
9What is the fallback if a filing is rejected?Agree escalation and whether cargo can be held at origin

Worked examples

Example 1 — Shenzhen to Los Angeles, 40HQ, DDP, first-time importer. The seller arranges DDP and assumes "the forwarder handles everything". But ISF needs the buyer's importer of record number, the factory's legal name and the container stuffing location. If the buyer has no IOR number or the factory name is a trading-company alias, the filing cannot be completed cleanly. The fix is a pre-booking data sheet and a written allocation of who supplies each of the 10 elements.

Example 2 — Ningbo to Rotterdam, LCL consolidation. There is no ISF. The relevant obligation is ENS under ICS2, filed at the appropriate level for the transport scenario. A consolidator handling multiple shippers must have complete and accurate data for each consignment before the container is loaded. Treating this as "the carrier's problem" and shipping without verified data is how LCL groups get held.

Example 3 — China to Egypt, FCL. The destination ACI workflow requires the shipment to be registered in advance and an ACID number to appear on the bill of lading and related documents. This is a separate pre-registration step, not an ISF or an ENS. B/L issuance without the number creates a document mismatch at destination.

Example 4 — Amazon FBA inbound, multiple suppliers consolidated in Shenzhen. One container, many SKUs and several factories. The ISF "manufacturer" and "ship-to party" fields must represent the actual supply chain and the actual FBA destination. Consolidation adds a data layer: the consolidator/stuffer details must be captured at the warehouse, not reconstructed after sailing.

Common mistakes

  1. Treating ISF and AMS as the same filing. Different data, different filer, different legal basis. Both are required for US-bound ocean cargo.
  2. Assuming DDP transfers statutory filing responsibility. It usually transfers the task and the cost, not the authority's expectation of an importer of record.
  3. Submitting incomplete manufacturer / stuffing / consolidator data. These three are the most frequently wrong or missing importer-side elements on China-origin shipments.
  4. Using a different HS code on ISF, invoice and entry. Inconsistency invites a hold and a classification review.
  5. Waiting until the container is gated in. The filing clock is tied to loading, not to gate-in; late data means a missed vessel.
  6. Reusing one destination's filing for another. ENS, ACI, ACID and ISF are separate regimes with different data sets.
  7. Assuming a rejected filing auto-corrects. A transmission rejection needs an active correction and re-transmission before loading.
  8. Quoting a penalty figure in a contract without verifying it. Penalty schedules change; use current authority guidance.

Pre-booking compliance checklist

  • [ ] Destination customs regime identified (ISF / ENS / ACI / other)
  • [ ] Importer of record confirmed, with a valid number
  • [ ] Filing party and broker named in writing
  • [ ] Written clause on filing duty, data supply and penalty allocation under DDP/DAP
  • [ ] Seller, buyer, consignee and ship-to party details verified
  • [ ] Manufacturer / supplier legal names collected from each factory
  • [ ] Country of origin determined per product, not assumed from the load port
  • [ ] HTS / commodity code pre-classified and consistent across documents
  • [ ] Container stuffing location and consolidator / stuffer identified
  • [ ] Vessel ETD and planned loading window known; data cut-off set earlier
  • [ ] Destination-specific registration completed (e.g. ACID) and reflected on the B/L
  • [ ] Confirmation of filing acceptance obtained before loading
  • [ ] Escalation path agreed in case of rejection or a "do not load" message

FAQ

Q: 1. What is ISF 10+2?
A US security filing for ocean cargo: 10 data elements from the importer (or its agent) plus 2 from the carrier (vessel stow plan and container status messages), submitted before the goods are loaded onto the vessel.

Q: 2. Who is responsible for filing ISF?
Legally the importer of record. In practice a licensed customs broker or the freight forwarder's agent files on the importer's behalf. The importer remains answerable for accuracy and timeliness.

Q: 3. What is the ISF deadline?
The commonly cited baseline is no later than 24 hours before the cargo is laden aboard the vessel at the foreign port. Work to an earlier internal cut-off, because the filing must be accepted, not merely transmitted.

Q: 4. What is the difference between ISF and AMS?
ISF is the importer-side security data set. AMS is the US carrier-side automated manifest system through which the carrier (or NVOCC) transmits manifest and the "+2" elements. Both apply to US-bound ocean cargo.

Q: 5. What are the 10 ISF data elements?
Seller, buyer, importer of record / FTZ ID, consignee, manufacturer/supplier, ship-to party, country of origin, HTSUS number, container stuffing location, and consolidator/stuffer — each with the associated name, address or identification details.

Q: 6. What happens if ISF is filed late or is inaccurate?
Consequences can include a "do not load" instruction, a missed sailing, a destination hold or exam, liquidated damages or penalties, and associated demurrage, detention and storage charges. Enforcement practice varies; confirm current CBP guidance.

Q: 7. Does DDP mean the seller handles ISF?
DDP typically means the seller arranges and pays for import formalities, including filing, but it does not automatically redefine the importer of record. Put the allocation of filing duties and penalty risk into the contract.

Q: 8. Is ISF required for air freight or LCL?
ISF applies to ocean cargo, including LCL shipments arriving by vessel. Air cargo follows different advance-data rules. Confirm the mode-specific requirement with your broker.

Q: 9. What is ENS and how is it different from ISF?
ENS (Entry Summary Declaration) is the EU's pre-arrival safety and security declaration under the Union Customs Code and ICS2. It is a separate regime for EU-bound cargo; ISF is US-specific. The data set and filer depend on the ICS2 release and transport scenario.

Q: 10. What is ACI eManifest and what is an ACID number?
Canada's ACI eManifest is the CBSA advance commercial information programme. Egypt's ACI scheme requires advance shipment registration producing an ACID number that must appear on the bill of lading and related documents. They are different programmes despite the shared acronym.

Q: 11. Can I update an ISF after filing?
Certain elements may be updated or filed flexibly under the rules, but you should not plan around that. Aim for a complete, accurate, accepted filing before the pre-loading deadline.

Q: 12. Does an NVOCC filing a House B/L change who files?
It can affect which party transmits which data set, but it does not remove the importer of record's responsibility. Confirm the house-vs-master data flow with your forwarder.

Q: 13. How does advance filing interact with normal customs clearance?
They are sequential, not interchangeable. Advance filing happens before loading at origin; entry/clearance happens at destination. A clean advance filing does not guarantee clearance, and a clean entry does not cure a missing advance filing.

Sources and further reading

  • US Customs and Border Protection (CBP) — Importer Security Filing ("10+2") programme guidance, data elements, timing and liquidated damages provisions. Verify current CBP publications before relying on any deadline or penalty figure.
  • CBP Automated Manifest System (AMS) and carrier / NVOCC manifest filing guidance for ocean cargo.
  • European Commission, Union Customs Code (UCC) and Import Control System 2 (ICS2) — Entry Summary Declaration requirements and phased release scope for safety and security data.
  • Canada Border Services Agency (CBSA) — ACI / eManifest programme requirements for marine cargo.
  • Egyptian customs / national ACI platform — advance cargo information registration and ACID number requirements; see the dedicated article linked on this site.
  • World Customs Organization (WCO) SAFE Framework of Standards — the international basis for advance electronic cargo information for risk assessment.
  • Incoterms® 2020 (International Chamber of Commerce) — allocation of costs and risks between buyer and seller; note that trade terms do not by themselves define statutory filing responsibility.
  • Harmonized Tariff Schedule of the United States (HTSUS) and the Harmonized System (WCO) — classification reference for the commodity code used in advance filings and entries.

This guide provides planning-level information, not legal, customs or compliance advice. Filing deadlines, data sets, ICS2 release scope, penalty schedules and destination-specific registration rules change over time and vary by transport scenario. Confirm current requirements with the relevant customs authority, a licensed customs broker, or your freight forwarder before booking or declaring.

Get your filing right before the container is loaded

Baton Logistics (Shenzhen Baton International Logistics Co., Ltd. / 佰通物流) is a Shenzhen-based NVOCC and freight forwarder founded in 2003 — not a freight broker — arranging FCL/LCL ocean freight, air freight, customs brokerage, consolidation and DDP/DAP door-to-door shipping from China to 100+ countries. As the party coordinating booking, documentation and carrier data on China-origin shipments, our operations team can help you map which advance-filing regime applies to your lane, collect the manufacturer, stuffing and classification data before the cut-off, and coordinate the filing with the licensed broker at destination.

Contact: overseas02@batongls.com · WhatsApp +86 191 2930 8513 · www.batongls.com

loading
Authority & standards:IATA · WCO · ICC Incoterms · IMO · U.S. CBP · GOV.UK · Trade.gov