After the WRO: A CBP Forced-Labor Detention Response Program

What is a CBP WRO response?

A CBP WRO response is the time-boxed admissibility workflow an importer runs after a shipment is detained or excluded under a Withhold Release Order or the UFLPA rebuttable presumption: assemble the supply-chain traceability and due-diligence package, decide whether to argue scope or rebut, and decide export versus destruction before the detention clock runs out. The forced labor detention either clears on clear and convincing evidence, or the goods leave U.S. commerce. GingerControl is a trade compliance AI platform whose research and monitoring layer (country-of-origin re-validation and Compliance Radar policy alerts) supports the evidence work beneath that response, while the admissibility argument and any CBP filing stay with the importer and its counsel.

How long do you have to respond to a forced labor detention?

Under the June 2026 CBP operational guidance, a UFLPA detention gives you 30 days from the notice to respond, with discretionary extensions capped at 90 calendar days total. Under the older WRO mechanism, 19 CFR 12.44 lets you export merchandise any time before seizure and gives 3 months from importation before the port director moves to exclusion or forfeiture.

The notice is already in your inbox. A container of your product, or a quarter's worth of containers, is sitting at the port under a forced labor detention, and the email tells you the merchandise has been detained pending an admissibility determination tied to a Withhold Release Order or the UFLPA rebuttable presumption. The clock that matters most is not the 30 days you think you have; it is the gap between the day the notice arrives and the day your team can produce a tier-by-tier traceability package that meets a clear and convincing evidence standard. For a compliance director or supply chain leader who owns thousands of SKUs across multiple sub-tier suppliers, that gap is where a detention becomes a write-off. GingerControl is a trade compliance AI platform that supports the country-of-origin re-validation and policy monitoring underneath a CBP WRO response, while the admissibility argument and any CBP filing stay with the importer and its counsel. Unlike a one-time supplier questionnaire, a response program assumes the detention is coming and keeps the evidence indexed before the notice lands.

Last updated: June 2026

Quotable insight: A forced labor detention is not won on the day the notice arrives; it is won or lost months earlier, by whether your traceability already exists. CBP measures your rebuttal against a clear and convincing standard, "highly probable," not "more likely than not." The detention clock does not pause while you email a Tier 3 smelter for records you never collected. The unit of readiness is the traced input, indexed before the port stops the box, not the supplier on your invoice.

This article is the enforcement-event companion to our UFLPA forced-labor due-diligence program guide, which covers the prevention side, how to design the program before anything is detained. Here the detention has already landed, and the question is operational: what do you do in the next 30 to 90 days, and how do you run that response as a standing capability rather than a one-time fire drill.

What actually happens when CBP detains your shipment

A forced labor stop is not a single event with a single deadline. It is a sequence, and each step has its own statute and its own clock. Understanding the sequence is the difference between spending your window on legal strategy and spending it on confusion about which rule applies.

The first distinction is detention versus exclusion. Per CBP's June 2026 operational guidance, CBP issues a detention when it has potential information that merchandise may connect to a prohibited source, and an exclusion when it has direct information that the goods were produced with prohibited inputs. CBP can exclude a shipment without first detaining it. The practical consequence: a detention notice is an invitation to submit evidence inside a window, while an exclusion has already decided against you and shifts the fight to a protest.

For a general detention, the timeline comes from 19 CFR 151.16:

Step	Deadline	Authority
CBP decides to release or detain	Within 5 business days of presentation for examination	19 CFR 151.16(b)
CBP issues the detention notice	Within 5 business days of the decision or failure to release	19 CFR 151.16(c)
Detention notice must state reason, length, tests, and how to accelerate	At issuance	19 CFR 151.16(c)
Final admissibility determination	Within 30 days of presentation for examination	19 CFR 151.16(d)
Failure to determine within 30 days	Treated as a decision to exclude under 19 USC 1514(a)(4)	19 CFR 151.16(e)

That deemed-exclusion provision is important and counterintuitive: if CBP goes silent past 30 days, the law treats the silence as an exclusion you can protest, not as a default in your favor. The clock running out does not return your goods; it converts your problem from a detention into an exclusion.

