Which In-Transit Containers Actually Qualify for the Tariff Treatment

When a tariff action carries an in-transit exemption, the eligibility test often starts with a physical loading date: when the cargo was loaded onto the final U.S.-bound vessel. That date is usually paired with a separate entry-for-consumption or withdrawal deadline, which means the question is not just when the shipment was filed. It is whether the shipment satisfies the full cutoff pair.

Here is why it matters. Your compliance team looks at a booking confirmation, sees a planned sailing date and a planned arrival, and concludes a shipment lands on the safe side of a cutoff. That conclusion rests on a schedule. The rule rests on physical events: cargo on board a specific hull on a specific date, then entered or withdrawn by the deadline the notice sets. When the schedule and the water disagree, the physical shipment record is the safer basis for the tariff analysis.

So the operational question is not “did we file correctly.” It is “which of our on-the-water boxes actually qualify for the treatment we’re assuming, and how do we check that against real ETAs instead of the sailing schedule the booking implied.” That check falls in the gap between compliance and ops, which is exactly why it gets missed.

Why this is live right now

The Section 122 10% global import surcharge that has been in effect since February is scheduled to lapse July 24, 2026 by statutory design. The Trade Act of 1974 caps a Section 122 action at 150 days unless extended by Congress; the statute governing that authority, 19 U.S.C. 2132, is the primary basis for the sunset, and no action has been taken to continue the surcharge past that window. The tariff’s legal status is separately contested: the Court of International Trade struck it down on May 7, but the Federal Circuit issued an administrative stay on May 12 and then granted a stay pending appeal on June 11, so CBP collection continued while the appeal proceeded. The July 24 date is a statutory sunset, not a sign the surcharge is currently invalid.

What might replace it is already in motion. Per the Dorsey & Whitney alert’s characterization of USTR’s Section 301 forced-labor investigations, USTR proposed a 10% rate on most goods from 15 trading partners and 12.5% on most goods from roughly 45 more, including China, Vietnam, India, Thailand, Japan and South Korea (those specific rate and partner-count figures are the alert’s summary rather than directly quoted regulatory text; confirm against the Federal Register notice before relying on them). The alert’s directly quoted observation is narrower: the comment period closed July 6, a hearing was held July 7, and that hearing date “appears to closely track” the Section 122 expiration.

Two things are worth stating plainly, because getting them wrong is how a program of containers gets mispriced. First, as of USTR’s most recent public posture, the effective date for any Section 301 replacement is not yet determined, and no vessel-loading or arrival cutoff has been published for it. Second (and this is our own read, not a sourced fact): we could not confirm whether a Section 301 replacement would carry an in-transit provision at all. No source reviewed for this piece confirms whether Section 301 actions have historically used the in-transit mechanic that the reciprocal tariffs and the Section 122 surcharge did, so treat that as an open question. Anyone quoting you a firm 2026 loading cutoff today is quoting a schedule that does not exist in the primary record yet.

That uncertainty is not a reason to wait. It is the reason to get your vessel-timing method built now, so that if a cutoff appears in a Federal Register notice or a CBP CSMS message, you can run every in-transit box against it in an afternoon instead of a fortnight.

What the mechanic actually is

The reciprocal-tariff rollout in 2025 is the closest verified precedent for how final-vessel loading cutoffs have worked in recent U.S. tariff actions. It settled three points that are worth treating as useful operating assumptions until a 2026 action says otherwise.

Eligibility starts with the final ocean vessel. Per CBP FAQ guidance summarized by trade-compliance advisers, exemption eligibility is based on the date cargo was loaded onto its final ocean vessel bound for the U.S., not the mode of transport generically and not the booking date. Mohawk Global, citing CBP guidance, notes the in-transit relief applied only to the vessel mode: air, rail and truck did not qualify regardless of departure date. This post is about ocean containers specifically for that reason.

A feeder leg does not count. International Trade Insights, citing May 2025 CBP guidance, reported that importers cannot use a feeder vessel’s loading date to qualify. The operative date is when cargo boarded the vessel that actually crosses into the U.S. port. According to that same retelling, cargo that stays on board a U.S.-bound vessel through intermediate foreign-port calls still qualifies, while cargo transshipped onto a different mother vessel does not inherit the feeder date.

The loading date is only half of the cutoff pair. Recent in-transit provisions also use an entry-for-consumption or withdrawal deadline. That second date matters legally, but the final-vessel loading date is often the harder operational fact to see at scale, especially when bookings, feeder movements, rolled cargo, and transshipment changes sit in different systems.

The clarity can arrive weeks after the deadline does. After the April 2025 provision took effect, CBP did not publish formal trade-community guidance clarifying the loading-date standard until six weeks later, on May 15, 2025, which produced real confusion and unintended duty assessments. And even the “entered for consumption by” half of a cutoff pair has been amended mid-voyage: CBP updated one in-transit end date from May 28 to June 16, 2025. The deadline can move while your cargo is already at sea.

