How to audit your App Store pricing after Apple’s automatic currency adjustments

Apple quietly re-prices your app in dozens of storefronts when exchange rates shift. Here is a step-by-step audit process — using the App Store Connect dashboard and the ASC API — to catch misalignments before they erode revenue or lose users.

Apple’s automatic currency adjustment mechanism is one of the most underappreciated threats to a carefully calibrated global pricing strategy. You can spend weeks fine-tuning your price points using PPP data and conversion math — then a single macro currency event silently resets your Turkish, Brazilian, or Indonesian price to a number you never chose.

This guide walks through a structured pricing audit: what triggers Apple’s auto-adjustments, how to spot the changes, how to evaluate whether the new price is better or worse than your original intent, and how to lock in manual overrides using both the App Store Connect dashboard and the ASC API.

How Apple’s automatic currency adjustments work

When you create a subscription or in-app purchase in App Store Connect and choose “globally equivalent pricing,” you are telling Apple to derive prices in all 175+ storefronts from your base currency — typically USD. Apple maintains a set of discrete price points in each territory and maps your base price to the nearest equivalent. These are not a continuous curve; they are specific steps Apple has defined, and your price must land on one of them.

Apple periodically reviews exchange rates and adjusts prices in affected storefronts to maintain parity with the base price. When a currency depreciates significantly — the Turkish lira, Argentine peso, and Nigerian naira have historically seen the steepest swings — Apple bumps the local price to the next higher price point to compensate. If a currency appreciates, prices may decrease, though this is less common in practice.

Apple sends an email notification to the account holder and any admin team members before these adjustments take effect. In practice, however, these emails often land in a shared alias, get filtered as marketing, or arrive during a period when no one is actively watching. The adjustments happen regardless of whether you acknowledge the notification.

When to run a pricing audit

Rather than auditing on a rigid fixed schedule, tie your audit cadence to events that signal exchange rate volatility or unusual subscriber behavior:

• Central bank rate decisions in emerging markets. Turkey’s TCMB, Brazil’s Copom, and India’s RBI each hold scheduled policy meetings; rate decisions can move local currencies several percent in a single session. A major policy surprise is a reliable audit trigger.
• Apple’s own email notifications. Even if you cannot act immediately, log these as audit triggers in your team’s task tracker so they do not get lost.
• A spike in churn from a specific storefront. RevenueCat data has consistently shown that churn rates in low-PPP markets are sensitive to even modest price increases. A sudden uptick in cancellations from Turkey or Brazil often means a price jump that customers found untenable, not a product quality issue.
• Revenue anomalies in Sales and Trends reports. A drop in net proceeds from a market where download volume is stable is a strong signal that price — not demand — has shifted. See our guide on reading Apple Sales and Trends for pricing decisions for a territory-level breakdown approach.
• Quarterly reviews, at a minimum. Even without a triggering event, run a full territory audit every quarter. Currency drift is slow enough that monthly checks may miss it, but quarterly is usually sufficient to catch changes before they compound.

Step 1: Pull your current prices with the ASC API

The App Store Connect dashboard lets you view prices territory by territory, but navigating 175+ storefronts manually is impractical for any app with broad distribution. The ASC API’s subscription price endpoints return your current pricing configuration in machine-readable form. Combined with a reference file of your intended prices, you can build a territory-by-territory diff that surfaces every divergence in seconds.

At a high level, an audit script does the following:

1. Authenticates with the ASC API using a JWT signed with your private key. If this is new territory for your team, see our walkthrough on App Store Connect API JWT authentication before starting.
2. Fetches the list of subscription products (or IAP products) for your app using GET /v1/subscriptions.
3. For each product, retrieves the active price schedule per territory via GET /v1/subscriptionPrices.
4. Compares retrieved prices against your “target” prices — the prices you intended to charge — stored in a CSV or JSON reference file that you maintain separately.
5. Flags any territory where the current live price differs from the target, and outputs a report sorted by revenue impact.

You do not need to build this from scratch. If you have already set up a price-update workflow with the ASC API, adding a comparison step is a natural extension of what you already have. The workflow authenticates, fetches, writes — the audit step is just a diff against your reference file inserted before the write.

Step 2: Evaluate each flagged territory

Not every price change Apple makes is harmful. Before reverting a change, ask three questions for each flagged territory:

