ISF 10+2 is an importer-owned data deadline even when a broker or forwarder transmits the filing.

What is due, and when?

CBP's current public guidance says ISF, commonly called 10+2, applies to cargo arriving in the United States by ocean vessel. Eight importer data elements are due no later than 24 hours before cargo is laden aboard the vessel destined for the United States. Container stuffing location and consolidator must be supplied as early as possible and no later than 24 hours before arrival at a US port under the flexibility described by CBP.

CBP says an inaccurate, incomplete, or untimely filing may lead to liquidated damages of $5,000 per violation. That is a possible enforcement amount, not an automatic charge or expected cost. The official guidance also says ISF is filed electronically through ABI or ACE, commonly by a licensed customs broker or third-party provider.

Do not let the booking confirmation become the first data request

The filing clock is tied to loading, while several data owners sit outside the importer's team. Create the request when the purchase order and ocean routing are known, then confirm the lowest bill-of-lading level and line-item relationships. Under 19 CFR 149.3, manufacturer or supplier, country of origin, and commodity HTSUS must be linked at line-item level.

Treat HTS and origin as controlled decisions, not fields for the forwarder to guess. The forwarder or consolidator may be the best source for stuffing and booking facts, while the importer and customs broker remain responsible for reviewing the filing basis appropriate to their roles.

Use field-level states and a cut-off, not one 'ISF complete' checkbox

Each element should show source, value, evidence, owner, review state, and last change. Useful states are not requested, requested, received, conflicting, reviewer question, approved for filing, transmitted, accepted, amended, and superseded. A complete seller name does not compensate for an unresolved HTS or stuffing location.

Set an internal cut-off earlier than the legal deadline so the broker or filer can validate and correct the dataset. Record the carrier loading milestone used for the deadline and escalate when the milestone changes; do not assume an ETA or estimated departure alone proves the loading cut-off.

• Are all elements tied to the lowest applicable bill and correct goods line?
• Do manufacturer or supplier, country of origin, and HTS reconcile at line level?
• Are stuffing location and consolidator sourced from the party that knows the physical event?
• Did the authorised filer acknowledge the approved version and any later amendment?
• Is the final filed evidence retained with the shipment and exception history?

How Tyllus supports the importer-forwarder handoff

Tyllus can keep purchase-order and shipment context, required-data requests, supplier and forwarder follow-up, documents, owners, deadlines, and attention states connected. The import team can see which ISF input is still missing or conflicting and retain the version sent to its broker or filing provider.

Tyllus does not determine HTS or origin, calculate a legal filing deadline, transmit ISF to ABI or ACE, act as a customs broker or filer, validate CBP acceptance, or guarantee that damages, inspection, or delay will be avoided. The importer and authorised professionals remain responsible for the filing and compliance decisions.

A citation-ready answer for import teams

ISF 10+2 is a pre-loading data-coordination requirement for US-bound ocean cargo. The durable control assigns each element to its real source, links goods identity at line level, gives the authorised filer time to review, and retains transmission and amendment evidence. Outsourcing transmission does not remove the importer's need for an accurate handoff.

Confirm the rule, shipment type, filing party, timing, flexible elements, and enforcement position with current CBP guidance and a qualified customs professional.