Apple just gave you three new ways to sell. All three still break at the border.

Yesterday Apple shipped the biggest change to how you sell subscriptions since 2016. I read every line of it. Not one decides what your app costs in India.

The WWDC 2026 keynote (June 8) opened the App Store up in ways developers have been asking for since auto-renewable subscriptions launched. App Store Bundles you can build with other developers. Group purchases, where one person buys seats for a team. Volume deals for schools and companies. The press is calling it the most significant structural change to how developers sell apps in a decade, and that's fair.

But read the list with one question in mind: which of these decides the price a customer in São Paulo actually pays? None of them. Every feature changes how you package or discount a price. Not one changes the number underneath. And the headline feature, cross-developer bundles, makes the pricing problem worse, not better.

If you ship subscriptions to both stores, here's what changed at WWDC 2026, what didn't, and the one thing you have to fix before any of it converts.

What Apple actually shipped, grouped by what it does

Apple's June 8 announcement is a long list. Strip it down to the parts that touch money and you get three new ways to sell:

• App Store Bundles and Suites. In Apple's words, bundles "give developers the ability to partner together and offer users more for less," so a customer can "subscribe to multiple favorite apps from different developers at a better price." This is the first time a bundle can cross developer accounts. Ships this year.
• Group purchases. In Apple's words, they "let a subscriber buy seats as a single purchase and then invite others to access the subscription." Built on StoreKit 2. Coming this winter.
• Volume purchasing. Enterprise and education buyers procure subscriptions at scale through Apple Business Manager and Apple School Manager. Available this fall.

Around those, Apple added the tools to support them: two new StoreKit 2 configuration options for multi-user subscriptions, Retention Messaging (offers shown during the cancellation flow), and Featuring Nominations that let game developers pitch limited-time discounts to the editorial team. (AppleInsider and The Next Web have good rundowns of the full set.)

Now line them up. Bundles are a new container. Group and volume are bigger containers. Retention messaging and game featuring are discounts. Every single one starts from a base price you set, per storefront, and does something to it. Not one of them sets that base price for you. Apple operates the App Store in 175 storefronts. The price in each of those 175 is still your job.

The one thing none of them touch: the price itself

Here is the part that trips up almost every developer I talk to. Apple localizes the storefront. It localizes the language, the currency symbol, the tax handling. It does not localize the price.

By default, your base price gets converted at the exchange rate and dropped onto the nearest price point in each storefront. So $19.99 per month converts to about ₹1,900 in India at the June 2026 rate (the rupee sits near 95 to the dollar). The locally affordable number, the one a customer there would actually pay without flinching, is closer to ₹500 on a purchasing power parity basis. That gap, ₹1,900 versus ₹500, is almost 4x, and it's the difference between convert and bounce.

Bundles, group plans, and volume deals all inherit that base price. Apple sets the bundle's discount percentage. It does not set the per-country base the discount applies to. So a 20% bundle discount on a price that's already 3x too expensive in Argentina is still 2.4x too expensive in Argentina. New container, same contents, still priced wrong everywhere you didn't fix it by hand.

This is not a bug in WWDC 2026. It's the same line Apple has always drawn. The storefront is Apple's job. The price is yours. The new features just give you more places to get it wrong.

Cross-developer bundles: two prices, two ladders, 175 storefronts

The bundle feature is the one I'd watch closely, because it's the one where the pricing problem compounds instead of staying flat.

Think about what a cross-developer bundle "at a better price" actually requires. Both apps need a base price set in each of the 175 storefronts. The bundle discount has to make sense in every currency. And two independent developers' price ladders have to line up across all 43 currencies the App Store supports. Apple's price point system has 900 fixed points since the 2022-23 overhaul. You don't get to pick an arbitrary number. You map to the ladder.

Now suppose App A is FX-converted (too high) in Brazil and App B is PPP-aligned. The bundle in Brazil is incoherent: the "discounted" combined price might still land above what a local competitor charges for one app at full price. The "more for less" promise only feels like a deal if both base prices were locally right to begin with. A bundle of two wrong prices is two wrong prices stapled together, now sharing one checkout.

