US CBP Launches Digital Certificate of Origin System

On July 10, 2026, U.S. Customs and Border Protection (CBP) launched a pilot of the “Digital Certificate of Origin” (DCO), a change that moves origin declarations one step further from traditional paper certificates to a real-time, data-connected layer. For independent-site businesses serving the U.S. market with B2B or B2C operations, order information, product HS codes, and origin declarations must be integrated into the CBP system via API, affecting not only customs clearance but also supply chain collaboration, delivery arrangements, and overseas procurement counterparties’ assessment of supplier compliance stability.

What rules have been explicitly released in this pilot?

The confirmed information shows that, effective July 10, 2026, CBP officially launched the DCO pilot. The pilot targets all B2B/B2C independent-site businesses exporting to the United States and requires them to transmit order data, product HS codes, origin declarations, and other core data to the CBP system in real time via API.

According to the provided summary, businesses that have not completed integration will face customs clearance delays and additional manual review. The summary also makes it clear that this mechanism will directly affect overseas buyers’ assessment of Chinese suppliers’ delivery certainty and compliance reliability.

The impact is now expanding from customs clearance to trade and fulfillment

Independent-site exporters directly serving the U.S. market

These businesses are the most directly affected, because the rules now clearly apply to their data submission methods. The impact is mainly reflected in order circulation, product classification, origin declaration preparation, and consistency of data related to customs clearance. In practical terms, this means companies need to convert information that may previously have been scattered across e-commerce systems, ERP, and customs materials into compliant data that can be transmitted in real time and remain consistent across systems.

Manufacturing and supply-chain support segments

For manufacturing companies undertaking export orders and their supporting suppliers, the impact may not be reflected directly in API access to CBP, but it will appear in the front-end customer’s data-matching requirements. From an operational perspective, once origin declarations and HS codes enter a real-time transmission scenario, the accuracy of basic data, product classification basis, and shipping information provided by the manufacturing side will more directly affect exporters’ declaration efficiency and delivery rhythm.

Overseas procurement and channel partners

As the summary has pointed out, this mechanism will affect overseas buyers’ assessment of Chinese suppliers’ delivery certainty and compliance reliability. For buyers and channel partners, the focus may not only be on whether goods can be shipped, but also on whether suppliers have the capability to complete data alignment as required, reduce manual review risks, and maintain delivery predictability. From an industry perspective, the rule change is moving “whether orders can be fulfilled smoothly” and “whether compliant data connectivity capabilities exist” into a closer position.

Supply chain service and compliance support segments

Supply chain service providers, customs coordination service firms, and compliance support teams related to export fulfillment may also be affected. The reason is that once companies need to submit core data in real time via API, the workflows around certificate verification, information consistency checks, exception handling, and review coordination may all need adjustment. What is currently more worth attention is whether such support links can keep up with enterprises’ requirements for real-time, accurate, and traceable data flows.

What is now more urgent is a practical shift

First confirm whether the data chain is complete

From an operational perspective, what companies need to focus on first is not an abstract policy interpretation, but whether key fields such as orders, HS codes, and origin declarations can form a complete chain in internal systems. If this information is fragmented and the sources are inconsistent, then even if interface capabilities are in place later, gaps may still occur during execution between declaration and delivery.

Put origin declarations and product classification under the same review lens

In practical terms, origin declarations and HS codes have both been included among the core data that must be transmitted in real time. What companies need to pay attention to is whether these two types of information remain consistent during internal preparation, review, and external submission. Since the input text does not provide a more detailed execution path, the current stage is more suitable for understanding this as a key review item rather than a mature process that has already formed a unified industry handling standard.

Reassess delivery commitments and customs clearance expectations

The confirmed facts show that businesses not connected to the system will face customs clearance delays and additional manual review. Based on this, companies need to be more cautious in managing uncertainty when making commitments to U.S. orders, scheduling deliveries, and communicating with customers. From an operational perspective, this change may first be reflected in fulfillment expectation management rather than immediately becoming a homogenized execution result for all companies.

Continue tracking subsequent execution paths

Because the current known content mainly focuses on pilot launch, integration requirements, and consequences of non-integration, companies still need to watch for more specific official statements, execution details, or supporting requirements. This is especially true for application methods under different business models, key product categories, and actual declaration processes, which are still areas that need continuous verification at this stage.

This looks more like a signal of execution-level advancement

From an observational standpoint, this piece of information is better understood as a change in the way rules are implemented, rather than simply as the addition of one more material requirement. The core issue is not only “whether origin declarations need to be provided,” but “how origin declarations enter the regulatory process in a systematized, real-time data format.” From an industry perspective, this means compliance capabilities are moving from document preparation capability toward data integration capability and fulfillment transparency.

At the same time, this change is still in a pilot context for now, and the industry still needs to continue observing the follow-up landing pace, execution path, and market feedback. In other words, it is already a clear execution signal, but given the differing impacts across company types and business scenarios, it is still not appropriate to draw a definitive conclusion at this stage.

For the industry, the focus is now no longer just “whether goods are shipped”

Taken together with the information already known, this event reflects that the U.S. import process has placed higher data-integration requirements on origin-related information. For independent-site exporters and their upstream and downstream partners, the impact will be seen in multiple links such as customs clearance efficiency, data consistency, buyer trust, and delivery predictability.

What is more appropriate to understand is that this is not a message staying only at the channel level, but a rules dynamic that has already reached the execution entry point; however, whether it will further evolve into broader and more refined industry requirements still needs to be continuously observed in combination with subsequent details, actual execution, and market feedback.

Source basis and follow-up verification directions

This article was generated based on the user-provided news title, event time, and event summary. Information sources usually associated with such events include announcements from regulatory agencies, releases by customs or trade authorities, industry association information, standards or rule documents, and reports from authoritative media.

It should be noted that the input content did not provide a specific official source link, so related details still need ongoing verification. Subsequent content worth continued attention includes: whether policy details are further clarified, whether execution paths are refined, whether corresponding changes appear in tender or procurement documents, how industry feedback evolves, and whether actual enterprise integration and fulfillment conditions produce new execution signals.