UFLPA is not a tariff: detentions, traceability files, and what the July 24 action actually is
The July 24, 2026 action is a Section 301 duty of 12.5% or 10%. UFLPA is a CBP import ban enforced by detention and answered with a traceability file to raw material. Moving origin changes the duty, not the exposure.
The July 24, 2026 action is a tariff: a Section 301 duty of 12.5% or 10%, paid at entry. UFLPA is not a tariff at all. It is an import prohibition that CBP enforces by detaining goods, and the only thing that releases a detained shipment is evidence about where its inputs came from.
The two get mixed up because USTR’s stated basis for the July 24 action involves forced labor, so both end up discussed under the same heading. They need different preparation. This post separates them, explains what a UFLPA detention involves, and lists what a traceability file has to contain. Where both fit in choosing an origin per part is covered in how to choose a sourcing origin per part.
What the July 24 action is
USTR’s Section 301 action took effect on July 24, 2026, covering 60 economies. As of September 26, 2026, it adds 12.5% on goods from China and most of the other economies covered, and 10% on the rest. FTA-qualifying goods are exempt, and so are all Section 232 goods, which pay their own 50% or 25% instead.1
It works like any other duty. It is a percentage of customs value, calculated per HTS code, and paid at entry. On the molded EPDM gasket we use as a standing example (HTS 4016.93.50, MFN 2.5%, List 3), China-origin duty is 40.0%: MFN 2.5%, plus the 25% List 3 rate, plus 12.5% from the July 24 action, confirmed per HTS code. The importer pays it and the goods are released.
The July 24 action changes what a part costs. It does not, by itself, stop a part from entering.
What UFLPA is
The Uyghur Forced Labor Prevention Act sets a rebuttable presumption. Goods mined, produced or manufactured wholly or in part in the Xinjiang Uyghur Autonomous Region, or by an entity on the UFLPA Entity List, are presumed to be made with forced labor and are barred from entry into the US.
There is no rate and nothing to pay. The presumption follows the inputs, so it applies to goods from any origin, China or elsewhere. CBP enforces it at the border, and the enforcement tool is detention.
| The July 24 Section 301 action | UFLPA | |
|---|---|---|
| What it is | A duty | An import prohibition with a rebuttable presumption |
| Who acts at the border | CBP collects it at entry | CBP detains goods it believes are in scope |
| What triggers it | Origin of the goods, per HTS code | Any input from the region or from an entity on the UFLPA Entity List |
| Applies to | China and most economies at 12.5%, the rest at 10% | Goods from any origin |
| Exempt | FTA-qualifying goods; Section 232 goods | Nothing by origin; the importer must show the goods are out of scope or rebut the presumption |
| How it is settled | Pay the duty | Produce documentary evidence |
| What it costs | A percentage of value | Time, storage, missed deliveries, and the goods if they are not admitted |
What a detention involves
When CBP detains a shipment under UFLPA, the goods stay at the port and the importer is notified. From there, CBP’s UFLPA guidance describes two routes.
The first is to show the goods are outside the law’s scope: that no input, at any tier, came from the region or from a listed entity. That is a documentary exercise, and it is the practical route for an ordinary supply chain. It works only if the file exists before the shipment leaves, because building it after a detention means asking sub-suppliers for records while the goods sit in storage.
The second is to seek an exception by rebutting the presumption. The law sets a high bar for that: clear and convincing evidence that the goods were not made with forced labor, full compliance with CBP’s guidance, and complete answers to CBP’s requests. It is a much heavier lift than showing the goods are out of scope.
If neither route succeeds, the goods are not admitted. The cost of a detention is rarely the shipment’s value alone. It is the line that stopped while the shipment waited.
What goes in the traceability file
The file follows each input back to its raw material, tier by tier, and backs every step with documents rather than assurances. A complete file holds:
- A bill of materials to raw material, listing every input and the material it is made from.
- A supplier map by tier: name and address for the final factory, its component suppliers, and their material suppliers, down to the raw material.
- Supplier declarations at each tier, stating where that supplier’s inputs came from.
- Purchase records that connect the tiers: purchase orders, invoices, payment records, packing lists and transport documents linking each tier’s inputs to the lot that was shipped.
- Production records tying input lots to finished lots.
- A dated screening record showing each named supplier, at every tier, was checked against the UFLPA Entity List.
Some inputs deserve the closest attention. CBP’s UFLPA guidance has identified high-priority sectors, among them cotton, polysilicon, aluminum and tomatoes. For a buyer of promotional products that means cotton totes and apparel. For an OEM it means aluminum castings and extrusions, and anything containing solar-grade polysilicon. For packaged food it means tomato products. A part made from one of those materials needs its trace taken all the way to the raw material, not stopped at the component supplier.
A different origin does not remove the exposure
Moving a part to an alternative origin changes its duty line. It does not change its UFLPA question, because the presumption looks at inputs, not at the address of the final factory.
Suppose a buyer moves a cotton tote from China to a 12.5% origin. If the fabric was woven from yarn spun from cotton grown in the region, the tote is in scope wherever it was sewn. An aluminum bracket machined at an FTA-qualifying origin from billet produced by a listed entity is in scope too. The reverse also holds. A factory in Zhejiang whose inputs trace cleanly, on paper, to sources outside the region and off the Entity List can supply with a defensible file.
The work overlaps with proving a rule of origin. Both start from the same bill of materials and the same input-by-input trace, so the file is built once and serves both. How that trace supports a 0% claim is in rules of origin, explained, and where it sits among the checks that pick a second origin is in China plus one in practice: the five checks.
In our program, the UFLPA file is a deliverable at the qualification stage, alongside the audit report and the signed NNN, at every origin. Supplier mapping starts in weeks 2–4, as set out on the process page, and the file is refreshed whenever a sub-supplier changes. It is one of the items in the compliance file described on the quality inspection page, and the FAQ covers the split of roles: you are the importer of record, and the agent prepares the document set and the compliance file.
What to do with this
- List your parts that contain cotton, polysilicon, aluminum or tomato inputs. Those are the first files to build, whatever the origin.
- Ask each final factory for its supplier map down to raw material, and screen every name against the UFLPA Entity List, with the date recorded.
- Build the traceability file and the rule-of-origin file from the same bill of materials, and update both when any supplier at any tier changes.
If the current factory has never been audited, that is the first thing a re-quote fixes. Send us the SKUs — ten business days, no fee, and the audit report is yours either way.
Footnotes
-
USTR’s stated basis for the 2026 Section 301 action was a finding on unenforced forced-labor import bans. That basis does not make it a forced-labor measure at the border. It is a duty, collected at entry, and it applies whatever a shipment’s UFLPA status. ↩