? Are you preparing to import food into the United States and need a clear, practical guide to completing your Importer Security Filing (ISF) without surprises?

What IS an ISF and why it matters for food imports

You should understand that the Importer Security Filing (commonly called ISF or 10+2) is a U.S. Customs and Border Protection (CBP) requirement designed to improve cargo targeting and security for ocean shipments bound for the United States. For food importers, ISF is not a stand-alone compliance item: it intersects with food-safety regimes such as the Food Safety Modernization Act (FSMA), Prior Notice, and the Foreign Supplier Verification Program (FSVP). Filing the ISF correctly reduces the risk of your cargo being held, delayed, or penalized — outcomes that are particularly costly with perishable food.

The core components: 10+2 explained

You must provide ten importer data elements, while the carrier supplies two additional elements. These are collectively referred to as 10+2. The 10 elements are primarily your responsibility as the importer or your authorized agent.

Party	Element	Purpose
Importer (you)	Seller (owner of the goods at time of sale)	Identifies source; helps CBP and agencies assess risk
Importer	Buyer (owner at time of entry)	Tracks who will bring goods into commerce
Importer	Importer of record number/FTZ applicant ID	Critical identifier for customs processing
Importer	Consignee number(s)	Identifies receivers in the U.S.
Importer	Manufacturer (full name and address)	Traceability for inspections or recalls
Importer	Ship-to name and address	Where goods are being delivered or stored
Importer	Country of origin	Tariff and safety determination
Importer	Commodity HTSUS number	Tariff classification and duty assessment
Importer	Container stuffing location	Security and traceability of packing origin
Importer	Consolidator (stuffer)	Who loaded goods into container
Carrier	Vessel stow plan/Container status messages (CSM)	Provides CBP with stowage and status for risk targeting
Carrier	Bill of lading number	Links the cargo to the vessel movement and documents

This table gives you the concise taxonomy you must supply. For food, manufacturer details, country of origin, and HTSUS classification often trigger additional regulatory scrutiny.

Who must file the ISF?

You are the importer of record — typically the entity listed for customs entry — and you are responsible for filing the ISF. However, you may authorize a customs broker, freight forwarder, or third-party service provider to file on your behalf. When you delegate, you are still legally responsible for ensuring the ISF is accurate and timely.

• If you use a customs broker or service provider, document the authorization in writing.
• If you’re an owner-operator of an importer of record company, you should either file or ensure your agent files.
• If the shipment is for a consignee that’s not the importer of record, coordinate data carefully to avoid mismatches.

When to file: timing requirements and practical margins

CBP requires that ISF be filed at least 24 hours before the cargo is loaded onto the vessel destined for the U.S. port. Missing that deadline exposes you to penalties and potential shipment delays.

• Mandatory window: At least 24 hours prior to vessel loading at foreign port.
• Best practice: File earlier — 72 hours or more — to allow for corrections and to accommodate carriers.
• Last-minute shipments: If you don’t have required details in time, consider delaying the shipment or arranging an unlocked charger hold with the carrier (risky and not recommended).

How to prepare accurate ISF data for food imports

You must compile precise data for each ISF element. For food, extra care is necessary because inaccuracies can trigger food-safety inspections or FSMA enforcement actions.

• Seller and buyer: Confirm legal names and addresses; include subsidiaries only when they are the actual contracting parties.
• Manufacturer: Provide full address, including region and postal code. For multi-site manufacturers, identify the specific facility that produced the food.
• HTSUS number: Use the correct six- to ten-digit HTSUS code. When uncertain, consult your customs broker and conduct a binding ruling if classification is materially uncertain.
• Country of origin: This should reflect the last substantial transformation, not just where ingredients were mixed.
• Container stuffing location and consolidator: Accurately record where stuffing occurred; this matters for fumigation, export documentation, and traceability.

Step-by-step ISF filing workflow (start-to-finish)

You should follow a defined process so filings are complete and defensible.

1. Gather documentation:

   • Commercial invoice, packing list, purchase order, sale contract.
   • Manufacturer and supplier contact info.
   • HTSUS numbers and declarations from your compliance team or broker.

