SUPPLY CHAIN SECURITY | 2026-10-22

Importer Security Filing (“ISF 10+2”): What California Ocean Importers Must File Before Lading, Who Is Responsible, and the Liquidated-Damages Risk of a Late or Wrong Filing

For every container of non-bulk cargo arriving by vessel, CBP requires an Importer Security Filing — ten data elements from the importer and two from the carrier — transmitted before the goods are loaded at the foreign port. Missing, late, or inaccurate filings expose the importer of record to liquidated damages under its customs bond, cargo holds, and increased exams, making ISF compliance a front-line operational risk for California importers.

Every California business that imports goods by ocean vessel must comply with one of U.S. Customs and Border Protection’s most unforgiving advance-data requirements: the Importer Security Filing , universally known as “ISF 10+2.” Created under the authority of the SAFE Port Act of 2006 and Section 3

For importers bringing goods into California’s ports — Los Angeles, Long Beach, Oakland — the Importer Security Filing is a compliance obligation that begins long before the container reaches the terminal. CBP uses the advance data to assess security risk before cargo is even loaded abroad, and the agency enforces the requirement through the importer’s customs bond. An importer that treats ISF as a routine clerical task, or assumes its freight forwarder has it handled, can be surprised by liquidated-damages claims and cargo delays that disrupt its supply chain. Understanding the rule’s structure, deadlines, and enforcement is essential to managing that risk.

What ISF Is and Why It Exists

ISF is an advance cargo-information program. After the September 11 attacks, Congress directed CBP to obtain data about ocean shipments before they are loaded onto U.S.-bound vessels, so the agency can perform security targeting while the cargo is still overseas. The SAFE Port Act of 2006 (Section 203) and Section 343(a) of the Trade Act of 2002 provided the mandate, and CBP implemented it in 19 C.F.R. Part 149. The rule is built around two filings: the importer’s security filing of ten data elements and the carrier’s filing of two. The combination gives CBP a picture of who is behind a shipment, what it contains, and how it is moving, before it can arrive at a U.S. port.

The Ten Importer Elements

Under 19 C.F.R. § 149.3, the importer (the ISF Importer) must transmit ten data elements for most shipments: (1) seller, (2) buyer, (3) importer of record number / FTZ applicant identification number, (4) consignee number(s), (5) manufacturer (or supplier), (6) ship-to party, (7) country of origin, and (8) commodity Harmonized Tariff Schedule number — these eight must be filed at least 24 hours before lading — plus (9) container stuffing location and (10) consolidator (stuffer), which may be provided somewhat later but no later than 24 hours before arrival. For FTZ and immediate-exportation type shipments, a reduced data set applies. The importer must also update the filing if information changes and withdraw it if the shipment will not be imported. Accuracy matters: the elements tie the shipment to real parties and a real tariff classification, and CBP compares them against other data.

The Two Carrier Elements

Under 19 C.F.R. § 149.4, the ocean carrier must submit two elements: the vessel stow plan (showing the physical location of containers aboard the vessel) and container status messages (reporting events and changes in status of containers). These are the carrier’s responsibility, not the importer’s, but they complete the “10+2” data picture. The split means that full ISF compliance for a shipment depends on both the importer and the carrier meeting their respective obligations, and an importer should understand which pieces it controls and which it does not.

Who Is the “ISF Importer” and Who Actually Files

The party responsible for the ten elements is the “ISF Importer” — generally the owner, purchaser, consignee, or agent (such as a licensed customs broker) who causes the goods to arrive by vessel. In most cases the importer of record is the ISF Importer, and it typically engages a customs broker or freight forwarder to transmit the filing to CBP. But delegating the filing does not delegate the liability: the ISF Importer remains responsible to CBP for timeliness and accuracy. This is a frequent source of trouble — an importer assumes its forwarder “has ISF covered,” but when a filing is late or wrong, CBP looks to the ISF Importer and its bond. Clear contracts, data hand-offs, and confirmation that filings were actually transmitted and accepted are essential.

Timing: Before Lading, Not Before Arrival

The defining feature of ISF is that the core data must be on file before the cargo is loaded onto the vessel at the foreign port — generally at least 24 hours before lading — not merely before the ship reaches the United States. This timing drives the entire upstream workflow: the importer must gather accurate seller, manufacturer, origin, and classification data from its foreign suppliers early, often before the goods are even containerized. Supply chains that assemble this information at the last minute routinely miss the lading deadline, which is precisely the kind of lapse CBP enforces. Building the data-collection step into purchase orders and supplier onboarding is the practical fix.

Enforcement: Liquidated Damages, Holds, and Exams