And you're no longer only responsible for your own ladder. You're trusting your bundle partner's. If they flat-priced their app in USD everywhere, your carefully localized prices get dragged into an incoherent combined offer the moment you bundle. The work didn't disappear at WWDC. It doubled, and half of it is now someone else's discipline.

Group and volume: the unit got bigger, so did the gap

Group purchases and volume deals have the same shape. They make the thing you sell bigger, which makes a wrong base price cost more, not less.

A 10-seat group subscription in Turkey at an FX-converted price is the affordability gap times ten. One mispriced seat is a shrug. Ten mispriced seats in a single transaction is the reason a team in Istanbul never starts the purchase. Volume purchasing through Apple Business Manager and Apple School Manager is the same story at institutional scale. A school district in Indonesia and a company in Germany should not be quoted the same seat price converted from one USD number. They have completely different ability to pay, and now they can both buy in bulk in one click.

The pattern holds across every feature: the bigger the unit you sell, the more a wrong base price compounds. Volume and group features make localized pricing more important, not less. They raise the stakes on the exact thing Apple still leaves to you.

You can't discount your way out of a wrong anchor

Retention Messaging and Featuring Nominations are both discount tools. Retention Messaging shows a subscriber an offer when they go to cancel. Featuring Nominations let game developers propose a limited-time discount for editorial placement. Both are useful. Both have the same blind spot.

A discount only works when the anchor is right. An introductory offer or a retention coupon off a price that was never localized is a discount off the wrong number. If your base price already fits the market, a retention offer is a nudge that saves a subscriber. If your base price is 3x too high in a country, that retention offer is you papering over a pricing mistake with a coupon, every single time someone tries to leave. You'll burn margin discounting a price that should have been lower from day one.

Get the base price right and discounts become a lever. Get it wrong and discounts become a tax you pay on every churned user in every market you never localized.

What actually changed for your pricing (nothing, and that's the tell)

I've shipped paid apps to both stores for 14 years. Every time Apple changes the store, I get the same question from other developers: does this finally fix pricing? It never does, because Apple's job is the storefront, not your number.

Every feature Apple announced at WWDC 2026 quietly assumes you've already set the right price in every country. The price points, the per-storefront base, the rounding so a Korean won or Japanese yen price doesn't read like a typo, the quarterly drift as exchange rates move under you, all of it is still yours. WWDC gave you more reasons to get localized pricing right and zero new tools to do it.

This is the same move as Apple's 12-month commitment subscriptions back in April: a new packaging option that does nothing about the underlying price. It's the same gap Google left when it cut subscription fees to 10% and most indies still paid 15% effective. The store gives you new mechanics. The price stays your problem.

That layer is exactly why I built PricePush. It calculates PPP-based prices for 190+ countries, handles the currency quirks (Apple bills some regions in USD and others in local currency, and PricePush knows which is which), applies per-market rounding so prices look native, and pushes the whole grid to App Store Connect and Google Play in one click. Set the base right once, and every new selling mode Apple ships sits on top of a number that already fits the market. If you want the full method behind that, the complete guide to localized pricing for mobile apps and the App Store pricing by country reference walk through it.

Use the new features. Fix the price first.

Build the bundles. Turn on group and volume if they fit your product. They're genuinely good additions, and the developers who were asking for them have a real reason to be happy this week.

But all three sit on a base price you still own, and the default base price is wrong across most of the world. So the order matters. Localize first. Then bundle, group, and discount on top of numbers that already fit each market, and every WWDC 2026 feature compounds your revenue instead of multiplying one pricing mistake across more SKUs and more countries.

You can run your own app's prices through PricePush free and see the per-country gap before you change anything. Start free, no credit card, and check what your $19.99 actually costs a customer in India, Brazil, and Turkey today. If the gap surprises you, the pricing page shows the plans, including the founding lifetime offer.

Antonio, Founder of PricePush