2. Assign responsibility:

   • Determine who files ISF (you, broker, forwarder). Document the delegation.

3. Prepare ISF data:

   • Fill all 10 importer elements; request carrier elements or BL from the carrier.

4. Submit ISF:

   • Electronically transmit to ABI or via your carrier/broker portal at least 24 hours before loading.

5. Verify acceptance:

   • Confirm CBP acceptance code or acknowledgment. If rejected, review and resubmit immediately.

6. Update as necessary:

   • If data changes after submission, file an amendment as soon as you know.

7. Monitor arrival:

   • Track vessel arrival, stevedore operations, and any CBP holds or exams.

8. Clear customs:

   • Ensure you or your broker file entry and pay duties; supply Prior Notice and FSMA documentation as required.

9. Receive and inspect:

   • Upon release, verify goods against invoices and quality standards.

10. Record retention:

• Keep records for at least five years (FSMA and CBP requirements vary by program); maintain electronic backups.

Practical compliance tips and strategies

You should adopt policies and controls that reduce errors and mitigate risk.

• Use standardized templates for supplier data and onboarding; require suppliers to provide full manufacturer addresses and facility identifiers.
• Integrate procurement, logistics, and compliance systems so that HTSUS and country-of-origin data flow into ISF submissions automatically.
• Train staff and agents to understand the special requirements for food: manufacturer identity, processing location, and ingredient sourcing.
• Conduct periodic audits of ISF filings: check a sample of submitted filings against supporting documents.
• Establish escalation protocols for rejected or amended ISFs to avoid last-minute frantic corrections.
• When in doubt on HTSUS, request a binding ruling from CBP for high-value or ambiguous classifications.

Compliance edge cases and how to handle them

Food imports can present unusual situations. You should know how to handle them.

• Split shipments and transshipments:

  • If a single PO is packed across multiple containers or vessels, submit an ISF for each container referencing the same underlying data where appropriate.
  • For transshipments, ensure the final intended destination is accurately reflected and that the ISF covers the movement to the U.S.

• Mixed loads (multi-origin consolidation):

  • For consolidated containers with multiple manufacturers or countries of origin, list each manufacturer and each country of origin for the respective cargo lines.

• Re-exported goods:

  • If food is temporarily imported into another country and then re-exported to the U.S., make sure the ISF reflects the most recent stuffing location and manufacturer identity.

• Changes after filing (amendments):

  • Amend promptly and document the reason for change. Repeated amendments can trigger audits or penalties.

• Unknown or variable HTSUS:

  • Use a conservative classification, but if the correct classification materially affects duties or safety classification, pause shipment or obtain a pre-shipment classification.

• Perishable goods and last-minute supplier changes:

  • Require contractual language with suppliers to provide timely data for ISF. For perishable goods, prioritize early confirmation of manufacturer and stuffing location.

Penalties, holds, and consequences of non-compliance

You are responsible for timely and accurate ISF submission. Non-compliance can produce several consequences:

• Penalties:

  • CBP may assess civil penalties for failure to timely file ISF or for submission of false data. Penalties can be significant and factor in whether the failure was voluntary or negligent.

• Delays and exams:

  • Incorrect or missing ISF can trigger inspections or examinations, which for food can include FDA sampling or holds.

• Cargo holds and vessel arrival delays:

  • A missing ISF can subject your container to a hold, and carriers may refuse to load cargo without complete ISF data.

• Increased scrutiny:

  • Repeated non-compliance can place your account on higher scrutiny lists, causing future shipments to face more frequent inspections.

• Risk to FSMA compliance:

  • ISF inaccuracies may complicate your ability to meet FSMA Prior Notice or FSVP obligations, particularly around traceability and supplier verification.

Coordination with FDA: Prior Notice and FSMA interplay

You must not treat ISF as the only filing requirement. FDA Prior Notice is required for food shipments and must be submitted before arrival. The ISF supports CBP’s risk assessment, while Prior Notice facilitates FDA’s import screening. You should coordinate both filings:

• Timing:

  • Prior Notice typically must be submitted at least two hours before arrival for most food; many importers submit both ISF and Prior Notice earlier to avoid issues.

