WWDC26 gave subscription apps real new tools: grouped in-app purchase submissions, cross-developer Bundles and Suites, group purchases, and a 12-month commitment plan. But the thing that quietly costs indie iOS developers the most money was left untouched. Apple still does not auto-adjust your auto-renewable subscription prices for local taxes, currency, or purchasing power. If you ship one US price and let Apple convert it, you are leaving conversions and revenue on the table in every market outside the US, and nothing announced this year changes that.
Here is what WWDC26 actually changed, what it did not, and how to price a paid iOS app across the top 25 App Store markets the right way.
On this page
- What WWDC26 actually changed for subscriptions
- The pricing trap WWDC26 did not fix
- How App Store price tiers work in 2026
- Why one US price leaves money on the table
- Four ways to price across markets
- Doing it by hand versus automating it
- What to do before your next submission
- FAQ
What WWDC26 actually changed for subscriptions
The headline subscription updates from the WWDC26 App Store guide:
| Change | What it does | Availability |
|---|---|---|
| Streamlined IAP submission | Group multiple in-app purchases, including subscriptions, into one submission, or combine them with In-App Events, custom product pages, and product page optimization tests | App Store Connect web and API support coming later this summer |
| Subscription Bundles and Suites | Sell access to multiple subscriptions as a single purchase (Bundles), or offer a set of subscriptions only available together (Suites) | Request details coming later this summer |
| Group Purchases | A subscriber buys multiple seats and invites others, each joining from their own account | Coming later this year |
| Volume Purchasing | Sell subscriptions to enterprise and education buyers through Apple Business Manager and Apple School Manager | Coming this fall |
| Monthly subscription with a 12-month commitment | A lower monthly price in exchange for a 12-month commitment | Available now, worldwide except the US and Singapore, on iOS 26.4 and later |
| Retention Messaging | Show value and offers to subscribers at the cancellation moment, with an API for real-time use | Coming this fall |
All useful. None of them set your prices for you.
The pricing trap WWDC26 did not fix
This is the part that matters most and gets the least attention.
For regular app prices and one-time in-app purchases, Apple will periodically auto-adjust local prices when exchange rates or taxes move, and gives at least 14 days notice. For auto-renewable subscriptions, it does not. Subscription prices stay exactly where you set them until you change them by hand, in every storefront, forever.
That has two consequences most indie devs discover too late:
The first is that your global subscription prices are a manual job from day one. There is no "let Apple handle it" mode for subscriptions the way there loosely is for one-time purchases.
The second is that the moment you set a custom price for any storefront, Apple stops applying its automatic tax and currency adjustments for that storefront too. Control comes with full responsibility for keeping those numbers current.
Practical rule: for subscriptions, every storefront price is one you own and maintain by hand, unless you automate it through the API. Apple will not move it for you.
So the real WWDC26 takeaway for a paid app is not Bundles or Suites. It is that worldwide subscription pricing is still entirely on you, and the new grouped submission flow just means you will be configuring more of it in one place.
How App Store price tiers work in 2026
Apple's 2026 pricing system gives you 900 price points across 175 storefronts in 44 currencies. 800 of those points are available by default, with 100 higher tiers up to $10,000 on request. The increments are fixed: $0.10 steps under $10, $0.50 steps from $10 to $50, and $1.00 steps above $50. The lowest point is $0.29, or its local equivalent such as 9 rupees in India.
You set a base price in your base country. Apple then generates comparable prices for the other 174 storefronts using exchange rates plus local tax, and applies regional rounding conventions (US prices ending in .99, Japanese prices rounded, and so on). Picking the wrong base country quietly distorts every other market, and changing it later wipes out any scheduled price changes, so it is worth getting right at the start.
Why one US price leaves money on the table
Apple's auto-conversion mirrors the dollar value of your price. It does not account for what people in a given country can actually pay. The gap between an auto-converted price and a purchasing-power-appropriate one routinely runs 2x to 3x in exactly the markets where your app most needs to convert.
A $19.99 base tier illustrates it (purchasing-power figures from PricePush reference data, April 2026):
| Market | Auto-converted price | Purchasing-power price | Difference |
|---|---|---|---|
| United States | $19.99 | $19.99 | 0% |
| Germany | 22.99 euro | 17.49 euro | about 24% lower |
| Brazil | R$129.90 | R$49.50 | about 62% lower |
| India | 1,899 rupees | 659 rupees | about 65% lower |
In India, an auto-converted price can land at 7 to 13 percent of median monthly income, against roughly 0.4 percent for the same dollar amount in the US. That is the difference between an impulse tap and a budget decision. Aligning prices with local purchasing power commonly lifts international revenue by 20 to 50 percent in price-sensitive regions, which is why it is one of the highest-leverage settings most developers never touch. It pairs naturally with localizing the app itself: a translated UI plus a local price reads as a properly localized product, a point we cover in the Xcode 27 translation agents guide.
Four ways to price across markets
There is no single correct curve, but most paid apps fit one of four strategies. Pick one as a starting point, then fine-tune individual markets.
Equal worldwide keeps 100 percent of your US price everywhere and leans on Apple's standard conversion. It is the simplest option and the one to beat, since it ignores ability to pay entirely.
Western premium holds full price in tier-1 markets (US, EU, UK, Australia, Japan, Korea) and ramps discounts down to roughly 50 percent in markets like India and Brazil.
Netflix-style mirrors the published ratios of a large subscription business. Some markets pay more than the US, most major Western markets land within about 10 percent of US, and emerging markets discount steeply, on the order of 35 percent in India and Brazil.
Indie sustainable is a gentler curve tuned for small SaaS: full price in major Western markets, about 50 percent in India, about 40 percent in Turkey. It is broad enough to convert without diluting your headline price.
Whatever you pick, round to a valid Apple price point and respect local conventions (prices ending in .90 in Brazil, familiar round numbers in Japan and India). And review the numbers quarterly, or monthly in high-inflation markets like Turkey and Argentina, because Apple will not move subscription prices for you.
Doing it by hand versus automating it
Setting purchasing-power prices across 25 markets by hand is genuinely miserable. Even five products across the major storefronts can mean well over a thousand individual price entries per refresh, and each one has to match a product ID that lines up between App Store Connect and your billing layer. This is the afternoon most indie devs lose to "why is my paywall empty?" The product is configured in one place and not the other, and the two never quite agree.
The clean way to do it is to drive both sides through their APIs so they cannot drift apart. App Store Connect has an API for creating subscription products and setting territory prices (with the new grouped submission flow getting web and API support later this summer), and RevenueCat has an API for the matching project, entitlement, offering, and packages. Set the base price once, generate the per-territory prices from a strategy, push them to App Store Connect, and create the matching RevenueCat objects in lockstep. The code, the store, and the billing layer agree on the first build.
Practical rule: drive App Store Connect and RevenueCat from their APIs, not by hand. When the store and the billing layer are generated from one source, product IDs and prices cannot silently drift apart.
That is exactly what Spaceport does. It generates a production-ready SwiftUI Xcode project with RevenueCat already wired up, then creates and prices your subscriptions across the top 25 App Store markets using one of the four strategies above, pushing everything to App Store Connect and RevenueCat through both APIs. You own the generated code outright, with no runtime dependency on Spaceport. It is a one-time purchase, not a subscription. If you would rather wire it yourself, the open-source RevenueCatSubscriptionKit package handles the subscription layer on its own.
What to do before your next submission
WWDC26 made App Store submissions tidier and gave subscription apps new ways to package and sell. It did not make worldwide pricing automatic. So before you ship your next paid iOS app:
- Choose your base country deliberately, since it anchors every other market and is painful to change later.
- Decide on a pricing strategy rather than defaulting to one US price everywhere.
- Set purchasing-power prices in your highest-potential markets, especially India, Brazil, and Turkey.
- Drive App Store Connect and RevenueCat from their APIs so product IDs and prices stay in sync.
- Put a quarterly pricing review on the calendar, because no one at Apple is going to do it for you.
While you are tidying the store listing, locale-correct screenshots are the other half of a localized launch. Our App Store screenshot automation guide covers capturing them across every market in one command, and the App Store optimization tips post covers the broader listing surface.
FAQ
Does Apple automatically set subscription prices for each country?
No. For regular app prices and one-time in-app purchases Apple periodically auto-adjusts local prices for currency and tax. For auto-renewable subscriptions it does not. Subscription prices stay where you set them in every storefront until you change them by hand, and WWDC26 did not change that.
Did WWDC26 add automatic worldwide subscription pricing?
No. WWDC26 added grouped IAP submissions, Bundles and Suites, group purchases, volume purchasing, a 12-month commitment plan, and retention messaging. None of them price your subscriptions per market. Worldwide subscription pricing is still a manual job unless you drive it through the App Store Connect and RevenueCat APIs.
What is the best base country for App Store subscription pricing?
Your base country anchors the auto-generated prices for the other 174 storefronts, so pick the market that represents your primary audience and revenue, usually the US for a global app. Changing it later wipes out scheduled price changes, so choose deliberately at the start.
How often should I review subscription prices?
Quarterly for most markets, and monthly in high-inflation markets like Turkey and Argentina. Because Apple does not move subscription prices for you, stale prices silently drift away from local purchasing power over time.
What is the difference between Bundles and Suites?
A Bundle sells access to multiple subscriptions as a single purchase. A Suite offers a set of subscriptions that are only available together. Both are new at WWDC26, with request details coming later in the summer.
The single highest-leverage setting in a paid iOS app is the one most developers never touch. WWDC26 is a good moment to finally touch it.
Spaceport generates production-ready SwiftUI Xcode projects with the boring-but-essential parts of a paid iOS app already wired up: RevenueCat subscriptions, onboarding, sign-in, analytics, an AI assistant scaffold, and App Store Connect pricing pushed across 25 markets with one of four purchasing-power-aware modes. The pricing workflow in this post is exactly what it automates. From an indie iOS dev, for indie iOS devs.