Understanding ISF: What Importers Need to Know to Stay Compliant
Simplify ISF compliance for U.S. ocean imports. Learn how Cargoo helps you stay compliant and avoid costly delays.
Dealing with complex and changing customs regulations is unescapable to those involved in global trade. When it comes to shipping goods to the U.S., a critical component of the regulatory framework is the Importer Security Filing (ISF), also known as “10+2.”
If you’re importing by ocean freight to the U.S., understanding ISF requirements is crucial for keeping your cargo moving and your business compliant. Let’s break it down.
The ISF is a requirement enforced by U.S. Customs and Border Protection (CBP) to ensure that detailed cargo information is submitted before goods are loaded onto vessels heading to the U.S. It applies only to ocean freight and was created to improve cargo security by identifying high-risk shipments in advance. Since its implementation in 2009, ISF has been a non-negotiable part of global trade for businesses importing goods by sea.
At its core, the ISF filing is a risk management measure. By requiring the importer of record to submit detailed information, such as the names and addresses of sellers and buyers, CBP can better protect supply chains.
The nickname “10+2” refers to the two sets of data required for the Importer Security Filing (ISF) process, as mandated by U.S. Customs and Border Protection.
ISF doesn’t determine whether your cargo is allowed into the U.S. or impact trade enforcement directly. However, U.S. Customs and Border Protection (CBP) uses the data to assess potential risks by cross-checking it with your customs entry.
Complying with ISF regulations directly impacts your ability to import efficiently and without costly disruptions. Missing deadlines, submitting inaccurate data, or failing to file altogether can result in severe financial penalties, cargo delays, and potential damage to business operations.
For high-volume importers, the stakes are even higher. Larger shipments mean more data, tighter timelines, and a greater need to ensure accuracy across your supply chain. Without the right systems and processes in place, the risk of errors multiplies, leading to challenges that can snowball quickly.
To comply with ISF, the importer of record must submit ten key data elements electronically to CBP at least 24 hours before cargo is loaded at the port of origin. These details include:
Seller
Buyer
Importer of Record Number
(or FTZ applicant ID)
Consignee Numbers
Manufacturer (or Supplier)
Ship-to Party
Container Stuffing Location
Commodity HTS (Harmonized Tariff Schedule) Number
Container Stuffing Location
Consolidator (Stuffer)
Vessel Stow Plan:
Details about how cargo is arranged on the vessel.
Container Status Messages (CSMs):
Updates on the status of containers as they move through the supply chain.
These must be submitted no later than 24 hours before the vessel arrives at a U.S. port.
The ISF filing itself is done electronically at the lowest bill of lading level, such as a house or regular bill, through the Automated Manifest System (AMS). Filing must occur at least 24 hours before the vessel departs its port of origin.
ISF filings are required at least 24 hours before your cargo departs the port of origin. To stay on the safe side, aim for 72 hours or even earlier whenever possible. The sooner you file, the better your chances of avoiding last-minute issues.
A customs bond is mandatory for ISF filings and can be either continuous or single-entry. A continuous bond is often recommended, as it covers both the ISF and the customs entry. In contrast, a single-entry bond requires an additional ISF bond for compliance.
If you’re importing bulk cargo, like grain or coal, ISF filing requirements do not apply.
Once the filing is submitted, CBP sends an acceptance or rejection message. However, incomplete filings may still be accepted without clear notification of missing data, increasing the risk of compliance issues.
While this might sound straightforward, gathering this information from multiple parties—like suppliers and freight forwarders—can be complex, especially when dealing with a multitude of international partners. Working with purpose-built ocean freight management software solutions can help ensure accuracy and timeliness of ISF filing.
Responsibility for ISF compliance falls on the importer, even if third parties like customs brokers or freight forwarders handle the submission. This makes it essential for importers to have clear communication and coordination across the supply chain. Accurate and timely data submission is not just a requirement; it’s a shared task that demands collaboration.
Failing to meet ISF requirements can lead to significant consequences:
Penalties
CBP imposes fines of up to $5,000 for every violation, whether it’s a late, incomplete, or inaccurate filing.
Do Not Load Orders
CBP issuing a “Do Not Load” order to ocean carriers, preventing your cargo from being loaded at origin.
Delays and Inspections
Non-compliance can trigger cargo holds, additional inspections, and logistical delays that disrupt your supply chain.
Reputational Risk
Persistent violations may lead to scrutiny from CBP, impacting your ability to operate smoothly in the future.
For businesses importing goods on tight schedules or working with perishable items, these consequences can be particularly costly.
While ISF 10 applies to US-bound cargo requiring 10 data elements, ISF 5 is a simplified filing for shipments that only transit through US ports (FROB – Freight Remaining On Board). It requires just 5 elements: booking party, carrier, vessel stow plan, container status, and ship’s itinerary. Both share the 24-hour advance filing requirement but serve different purposes – ISF 10 for imports, ISF 5 for transit cargo.
Preparing for ISF compliance starts with understanding the process and building strong internal practices. Here’s what importers can do to stay ahead:
Organize Your Data
Ensure you have systems in place to collect and store the required information well in advance of shipment.
Coordinate with Partners
Work closely with suppliers, freight forwarders, and customs brokers to ensure data is accurate and deadlines are met.
Train Your Team
Educate staff on ISF requirements and make compliance a priority across your organization.
Monitor Changes
Stay informed about updates to ISF regulations to ensure your processes remain compliant.
Preparation isn’t just about meeting deadlines—it’s about creating a process that ensures reliability and reduces risk.
For importers looking to reduce the effort and uncertainty of ISF compliance, Cargoo provides a purpose-built solution that streamlines the entire process. By leveraging existing shipment data and automating key steps, Cargoo eliminates redundant data entry and manual coordination between parties. The solution connects exporters, importers, and customs brokers in a secure environment where shipping information flows directly into ISF documentation, while built-in validation helps ensure accuracy and completeness.
ISF compliance doesn’t have to feel overwhelming. With Cargoo’s structured approach to data management and status tracking, importers can handle this requirement efficiently, maintain compliance, and focus on strategic operations.
Contact us to learn how Cargoo can help streamline your US-bound import operations while reducing risk and manual effort.
Simplify ISF compliance for U.S. ocean imports. Learn how Cargoo helps you stay compliant and avoid costly delays.
ICS2 compliance brings new customs compliance challenges for EU imports. Discover key data requirements, roles, and how Cargoo simplifies the process for seamless shipments.
Discover ICS2 compliance essentials for EU imports. Learn how to streamline customs processes and avoid delays with Cargoo’s solutions.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
_cfuvid | session | Calendly sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wpEmojiSettingsSupports | session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
Cookie | Duration | Description |
---|---|---|
__hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_clck | 1 year | Microsoft Clarity sets this cookie to retain the browser's Clarity User ID and settings exclusive to that website. This guarantees that actions taken during subsequent visits to the same website will be linked to the same user ID. |
_clsk | 1 day | Microsoft Clarity sets this cookie to store and consolidate a user's pageviews into a single session recording. |
_ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gcl_au | 3 months | Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services. |
_gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
_lfa | 2 years | Leadfeeder - to store and track audience reach |
CLID | 1 year | Microsoft Clarity set this cookie to store information about how visitors interact with the website. The cookie helps to provide an analysis report. The data collection includes the number of visitors, where they visit the website, and the pages visited. |
FPID | session | Google Tag Manager sets this cookie for server-side tagging. |
FPLC | session | Google Tag Manager sets this cookie for tracking between domains. |
hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
MR | 7 days | This cookie, set by Bing, is used to collect user information for analytics purposes. |
SM | session | Microsoft Clarity cookie set this cookie for synchronizing the MUID across Microsoft domains. |
Cookie | Duration | Description |
---|---|---|
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
ANONCHK | 10 minutes | The ANONCHK cookie, set by Bing, is used to store a user's session ID and verify ads' clicks on the Bing search engine. The cookie helps in reporting and personalization as well. |
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
li_gc | 6 months | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
MUID | 1 year 24 days | Bing sets this cookie to recognise unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
SRM_B | 1 year 24 days | Used by Microsoft Advertising as a unique ID for visitors. |
Cookie | Duration | Description |
---|---|---|
_lfa_test_cookie_stored | less than a minute | Description is currently not available. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |