On June 23, 2026, a new compliance issue entered the workflow for cross-border digital services tied to the US market. After a June 22 announcement, US Customs and Border Protection (CBP) began a pilot at the ports of Los Angeles and New York covering origin declarations for digital service exports, with Chinese SaaS website-building providers serving US clients now required to submit a Digital Service Origin Self-Declaration Form (Form DS-ORIGIN). For SaaS vendors, US distributors, procurement teams, and contract managers, the significance lies less in the form itself and more in the fact that code development location, server deployment location, and the country of origin for AI model training data are being brought into the transaction process.

What the pilot requirement currently confirms

According to the information provided, CBP announced on June 22, 2026 that it was launching an origin declaration pilot for digital service exports effective immediately at the ports of Los Angeles and New York. The pilot applies when Chinese SaaS website-building service providers, including MaiKaipu, provide services to US customers. In those cases, the service process must be accompanied by the submission of Form DS-ORIGIN.

The declaration form is described as requiring three specific disclosures: where the core code was developed, where the servers are deployed, and the country from which AI model training data originates. The provided information also confirms that this development is expected to affect cooperation workflows and contract clause design between US distributors and Chinese SaaS service providers.

Where the operational pressure is likely to appear

For Chinese SaaS website-building providers, documentation becomes part of delivery

From an industry perspective, the immediate impact for service providers is that service delivery to US clients may no longer be handled only as a technical or commercial matter. The required declaration touches product development, infrastructure deployment, and AI-related data sourcing, which means internal teams may need to align around information that was previously managed separately. What deserves closer attention is whether providers can consistently describe these elements in a way that supports customer onboarding and ongoing account delivery.

For US distributors, the contracting process may become more detailed

Analysis shows that US distribution partners may feel the impact most clearly in pre-sales review, vendor onboarding, and contract drafting. If a declaration must accompany service provision, distributors are likely to focus more closely on what suppliers can certify, how that certification is worded, and what responsibilities sit with each party if submitted information later needs clarification. The practical issue is not only compliance filing, but also how representation, disclosure, and liability language are framed in commercial agreements.

For buyers and procurement teams, supplier transparency becomes a near-term checkpoint

Observably, procurement and vendor management teams may need to ask more specific questions before approving service arrangements involving Chinese SaaS providers. Because the required items include code origin, server location, and AI training data source country, the review process may move beyond pricing and functionality into traceability of service components. The change to watch is whether this creates longer review cycles or additional documentation requests during vendor selection and renewal.

What companies should watch in the next stage

Monitor whether the pilot language stays narrow or expands

Analysis shows that the current confirmed fact is a pilot beginning at Los Angeles and New York. What deserves closer attention is whether subsequent official wording keeps the scope limited to the currently described scenario or broadens the operational reach. Companies involved in US-facing SaaS delivery should therefore track any updates in official descriptions of covered services, filing expectations, and implementation language.

Prepare internal records around the three declared elements

For providers and their commercial teams, the most practical near-term focus is document readiness. The three disclosed items named in the input information are specific, and that means teams may need a workable internal process for collecting and validating statements about core code development location, server deployment location, and AI model training data source country before customer delivery milestones are reached.

Review contract language and customer communication flows

Because the provided summary explicitly notes an effect on cooperation processes and contract clause design, legal, sales, and account teams should pay close attention to how declarations are referenced in order forms, service agreements, onboarding checklists, and distributor communications. It is more appropriate to understand this as a workflow issue as much as a policy issue, especially where multiple parties share responsibility for service fulfillment.

Separate confirmed rules from evolving practice

Observably, there is a difference between a pilot requirement being announced and the market settling on a standard operating response. Companies should avoid assuming broader conclusions than the current information supports. The near-term task is to distinguish what is already required in the described pilot from what may still depend on later clarification, especially in customer-facing commitments and internal compliance procedures.

Why this reads as a policy signal, not yet a settled endpoint

Analysis shows that this development is important because it brings origin-style disclosure logic into digital service transactions, at least within the pilot described. That does not by itself confirm a wider or permanent framework beyond the information provided. Still, the inclusion of code location, server location, and AI training data source country suggests that digital service trade is being examined through a more detailed provenance lens.

It is more appropriate to understand this as a short-term operational change with longer-term signaling value. In the short term, the issue is process: filings, declarations, and contract wording. In the longer view, the industry will likely watch whether digital services supplied across borders face more structured origin and disclosure expectations. For now, continued observation remains necessary because the current information is limited to a pilot announcement and its immediate implications.

How to read the development at this stage

At this point, the most balanced reading is that CBP's pilot creates a concrete new compliance touchpoint for certain Chinese SaaS website-building providers serving US customers, while also sending a broader signal about how digital service origin may be framed in cross-border transactions. The effect should not be overstated beyond the facts provided, but it also should not be treated as a minor paperwork detail. For affected businesses, the issue sits at the intersection of service delivery, supplier transparency, and contract execution, and is best treated as a live development that warrants close monitoring rather than a fully settled market rule.

Basis of this article

This article is based on the user-provided news title, event date, and event summary. In coverage of developments of this kind, commonly relevant source types may include official agency announcements, company statements, industry association releases, authoritative media reporting, and standard-setting documents. A specific official source link was not provided in the input, so the underlying text and any later implementation details still require ongoing verification. Continued attention should focus on whether CBP issues further clarification on pilot scope, filing practice, or any expansion beyond the currently described locations and service scenario.