CBP enforces ISF primarily through liquidated damages assessed under the importer’s customs bond for filings that are late, inaccurate, incomplete, or not filed. Beyond monetary claims, non-compliance can trigger cargo holds (CBP can refuse to allow the cargo to be loaded or can hold it on arrival), “do not load” messages, and increased examination rates that slow a shipment and add demurrage and detention costs. CBP has published mitigation guidelines for ISF liquidated-damages claims and historically emphasized education and “informed compliance” before strict enforcement, but importers should not count on leniency: repeated or egregious violations draw real claims. The combined exposure — monetary claims plus operational delay — is what makes ISF a priority rather than a formality.

Responding to an ISF Liquidated-Damages Claim

If CBP issues a liquidated-damages claim for an ISF violation, the importer is not without recourse. The importer may file a petition for mitigation or cancellation, presenting the facts and any mitigating circumstances (a first offense, a good compliance record, prompt corrective action, or carrier/forwarder error). CBP evaluates petitions under its published mitigation guidelines, which consider factors such as the importer’s history and the presence of aggravating or mitigating circumstances. A well-documented petition — showing what happened, why, and what the importer has done to prevent recurrence — can substantially reduce or eliminate the claim. Because deadlines to petition are strict and the framework is technical, importers facing a claim benefit from prompt, experienced trade counsel rather than simply paying the demand.

Integrating ISF With Broader Customs Compliance

ISF does not stand alone. The same shipment is subject to entry requirements, classification and valuation rules, country-of-origin marking, and potentially AD/CVD or forced-labor scrutiny. The ISF data — especially manufacturer, country of origin, and HTS number — should be consistent with what the importer later declares on entry, because CBP cross-checks the two. Inconsistencies can draw attention and undermine the importer’s claim to have exercised reasonable care. A mature compliance program therefore treats ISF as part of an integrated data flow, not a siloed task, and uses the discipline of gathering accurate ISF data early to improve the accuracy of the eventual entry as well.

Practical Steps for California Importers

To manage ISF risk, California importers should: identify the ISF Importer for each shipment and confirm who is transmitting the filing; collect the ten elements early by building supplier data requirements into purchase orders; confirm acceptance of each filing rather than assuming it went through; reconcile ISF data with entry data to avoid inconsistencies; maintain their customs bond and understand its exposure to ISF claims; and keep records of filings and corrections. When a liquidated-damages claim arrives, respond promptly with a documented petition. Because the rule’s deadlines are tied to events overseas and its enforcement runs through the bond, importers who treat ISF as a disciplined, front-loaded process — not a last-minute formality — avoid the holds and claims that catch less-prepared competitors. It is also worth building internal accountability: designate who owns ISF for each shipment, track filing confirmations in the same system that manages purchase orders, and audit a sample of filings periodically to catch recurring data errors (wrong manufacturer, stale HTS numbers, mismatched consignee) before CBP does. An importer that can show CBP a documented, repeatable ISF process — and prompt correction of any lapse — not only reduces the frequency of violations but strengthens every mitigation petition it may ever need to file, because CBP’s progressive-enforcement approach rewards exactly that kind of demonstrated diligence. Treating ISF as a managed program rather than a clerical afterthought is, in the end, both the cheapest way to avoid claims and the strongest defense when one arrives. For a California importer whose business depends on predictable, on-time cargo flow through Los Angeles, Long Beach, or Oakland, the operational cost of an ISF hold — demurrage, detention, missed delivery windows, and disrupted downstream commitments — frequently dwarfs the liquidated-damages claim itself, which is all the more reason to invest in getting the filing right the first time rather than managing the consequences after the fact.

Progressive Enforcement and the Compliance Record

CBP’s historical approach to ISF enforcement has emphasized progressive treatment: the agency considers an importer’s overall compliance record rather than treating every discrepancy identically. A first, isolated error by an importer with an otherwise clean history is treated very differently from a pattern of late or inaccurate filings. This matters for two reasons. First, it means an importer’s past conduct is itself an asset or a liability: a documented record of accurate, timely filings strengthens any later mitigation petition, while a history of lapses invites escalating claims. Second, it means importers should self-correct promptly — filing updates when data changes, and documenting corrective measures after any error — because the record of responsiveness is exactly what CBP weighs. An importer that treats a single liquidated-damages claim as a signal to tighten its process, and documents that it did so, is in a far stronger position if a second issue ever arises. Conversely, ignoring early warnings and continuing to file carelessly converts what might have been forgiven lapses into a pattern that supports full enforcement.

ISF in Special Situations

