Skip to content
HAINAN SETUPChina market entry

Selling SaaS in China: WFOE, ICP, Data and Hainan

A practical briefing for overseas SaaS founders comparing cross-border sales, a China WFOE and local partners, with ICP, data and Hainan decision points.

September 16, 2026 · Hainan Setup Editorial Team · 6 min read

TL;DR

An overseas company has three broad ways to sell SaaS in China: cross-border without a local entity, through its own wholly foreign-owned enterprise (WFOE), or through a local partner. That choice affects contracting, payment collection, mainland hosting, ICP or EDI analysis, and where customer data is processed. There is no universal route for every product. The difficult part is usually sequencing the commercial model, licences and data architecture before deployment—not installing the software.

Three Ways to Sell SaaS in China

Path A — Cross-border, no local entity

The overseas company signs the contract and receives payment offshore. This can work when customers accept foreign contracting, settlement and hosting. It does not create a standard mainland company filing subject, so the company should not assume it can place the service on a mainland cloud region or operate a licensed internet service itself.

This route avoids immediate incorporation, but procurement, invoicing, latency, support and data transfers can become sales obstacles. It is usually a market-test route, not a complete local operating model.

Path B — A wholly foreign-owned enterprise

A WFOE is the conventional self-operated route. The China company can sign local contracts, receive renminbi and employ staff. In return, it must maintain accounting, tax, employment and corporate compliance. Its business scope, ownership and product must support any telecom licence application.

A mainland deployment triggers the ICP filing track. Whether the service also needs a B25 commercial ICP or B21 EDI assessment depends on what users pay for and what the platform actually does. A subscription label alone does not decide the category.

Path C — Local partner, reseller or joint venture

A qualified partner may contract with customers, provide channels or operate parts of the local stack. This can shorten the commercial launch when the partner already has customers and suitable capabilities. The trade-off is less control over pricing, data access, customer ownership, service quality and margin.

Use cross-border sales to test demand, a WFOE when local control justifies the overhead, and a partner when regulated capability or distribution matters more. Hybrid arrangements require clear written responsibilities.

The Licensing Stack — ICP Filing, ICP License and EDI

These are related workstreams, not interchangeable labels. A website or service hosted in mainland China normally needs an ICP filing through its access provider. Filing covers the non-commercial internet-information track; it is not permission to operate a paid regulated service.

A B25 commercial ICP licence applies to qualifying paid internet-information services. B21 EDI covers specified online data processing and transaction or transaction-processing services. A third-party marketplace commonly needs a B21 assessment. Some SaaS models may also trigger review, but charging a subscription does not mean every product automatically needs EDI.

The practical sequence is entity and business scope first, then mainland hosting and filing, then the applicable licence application. Licensing can take weeks or months beyond entity preparation and provider review, so do not build a launch plan around a fixed approval date. Our detailed guide explains the distinction between ICP filing vs ICP license and the foreign-investment questions.

Where Your Data Lives — PIPL and Localization

Personal information collected through China operations is subject to the Personal Information Protection Law. Map what is collected, why, where it is stored, which overseas systems receive it and who has access. If data leaves China, document the applicable exemption or regulatory route; sector and important-data rules may add requirements.

China does not impose universal data localization on every ordinary business. Even so, many SaaS teams choose a mainland cloud region for performance, customer expectations or regulated data, then separate China customer content from global analytics and support tools. That is an architecture decision, not a shortcut around consent, minimization, security or outbound-transfer duties. Review the cross-border data transfer pathway before connecting the China environment to a global CRM, support desk or product database.

Does Hainan Make Sense for a SaaS WFOE?

Hainan may be a practical base when management, staff, customer operations or product work will be there. Its business-service environment can support registration, a suitable address, bank onboarding and compliance. The Hainan tech startup guide tests the operating fit beyond the tax headline.

The 15% corporate income tax rate is not guaranteed to a SaaS company. The business must fit an applicable encouraged-industry catalogue, meet the qualifying-revenue test and maintain substantive operations in Hainan. People, premises, management, accounts, contracts and value creation need to support the position. Use the Hainan 15% corporate income tax guide for the current eligibility framework. Registration in Hainan or using “software” in the business scope is not enough.

A Realistic Sequencing

For a self-operated launch, use this order:

  1. Choose the commercial path. Confirm customers, contracting party, payment flow, product functions and control requirements. Allow days to a few weeks for internal decisions and local screening.
  2. Form the WFOE and set the business scope. Prepare investor documents, registration materials, address, tax and bank onboarding. Straightforward formation is commonly planned in weeks, while banking and regulated matters can extend the programme.
  3. Select the domain and cloud architecture. Decide which workloads remain overseas, which run in mainland China and which vendors can support filing.
  4. Complete ICP filing. Align the domain, filing subject and provider materials before public mainland deployment. Provider preparation and authority review should be planned in weeks, not as an instant step.
  5. Apply for B25 ICP or B21 EDI if the model requires it. Treat this as a separate licence workstream measured in weeks or months; approval remains with the authorities.
  6. Finish data and contract controls. Map PIPL notices, customer terms, processing roles, transfer mechanisms, cybersecurity controls and vendor agreements.
  7. Launch local sales and payment. Test invoicing, support, renewals and compliance evidence before scaling.

Frequently Asked Questions

Do I need an ICP license to sell SaaS into China?

Not in every model. Overseas hosting does not use the mainland ICP filing track. A mainland-hosted site needs filing, while B25 ICP licensing and B21 EDI licensing depend on the service and revenue model. Paid SaaS is assessed case by case.

Can a foreign SaaS company host on a China cloud server without a local entity?

Do not assume an overseas company alone can use the standard mainland company filing path. Mainland cloud deployment normally requires a recognized filing subject and provider verification. Confirm the applicant route before buying infrastructure.

Does every SaaS need an EDI license?

No. B21 EDI covers specified online data processing and transaction-processing activities. A marketplace or transaction platform commonly needs assessment, but a subscription does not by itself prove that every SaaS product falls within B21.

Is the Hainan 15% tax rate guaranteed for SaaS?

No. The company must fit an applicable encouraged-industry catalogue, earn the required qualifying revenue and maintain substantive operations in Hainan. A software label or Hainan registration alone is insufficient.

Continue reading

Related Hainan insights.

Use the next guide to connect this decision to the rest of the company setup.