App Store pricing adjustments: how Apple's automatic price syncing works and when to take manual control

Apple automatically adjusts App Store prices in 175 territories when exchange rates shift significantly. This guide explains how globally equivalent pricing works, when to let Apple adjust automatically, and how to build a monitoring workflow that keeps you in control.

Apple can silently revise your App Store prices across 175 territories whenever exchange rates shift past a threshold. Many developers discover the mechanism only after the fact — a price they carefully calibrated has moved 15% and taken subscriber conversions with it. This guide explains how automatic pricing adjustments work, what the globally equivalent pricing toggle actually controls, and how to build a monitoring workflow that keeps you ahead of every change.

What App Store pricing adjustments actually are

When Apple overhauled its pricing model in late 2022 it introduced two things simultaneously: a dramatically expanded set of price points across currencies, and a mechanism called globally equivalent pricing. The core idea is that you designate one territory as your base currency — for most US-registered developers that means USD — and Apple continuously calculates what the equivalent price should be in every other territory based on current exchange rates, rounding to the nearest point on the local pricing grid.

Pricing adjustments happen when the exchange rate between your base currency and a territory's currency drifts enough to make the current local price point a poor match for the base. Apple monitors this drift and, when the gap exceeds a threshold, proposes an adjusted price. You receive a notification in App Store Connect and have a review window — historically around 14 days, though Apple's documentation does not guarantee a fixed duration — to evaluate and, if you choose, override the change before it goes live.

The mechanism is designed to protect you from currency depreciation silently eroding your revenue over time, and to prevent your app from looking overpriced in markets whose currency has strengthened against USD. But it also means that a deliberate pricing strategy — one calibrated to local purchasing power rather than currency equivalence — can be quietly revised without you noticing. Knowing when to let it run and when to intervene is the core operational decision this mechanism creates.

How the globally equivalent pricing toggle works

Inside App Store Connect, under Pricing and Availability → Price Schedule, you'll find a control labelled "Automatically adjust prices based on your base country or region." When this is enabled, Apple treats your base territory price as the single source of truth and recalculates all other territory prices whenever exchange rates shift materially.

When the toggle is disabled for a specific territory, your manually entered price is locked. Apple will not override it during a global adjustment round. This per-territory granularity matters in practice: you can allow automatic adjustment in the majority of markets while keeping specific prices locked in territories where you've made a deliberate purchasing-power or competitive decision.

Tax-inclusive pricing adds a layer of complexity. In the EU, UK, India, and a growing list of other territories, the price the customer sees already includes VAT or GST. When Apple calculates an equivalent price, it targets the displayed price — the customer-facing number — which means your net proceeds vary by local tax rate even when the "price" appears equivalent. A €9.99 subscription in France and a $9.99 subscription in the US look equivalent on screen, but Apple's proceeds to you differ because French VAT is baked into the €9.99 while the US price is pre-tax. Automatic adjustments do not compensate for this difference. They target the customer-facing number only.

How Apple calculates adjusted prices

Apple's adjustment logic takes the base territory price, applies the current mid-market exchange rate, and then rounds to the nearest point on the local currency price grid. The grid is not purely mathematical — Apple maintains a set of anchor price points in each currency aligned with local pricing conventions: 99-cent endings in USD, round numbers in JPY, .49/.99 structures in EUR. The result is a price that looks "native" in the local market rather than a literal currency conversion.

The precise threshold at which Apple triggers an adjustment is not publicly documented, but analysis in the Apple developer community suggests the system responds to drifts in the 5–10% range from the last-set price point. Apple's developer documentation confirms that adjustments are proposed rather than immediately applied, giving you the review window to accept or override.

When to let Apple adjust — and when to override

Automatic adjustment is a reasonable default if your pricing strategy is anchored to USD revenue equivalence: you want your international prices to track your US price, and you're not managing per-territory positioning actively. The mechanism protects you from currency depreciation making your app cheaper over time without your noticing.

There are several scenarios, though, where accepting the automatic adjustment is the wrong call:

