China Entry Path Navigator
This page closes the gap between a broad China question and the first path a team should actually open.
Bring one object, one market scope, and one decision question. We will tell you whether the next layer is S21, S22, or S42.
brand + China + decision question
Use this page when the China question is real, but the path order is still unclear enough to slow the next spend.
Compare the path before you debate the spend.
Every path below is a way to sort the first blocker before a team turns comparison into commitment.
Approval first
Typical blocker
Regulatory friction and entry structure.
When this path tends to matter
When the object is close to Approval or Launch and the first real risk is legal entry structure rather than awareness.
Often leads into
S22.
Local partner first
Typical blocker
Route-to-market structure and local operator logic.
When this path tends to matter
When the object has enough proof to enter the conversation, but local route structure is still the main unknown.
Often leads into
S21 plus S42.
Education and sample channel first
Typical blocker
Training burden and sample-account adoption.
When this path tends to matter
When the technology needs teaching, operational proof, and sample-account adoption before broader channel logic becomes reliable.
Often leads into
S42, then S21.
Combination pathway first
Typical blocker
Bundle logic and pathway fit.
When this path tends to matter
When the object is more likely to enter China as part of a treatment stack, peri-procedure pathway, or portfolio bundle than as a single SKU.
Often leads into
S42 or S21.
Public evidence first. Private certainty later.
The public version should sharpen the question, not pretend it can close every commercial, legal, or clinical ambiguity on first read.
What this page does use
Regulatory records, review timelines, company disclosures, launch activity, public training moves, and other public, reviewable evidence.
What this page does not use
Gray-channel rumors, unreviewable market-share claims, private partner lists, or hidden operating assumptions presented as settled fact.
Why the boundary matters
This is a map for orientation. It is not final legal, medical, or investment advice, and it should not be read as a promise that one path always wins.
Map, not mandate.
No single score. No forced certainty. No substitute for legal, medical, or investment advice. Use the public page to identify the right question, then take the next layer into the right service.
Choose the handoff that matches the blocker.
The map only earns its keep if it moves the reader into the right next layer. These are not three versions of the same engagement.
Path judgment and stage positioning
Use this when the team still needs to compare routes, locate the object on the path, and decide what question should be solved first.
Request a path clarificationEntry-condition and approval friction breakdown
Use this when legal entry prerequisites, approval sequencing, or regulatory friction are already the main blocker.
Request a path clarificationPartner, education, and sample-channel design
Use this when the real work is choosing partner structure, training build-out, or sample-account logic without distorting the route.
Request a path clarification