• Data overlap:

  • Ensure consistency between ISF manufacturer names/addresses and Prior Notice facility names to avoid mismatched records that trigger holds.

• FSVP:

  • Under FSMA, you must ensure that your foreign supplier meets food-safety requirements; documentation of supplier verification should be ready in case of inspection.

Technology and data integrity

You will find that technology is your ally when data volumes grow.

• Use an integrated import management system:

  • This reduces manual entry errors and can route ISF to customs automatically.

• Validate addresses and manufacturer names:

  • Use consistent naming conventions and address validation to avoid CBP rejections.

• Electronic records:

  • Keep electronic logs of ISF acceptances, amendments, and correspondence with carriers and brokers.

• Automation with caution:

  • Automate repetitive tasks but implement controls to catch anomalies, such as multiple addresses for the same manufacturer.

Working with third-party agents and authorized filers

You can outsource your ISF filing, but you remain responsible. Treat your contracts and operational relationships with care.

• Written authorization:

  • Keep a written and dated agreement that defines who files, who corrects, and who is responsible for errors.

• SLAs (Service Level Agreements):

  • Establish timelines for file submission, acceptance confirmation, and error remediation.

• Audit rights:

  • Include the right to audit filings and records in your contracts with agents.

• Insurance and indemnities:

  • Consider contractual indemnities for gross negligence by agents; insurance can cover certain liabilities.

Useful checklist for every food ISF filing

Use this checklist before submission to increase accuracy.

• Confirm importer of record number or FTZ ID.
• Verify seller and buyer legal names and addresses.
• Confirm manufacturer full name and physical address.
• Confirm country of origin and document the basis (last substantial transformation).
• Confirm HTSUS numbers for each line item.
• Confirm container stuffing location and consolidator name.
• Obtain bill of lading and carrier details.
• Check for split containers or multi-manufacturer loads and add all relevant manufacturer entries.
• Coordinate Prior Notice and FSVP documentation as needed.
• Submit ISF at least 24 hours before loading, and ideally sooner.
• Confirm CBP acceptance and archive the acknowledgment.

Common errors and how to avoid them

You can prevent many mistakes by focusing on a few recurring problem areas.

• Incomplete manufacturer addresses:

  • Ask suppliers to provide complete facility addresses; reject ambiguous replies.

• Wrong HTSUS:

  • Use consistent HTSUS assignment protocols and consult your broker for unclear codes.

• Late submission:

  • Build internal timelines and refuse to accept shipments without ISF data.

• Mismatched data across filings:

  • Reconcile ISF, Prior Notice, and customs entry data as part of pre-shipment routines.

• Multiple parties with similar names:

  • Use unique identifiers (EINs, importer numbers) where possible to prevent confusion.

Sample scenarios and practical solutions (user journey completion)

You should be able to handle common importer journeys. Below are scenario-based instructions to help you apply the rules.

Scenario 1: You import canned vegetables from three different manufacturers in a consolidated container.

• Ensure you list each manufacturer and the country of origin for their product lines in the ISF.
• If HTSUS differs by product, map each line to the correct classification.
• Coordinate with the consolidator for accurate stuffing location details.

Scenario 2: You discover the manufacturer address was wrong after filing.

• Amend the ISF immediately with the corrected address and document why the change occurred.
• Keep an audit trail of communication that shows the supplier provided incorrect data.

Scenario 3: Your carrier requests ISF data late, threatening to miss the 24-hour window.

• Prioritize contingency by postponing loading if possible or arranging for expedited data retrieval from your supplier.
• Consider contractual penalties for suppliers who fail to provide timely ISF information.

Scenario 4: Your shipment triggers an FDA inspection upon arrival.

• Provide CBP and FDA with requested documentation: Prior Notice, FSVP records, supplier verification, and ISF acceptances.
• Cooperate with the inspection and maintain transparent records to shorten examination time.

Recordkeeping and audits

You must retain ISF records, supporting documents, and correspondence in case of CBP or FDA audits.

• Required retention:

  • Keep records for at least five years; FSMA and CBP may require extended documentation in case of recalls or investigations.

