U.S. Customs trial point digital certificate of origin

On July 9, 2026, U.S. Customs and Border Protection (CBP) launched a “Digital Certificate of Origin Pilot” at the Port of Los Angeles and Port of New York, connecting independent site export data directly to the customs system as a practical requirement for some businesses to enter a more efficient customs clearance process. For Chinese export companies targeting the U.S. market, this change is not merely a format adjustment for documents; it involves moving order-level certificates of origin, HS codes, and component traceability data upstream into the customs clearance process. Textile, electronics, and furniture-related sellers and their supply chain service providers will all need to re-examine data preparation, system integration, and delivery arrangements.

What requirements have been clearly defined in the pilot arrangement

Confirmed information shows that on July 9, 2026, CBP announced the launch of the “Digital Certificate of Origin Pilot” at the Port of Los Angeles and Port of New York. Chinese export companies participating in the pilot and their independent sites will need to connect to the CBP system via API and synchronize order-level certificates of origin, HS codes, and component traceability data in real time.

The first batch of pilot coverage includes textiles, electronics, and furniture, with rollout expected to expand to major ports across the Americas in the third quarter of 2026. The disclosed implementation results point to two things: first, after integration, customs clearance time will be significantly shortened; second, the inspection rate for companies that have not yet integrated will increase by 300%.

From orders to customs clearance, the impact is not limited to the declaration stage

Independent site export companies are first to face data connectivity requirements

For export companies that sell directly to the U.S., the impact of this change is the most immediate. The reason is that the pilot does not simply stop at paper certificates of origin; it requires companies to synchronize order-level information with CBP in real time via API. The business impact is mainly reflected in order creation, product classification, retention of certificates of origin, and data verification before shipment. What companies need to pay attention to is whether their independent sites have the ability to output structured data to external regulatory systems, and whether origin, HS codes, and component information remain consistent across different stages.

Manufacturing and supply chain links will bear more detailed traceability pressure

Textiles, electronics, and furniture are among the first covered categories, which means that relevant manufacturers and upstream suppliers may feel requirement changes driven by increased data transparency earlier. From the analysis, once order-level component traceability data becomes customs-required information, production and procurement teams will need to provide materials, parts, or product information that can be matched to specific orders more consistently. The impact is mainly reflected in inventory preparation, batch matching, and pre-shipment data consolidation. Companies need to pay attention to the completeness of supplier-provided information, as well as whether internal data can support rapid verification and submission.

The role of supply chain service providers will shift from filing execution to data collaboration

For customs brokers, logistics providers, and other supply chain service companies, the signal released by this pilot is that customs clearance efficiency and inspection risk will depend more on front-end data quality, rather than traditional document submission alone. Observations suggest that service providers will need to pay more attention to the alignment between customer order data, HS codes, origin statements, and logistics arrangements. If a customer has not yet completed system integration or data standardization, delivery cadence, port selection, and abnormal handling may all be affected.

What should be prepared at this stage

First verify whether order-level data can be output stably

What companies should pay more attention to at present is whether order-level certificates of origin, HS codes, and component traceability data have already formed a data structure in the internal system that can be called, verified, and continuously updated. If this information is still scattered across manual spreadsheets, supplier emails, or multiple systems, the difficulty of subsequent integration and real-time synchronization will increase significantly.

Move compliance review upstream to before shipment

From the analysis, within pilot-covered categories, the practice of relying on post-shipment supplementary explanations or manual verification will likely struggle to meet efficiency requirements going forward. Companies should focus on the consistency of pre-shipment data, including whether origin statements match product information, whether HS codes are consistent with the declaration route, and whether component traceability data can correspond to specific orders.

Pay attention to the port scope and category expansion pace

The confirmed information indicates that the pilot is expected to expand to major ports across the Americas in the third quarter of 2026. Based on this, companies with substantial business volume in the Americas need to keep tracking whether the port coverage, applicable categories, and execution routes become clearer. For businesses not yet included in the pilot, they should also assess the impact on delivery arrangements and internal processes when later switching.

Be aware of the chain reaction of inspection risk on delivery timelines

The increase in the inspection rate for companies not connected by 300% has already sent a clear signal, but the actual impact on different companies still needs to be judged in combination with subsequent execution. At the current stage, companies should understand it more as a warning of rising risk, and focus on how changes in inspection probability may create chain reactions in delivery commitments, inventory arrangements, and customer communication.

This looks more like an execution signal than just a technical test

From an industry perspective, this information is better understood as customs supervision officially incorporating “digital filing capability” into actual admission conditions, especially for independent site export models, where system connectivity and real-time data synchronization are shifting from efficiency tools to compliance requirements. Observationally, this pilot already has a clear execution scenario, covered categories, and port scope, so it cannot be viewed merely as a long-term direction.

At the same time, there are still aspects of this change that require continued observation, including the subsequent rollout pace, execution routes at different ports, the actual operational requirements after company integration, and the specific performance of inspection rate changes at the business level. The more stable approach at this stage is to view it as a supervision signal that has already landed, while continuing to track details and execution feedback.

For the industry, the change has already begun to move forward

Overall, the core change released by the launch of the U.S. Customs “Digital Certificate of Origin Pilot” is that origin, classification, and component traceability information is moving from the traditional single-certificate level to the order-level real-time transmission level. For export chains related to textiles, electronics, and furniture, the impact will not be limited to customs declaration; it will extend to procurement, manufacturing, data retention, system integration, and delivery management.

At present, it is more appropriate to understand this information as a rule-change signal that has already entered the execution stage, rather than as a purely policy discussion. Whether it will further evolve into a broader customs threshold still needs to be observed in combination with the subsequent rollout scope, route refinement, and industry feedback.

Basis of this article and directions for follow-up verification

This article was generated based on the information title, event time, and event summary provided by the user, and the information used is limited to this input. For such events, it is usually still necessary to cross-check against official announcements, releases from regulatory bodies, customs or trade authorities, industry association information, standard organization documents, and reports from authoritative media.

This input does not provide a specific official source link, so the relevant statement still needs to be cross-confirmed with subsequently published public information. The following items still require close observation: whether policy details become clearer, whether execution routes are consistent across ports, the integration progress of companies in relevant categories, industry feedback, and the actual implementation situation of enterprises.