CBP's UFLPA Dashboard Counts Import Lines, Not Detentions
CBP counts affected import lines and combines several outcomes. Importers need consistent units, case histories and denominators before treating dashboard movements as a change in enforcement risk.
Primary lensCustoms enforcement
Sub-topicUFLPA enforcement
Evidence base7 records used
Use caseCustoms exposure review
DHS's October 29 addition of three companies to the Uyghur Forced Labor Prevention Act Entity List gives importers a reason to update supplier screening. It does not tell them how likely their next entry is to be stopped. That assessment requires comparable counts and a denominator of imports exposed to review.
CBP has also been directing users back to its enforcement data. Its October 21 webinar announcement advertised training on the updated UFLPA dashboard for October 28. The dashboard is useful for examining the composition of recorded enforcement activity. Reading it as a direct measure of detention risk, however, skips three questions. What is being counted, which outcomes are combined, and what population is missing from the denominator?
For an importer deciding whether to change sourcing or add inventory, those questions come before the trend line.
One entry can contribute several counts
CBP's January 28 revision changed the unit behind its shipment count. The previous dashboard counted affected goods together under one cargo release entry, or one bill where no entry was present or required. The revised dashboard counts individual import transactions within an entry.
The guide's example makes the difference concrete. An entry has five lines, and three are subject to UFLPA enforcement. The earlier dashboard counted one shipment. The revised dashboard counts three. CBP says the change altered the count while leaving the total value of stopped goods unchanged.
An importer cannot append those three observations to a historical series that still treats the same event as one. Nor can it divide an affected-line count by a denominator of containers or entries and call the result a detention rate.
Historical comparison remains possible within the revised series when the unit, filters and period are consistent. The problem is mixing old and revised extracts. A retrospective increase produced by the counting change is not evidence that CBP stopped additional cargo.
Value offers a useful second view, but it measures financial exposure. A small number of expensive goods can dominate it. Count and value answer different operating questions.
Dashboard outcomes combine different case histories
CBP defines a stopped shipment as one flagged by its automated systems for a potential UFLPA violation, with cargo release halted for further review. The review can involve electronic data, documents or physical inspection. Its data dictionary expressly says that not every stop resulted in physical detention or examination.
The same dictionary groups excluded, exported and destroyed goods under Denied. These goods did not enter U.S. commerce, but the category does not separate a formal exclusion from the other dispositions. Pending includes both cases awaiting importer action and cases awaiting CBP review or decision. Released records admission into U.S. commerce.
These distinctions affect the conclusions a compliance team can draw. A higher Denied share cannot, by itself, establish a higher formal exclusion rate. A large Pending balance does not show how much delay belongs to CBP and how much belongs to an importer still assembling evidence. A Released outcome does not identify which argument or document secured admission.
Comparisons also need a common observation date. An unresolved case can later move into an outcome category, changing the historical mix without a new stop. Teams comparing recent cases with older ones should account for the extra time older cases have had to reach a decision.
Congress asked for a broader record
The distinction was visible in the September 3 congressional request for a DHS enforcement briefing. Lawmakers asked for detained, released, excluded and seized shipments under both UFLPA and Section 307, with trends, sector breakdowns and countries of shipment.
That is not a description of the public dashboard. CBP's published scope covers UFLPA and excludes Withhold Release Orders, Findings and CAATSA actions. Its geographic filter is country of origin. That is a different field from the country from which goods were shipped. Its displayed outcome categories do not provide a separate seizure series.
Whether comparing a congressional briefing, a customs report or an internal case register, the analyst has to reconcile those differences first. A broader enforcement total cannot be treated as an update to a UFLPA-only series. A transport route cannot silently replace declared origin. A change in category coverage can otherwise look like a change in enforcement intensity.
Build the comparison around the importer’s own entries
The dashboard's stopped population does not supply all the unstopped imports needed to estimate an importer's probability of intervention. A country's share of recorded stops describes the distribution of those stops. It does not reveal the share of that country's imports that CBP stopped.
An importer can build a more useful denominator from its own entry data. The record should retain the entry number and affected line, product classification, declared origin, supplier and producer identities, value, stop date and subsequent outcome dates. Formal detention, exclusion, export, destruction and seizure should remain separate fields where they apply.
Operational rates can then answer a defined question, such as the share of comparable imported lines stopped during a specified period. Review times should distinguish time spent preparing importer submissions from time awaiting CBP action. Those are internal measures, with limits set by the company's own trade and case history. They are not national probabilities derived from the dashboard.
Producer tracing remains essential when the entity list changes. Traverse's analysis of upstream screening explains why the role of a listed producer matters to the evidence file. The measurement task adds the affected entry lines and their case history to that supplier record.
Preserve the extract before changing the control
CBP's current methodology note says the dashboard uses live system data and can change with corrections, system updates, definitions and additional information. The 2026 version replaces the earlier dashboard, whose data will no longer be updated.
Each compliance review should therefore preserve its extraction date, fiscal period, selected filters, counting unit and treatment of unresolved cases. If a later extract changes an earlier period, first determine whether the difference comes from new cases, later outcomes or a data revision.
DHS's October 29 UFLPA Entity List update calls for a supplier and product check now. A change in a dashboard total calls for a measurement check before it supports a new sourcing restriction, inventory buffer or enforcement forecast.
Daily Trade Brief
Get the next one in your inbox.
New U.S. trade actions and the analysis that changes an import, customs, or counsel file, on weekday mornings after you confirm your address.
From reading to review
Run the numbers on your lane.
The duty calculator runs the current stack for any HTS code and origin. A free account opens full tool output, AD/CVD detail, Chapter 98 processing, and available exports.