App Store tier pricing vs. custom pricing: when to use each in 2026

How Apple's globally equivalent pricing and custom per-territory price overrides work in practice, and which approach suits your subscription app's stage and market mix.

Most iOS developers pick a price and let Apple fill in the rest—setting $9.99 in the United States and trusting that the resulting ₹899 in India or R$49.90 in Brazil is close enough. For simple utility apps with concentrated revenue in high-income markets, that instinct is defensible. For subscription apps building toward global scale, it leaves material conversion improvements on the table in exactly the markets where headroom is highest.

Since Apple's Spring 2023 pricing overhaul, developers have had two practical choices: rely on globally equivalent pricing to generate territory prices automatically, or override specific territories with custom price points. Understanding which approach to use—and when to combine them—is one of the more underused levers in iOS subscription strategy.

This guide explains how each system works, where they diverge, and the conditions that tip the decision one way or the other. For background on how Apple's tier system evolved, see our primer on Apple's price tier system.

From 87 tiers to 900 price points: how we got here

Until early 2023, App Store pricing ran on a fixed tier grid. Tier 1 mapped to $0.99 in the US, ₹75 in India, ¥120 in Japan—Apple set the currency equivalents and updated them infrequently. Developers could select a tier but had no mechanism to set a different price in India without changing the tier globally, which meant changing the price everywhere simultaneously.

The 2023 overhaul changed the architecture fundamentally. Apple replaced the roughly 87 commonly used tiers with approximately 900 price points, introduced the concept of a base territory, and—critically—allowed developers to override any territory's price independently of every other territory. Globally equivalent pricing became the default; custom territory prices became an opt-in layer on top of it.

For most apps, the migration was invisible: App Store Connect translated the old tier to the nearest new price point automatically. But the new architecture exposed a capability that simply did not exist before—the ability to set your subscription at $9.99 in the US while pricing it at ₹499 in India, without those two decisions affecting each other in any way.

How globally equivalent pricing works in practice

When you set a price in App Store Connect today, you select a base territory—most developers use the United States—and choose a price point in that territory's currency. App Store Connect then generates globally equivalent prices for every other territory Apple supports, currently covering 175 storefronts.

Apple's globally equivalent prices are not simple exchange-rate conversions. According to Apple's developer documentation, the calculation aims to produce prices that are locally equivalent in purchasing power, meaning a blend of nominal exchange rates and purchasing-power-parity adjustments snapped to the nearest available price point in the local currency. The exact weighting formula is not published.

The result is a reasonable starting point. A $9.99 subscription might auto-generate as £8.99 in the United Kingdom, €9.99 in Germany, and ₹899 in India. Apple also updates these automatically when currencies move significantly—though with a lag that can leave prices out of step with current exchange rates for weeks or months at a time. For more on how that lag affects revenue in practice, see our post on currency conversion in global iOS pricing.

Two structural limitations emerge over time. First, Apple's auto-updates maintain purchasing-power equivalence but do not optimize for conversion rate—those are different objectives. Second, Apple's globally equivalent price for a territory may sit materially above what local competitors charge, and competitive pricing tends to drive conversion decisions more directly than abstract PPP equivalence does.

What "custom pricing" actually means in App Store Connect

The phrase "custom pricing" circulates loosely in the iOS developer community and means different things in different contexts. In App Store Connect's pricing editor, custom pricing simply means overriding the globally equivalent price for one or more territories with a specific price point you choose. It is not a separate mode to enable or a separate feature to apply for—it is a per-territory edit within the standard pricing workflow.

When you navigate to a subscription product's pricing page, you see your base price alongside the auto-generated globally equivalent prices for all 175 territories. Click into any territory, select a different price point from Apple's list of available options in that currency, and save. The override takes effect at the next applicable purchase or renewal event in that territory and persists until you manually change or reset it.

For subscriptions specifically, a custom price override applies to every renewal in that territory, not just the initial purchase or trial conversion. This compounds across each subscriber's lifetime: a lower custom price widens the conversion funnel and reduces per-subscriber LTV simultaneously. Whether the net revenue outcome is positive depends on how much conversion actually improves—a number that only territory-level data can answer reliably.

Globally equivalent vs. custom pricing: a direct comparison

The table below summarizes the practical differences across the dimensions most relevant to subscription app operators making this decision.

When globally equivalent pricing is the right default

For many apps and teams, Apple's automatic globally equivalent pricing is the right call—not because it is optimal everywhere, but because the management overhead of territory overrides only pays off at a certain revenue scale and data maturity.

Globally equivalent pricing tends to be sufficient when:

