What in-app purchase localization covers and where shoppers see it
A shopper meets your price in three places. The product page can show in-app purchase display names near your offers. The purchase sheet shows the name and a short description at the exact second of payment. Subscription settings show both strings for months after, each time a user wonders what they pay for. One English leftover in any of these spots tells a shopper the product is foreign, right when trust matters most. Our description guide makes the same point about listing copy: the words closest to money carry the most weight.
In-app purchase localization covers four layers that most indies find one by one, usually after a confused support email. Each in-app purchase carries a display name of up to 30 characters plus a description of up to 45 characters, and each storefront language needs its own pair. Each subscription carries the same pair under the same limits. Each subscription group carries its own display name of up to 30 characters, which shoppers see when they compare plans inside one group. Behind these sit two internal strings buyers never see: the reference name of up to 64 characters that labels the item in your reports, and the product ID, a unique code you can never reuse even if you delete the item. Reference names stay in your language since only your team reads them, while each shopper-facing string needs a real translation. Prices need no translation work at all because Apple converts and shows them per storefront alone, so the whole job is words plus review assets.
The demand signal hides inside setup docs. Purchasely documents the Add Localization button flow for its paywall users, Apple documents adding and removing localizations for subscriptions and groups, and Develak's 2026 review guide shrinks the whole job to one setup bullet, which tells you most teams treat it as an afterthought. That's the opening. A polished listing with English purchase sheets loses to a fully local one at the tap that counts.
The in-app purchase fields you must localize in every market
Start with an inventory, because App Store Connect spreads purchase words across more screens than anyone expects. Open the Monetization section and list each in-app purchase, each subscription, and each group. Write down which languages each one already covers. Most indies find one pattern: the listing ships in twelve languages while purchases cover two, usually English plus one early market. That gap is your work list, ordered by revenue per storefront.
The per-item fields follow one shape. Each consumable, non-consumable, and subscription takes a display name and a description per language. The name gets 30 characters and the description gets 45. The subscription group takes its own display name of 30 characters per language, which appears where shoppers compare plans. Purchasely's setup doc shows the mechanics: open App Store Information for the item, click Add localization, pick the language, and enter the pair. Apple's subscription docs describe the same step for groups and plans. Keep reference names in English and keep product IDs stable, since changing either breaks your reports and your code mapping.
Two platform rules shape the whole job. First, you need the right role. Screenshipper's 2026 guide notes that managing languages needs the Account Holder, Admin, App Manager, or Marketing role, and you can only add or remove languages while the app is in an editable state. So batch this work before you submit the version, not after. Second, storefronts without a localization fall back to your default-language strings. Pick that default on purpose. If Japan earns real money and your default purchase language is English, each unlocalized string a Japanese shopper meets reads foreign. Our locales reference orders markets by reach, and our strategy guide sequences the work by revenue, so fund purchase copy in the same order you funded the listing. Subscription group localizations and subscription localizations go through review on their own track, apart from your app version, so a copy fix to a plan name never forces a binary rebuild.
Write names that fit 30 characters in every tongue
Thirty characters punish direct translation. An English plan name like Pro Monthly glides in at 11 characters, while its German twin can swallow 25 before you add a space. French articles and Spanish prepositions eat the rest. The fix is the same packing habit our keywords-field guide teaches for the 100-character keyword set: draft from meaning, not from English word order.
Build each name from your listing glossary. Your localized title and subtitle already hold the market's words for your core promise, checked by a native reader during the listing pass. Pull the noun from there. A fitness app whose Japanese subtitle promises home training in 7 minutes already owns the phrase its monthly plan name should reuse. This reuse does three jobs at once: it keeps vocabulary consistent between the listing and the purchase sheet, it shortens the native check because most words already passed one, and it feeds your machine translation glossary the approved terms, as our machine translation guide explains.
Spend the 45-character description on facts, not praise. Name what unlocks, state the billing period in local terms, and stop. Monthly offline maps and new routes fits where Unlock the full pro experience with all premium features fails, and only the first survives translation into longer tongues. Skip superlatives completely. Review already dislikes generic praise in metadata, and Develak's guide shows reviewers checking subscription disclosures closely, so a description that states plan, period, and price behavior passes faster than one that sells.
- Don't stuff keywords into display names the way some guides suggest for subtitles. Purchase names show at payment time, and stuffing reads as spam when a card is on screen.
- Keep the group name distinct from plan names inside it. If the group is called Premium and the plan is also called Premium, the comparison screen shows the same word twice and shoppers stall. Name the group for the family and each plan for its period or tier.
- Confirm length in the real script. Japanese counts differently than Latin text, and a name that fits in romaji can overflow in full kanji plus katakana.
Our QA pass covers per-locale length checks, and purchase names deserve the same treatment as titles. Open each purchase sheet in its storefront language before you submit, and fix every truncation while the fix is cheap.
The indie workflow from listing glossary to approved purchase
- Export the glossary row for the market: title, subtitle, keywords, and description terms your listing already ships.
- Draft each display name and description from that row, longest market first. German and French expose length pain early, while English hides it.
- Hand the set to one native checker with the limits printed at the top and one instruction: flag anything a local wouldn't say on a payment screen. Pay for this hour. It's cheaper than one refund wave.
- Enter the strings in App Store Connect. Add each language per item, paste the pair, and save.
- Prepare review assets. Purchasely's doc states the rule plainly: each in-app purchase needs a screenshot for the reviewer plus optional review notes, and you can't submit without the image. Write notes that tell the reviewer where the purchase lives in the app and which languages changed.
- Submit the purchase localizations on their own track. Apple reviews subscription and group localizations apart from the app version, so a copy fix never waits on a binary.
Then verify like a shopper. Switch a test device to each storefront language and walk the whole money path: product page, purchase sheet, settings screen. Our QA pass gives the full routine, and purchase words ride along with it.
Read results per territory with our measurement routine: trials started, upgrades completed, and refund requests per market on equal windows before and after. A market whose upgrades climb while refunds fall paid for its evening. Fold each winning phrase back into the glossary so the next surface, from custom product pages to in-app events, inherits proven words.
How App Store Localizer fits your purchase pass
App Store Localizer covers the listing half that purchase copy builds on. Paste a public App Store URL and the tool pulls your title, description, icon, and screenshots through Apple's public lookup. It translates the title, subtitle, description, and 100-character keyword field per target locale, then re-renders screenshots with localized captions. Keyword suggestions come from free heuristics over your listing plus pasted source keywords, so verify each term against local behavior. It covers about 20 locales, including Japanese, German, French, Spanish, Korean, Simplified and Traditional Chinese, Italian, Dutch, Brazilian Portuguese, Swedish, Norwegian, Danish, Finnish, Polish, Turkish, Arabic, Hebrew, Thai, Indonesian, Hindi, and Vietnamese, with English as the source.
Two boundaries matter. The tool renders two listing sizes, iPhone 14 Plus at 1284 by 2778 and iPad Pro 12.9-inch at 2048 by 2732, while purchase sheets use the system's own layout, so reuse the checked captions and strings as source material and let Apple lay out the sheet. And the tool handles listing content only: no in-app strings, no Google Play, no video previews, no human review, and no paid volume data. Enter display names and descriptions in App Store Connect yourself, using the glossary the tool output gave you. Download the assets or publish to App Store Connect, then submit purchase fields per locale in Connect. Packages are one-time: Starter costs $19.99 for three languages with all screenshots for one listing, and Global costs $99.99 for each supported language for one listing, with no subscription.
Frequently asked questions
- Do I need to localize purchases if my listing is already localized? Yes, because Apple treats them as separate tracks. A localized listing with English purchase sheets breaks trust at payment time, and unlocalized storefronts fall back to your default-language strings. Fund purchase copy in the same market order you funded the listing.
- Where do shoppers actually see these strings? On your product page near offers, on the purchase sheet at payment time, and in subscription settings for months after. The purchase sheet matters most since the card is on screen.
- Do purchase localizations need their own review? Yes. Each in-app purchase submits with a reviewer screenshot plus optional notes, and subscription and group localizations are reviewed apart from your app version. A copy fix ships on the purchase track with no binary rebuild.
- What are the exact character limits? Display names get 30 characters for in-app purchases, subscriptions, and subscription groups. Descriptions get 45 characters. Reference names get 64 characters but stay internal. Product IDs are unique codes you can never reuse.
- Can I add a language later without breaking anything? Yes, with the right role and timing. You need the Account Holder, Admin, App Manager, or Marketing role, and languages can only change while the app is editable. Batch new languages before version submission, then submit the purchase localizations on their track.
Paste your App Store URL at https://asolocalization.com today. You'll ship the listing foundation for three markets in one afternoon, then draft each display name and description from those checked strings. When the next plan launches, our QA pass catches defects, our measurement routine reads each market on equal windows, and our rejection guide covers the flags to avoid. One honest plan name per market beats ten English purchase sheets.