Did the local currency genuinely depreciate? If Apple raised your Turkish price from ₺199 to ₺219 because the lira lost 10% of its value, the new price may actually be the right economic outcome — ₺199 was already underpriced in USD terms at the new exchange rate. Reverting it would mean you are now charging even less in real terms than you intended.

Does the new price exceed the local affordability ceiling? Research published by Phiture and RevenueCat suggests that subscription churn rates in low-PPP markets are highly sensitive to price-to-income ratios. If an auto-adjusted price pushes past the threshold local consumers can absorb, the revenue loss from cancellations may outweigh the per-subscriber uplift.

Does the new price land on a clean local number? Consumers in many markets anchor on round numbers. A price of ₺219 can feel arbitrary compared to ₺199 or ₺249. Pricing psychology work in emerging markets suggests that off-step prices — ones that do not match local “charm” conventions — underperform equivalent round numbers.

The table below summarizes a decision framework for the most common scenarios:

Step 3: Apply manual overrides where needed

Once you have decided what each flagged territory’s price should be, apply manual overrides using the POST /v1/subscriptionPrices endpoint. Specify the territory, the price point ID for your chosen price, and set the start date to immediately (or a scheduled future date if you want to coordinate with a marketing push). The key difference from globally equivalent pricing is that a manually set price is pinned — Apple will not override it in future auto-adjustment runs.

The tradeoff of pinning is maintenance overhead. A price you set manually in Turkey a year ago may now be significantly below or above your intended USD equivalent, because you are no longer tracking the exchange rate on Apple’s behalf. Consider building a quarterly reminder into your workflow to review whether manually managed prices still reflect your pricing intent — even a simple calendar event for each quarter is better than nothing.

For teams managing pricing across a portfolio of apps or a large number of territories, the AppsOps pricing dashboard provides territory-level overrides with an audit trail, making it easier to track who changed what and when without building bespoke tooling.

Step 4: Build ongoing monitoring so audits stay lightweight

A one-time audit is a snapshot, not a system. Apple’s auto-adjustments are ongoing; currency markets do not stand still. After completing an initial audit, put lightweight monitoring in place so the next audit takes minutes rather than days:

• Redirect Apple’s notification emails to a monitored inbox or Slack channel. The account holder email should go somewhere that is actively watched, not a shared alias where it can accumulate unread.
• Run a weekly ASC API price pull that diffs current prices against your reference file and sends a Slack message or email alert when any territory diverges by more than a defined threshold. A cron job or CI pipeline step is sufficient; this does not require a sophisticated system.
• Watch storefront-level churn in your analytics tool. A sudden increase in cancellations from a single market — especially a volatile-currency market — is one of the fastest early-warning signals that a price change has surprised customers.
• Add a pricing section to your quarterly business review. Even a 15-minute pass through the territory-level proceeds data in Sales and Trends is enough to catch slow-moving drift that the automated checks might classify as within tolerance.

Common mistakes to avoid

Treating the audit as a one-time exercise. Currency markets move continuously. An audit that takes two weeks to complete may already be partially stale by the time it is done. Build a lightweight automated check that runs weekly, even if a full manual review only happens quarterly.

Reverting all changes without evaluating them. If Apple raised your Turkish price and the lira has genuinely depreciated, reverting to the old price means you are now charging even less in USD terms than you originally intended. Accept economically justified changes; override only where Apple’s adjustment overshoots your affordability target or breaks a clean local price point.

Ignoring markets below your current revenue threshold. Small-revenue markets today can become significant as purchasing power rises. Countries like Vietnam, Indonesia, and the Philippines have growing middle-class consumer bases and rising app spending. Setting a hostile or incoherent price impression in these markets during their growth phase is a recoverable mistake, but it takes time to fix a reputation for poor value.

Not documenting the intent behind manual overrides. Without documentation, a new developer looking at your pricing configuration will not know whether Turkey’s ₺249 price was a deliberate PPP-based decision or a leftover from a test. A comment in your pricing reference file, a Notion page, or an internal changelog — any audit trail is better than none and costs almost nothing to maintain.

Sources and further reading

• Apple Developer — Set a subscription price (App Store Connect Help)
• Apple Developer Documentation — App Store Connect API overview
• RevenueCat — Global pricing strategies for subscription apps
• Phiture — App Store subscription pricing strategies
• Sensor Tower — App Store pricing insights and benchmarks
• AppFollow Blog — App Store optimization and subscription analytics