Assume an overseas brand with some reference-market proof. The problem is not whether China is attractive in the abstract, but which route is actually open first.
Navigator derivative / public version v0
China Entry Path Map
The same overseas brand does not enter China through the same first move. This page is a comparative map for path order, blockers, and the next best question before a team overcommits.
Map, not mandate
Public version
Four high-frequency paths
Start by comparing the path. Only then decide whether the next layer is path judgment, entry-condition breakdown, or partner and channel design. No single score. No forced certainty.
brand
China
Which path opens first without forcing false certainty?
brand + China + decision question
Read this page as a derivative of the Navigator. It is built for an overseas brand with reference-market proof, usually sitting around the Approval / Launch transition.
Compare the path before you debate the spend.
Every path below answers the same six questions: what has to be true first, what is usually blocking, who it fits, who it does not fit, which service naturally follows, and what should be validated next.
One brand is blocked by regulatory friction. Another is blocked by training burden or weak local route structure. Path order changes the work.
Once the path is clearer, the right next layer is usually S21, S22, or S42, not a generic contact flow.
Path A
Approval first
regulatory friction
channel readiness
Use this path when the object already looks close to Approval or Launch, and the first real risk is legal entry structure rather than awareness.
Preconditions
A clear entry objective already exists, and the brand has enough reference-market proof to justify route analysis.
Fit
Higher-ticket, compliance-heavy brands that cannot rely on gray-channel trial-and-error.
Not for
Brands with weak proof, unstable positioning, or category questions that are still earlier than approval logic.
Default service
S22, with S21 only if path order is still unclear.
Path B
Local partner first
channel readiness
commercial proof
Use this path when the object has enough proof to enter the conversation, but the route-to-market and local operator structure are still the main unknowns.
Preconditions
The brand already has some evidence base, but lacks a stable local route, partner logic, or go-to-China operating shape.
Fit
Brands comparing distributors, regional partners, or a first local operating structure before committing to scale.
Not for
Cases where regulatory route itself is still highly unresolved or the China thesis has not narrowed enough to evaluate partners.
Default service
S21 + S42 to compare path order before partner design hardens too early.
Path C
Education and sample channel first
training burden
channel readiness
Use this path when the technology needs teaching, operational proof, and sample-account adoption before broader channel logic becomes reliable.
Preconditions
The brand must establish training rhythm, KOL education, or sample accounts before any route signal is trustworthy.
Fit
Higher-education-burden categories, operator-dependent technologies, and brands that need reference use before route expansion.
Not for
Simple, standardized products that can move without a heavy training loop or sample-channel build.
Default service
S42 first, then loop back into S21 when sample-market evidence sharpens.
Path D
Combination pathway first
market pull
commercial proof
Use this path when the object is more likely to enter China as part of a treatment stack, peri-procedure pathway, or portfolio bundle rather than as a single hero SKU.
Preconditions
The brand fits better as part of an existing care sequence or offer stack than as a standalone category wedge.
Fit
Peri-procedure, maintenance-stack, or portfolio-style brands that gain traction through pathway logic instead of single-product push.
Not for
Cases where the object already has a sharp standalone hero-product wedge and forcing a bundle story would slow entry.
Default service
S21 first, then route into S42 or S22 depending on the blocker.
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.
Start with S21Entry-condition and approval friction breakdown
Use this when legal entry prerequisites, approval sequencing, or regulatory friction are already the main blocker.
Explore S22Partner, 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.
Discuss S42