China game ISBN — approval before durable listings

For monetized games, Mainland China store durability usually hinges on Chinese publishing approval — the ISBN path — not on App Store Connect alone. Most product teams need a qualified Chinese publishing entity. Treat approval as a gated program with frozen build materials, then list stores. This Guide is a decision map.

What China game ISBN means

Hard names your program will use (rewritten from how ISBN programs actually run):

• What “ISBN” means here — The game publishing approval number (网络游戏出版物号 / 版号 path). Without it, major stores generally will not host durable paid or IAP game listings.
• Who may apply — Submissions go through a qualified Chinese publisher (typically holding network publishing credentials). A global studio cannot usually file alone.
• Why it blocks stores — Apple China and domestic Android/game channels expect the approval path for monetized games. Listing without it invites removal waves.
• Timing (order of magnitude) — International titles commonly sit on a ~6–12 month class of clock. Materials quality and category shift outcomes; boards need named uncertainty, not fake weeks.
• Scope of approval — Permission for a defined game version under a defined publishing entity — not a forever license for sequels, spin-offs, or radical monetization pivots without further process.
• Not the whole compliance story — Privacy materials, app filing, and store questionnaires still apply after approval. For-profit internet culture operating models may also need the sibling Network Culture Business License path. Spine context: Publish a game in China.

Vocabulary first. Next: which decisions you lock, and where your process stalls.

What must be locked before ISBN submission

Missing any of these stops your product team before a real ISBN submission.

Precondition	Why your process stalls
Publishing vehicle agreed — qualified Chinese publisher / entity	No valid applicant; opaque brokers without a clear entity are hope, not a plan
Scope freeze — name, platforms, monetization, playable content	Rework mid-review is the default delay mode
Authorization & corporate pack — studio–publisher letters, entity certificates	Incomplete legal packs bounce before content review starts
Materials package — builds, checksums, Chinese metadata, age inputs, privacy answers	Incomplete packages are the most common self-inflicted stall
China-reachable contacts — people reachable on Chinese mobiles during review	Silent stalls when reviewers cannot reach anyone
Studio–publisher RACI — submission, supplements, takedown response, commercial terms	Verbal ownership fails during removal events

Replace “ISBN in Q3” with “submission package locked by DATE; review cycles variable; UA gated on listing durability.” Boards hate uncertainty less when uncertainty is named.

From publisher vehicle to approval record

Step	Outcome	Failure if skipped
1. Publishing vehicle	Chinese publisher/entity agreed	No valid applicant
2. Scope freeze	Version, platforms, monetization defined	Rework mid-review
3. Materials package	Builds, text, age ratings, required docs	Incomplete submission
4. Submission & rounds	Official review cycles managed	Silent stalls
5. Approval / ISBN record	Identifier and approved scope clear	Stores reject or remove
6. Store enablement	Apple China + Android/game channels	License with no distribution
7. Live duties	Updates, content, anti-addiction ops	Post-launch suspension

What to freeze before you submit

• Game name and Chinese metadata strategy
• Core loops and monetization (IAP tables, ads)
• Target platforms (iOS / Android)
• Content that reviewers will actually play
• Privacy/security answers consistent with the build

Studio vs publisher responsibilities (write them down)

Studio — build quality, global IP, feature roadmap, marketing assets. Publisher — local submission, relationship with authorities/stores, many compliance ops. Shared — content calendar, takedown response, commercial terms.

After approval

Approval is not “done.” Store listings, package updates, and major content drops may need coordinated notifications. Keep the China build pipeline and the compliance owner linked. Approval/ISBN is permission to publish a defined game scope under a defined entity.

Working cadence during review

• Freeze marketing claims that imply a firm Mainland China launch date
• Keep a weekly status with the publisher (submitted / supplemental requested / idle)
• Prepare store metadata in draft so listing can follow quickly after approval
• Do not start large China influencer retainers that assume a date you do not control

Silence from a broker is a risk signal. Demand visibility into which step the package is in.

Why ISBN stalls cascade into store failure

No publishing vehicle → no submission. App Store Connect territory toggles do not create a qualified Chinese applicant.

Unfrozen product → year-long “two-month” projects. Mid-process economy or content changes force supplemental rounds.

Incomplete materials → idle in queue. Corporate certificates, authorizations, build hashes, and Chinese metadata are gates, not paperwork theater.

Approval without store enablement → license with no players. ISBN does not distribute itself across Apple China and Android/game channels.

UA on submit day → burned budget. Paid acquisition before approval and listing stability funds removal waves.

Global live-ops drift → review and store inconsistency. China-approved content that diverges from the trunk needs a deliberate China branch strategy.

ISBN alone → false “fully compliant” story. Privacy, app filing, and store security questionnaires still exist.

No evidence pack → slow appeals. When channels ask “prove you can publish,” hours matter: keep approval/ISBN references, submission receipts, correspondence summaries, build hashes, and listing IDs.

Broker risk, scope drift, removal waves

• Opaque “guaranteed ISBN” brokers — diligence the publisher like a critical vendor: entity, timeline assumptions, rejection handling.
• Version-scope violations — shipping a wildly different build than approved invites trouble; align release engineering with approved scope.
• Sequels, DLC, major pivots — assume material changes need publishing-entity advice before ship; a global “season 3 rework” can be a China compliance event.
• Portfolio one-offs — multi-title studios that do not standardize contracting, materials templates, and China branch policy repeat first-game pain.
• Removal waves — public enforcement often targets unlicensed or non-compliant listings; defense is documentation that maps listing → valid approval → current package, not PR.
• Free-to-play assumptions — “no IAP” does not automatically skip publishing rules; confirm classification before marketing a China date.

Materials checklist (starter)

• Corporate certificates for the publishing entity
• Authorization letters between studio and publisher
• Build package and checksum records
• Chinese description, screenshots, and age rating inputs
• Privacy and content commitments aligned to the build
• Contact persons reachable on Chinese mobiles during review

When you need a China landing partner for ISBN

Most product teams exploring Mainland China entry need a China landing partner to select a real publishing vehicle, freeze a submittable package, manage review rounds, and connect approval to store enablement Your team still owns scope and product decisions; the partner path makes the ISBN gate executable when Chinese publishing rails are not already in-house.

What we can offer?

China game ISBN / publishing approval is a scheduled gate with clear studio–publisher ownership. Chinaready helps your product team make that gate real — vehicle, scope freeze, materials, timeline — then turn approval into durable store presence:

1. China Readiness Assessment — Test whether the publishing vehicle, content freeze, and submission pack are real before a China quarter is committed externally.
2. China Access Acceleration — Keep review and player paths reachable in Mainland China while approval and listing work proceed.
3. China Product Hosting — Host China-critical game services where approved builds and live-ops can run for Mainland China users.
4. Mobile App Distribution — Convert approval into durable Apple China and Android/game listings with package ops that survive updates and appeals.

Contact us when you need the ISBN gate integrated with your Apple and Android channel matrix.