Direct answer: For covered ocean cargo, the ISF importer must transmit or arrange an accurate filing under current 19 CFR Part 149. For a standard ISF-10, the eight core importer elements are generally due at least 24 hours before lading; container-stuffing and consolidator data follow separate timing. Keep the legal importer, filer, bill level and FBA receiving reference distinct, and hold release when a changed fact has no accepted correction.

This refreshed guide is for sellers, importers, customs brokers, filers and operations teams moving China-origin inventory to a US FBA or 3PL receiving path. It explains evidence control, not a customs ruling, an Amazon appointment promise or a guaranteed check-in date. Reviewed: 8 October 2026. The current regulation, appointed filer and shipment-specific instructions control if they differ from this operating summary.

Key takeaways

  • Name the legal ISF importer and authorized filer before supplier release.
  • Use one evidence row per required value with source, owner, date and exception state.
  • Keep seller, buyer, importer, consignee, manufacturer or supplier and ship-to roles separate.
  • Record the bill level used for the filing; a booking, container or FBA reference is not automatically the same identifier.
  • Treat a rejected add as no active filing until the filer resubmits and receives acceptance.
  • Preserve amendments and connect the filing record to entry, delivery and receiving evidence.

What changed in this refresh

The earlier version relied on a 2025 Government Publishing Office snapshot. This version links the current Electronic Code of Federal Regulations Part 149, rechecks CBP’s current ISF page and carrier requirements, and keeps the practical limitations that matter to FBA teams. The update also separates standard ISF-10 timing from the later physical-loading data and makes the rejected-add consequence explicit.

Amazon documentation remains a separate control. Current Seller Central shipment and routing requirements govern the fulfillment handoff, while the Fulfillment Inbound API reference describes software objects and operations. Neither page turns Amazon into the importer, ISF filer or customs decision-maker.

ISF release-control table

Control point Evidence to hold Release decision
Responsible party Importer identity, filer authority, broker contact and shipment owner Hold until legal role and filing authority are confirmed.
Core ISF-10 data Seller, buyer, importer-of-record number, consignee number, manufacturer or supplier, ship-to party, origin and six-digit HTSUS data Confirm the standard 24-hour-before-lading deadline with the filer.
Physical-loading data Actual stuffing location and consolidator or stuffer Supply as early as possible and confirm the Part 149 deadline for the voyage.
Bill match Lowest-level bill reference transmitted, bill type or number and filer response Resolve a missing or incorrect match before arrival.
Correction state Original value, new value, reason, approver, transmission result and affected records Do not close the exception until the responsible filer confirms acceptance.
Receiving link FBA or 3PL shipment reference, carton map, delivery and check-in evidence Keep fulfillment status separate from ISF and entry status.

Name the importer and filer before cargo release

Start with the entity responsible for the filing and the person authorized to send or arrange it. Record the customs broker or filing agent, the bond arrangement where relevant, and the internal contact who can answer questions. The US customs readiness file and US importer readiness workbook help connect role evidence to the broader entry file, but they do not appoint a filer.

Then identify commercial parties from the actual transaction. Seller and buyer may differ from the exporting factory and US importer. A sourcing company, trading company, marketplace seller and manufacturer can all appear in one chain. Use the purchase order, commercial invoice, contract and entity records to determine which party belongs in each field; do not copy a prior shipment’s names because the cartons look similar.

Manufacturer or supplier identity should be tied to the goods being shipped. For consolidation, preserve each supplier against its SKU or carton group. The supplier consolidation service can coordinate factory cutoffs, but it does not replace the legal importer or filer evidence.

Build the core data as an evidence worksheet

Create one row for each importer-supplied data element with columns for value, source document, owner, validation date and exception status. For a standard ISF-10, the current rule generally covers seller, buyer, importer-of-record number, consignee number, manufacturer or supplier, ship-to party, country of origin and six-digit HTSUS number. The filer should confirm the applicable filing type and current definitions.

Country of origin and classification must be product-specific. A supplier label such as “accessory” or a marketplace category is not a classification rationale. Link the proposed Harmonized Tariff Schedule treatment to product facts and the importer’s review. If the product or tariff conclusion is unresolved, mark a hold instead of supplying a convenient historical code.

The ship-to party should reflect the first scheduled delivery location after customs release under the filing rules. An FBA fulfillment-center code by itself may not provide a complete legal name or address. Validate the current delivery instruction and log any destination change in the amendment register.

Separate physical-loading data from the 24-hour core

Container stuffing location and consolidator or stuffer describe the physical load. For a factory-loaded container, confirm where the container is actually stuffed. For less-than-container-load cargo, confirm the facility that consolidates or stuffs it. A booking office is not automatically the physical location, and a forwarder name is not automatically the consolidator for every shipment.

Under current Part 149, these physical-loading data have separate timing from the core ISF-10 data. They should be supplied as early as possible, with the responsible filer confirming the before-arrival limit and any special rule for a voyage shorter than 24 hours. Do not generalize the standard 24-hour-before-lading deadline to every field or filing type.

Use the ocean service scope and the current carrier booking record to identify the actual loading event. A carrier cutoff is an operational milestone; it does not itself prove that CBP accepted the filing.

Connect the filing to the correct bill level

The filer needs transport references that allow CBP to associate the ISF with the carrier record. Obtain the bill information from the party controlling the booking and record the bill type and number used. A master bill, house bill, booking number and container number are different identifiers. The current CBP FAQ explains why the filing should use the lowest bill level transmitted in ACE for the applicable shipment.