• Revenue is concentrated in high-income markets. If the United States, United Kingdom, Canada, Germany, Australia, and Japan account for the large majority of your subscriptions, price sensitivity in lower-PPP markets is a marginal concern. Apple's globally equivalent prices in those markets are generally close to category norms.
• You lack territory-level conversion data. Custom pricing without data to guide it is speculation. Globally equivalent pricing gives you a neutral baseline from which to measure territory-by-territory conversion rates before committing to overrides.
• Your team cannot sustain quarterly review cycles. Custom prices that are set once and never revisited can go stale faster than Apple's own auto-updates—particularly after currency events in markets like Turkey, Argentina, Egypt, or Nigeria. If you cannot commit to monitoring, the automatic system is the safer default.
• You are pre-scale in international markets. At very low subscriber counts per territory, conversion-rate differences are statistically noisy. It is worth waiting until you have enough volume to measure a change before optimizing for it.

When custom territory pricing justifies the overhead

Custom territory overrides earn their management cost when the gap between Apple's globally equivalent price and the market's actual willingness to pay is large enough to suppress conversion materially. Research from Phiture and data published in RevenueCat's annual subscription reports have consistently pointed to price as a primary friction point in low-to-middle-income markets—not a secondary one behind discoverability or product fit.

Custom pricing is worth the overhead when:

• Territory-level data shows a conversion gap you cannot explain by product-market fit. If your India trial-to-paid conversion rate sits 40–50% below your US rate and qualitative signals point to price, a lower custom price is a testable hypothesis. App Store Connect's subscription analytics provide enough cohort data to measure lift once you run the change over a meaningful period.
• A currency shock has left your effective price well above category norms. Turkey, Argentina, Egypt, and several Sub-Saharan African markets have experienced rapid local currency depreciation that Apple's auto-adjustments did not fully absorb in real time. In these situations, a manual override—combined with a commitment to revisit it quarterly—is necessary to stay competitive on price.
• A major competitor has localized their pricing. If a competing subscription app reduces its price in India by 30%, your globally equivalent price may suddenly sit well above what users in that category expect to pay. Custom pricing lets you respond to that competitive move without changing your global tier or base price.
• You are running structured territory-level price tests. Using different custom prices in comparable emerging markets as a proxy A/B test—then monitoring conversion and first-year LTV—is one of the more rigorous approaches available given the current limitations of Apple's native pricing experiments. Our guide on A/B testing iOS app prices safely covers the methodology in more depth.

The revenue arithmetic matters here and cuts both ways. A lower custom price in a given territory reduces per-subscriber revenue but increases subscriber volume. Whether the net effect is positive depends on your churn rate assumptions, payment failure rates (which tend to be higher in markets with lower card penetration), and the marginal value of incremental subscribers in that territory. The direction is generally positive in markets where the current price is a genuine barrier—the question is how much conversion lift you actually get and over what time horizon you evaluate the trade-off. Our post on PPP pricing explained covers the underlying purchasing-power dynamics in more depth.

Setting and maintaining custom prices in practice

In App Store Connect, custom prices are set at the product level—separately for each subscription product and each non-consumable in-app purchase. Navigate to the product's pricing page, select the territory you want to override from the territory list, choose from the available price points for that currency, and save. The override persists until you explicitly change or reset it to the globally equivalent default.

For teams managing overrides across multiple territories and a portfolio of products, the App Store Connect API is the practical path. The inAppPurchasePriceSchedules endpoint for subscriptions—and the equivalent endpoint for other purchase types—lets you read the current territory price configuration in bulk and push updates programmatically. A common workflow is to maintain an internal table of target prices per territory, compute PPP-adjusted price points on a quarterly cadence using World Bank or IMF purchasing-power data, and script the updates via API rather than clicking through App Store Connect's UI for each change. For authentication setup and the general API architecture, see our post on App Store Connect API automation.

Two maintenance triggers are worth building into your calendar:

1. After Apple's periodic automatic price adjustments. Apple periodically recalibrates globally equivalent prices across territories. After each adjustment notice from App Store Connect, review your custom overrides to confirm they still represent the positioning you intended—and that Apple's new globally equivalent price has not moved past or under your custom override.
2. After a significant currency move in any territory you have overridden. A 15% or greater move in a territory's exchange rate is a reasonable trigger for reviewing that override. The goal is not daily monitoring—it is avoiding a situation where a market correction leaves your effective local price materially above or below the positioning you decided on.

Sources and further reading

• Apple Developer: Auto-Renewable Subscriptions — overview and pricing guidance
• App Store Connect API Reference — Apple Developer Documentation
• RevenueCat Blog — subscription analytics data and pricing research
• World Bank International Comparison Program — global purchasing power parity data
• Phiture Mobile Growth Stack — App Store pricing and localization research
• Sensor Tower Blog — App Store market data and category benchmarks