• Recommended storage:

  • Use encrypted, backed-up electronic systems with clear version control for amendments and acknowledgments.

• Audit preparation:

  • Periodically conduct internal mock audits to ensure you can produce ISF files, Prior Notice records, supplier verification, and shipping documentation.

Filing amendments: when and how to do it

Amend an ISF whenever material information changes after filing. Amendments should be timely and clearly documented.

• Common amendment reasons:

  • Changed manufacturer information, corrected HTSUS, corrected consignee, or corrected stuffing location.

• How to amend:

  • File electronically with the corrected fields and include a brief reason in your internal records. CBP will accept amendments but repeated corrections indicate systemic problems.

• Timing:

  • Amend as soon as you know; delays can increase operational risk.

FSMA and FSVP considerations for importers

ISF does not replace FSVP obligations. You must ensure the foreign supplier follows appropriate preventive controls.

• Supplier verification:

  • Keep written verification that suppliers follow preventive measures such as hazard analysis, corrective actions, and sanitation programs.

• Traceability:

  • ISF manufacturer and ship-to data should align with your traceability matrix to support rapid recalls.

• Documentation:

  • Maintain FSVP documentation that demonstrates risk-based supplier evaluation and verification activities.

Frequently asked questions (answers with moderate depth)

You should find straightforward answers to common questions.

• Q: Can a customs broker file ISF for me?

  • A: Yes, but you remain responsible. Provide written authorization and ensure the broker follows your data standards.

• Q: What happens if ISF is rejected?

  • A: You must correct and resubmit immediately. Keep the carrier and CBP informed if the rejection risks missing the 24-hour window.

• Q: Does ISF apply to shipments arriving by air?

  • A: No. ISF (10+2) applies only to ocean shipments destined for the U.S.

• Q: Are there exemptions?

  • A: Certain import scenarios like empty containers, pipelines, or shipments not arriving by vessel may be exempt. Confirm with CBP guidance for edge cases.

• Q: How does ISF relate to Prior Notice?

  • A: They are separate filings to different agencies; both are required for food and should be consistent.

Performance metrics you should monitor

You should track KPIs that indicate how well your ISF process works.

• On-time ISF submission rate (goal: 98%+).
• Number of ISF amendments per month (lower is better).
• Number of rejections and average resolution time.
• Number of CBP exams/holds per number of shipments.
• Time from vessel arrival to cargo release.

Sample timelines and SLA suggestions

You should set realistic service level agreements with carriers and brokers.

Activity	SLA recommendation
Supplier data delivery to importer	7–14 days before vessel loading
ISF submission by filer	72–24 hours before vessel loading
Carrier acknowledgment	Within 4 hours of ISF submission
ISF rejection resolution	Within 2 hours of rejection notification
Amendments turnaround	Within 4–24 hours depending on nature

Use the table above to set expectations with partners and provide buffer time for complex shipments.

Final compliance checklist (actionable steps)

You must act proactively every time you import food. Use this final checklist before shipment.

• Confirm importer of record ID.
• Verify supplier/manufacturer details (names and full addresses).
• Confirm HTSUS numbers for all articles.
• Verify country of origin reasoning and documentation.
• Coordinate stuffing location and consolidator info.
• Submit ISF at least 24 hours before loading; aim for 72+ hours.
• Cross-check ISF with Prior Notice and FSVP documentation.
• Retain acceptance acknowledgments and amendment records.
• Monitor KPI dashboard and escalate anomalies.
• Perform periodic audits and supplier re-verifications.

Closing perspective: a fresh but thorough approach

You are navigating a system built to manage risk and protect public health, but the operational reality is human and messy. Treat ISF filing not as a bureaucratic checkbox but as a core part of your food-safety and logistics program. Build relationships with reliable suppliers and agents, invest in data integrity, and maintain an audit trail that proves you acted responsibly. When you do these things, you reduce the chance that perishable food gets stuck on a wharf, that a client’s shelf is empty, or that a traceability gap becomes a headline.

If you implement the processes and controls described here, you will be equipped to file ISFs accurately, address common edge cases, and meet the expectations of CBP and FDA — preserving both supply continuity and consumer safety.