
If you import physical products, a shipment held at the border is no longer a rare surprise. It is a business risk you can plan for. In June 2026, U.S. Customs and Border Protection (CBP) published updated forced labor guidance for importers, and the message is clear: the companies that move fastest are the ones who already know their supply chain.
This guide walks non-technical founders through what UFLPA compliance asks of you, why documentation is where most importers struggle, and how purpose-built software can turn a scramble into a routine.
The Uyghur Forced Labor Prevention Act (UFLPA) creates a rebuttable presumption that goods made wholly or in part in China's Xinjiang region, or by certain listed entities, are made with forced labor and cannot enter the United States. "Rebuttable" is the important word. The goods can still be admitted, but only if the importer proves otherwise with clear and convincing evidence.
That puts the burden of proof on you, not on CBP. And proof means paperwork that traces your product back through every tier of its supply chain.
According to a Holland & Knight summary, CBP issued its Forced Labor Enforcement Operational Guidance for Importers on June 9, 2026. It replaces CBP's 2022 guidance, which covered only the UFLPA, with a single reference covering the UFLPA, Section 321A of CAATSA, and Withhold Release Orders and Findings under 19 U.S.C. § 1307.
Three practical takeaways stand out:
The same summary reports that, from fiscal year 2025 through April of fiscal year 2026, 17,651 shipments were detained under the UFLPA alone, with electronics, automotive and aerospace, and machinery among the largest categories by value. These are figures as reported by the law firm; check CBP's own publications for the latest numbers.
In our experience building traceability products, the legal framework is rarely the hardest part. The hard part is data:
None of these are legal problems. They are software problems, and software solves them well.
Every purchase order, bill of materials, invoice, and certificate is linked to the shipment it supports. When CBP asks a question, you answer from one source of truth instead of reconstructing history.
The system captures suppliers beyond tier one, flags gaps where origin is unknown, and prompts suppliers to supply missing data instead of leaving you to chase it.
Because documents are indexed and standardized as they come in, a submission-ready package takes hours rather than weeks. That matters when response windows are measured in days.
Rules can flag a new supplier, a changed origin, or a shipment of a high-priority product category for review before it ships, not after it is detained.
Off-the-shelf trade compliance platforms are a sensible start if your supply chain is simple. Custom software earns its keep when you have unusual products, many suppliers, or a need to connect compliance data to your existing ERP, inventory, or ecommerce systems. Many of our clients blend the two: a proven platform for the standard workflows, plus a lightweight custom layer for what makes their business different.
If you are weighing the options, start with a small question: if CBP detained one of your shipments tomorrow, how long would it take to assemble the proof? If the honest answer is "weeks," you have found your first project.
This article is general information, not legal advice. Work with qualified customs counsel on your specific situation.
Esipick is a boutique, purpose-driven software agency that has been helping founders build trustworthy digital products since 2013. We design brand protection and traceability systems, and our AI development practice can automate document intake and supplier risk scoring. If counterfeits are also part of your risk picture, see our overview of anti-counterfeiting software.
Curious what a right-sized traceability system would look like for your business? Book a free call with our team, or explore our AI venture at esipick.ai. You can also start from our home page.