App Store In-App Purchase Localization in Simplified Chinese — IAP Display Names for China

IAP copy vs app listing copy

App Store Connect stores in-app purchase strings in a separate localization layer from your app listing. Each IAP product — consumable, non-consumable, auto-renewable subscription, or non-renewing subscription — has its own display name and description per locale. These fields appear on the system purchase sheet, subscription management screens, and (for subscriptions) the App Store subscription detail page — not on your product page gallery or Search snippet.

• App listing — title, subtitle, keywords, description, promotional text, What's New, screenshot overlays. Different Connect rows.
• In-app purchases — display name + description per IAP product ID, localized under Features → In-App Purchases → [product] → App Store Localization.
• In-app UI — paywall screens, pricing labels, and feature gates inside your app binary. Not covered here — you ship those in Xcode.

This page covers IAP display names and descriptions only. For listing fields, see our China storefront listing guide, description guide, or subtitle guide.

Where IAP localization lives in App Store Connect

In App Store Connect, open your app → Features → In-App Purchases (or Subscriptions for auto-renewable groups). Select a product, then add or edit localization rows for each locale — including Simplified Chinese (zh-Hans). Each row has:

• Display Name — the product title buyers see on the purchase sheet (commonly capped at 30 characters — verify in Connect before you save)
• Description — one or two lines explaining what the buyer gets (commonly capped at 45 characters — verify in Connect)

Subscription groups share a group-level display name in some views, but individual subscription tiers still carry per-product localization rows. Non-consumables and consumables follow the same display name / description pattern. Empty zh-Hans rows may fall back to English — which is exactly the problem this page addresses.

Why an English-only paywall kills conversion on the China storefront

US and EU indie teams often ship IAP products with English-only localization because StoreKit product IDs and server-side entitlements work fine without zh-Hans strings. The listing looks localized; checkout does not. On the China storefront, that mismatch shows up at the worst moment — when a buyer has already decided to pay:

• Purchase sheet in English — “Annual Pro”, “Remove Ads”, “Premium Access” with no Chinese context for what unlocks
• Subscription tier confusion — three English tier names that differ by one adjective (“Basic”, “Plus”, “Pro”) with no zh-Hans differentiation
• Feature jargon — internal codenames (“Tier 2”, “Bundle A”) pasted as display names because engineers named the StoreKit product first
• Mismatch with localized listing — Chinese description promises “专业版解锁全部功能” but the purchase sheet still says “Unlock Pro Features”
• Trust drop at payment — buyers who read Chinese everywhere else hit English at Apple Pay and assume the app is not maintained for China

Better zh-Hans IAP copy reduces paywall abandonment — it does not replace in-app UI localization, pricing strategy, or Apple’s review decisions. This is Connect copy you paste, not code you compile.

Character limits on IAP display name and description

Apple caps IAP strings tighter than listing fields. Count characters in Connect before you save — limits can vary slightly by product type:

• Display Name — commonly 30 characters for consumables, non-consumables, and subscriptions. This is the product title on the purchase sheet, not your app name.
• Description — commonly 45 characters. One concrete benefit or scope line — not a mini marketing paragraph.

Chinese IAP names often need fewer characters than English equivalents when phrasing is tight — you do not need to fill every slot. A 12-character zh-Hans display name that states the outcome (“年度专业版”) beats a 30-character English paste. Cut tier adjectives that repeat across products — differentiate by duration or scope instead.

Subscription tiers vs one-time unlocks

Different IAP types need different naming strategies in zh-Hans:

• Auto-renewable subscriptions — display name should state duration or tier (“月度订阅”, “年度专业版”). Description clarifies renewal and what unlocks.
• Non-consumables — display name names the permanent unlock (“永久去广告”, “完整功能包”). Description states one-time purchase, no subscription.
• Consumables — display name states quantity or unit (“100 积分包”, “额外导出次数”). Description clarifies consumable nature.
• Free trial + paid tier pairs — trial and paid products need distinct zh-Hans names so buyers do not confuse “7-day trial” with “monthly plan” on the sheet.

Align IAP names with what your localized listing promises — if the description mentions “专业版”, the purchase sheet should use the same term, not a different English brand name.

Why machine-translated IAP copy fails at checkout

• Literal “Pro” → “专业版” on every tier with no differentiation between Basic, Plus, and Pro
• English duration words preserved (“Monthly”, “Yearly”) instead of Chinese subscription habits (“月度”, “年度”)
• Marketing superlatives (“Best value”, “Most popular”) translated without context — Chinese buyers expect scope, not slogans
• Feature lists crammed into the 45-character description field — overflow truncates mid-sentence on the purchase sheet
• Inconsistent terminology between IAP names and your zh-Hans listing description

