Platform · 07 Editorial guide
E-commerce & platform operations
A digital business can be marketplace operator, seller, advertiser, payment or logistics intermediary and data handler at different stages. Legal duties follow the actual function, not the product team's label.
First job Classify platform/operator role and transaction flow before assigning regulatory duties.
Start here
Key considerations
The first questions are about urgency, governance and preservation — before collection expands or interviews begin.
- Who contracts with the customer and receives payment?
- Can third-party merchants independently offer goods or services?
- Which onboarding, platform-rule, product, complaint or enforcement event is live?
Direct answer
What this page decides
02
China platform compliance starts by deciding whether the service merely supports a seller or provides an online marketplace where parties transact independently. A platform operator must verify and register merchant identity and licensing information, update it periodically, preserve product/service and transaction records, maintain fair and intelligible rules, and respond to unlawful listings, consumer-safety risks, IP notices and regulator requests. When the platform also sells self-operated goods, advertises, ranks, pays, fulfils or handles personal information, those roles add separate duties. The Platform Rules Supervision Measures effective February 1, 2026 also require platform rules to be clear, public, fair and fairly executed. Build one control map per function rather than relying on a broad intermediary disclaimer.
At a glance
Which fact changes the next route
Use the fact that changes ownership or urgency to decide the next move.
| Question | Why it matters | Next route |
|---|---|---|
| Is the platform also the seller or contracting party? | Self-operated sales and mixed storefront presentation can create direct seller and consumer obligations. | Trace contracting name, invoice, payment recipient, fulfilment and customer-facing representations. |
| Are merchant identity and licences current? | Platforms must verify, register and periodically update operator and permission information. | Test onboarding, six-month refresh, exception monitoring and regulator reporting evidence. |
| Can rules or algorithms materially affect merchants or consumers? | Rule changes, ranking, penalties and access restrictions must be transparent and fairly governed. | Inventory rules, change notices, consultation or comment steps, execution logs and appeals. |
| Is a prohibited-product, safety, IP or complaint signal open? | Different notice-and-action standards and preservation duties apply. | Classify the signal, preserve the listing and transaction record, and route it to the correct response owner. |
Scope
What this page owns — and what it does not
Practical workflow
Action, evidence, legal gate, output
| Action | Documents / evidence | Legal gate | Output |
|---|---|---|---|
| Map functions and legal entities | User journey, contracts, invoices, payment and fulfilment flows | Platform, merchant, self-operated seller or other regulated role | Role-by-stage matrix |
| Audit merchant and listing controls | Identity/licence checks, refreshes, product gates and prohibited-list rules | Lawful merchant and offer | Onboarding and catalogue control record |
| Govern rules and transactions | Platform terms, change history, ranking, penalties, appeals, order/refund and retention records | Clear, fair, published and consistently executed rules | Rule and evidence register |
| Operate incident response | Complaints, notices, takedowns, safety signals and authority requests | Correct standard, action, notice, preservation and report | Closed response file |
Documents
What to gather before the next call
These items help clarify the file; they are not a legal requirement list.
| Item | Why needed | Who holds it | Risk if missing |
|---|---|---|---|
| Role and transaction-flow map | Shows who contracts, sells, pays and fulfils | Product, legal, finance and operations | Intermediary labels contradict actual conduct |
| Merchant verification and licence file | Supports entry and periodic re-verification | Merchant governance | Unqualified or unidentifiable sellers remain active |
| Platform-rule versions and execution logs | Prove notice, fairness and consistent enforcement | Policy, product and appeals teams | Opaque or discriminatory rule action |
| Listing and transaction records | Preserve offer, order, payment, logistics and after-sales evidence | Platform engineering and operations | Consumer or regulator issue cannot be reconstructed |
| Notice, complaint and takedown records | Show classification and timely response | Trust, safety, IP and customer service | Known risk continues or lawful content is mishandled |
Common failure points
Where files usually break
Calling all activity ‘platform services’ while the operator sells or contracts directly.
Verifying merchants only at onboarding and not updating identity and licence data.
Changing ranking, fees, penalties or exit rules without compliant publication and execution controls.
Keeping complaints, IP notices and product-safety signals in disconnected queues.
Retaining a policy but not the listing, transaction and decision evidence showing how it was applied.
Decision map
Keep the question bounded.
- Map roles and transactionIdentify platform operator, in-platform merchant, self-operated seller, advertiser, livestream actor, payment and fulfilment parties at every customer step.
- Audit rules and evidenceReconcile merchant onboarding, platform rules, listings, ranking, orders, payment, delivery, refunds, complaints, takedowns and regulator-access records.
- Assign control and responseSeparate merchant verification, prohibited products, consumer safety, IP notices, advertising, competition and data duties with owners and clocks.
Curated resources
Open the asset that matches this job.
No canonical deep guide is assigned yet. Use this route for orientation and continue to local context or qualified counsel.
Helpful to prepare
Facts that make the next conversation clearer.
These items are orientation aids, not a legal requirement list.
Counsel hand-off
What to bring when you instruct
This topic route organises the national legal question. It does not decide rights, strategy, liability, approval outcome or procedural result on the facts. Use qualified PRC counsel where fact-specific advice or representation is required.
Local context
Add the city when the forum practice changes.
Add city or province context only when the responsible authority, court, registration practice, permit process or local implementation changes after the national route is identified.
Open city and province guidesCounsel hand-off
Need contract counsel?
This hub organises parties, chops, drafting and performance. It does not create a binding contract or decide a breach on your facts.
Find contract counselLegal review
Who reviewed this guide
Subject to editorial/legal review. No reviewer is assigned to this route.
Need qualified counsel?
Move carefully. Move with a record.
Use the portal to identify counsel for this practice and related China-side issues.