The forced-labor-specific timelines layer on top. For a UFLPA detention, the June 2026 CBP Forced Labor Enforcement Operational Guidance for Importers gives the importer 30 days from the detention notice to respond, with extensions that are discretionary and capped so the total response period does not exceed 90 calendar days from the notice. For a WRO under 19 U.S.C. 1307, the disposition rules in 19 CFR 12.44 let you export the merchandise "at any time prior to seizure," and provide that if no finding has issued and the goods have not been exported within 3 months after the date of importation, the port director checks whether the proof of admissibility required by 19 CFR 12.43 was timely submitted. If it was not, the port director excludes the goods, and for merchandise covered by a formal finding under 12.42(f), seizes them and commences forfeiture.

Bottom line: For a compliance director facing a forced labor detention, the first 48 hours are a triage problem, not a legal-brief problem: confirm whether you received a detention or an exclusion, identify whether the authority is UFLPA or a WRO, and pin the exact clock (30 days, the 90-day cap, or 3 months from importation). Build the legal argument second; get the deadline right first.

What goes in the admissibility package, and the two ways to argue it

Once the clock is pinned, the response forks into two arguments, and CBP names them. You either run an applicability review or an exception review, and they require fundamentally different evidence.

An applicability review argues that the UFLPA does not apply at all because the goods have no nexus to the Xinjiang Uyghur Autonomous Region (XUAR) or to an entity on the UFLPA Entity List. The evidence is supply-chain tracing from the raw material through to export, documentation proving the inputs never touched a prohibited source. An exception review concedes the nexus exists but argues the statutory exception is met: you must show by clear and convincing evidence that the merchandise was not produced wholly or in part by forced labor. CBP's UFLPA enforcement FAQ defines clear and convincing as "a higher standard of proof than a preponderance of the evidence" that "generally means that a claim or contention is highly probable." That is a deliberately demanding bar, and it is the part enterprise teams most often underestimate.

CBP's operational guidance frames the documentation in three categories. The admissibility package has to satisfy all three:

Evidence category	What it proves	Typical exhibits
Due diligence	The importer ran a real forced-labor risk program, not a paper policy	Risk assessments, supplier code of conduct, audit findings, remediation records
Supply chain tracing	Every input can be followed from raw material to finished good	Tier-by-tier transaction records, production records, origin certificates, shipping documents
Supply chain management measures	The program is enforced and ongoing	Contractual clauses, supplier engagement logs, training records, corrective-action history

The hard category is tracing. A listed entity rarely sells to you directly; it sells a raw input, polysilicon, cotton, aluminum, lithium, to a sub-tier processor several layers below your Tier 1 supplier. An admissibility package that proves your direct supplier is clean while leaving Tier 3 dark does not meet the standard, because the presumption reaches the raw-material tier and so must your tracing. GingerControl's role sits squarely in this row: country-of-origin re-validation that organizes the tier and origin data so counsel can see where the documentary chain holds and where it breaks, before the package is submitted. GingerControl does not make the admissibility determination or decide whether the evidence is legally sufficient; that is the importer's and counsel's call.

Export versus destruction: the decision behind the package

If the evidence will not get there in time, or at all, the detention becomes a disposition problem, and the choice is export versus destruction. The two paths are not symmetric.

Under the WRO regime, 19 CFR 12.44 permits export "at any time prior to seizure," which makes re-export the default escape valve as long as you act before CBP seizes the goods or they are deemed abandoned. Re-export preserves the merchandise value (you can sell it into a market that does not enforce 19 USC 1307) and avoids a forfeiture record. Destruction is the fallback when the goods cannot be moved, cannot lawfully be sold elsewhere, or when CBP has already issued a finding and moved toward seizure. Once the port director seizes merchandise covered by a 12.42(f) finding and commences forfeiture under part 162, the export window is gone.

"Merchandise detained pursuant to § 12.42(e) may be exported at any time prior to seizure pursuant to paragraph (b) of this section, or before it is deemed to have been abandoned as provided in this section, whichever occurs first." (19 CFR 12.44(a))