Machine translation is fine for internal drafts. Finished IAP copy needs idiomatic zh-Hans that matches how Chinese users describe what they are buying — while keeping the product voice of your English originals. AppLocale rewrites IAP strings by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans IAP copy looks like

At the paywall, buyers decide in seconds. Strong Chinese IAP strings state scope and duration in plain language:

• Display name: outcome or tier + duration — “年度专业版”, “永久去广告”, “100 次导出包”
• Description: one line on what unlocks or renews — “解锁全部功能，按月自动续费”
• Consistent terms across all tiers — if “专业版” means full features, every full-feature tier uses it
• English product names kept only where Chinese users expect them (e.g. brand names); everything else idiomatic

zh-Hans and en-US IAP strings can differ in length and structure when the underlying promise matches — avoid mirroring English tier adjectives that do not translate.

What you send

• Your live App Store listing URL
• Your current English IAP display names and descriptions (paste from App Store Connect — one block per product ID is fine)
• Target locales (e.g. zh-Hans, or zh-Hans + en-US alignment)
• Your deadline if you have a submission date in mind
• Reply from the email address on your Stripe receipt after checkout

What you get

• Simplified Chinese (zh-Hans) — IAP display names and descriptions, paste-ready for App Store Connect localization rows
• English (en-US) — aligned IAP strings when both locales need the same promise in native phrasing
• Character-count notes — which strings fit Connect limits and what to trim
• Paste-ready delivery — formatted files you copy directly into each IAP product’s localization row
• 24-hour turnaround — delivered to the email on your Stripe receipt

Who this is for

US and EU indie iOS developers and small teams with a live or draft China storefront whose app listing is localized but in-app purchase display names and descriptions are still English-only — and who want zh-Hans paywall copy that converts without hiring a full-time localization contractor or touching StoreKit code. If you searched for App Store IAP Chinese, in-app purchase localization zh-Hans, or China App Store subscription display name rewrite, this is the deliverable.

What we do not promise

• No guaranteed App Store ranking, keyword position, download growth, or subscription conversion lift
• No fabricated social proof, review quotes, ratings, or traffic numbers
• No app listing title, subtitle, keyword, description, What's New, promotional text, or screenshot overlay work on this SKU alone
• No StoreKit configuration, Xcode project edits, server-side receipt validation, or in-app UI translation
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

What does Simplified Chinese in-app purchase localization include?

Paste-ready zh-Hans display names and descriptions for your in-app purchases in App Store Connect, rewritten from your current English IAP copy while keeping your product voice. Delivered within 24 hours to the email on your Stripe receipt.

What do I send after payment?

Your live App Store listing URL, your current English IAP display names and descriptions (paste from App Store Connect), target locales (e.g. zh-Hans), and your deadline. Reply from the email address on your Stripe receipt — we deliver to that Stripe email.

How is IAP localization different from app listing copy?

In-app purchase display names and descriptions are separate fields in App Store Connect under each IAP product — not the app title, subtitle, keywords, description, promotional text, What's New, or screenshot overlays. IAP copy appears on the purchase sheet and subscription management screens buyers see at checkout.

Do you write StoreKit code or configure IAP products?

No. This is listing and copy work only. You paste finished zh-Hans strings into App Store Connect IAP localization rows. We do not edit Xcode projects, StoreKit configuration files, or server-side receipt validation.

Is this machine translation?

No. We rewrite your IAP display names and descriptions by hand. We do not paste Google Translate or ChatGPT output into deliverables. Machine drafts are fine for internal notes — finished store copy is edited for zh-Hans readability at the paywall.

How fast is delivery?

Within 24 hours after your Stripe receipt. Send your App Store URL, English IAP copy, target locales, and deadline from the email on your receipt.

Do you guarantee App Store rankings or conversion rates?

No. We improve clarity from your existing IAP copy. We do not promise keyword position, search rank, download growth, or subscription conversion lift.

How much does AppLocale cost?

$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.

What is AppLocale not?

Not app listing title/subtitle/keyword/description work, not What's New or promotional text, not screenshot overlays, not StoreKit engineering, not ranking guarantees, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — in-app purchase localization in Simplified Chinese

$79 one-time

Buy on Stripe

After checkout, reply from your Stripe receipt email with your App Store URL, current English IAP display names and descriptions, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. Sold by Fortune Insight, LLC.