Several situations change the ISF analysis. Foreign-trade-zone admissions and immediate-exportation and transportation-and-exportation shipments use a reduced ISF data set, reflecting that the goods are not entering U.S. commerce in the ordinary way. Transshipment and routed transactions (where the foreign seller controls the carrier) raise questions about who possesses the required data and who is responsible for filing, which should be resolved by contract before the goods move. Bulk cargo is generally exempt from the ISF-10 requirement, and break-bulk cargo may receive different treatment. Goods moving under a bonded movement, or destined for a bonded warehouse, still require ISF because they arrive by vessel. Because the rules vary by shipment type, an importer with a mixed portfolio of transactions should map its ISF obligations transaction type by transaction type rather than assuming a single workflow covers everything; a process built only for ordinary consumption entries can miss the requirements that apply to its FTZ or in-bond movements.

Working With Your Customs Broker on ISF

Most importers rely on a customs broker or freight forwarder to transmit the ISF, and the relationship should be managed deliberately. The importer should confirm, in writing, who is responsible for the filing, what data the importer must supply and by when, and how the importer will receive confirmation that each filing was transmitted and accepted by CBP. The importer should insist on receiving the ISF transaction numbers and acceptance messages, not merely a verbal assurance. Powers of attorney and service agreements should address liability for filing errors, though as a legal matter the ISF Importer remains responsible to CBP regardless of private allocation. Because the broker acts on the importer’s data, the quality and timeliness of the importer’s inputs largely determine the quality of the filing — which is why the discipline of gathering accurate supplier data early is the single most effective ISF-compliance investment an importer can make.

Related Guides

• California International Trade & Customs Lawyers
• Antidumping & Countervailing Duties: Separate, All-Others, and NME Rates
• OFAC Sanctions Compliance: Strict Liability and the Framework

Frequently Asked Questions

What is ISF “10+2”?

It is CBP’s Importer Security Filing requirement for non-bulk cargo arriving by ocean vessel: ten data elements filed by the importer and two by the ocean carrier, transmitted to CBP before the goods are loaded at the foreign port. It is codified at 19 C.F.R. Part 149 under authority including 19 U.S.C. § 1415, the SAFE Port Act of 2006, and Section 343(a) of the Trade Act of 2002.

What are the ten importer elements?

Under 19 C.F.R. § 149.3: seller, buyer, importer of record/FTZ applicant ID, consignee number(s), manufacturer or supplier, ship-to party, country of origin, and HTS number (these eight at least 24 hours before lading), plus container stuffing location and consolidator (which may be filed later but no later than 24 hours before arrival). A reduced data set applies to FTZ and immediate-exportation shipments.

What are the two carrier elements?

Under 19 C.F.R. § 149.4, the ocean carrier files the vessel stow plan and container status messages. These are the carrier’s responsibility, but together with the importer’s ten elements they complete the “10+2” data CBP uses for security targeting.

When must the ISF be filed?

Generally at least 24 hours before the cargo is laden aboard the vessel at the foreign port — before loading, not merely before U.S. arrival. The stuffing-location and consolidator elements can be provided later but no later than 24 hours before arrival. The early deadline is why importers must collect supplier data well in advance.

Who is responsible if the filing is late or wrong — me or my broker?

The ISF Importer (usually the importer of record). You can delegate the filing to a customs broker or forwarder, but not the liability: CBP looks to the ISF Importer and its customs bond for late, inaccurate, or incomplete filings. Confirm that filings were actually transmitted and accepted. Call Trembach Law Firm at (213) 645-2246.

What happens if I don’t comply?

CBP can assess liquidated damages under your customs bond and can hold cargo, issue “do not load” messages, or increase examinations — adding demurrage, detention, and delay. Enforcement runs through the bond, so ISF failures have both monetary and operational consequences.

Can I challenge an ISF liquidated-damages claim?

Yes. You can file a petition for mitigation or cancellation under CBP’s mitigation guidelines, presenting mitigating facts — a first offense, a strong compliance record, prompt corrective action, or carrier/forwarder error. A well-documented petition can substantially reduce or eliminate the claim, but the deadlines are strict. Call Trembach Law Firm at (213) 645-2246.

How does ISF relate to my customs entry?

The ISF data — especially manufacturer, country of origin, and HTS number — should be consistent with what you later declare on entry, because CBP cross-checks them. Inconsistencies draw scrutiny and can undermine your reasonable-care position. Treat ISF as part of an integrated compliance data flow, not a standalone task.

Talk to a California Trade Lawyer About ISF Compliance

The Importer Security Filing is a front-line compliance obligation for every California ocean importer, and its enforcement through liquidated damages and cargo holds makes accuracy and timeliness essential. Trembach Law Firm, led by Anatolii Trembach (LL.M.; admitted in California), advises importers on ISF responsibility and bond exposure, responds to liquidated-damages claims with documented mitigation petitions, and integrates ISF with broader customs compliance. Call (213) 645-2246 for a confidential consultation.

Contact Trembach Law Firm at (818) 514-7680 for a confidential consultation.

Trembach Law Firm | 27001 Agoura Road, Suite 350, Calabasas, CA 91301