The decision is therefore a sequencing problem, not just a financial one. A team that spends all 30 or 90 days on a rebuttal it cannot win has often also let the export window narrow, because export is cleanest before seizure. A standing response program decides early, in parallel, whether the realistic outcome is a winnable rebuttal or a managed export, and it protects the export option while the rebuttal is still being attempted.

Why a one-time response fails and a standing program does not

Most companies treat the first forced labor detention as a unique crisis. It is not. It is the first instance of a recurring event class. The FLETF keeps expanding the UFLPA Entity List, which reached 144 entities after the January 2025 additions, and keeps adding high-priority sectors, so the population of SKUs that can be stopped only grows. CBP's enforcement volume confirms the pattern: the agency reviewed more than 18,000 shipments worth roughly $3.81 billion for UFLPA admissibility cumulatively through early 2026, and in fiscal year 2025 stopped about 7,325 shipments, of which only roughly 6.5% were ultimately released into U.S. commerce.

That release rate is the number that should reframe the problem. When roughly 93 to 94 percent of stopped shipments do not clear, the detention is not an anomaly to be argued away once; it is a near-certain outcome for exposed product lines that has to be managed as a process. A standing program changes three things relative to a reactive scramble:

Response element	One-time scramble	Standing response program
Clock awareness	Deadline discovered after reading three regulations	Authority and clock pinned in the first 48 hours from a runbook
Traceability evidence	Requested from sub-tier suppliers under deadline pressure	Pre-collected, indexed, and re-validated before any notice
Applicability vs exception decision	Debated for weeks before counsel can advise	Decided from an existing supplier map in days
Export vs destruction	Defaulted to destruction after the export window closed	Decided in parallel while the export option is protected
Next detention	Starts over from zero	Same runbook, faster each time

Bottom line: For a compliance director who owns forced-labor risk across thousands of SKUs and multiple sub-tiers, the difference between a scramble and a program is whether the detention clock is spent on legal review or on discovery. With a roughly 6.5% release rate on stopped shipments, the second, third, and fourth detentions are coming, and the program is what makes each one faster instead of starting from zero.

GingerControl supports the infrastructure layer of that program. The table below maps each part of a standing response to the GingerControl offering that supports it, and to what stays with the importer and its counsel.

GingerControl offering	What it supports in a detention response	What stays with you and counsel
GingerControl Compliance Radar	Monitors CBP and federal forced-labor policy across its sources and personalizes alerts to your own product records, so a new UFLPA designation or high-priority sector surfaces against the SKUs it touches	Deciding whether a flagged SKU is actually in scope
GingerControl AI Integration	Builds country-of-origin checks into the workflow so origin and tier data are organized before a notice lands	The admissibility argument and its legal sufficiency
GingerControl Trade Advisory	Supports CBP audit response and country-of-origin re-validation behind the package	The detention filing, the export-versus-destruction decision, and any protest

Compliance Radar monitors CBP and federal forced-labor policy across its sources, including the Federal Register and CBP Rulings, and personalizes alerts to a company's own product records, so a new UFLPA designation or high-priority sector surfaces against the SKUs it actually touches rather than as a raw feed. GingerControl's AI Integration service builds country-of-origin checks into the workflow, and Trade Advisory supports CBP audit response and country-of-origin re-validation. The admissibility argument, the export-versus-destruction decision, and any CBP filing remain with the importer and its counsel.

GingerControl is a trade compliance AI platform that helps importers, exporters, and customs brokers classify products, simulate tariff costs, track policy changes, and re-validate country of origin. On forced labor specifically, it is research and monitoring infrastructure, not a substitute for the legal judgments a detention response requires. That boundary follows the same logic CBP applied in rulings such as HQ H290535 and HQ H350722, which reserve customs-business determinations for licensed professionals; GingerControl supports the importer or its licensed broker and counsel, and does not file detention packages, prepare protests, or decide admissibility.

What to do in the first week of a forced labor detention

The first week sets up everything that follows. A defensible sequence:

Confirm the instrument and the clock. Is it a detention or an exclusion? UFLPA presumption or a WRO under 19 USC 1307? Pin the exact deadline (30 days, 90-day cap, or 3 months from importation) and calendar it with counsel.
Pull the existing traceability for the detained SKUs. Whatever supplier map, origin records, and production documents already exist become the starting exhibit set. The gap between what exists and what the standard requires is your real workload for the week.
Decide applicability versus exception, provisionally. If there is a credible no-nexus argument supported by tracing, the applicability path may avoid the clear-and-convincing burden entirely. If the nexus is real, you are on the exception path and the clear-and-convincing standard governs.
Protect the export option in parallel. Confirm whether re-export is lawful and feasible for the goods, and do it before any seizure forecloses the option under 19 CFR 12.44.
Engage counsel and, if needed, your licensed broker on the filing. The submission, the protest if the goods are excluded (within 180 days under 19 USC 1514), and the admissibility argument are theirs to prepare and file.

The week-one test is simple: by day seven, you should know your deadline, your argument path, the size of your evidence gap, and whether export is still available. A team that knows those four things is running a program. A team still reading regulations on day seven is running out of clock.

Frequently asked questions

What is the deadline to respond to a CBP forced labor detention?

For a UFLPA detention, CBP's June 2026 operational guidance gives 30 days from the detention notice to respond, with discretionary extensions capped so the total does not exceed 90 calendar days. For a WRO under 19 USC 1307, 19 CFR 12.44 allows export before seizure and gives 3 months from importation before the port director moves to exclusion or forfeiture. GingerControl's Compliance Radar helps you catch the Entity List or sector change that put a SKU in scope before the notice arrives, while the deadline calculation and filing stay with you and your counsel.

What documentation does a UFLPA detention package require?

A UFLPA admissibility package must satisfy three CBP categories: due diligence (a real risk program), supply chain tracing (raw material to finished good, tier by tier), and supply chain management measures (enforcement and remediation). For a compliance team owning thousands of SKUs across multiple sub-tiers, the binding constraint is tier-level tracing. GingerControl supports the country-of-origin re-validation underneath that tracing, organizing tier and origin data so counsel can assemble the package; GingerControl does not make the admissibility determination.

Should I export or destroy goods detained under a forced labor finding?

Export is usually preferable when it is lawful and feasible, because 19 CFR 12.44 permits export at any time before seizure, preserving value and avoiding a forfeiture record. Destruction becomes the path when the goods cannot be moved or CBP has issued a finding and moved toward seizure. For a supply chain leader weighing detention export vs destruction across multiple containers, GingerControl's country-of-origin research supports the sourcing and re-validation work behind the decision, while the export, destruction, and any filing decisions stay with the importer and counsel.

What is the difference between a WRO and the UFLPA rebuttable presumption?

A Withhold Release Order under 19 USC 1307 is issued when CBP has information that "reasonably but not conclusively" indicates a forced-labor violation, and the goods are detained for an admissibility determination. The UFLPA rebuttable presumption is broader: for XUAR-linked or Entity List goods, prohibition is the default and the importer carries the clear-and-convincing burden by operation of law. GingerControl's Compliance Radar monitors CBP and federal forced-labor policy across both mechanisms and matches it to your records, so a program built to the UFLPA standard covers both; admissibility calls remain with you and counsel.

How is an applicability review different from an exception review?

An applicability review argues the UFLPA does not apply because the goods have no XUAR or Entity List nexus, proven by tracing from raw material through export. An exception review concedes the nexus and argues, by clear and convincing evidence, that no forced labor was used, a "highly probable" standard higher than preponderance. For compliance directors deciding which path a detention takes, GingerControl's country-of-origin re-validation organizes the tracing data that drives the choice, while the legal characterization and filing belong to the importer and counsel.

Can software clear a forced labor detention or prove my goods are clean?