Keep the Amazon or 3PL receiving reference alongside, but separate from, the carrier identifiers. The receiving reference tells the destination how to process inventory; it does not identify the ocean manifest or prove that CBP matched the filing. A control table should let an operator move from purchase order to cartons, bill, entry and warehouse receipt without treating one number as all five.

Reconcile the filed quantity and commodity scope with the final load plan. If a supplier is removed, a carton is rebuilt or inventory changes destination, determine whether the filing, invoice, bill instructions or receiving plan needs correction. The carton-to-shipment reconciliation guide provides the physical mapping; this ISF file adds the filing owner and transport match.

Read filing responses as control states

A transmission event is not the same as a usable filing. Record whether the add was accepted or rejected, whether CBP reported a bill match, and whether later corrections were accepted. CBP’s ISF FAQ states that a rejected initial transaction has no active ISF record and must be corrected and resubmitted as a new add. Keep the rejection, corrected transmission and acceptance evidence together.

Keep acknowledgement, timestamp, bill type and number, filer contact and next action in one status log. If a bill splits or changes, ask the responsible filer whether the correction is an amendment, a new add or another permitted action. Operations staff should not infer legal status from a carrier dashboard, sailing event or warehouse shipment ID.

Use a simple state vocabulary: draft for incomplete data, submitted for a transmission awaiting response, accepted for filer-confirmed acceptance, rejected for an add with no active record, and amended only when the filer confirms the correction path. A status label without evidence is not closure.

Apply a pre-loading release gate

  1. Identify the importer, filer, broker authority and internal escalation owner.
  2. Freeze the purchase order, invoice, packing list and supplier-to-SKU map used for filing.
  3. Validate seller, buyer, importer, consignee, manufacturer or supplier and ship-to values.
  4. Document country of origin and a product-specific six-digit HTSUS basis for filer review.
  5. Confirm actual stuffing location, consolidator or stuffer and the applicable deadline.
  6. Record the lowest-level bill type and number used by the filer.
  7. Submit or arrange the filing early enough to resolve discrepancies before loading.
  8. Capture the response, bill-match result, timestamp and filer contact.
  9. Hold cargo when a required value, authority or accepted response is missing.
  10. Link the accepted filing to the entry, delivery references and FBA or 3PL receiving record.

Use the inbound readiness checker to find missing importer, label, carton and receiving data, then add the ISF-specific evidence to the shipment file. The tool supports planning; it does not decide legal filing fields or replace the appointed filer.

Control amendments and destination handoff

Shipment facts can change between purchase order, booking, loading and arrival. Create a dated amendment table with original value, revised value, reason, approver, filer confirmation and affected records. Changes to supplier allocation, consignee, destination, stuffing location, consolidator, HTS data or bill references should never be handled as an untracked email correction.

After import, reconcile the ISF record with the entry summary and physical receiving result. Customs release, terminal or CFS release, inland delivery, appointment, warehouse receipt and Amazon check-in are separate milestones. The appointment and rejection recovery guide helps keep destination exceptions separate from filing status.

When requesting a shipment-specific plan, provide origin, destination, product description, cartons, finished dimensions, gross weight, cargo-ready date, importer status and required stock date through the North America inbound plan form. A complete brief lets the broker, carrier and receiver answer their own questions without merging their roles.

Limitations and shipment-specific review

This guide cannot determine a classification, duty amount, product approval, bond suitability, filing deadline for an unusual shipment type, carrier acceptance, Amazon appointment or guaranteed inventory date. CBP rules, the legal importer, the authorized filer, the carrier and Amazon account instructions control different questions. Recheck every live source when the SKU, quantity, packaging, importer, destination, bill or receiving reference changes.

Frequently asked questions

Does Amazon file ISF for an FBA seller?

An FBA destination does not automatically become the ISF importer or filer. The importing business must identify the responsible importer, authorize the filing arrangement and confirm it with the appointed customs broker or filer for the actual ocean shipment.

Which ISF data is generally due 24 hours before lading?

For a standard ISF-10, seller, buyer, importer-of-record number, consignee number, manufacturer or supplier, ship-to party, country of origin and six-digit HTSUS number are generally due no later than 24 hours before lading at the foreign port. Confirm the shipment type and current rule with the filer.

When are stuffing-location and consolidator details due?

They have separate timing under 19 CFR Part 149 and should be supplied as early as possible. The rule includes a before-arrival limit and a special condition for voyages shorter than 24 hours, so the responsible filer must confirm the deadline for the actual cargo.

What happens if an ISF add is rejected?

A rejected initial add does not create an active ISF record. Correct the data and resubmit through the responsible filer, then retain the rejection, corrected transmission and acceptance evidence. Do not treat a carrier booking or FBA reference as proof that the filing exists.

Can an ISF be amended after filing?

Shipment facts can change, but the appointed filer should choose the permitted correction or amendment path. Record the original value, new value, reason, approver, transmission status and affected bill or entry records. Never overwrite the prior value without an audit trail.

Is an FBA shipment ID enough for ISF?

No. An FBA shipment or receiving reference identifies an intended fulfillment handoff. ISF needs trade-party, commodity, loading and transport data, including the bill level used for matching. Keep both identifiers connected but separate in the evidence file.

Official sources and review notes

Source note: These six official pages were opened and checked on 8 October 2026. Current CBP rules, the appointed filer, carrier instructions and Amazon account requirements remain controlling for the shipment.

Change log

8 October 2026: Replaced the 2025 GovInfo snapshot with current eCFR Part 149, rechecked CBP and Amazon sources, clarified standard ISF-10 versus physical-loading timing, documented rejected-add handling and expanded bill-level, amendment and receiving-link controls.