The rate changed mid-voyage. Which rate applies to your shipment, and what can you still do about it?
US customs law keys duty rates to the time of entry, which for ocean shipments is typically when the goods arrive and entry is filed, not when the container left the factory. A rate increase announced while goods are mid-Pacific applies to those goods if it takes effect before entry. The purchase contract, the invoice date, and the shipment date are all irrelevant to the rate question, however unfair that feels.
This is why rate-change announcements create scrambles at ports. Importers with goods on the water do frantic math: can the vessel arrive and enter before the effective date? Sometimes the answer is yes, and the savings from a few days of acceleration dwarf the expediting cost. Sometimes the goods are three weeks out and the math is just grief. Knowing which situation you are in requires tracking both the regulatory calendar and your containers in one view.
Acceleration is the first lever. If the new rate takes effect on a known date, importers can sometimes expedite discharge, pre-file entry documentation, and arrange for immediate entry processing on arrival. This works best for importers with brokers on standby and clean paperwork; a documentation scramble at the port burns the very days you are trying to save.
Foreign trade zones offer the more structural answer. Goods admitted to an FTZ before a rate increase can, in many cases, enter US commerce later under the rate in effect at admission, effectively freezing the old rate. This does not help goods already on the water for the current change, but importers who route recurring shipments through FTZs buy themselves insurance against the next one. After the second surprise rate change, the FTZ math usually sells itself.
When rate changes come through Section 301 or similar actions, they often arrive with product exclusion processes. An exclusion granted for your specific HTS classification can retroactively remove the additional duty, sometimes with refunds back to the effective date. The catch is timing: exclusion windows open and close, and the application requires showing the product is not strategically important and cannot be sourced domestically.
Rate changes also sometimes include grandfather provisions or transition rules for goods already in transit, though these are the exception rather than the rule. Read the Federal Register notice itself, not the summary; the transition language, when it exists, hides in the details. And document everything about the shipment timeline now, because any future exclusion or protest will demand proof of when the goods moved.
The importers who handle this well treat rate volatility as a standing risk, not a series of surprises. That means a monitoring feed on tariff actions affecting their HTS codes, a pre-negotiated expediting arrangement with their broker and forwarder, and a standing analysis of which shipments would benefit from FTZ admission. When the announcement drops, they execute a plan instead of forming a committee.
Pricing needs the same treatment. Landed cost models should carry a tariff-volatility buffer, sized to the importer's exposure, so a mid-voyage rate change compresses margin instead of erasing it. And customer-facing promises should never assume a duty rate; quote DDP totals with the rate disclosed and a clause for regulatory changes. The ocean is long, and the tariff schedule is longer.
No, not as a favor. The rate in effect at entry applies by law. Relief comes through the mechanisms described here, exclusions, FTZ timing, transition provisions, not through discretion at the port.
It compresses the timeline, which usually helps: goods ordered after an announcement can often arrive before the effective date. But air freight costs far more than the duty savings in most cases, so run the numbers before expediting by air.
Map every in-transit shipment to its HTS codes and the entry dates, then cross-reference against pending tariff actions and their effective dates. This is exactly the monitoring workload that duty-watch tooling exists to automate.