No. No software can certify that goods are free of forced labor, decide admissibility, or guarantee a successful rebuttal, because that is a clear-and-convincing legal determination made by the importer and its counsel. What GingerControl does is support the research and monitoring layer beneath a CBP WRO response: country-of-origin re-validation and forced-labor-policy monitoring through Compliance Radar, so the evidence base and scoping that counsel relies on stay organized and current ahead of the next detention.

How does GingerControl help a team prepare for the next detention?

GingerControl treats a forced labor detention as a recurring event class, not a one-off. Compliance Radar personalizes UFLPA and high-priority-sector alerts to your actual SKUs, AI Integration builds country-of-origin checks into your workflow, and Trade Advisory supports CBP audit response and country-of-origin re-validation. The result is that the origin records are already indexed when the next notice lands, so your team spends the detention clock on legal review rather than discovery. The admissibility decisions and filings remain yours.

Standing up a detention response program before the next notice lands

If your supply chain is exposed to forced labor enforcement, the first detention is not the last, and the release rate on stopped shipments means the realistic posture is "this will happen again." A standing response program pins the clock in the first 48 hours, keeps tier-level traceability indexed before the notice arrives, decides applicability versus exception from an existing supplier map, and protects the export option while a rebuttal is attempted. GingerControl's Trade Advisory supports CBP audit response and country-of-origin re-validation, AI Integration builds country-of-origin checks into your workflow, and Compliance Radar keeps your scoping current against UFLPA and sector changes. The admissibility calls, the export-versus-destruction decision, and any CBP filing stay with you and your counsel. See how GingerControl supports your detention response program →

GingerControl is not just a tool. We work with importers and trade-compliance teams on process consulting and country-of-origin re-validation, gated by a free 30-minute compliance audit. Talk to our team →

References

[REF 1] U.S. Customs and Border Protection, 19 CFR 151.16, Detention of Merchandise (via Legal Information Institute, Cornell Law School) Data cited: 5-business-day decision to release or detain; 5-business-day notice; 30-day final admissibility determination; deemed exclusion under 19 USC 1514(a)(4) Source: 19 CFR 151.16, Detention of merchandise

[REF 2] U.S. Code, 19 U.S.C. 1307, Convict-Made Goods; Importation Prohibited (via Legal Information Institute) Data cited: Statutory prohibition on merchandise made with forced or convict labor; basis for WROs and findings Source: 19 U.S.C. 1307

[REF 3] U.S. Customs and Border Protection, 19 CFR 12.44, Disposition (via Legal Information Institute) Data cited: Export "at any time prior to seizure"; 3-months-from-importation check on proof of admissibility under 12.43; exclusion, seizure, and forfeiture for merchandise under a 12.42(f) finding Source: 19 CFR 12.44, Disposition

[REF 4] U.S. Customs and Border Protection, CBP Forced Labor Enforcement Operational Guidance for Importers (June 9, 2026) Data cited: Detention vs exclusion distinction; 30-day UFLPA response with discretionary extensions capped at 90 calendar days; applicability review vs exception review; three documentation categories Source: CBP Forced Labor Enforcement Operational Guidance for Importers

[REF 5] U.S. Customs and Border Protection, FAQs: Uyghur Forced Labor Prevention Act (UFLPA) Enforcement Data cited: "Clear and convincing evidence" defined as a higher standard than preponderance, meaning a claim is "highly probable"; importer burden to overcome the rebuttable presumption Source: CBP, FAQs: UFLPA Enforcement

[REF 6] U.S. Customs and Border Protection, Uyghur Forced Labor Prevention Act Statistics Data cited: 18,000+ shipments worth roughly $3.81 billion reviewed cumulatively through early 2026; FY2025 ~7,325 shipments stopped with roughly 6.5% released Source: CBP, UFLPA Statistics

[REF 7] U.S. Department of Homeland Security, UFLPA Entity List Data cited: UFLPA Entity List of 144 entities following the January 2025 additions Source: DHS, UFLPA Entity List

[REF 8] U.S. Code, 19 U.S.C. 1514, Protest Against Decisions of Customs Service (via Legal Information Institute) Data cited: 180-day window to file a protest of an exclusion decision Source: 19 U.S.C. 1514