Put those together and the exposure is clear. The number that decides whether your shipment can use a given tariff treatment may start with a physical loading date on a named hull, documented on the on-board bill of lading rather than the booking. It also has to be checked against the entry or arrival deadline the notice sets. Neither side of that cutoff pair is reliably visible in a planned sailing schedule.

Why the sailing schedule can’t answer the question

The gap between planned and actual transit is not a rounding error. It is large enough to flip a container from one side of a cutoff to the other.

Illustrative timing check only: rerun against your own bills of lading, current transit data, and any confirmed cutoff before relying on it.

Blended transpacific transit time from China to the U.S. West Coast was running 36.2 days for the week ending July 6, up from 35.2 days the week before, per the Flexport Ocean Timeliness Indicator. A one-day swing week to week comes purely from lane congestion, before any tariff deadline enters the picture.

The spread across timing measures is wider still. A dedicated fast service such as Matson’s CLX (Shanghai to Long Beach) can advertise transit as low as 11 days, while standard carrier port-to-port loops are often quoted closer to 16 to 20 days. Flexport’s blended Ocean Timeliness Indicator is broader: it measures from cargo-ready date at origin to departure from the destination ocean port and excludes premium services, which is why its China-to-U.S. West Coast figure can sit much higher. The point is not that these are identical metrics. It is that a booking’s quoted port-to-port transit is a poor proxy for whether a specific box clears a legal cutoff.

The worked example (hypothetical, illustrative calculation, not a sourced figure). A 40-ft container of furniture parts, roughly $150,000 declared value, books from Ningbo on a standard transpacific loop. The booking confirmation implies arrival comfortably inside a hypothetical exemption window. Price the voyage at the real blended 36.2-day transit instead of the quoted 18-to-20-day port-to-port figure, and the on-board date needed to make that cutoff slips by about two weeks. On a $150,000 entry, a hypothetical 12.5%-versus-0% rate delta would work out to roughly $18,750 of duty riding on which side of the line that box lands (a 10%-versus-12.5% delta is smaller but still four figures). Across a program of containers, the same two-week slippage becomes a six- or seven-figure swing.

Caveat, stated once and meant: the cutoff pair used to frame this example is illustrative only. As of this writing no such 2026 cutoff exists in the Federal Register or a CBP CSMS notice. Rerun the whole example against a confirmed date if and when one is published.

Shippers are already treating this as a timing problem rather than a paperwork problem. U.S. container imports were on track for an all-time monthly record in July 2026 as retailers front-loaded ahead of the Section 122 uncertainty, with August volume forecast to fall to 2.22 million TEU, down 4.5% year over year. That pull-forward is the market voting with its sailings: shippers are moving boxes early because the water’s calendar, not the compliance file’s, is the one that decides duty exposure.

The check, done manually

Until a 2026 cutoff is confirmed, the method is what matters. This is the takeaway: if a date does land, the shippers with the least exposure are the ones that can already map in-transit containers to loading dates, vessel events, and real ETAs. For each in-transit container you believe may qualify for a given tariff treatment, work these in order:

Pull the on-board bill of lading date for the final U.S.-bound vessel, not the booking date and not the feeder leg. This is the loading date the rule may test.
Confirm the box stayed on that hull. If it was transshipped onto a different mother vessel, the earlier loading date does not carry over.
Replace the quoted transit with a real ETA. Use current lane transit data, not the booking’s port-to-port promise, to project arrival and the entry-for-consumption date.
Compare both dates against the actual published cutoff pair (loading cutoff and arrival/entry cutoff), once one exists in the Federal Register or a CBP CSMS message. Do not run the check against a date pulled from a search summary: search-engine AI summaries have been observed confabulating the 2025 cutoff dates as 2026, though that pattern could not be independently verified.
Re-run any box near the line whenever the deadline moves. The “entered by” date has been amended mid-voyage before.

If you are running this manually across a live program of boxes, the slow part is not the arithmetic. It is getting a trustworthy loading date and a real ETA for every container at once, then re-checking when the lane slips or the deadline moves. If that is the workflow you are staring at, Ocean Visibility is where that container-level timing check lives.

The compliance team owns the classification and duty analysis, but the exposure often turns on a cutoff pair: loading date on a named hull, then entry or arrival timing against the published deadline. Check every on-the-water box against those dates before the cutoff lands, not after.

Leave a ReplyCancel reply

New Report: The Future of SCM, and Why Visibility Alone Is No Longer Enough

[TRADLINX Report] 2026 Shipping Market Outlook: Falling Rates, Rising Risks

Four Service Changes on the India–Middle East Map, and One That Can Flip Back