• PPP-calibrated pricing: If you've set India at ₹299 or Brazil at R$24.90 based on local purchasing power rather than USD currency equivalence, an auto-adjustment will override that deliberate decision. Lock those territories manually. For background on why purchasing-power pricing matters in these markets, see Why a $9.99 app shouldn't cost ₹830 in India.
• Volatile-currency markets: In markets like Turkey or Argentina, exchange rates can swing dramatically month to month. Accepting every auto-adjustment means your price moves with the market, which can create subscriber confusion and unexpected renewal price changes. Many operators in these markets choose to lock a price for 6–12 months and review manually. Our post on pricing in currency-volatile markets goes deeper on the Brazil, Turkey, and India cases.
• Competitive anchoring: In some categories, the competitive ceiling in a territory sits well below the USD-equivalent price. If the top productivity apps in Japan are priced at ¥600–¥800, an auto-adjustment that pushes you to ¥1,500 hurts conversion regardless of the mathematical equivalence to your US price.
• Active pricing campaigns: If you're executing a deliberate price increase on your subscription, you want full control over the sequencing and territories. Auto-adjustments running in parallel can produce contradictory price movements that confuse subscribers and complicate the grandfathering rules. Consider locking all territories during any active pricing campaign and re-enabling auto-adjustment once the campaign closes.

RevenueCat's published research on subscription revenue across geographies has consistently highlighted that the highest LTV doesn't come from the territory with the highest nominal price — it comes from the territory where the price-to-perceived-value ratio is right for the local market. Automatic adjustment keeps your nominal prices globally equivalent. It does not keep your value perception globally equivalent.

A practical monitoring workflow

Apple sends email notifications to the developer account's contact address and surfaces alerts inside App Store Connect when a pricing adjustment is proposed. Building a reliable monitoring process around these notifications has three components:

1. App Store Connect notification routing: Navigate to Users and Access → Notifications and confirm that pricing-related alerts are routed to at least one team member who checks email regularly. Finance and Admin roles are typically the default recipients — make sure those inboxes are monitored, particularly over weekends, since Apple can propose adjustments on any day.
2. App Store Connect API price queries: The appPriceSchedules endpoint in the App Store Connect API lets you retrieve the current price for every territory programmatically. Scheduling a weekly fetch and diffing against your expected pricing matrix lets you catch adjustments that went live before you reviewed them. The price-update workflow guide covers the scaffolding for this kind of automated diff. For API access setup, start with the App Store Connect API key guide.
3. Currency rate monitoring: Maintaining a lightweight script that tracks the mid-market rate between USD and your top revenue territories gives you advance warning before Apple proposes anything. If EUR/USD moves 8% in a single month, an adjustment proposal for EU territories is likely coming. You can get ahead of it — decide whether to lock or accept — before the notification even arrives.

For teams managing multiple apps, the API becomes essential. Checking each app's price schedule manually across 150+ territories per app is impractical at any scale. A script that fetches appPriceSchedules for each app and surfaces any territory where the current price doesn't match your internal pricing matrix can run as a daily job and send a Slack alert when it finds a divergence.

How adjustments interact with subscription grandfathering

For subscription apps specifically, pricing adjustments can interact with Apple's grandfathering rules in ways that are worth understanding before they happen rather than after. When Apple proposes an adjustment that raises a subscription price in a territory, existing subscribers in that territory may potentially be subject to Apple's price increase notification flow — even though the increase was not something you proactively initiated through the standard price change process.

Apple's documentation on grandfathering rules addresses developer-initiated price changes clearly; the interaction with auto-adjustment-triggered increases is more nuanced and worth verifying for your specific configuration. The Apple grandfathering rules guide covers the baseline mechanics. If you're running active subscriptions in markets where auto-adjustment is likely to trigger a price increase, testing the subscriber notification behavior in sandbox before it goes live in production is a sensible precaution.

Phiture's research on subscription retention has suggested that unexpected price changes are among the higher-risk churn triggers in emerging and price-sensitive markets. An auto-adjustment that raises your Brazilian subscription from R$24.90 to R$29.90 may look like a rounding error from a USD perspective, but it represents a meaningful change for a subscriber evaluating renewal. Building in a manual review step for any territory that accounts for more than 5% of your subscription revenue is worth the small operational overhead — and is especially important in markets where you've actively invested in PPP-calibrated pricing to drive volume.

Sources and further reading

• Apple — App Store Connect Help (pricing and availability)
• Apple — App Store Connect API reference
• RevenueCat Blog — subscription revenue research and iOS monetization analysis
• Phiture Mobile Growth Stack — app growth and retention research
• AppFollow Blog — App Store operations and metadata tracking
• Sensor Tower Insights — App Store market data and benchmarks