Communicating iOS subscription price changes to users: Apple’s notifications, your in-app messaging, and the consent window

A practical guide to the full communication sequence when you raise your iOS subscription price—what Apple tells subscribers automatically, when you should add your own messaging, and how to handle users who don’t consent.

Raising your iOS subscription price is a two-step process. Most developers focus entirely on the first step—picking the new price, updating App Store Connect, and saving. The second step—the communication sequence that follows—is where price increases succeed or collapse.

Apple handles some of the communication automatically, but the system has clear gaps. Fill those gaps well and a 30% price increase can land quietly, with the majority of subscribers renewing. Ignore them and you'll see a spike of cancellations and negative reviews within 48 hours of Apple's emails going out.

This guide covers what Apple sends, when it sends it, what you should layer on top of it, and how to manage the consent window that Apple requires for certain types of price increases.

What Apple communicates automatically—and when

When you raise your iOS subscription price in App Store Connect, Apple's behavior depends on whether the increase requires subscriber consent or not.

Increases that require consent apply when you raise the price beyond Apple's defined threshold in a given period, or in certain markets where Apple mandates explicit agreement. In this mode, Apple sends an email to every affected subscriber explaining that the price will change and that they must agree to the new price by their next renewal date—or their subscription is cancelled automatically rather than renewed at the higher amount. Apple also displays an in-app prompt asking the user to approve the change.

Auto-renewing price increases—raises that fall below Apple's consent threshold—are also communicated via email, but the subscriber doesn't have to actively agree. Their subscription renews at the new price unless they cancel before the renewal date. Apple introduced a cap on how large an auto-renewing increase can be to prevent developers from bypassing the consent mechanism by making incremental raises.

In both the consent-required and auto-renewing cases, Apple's email typically arrives within 24 to 72 hours of your App Store Connect change taking effect. The email carries Apple branding, names the app, states the old and new price, and includes the upcoming renewal date. Many subscribers don't immediately recognize which app it's for—especially if the app name is generic or if they hold multiple subscriptions across the App Store.

Apple also shows an in-app notice the next time the subscriber encounters a purchase prompt inside your app, though the timing of this prompt relative to the email is not developer-controlled.

The gaps Apple's communication doesn't fill

Apple's emails are functional but impersonal. They state facts and provide a call to action. What they don't do:

• Explain why the price is increasing
• Remind the subscriber of the value they've received
• Offer alternatives such as downgrading to a cheaper tier
• Acknowledge the relationship the user has built with your product over time
• Provide a way to reach your support team with questions

For most apps in productivity, health, and utility categories, users have built habits around the product. They're not evaluating it from scratch. A cold Apple email asking them to authorize a higher payment triggers re-evaluation of the subscription's value—often in a moment when your app is not open and is not reminding them why they love it.

Your job is to reach the user before Apple's email does—so that when they see it, the context is already set, they understand the reason, and they've had time to make peace with the change. This is the core principle behind a three-phase communication sequence.

The three-phase communication sequence

A well-executed price increase uses three distinct phases, timed relative to when your App Store Connect change will take effect.

Phase 1: Your pre-announcement

Write your pre-announcement for someone who is a satisfied user but hasn't thought about your subscription in months. Lead with the value they've been receiving, not the price change. Keep the in-app modal under 150 words—longer copy loses people on mobile.

A reliable structure: "You've [used feature X / completed Y sessions / saved Z hours] with [App Name] this year. To keep [specific feature] and [specific feature] improving, we're adjusting our subscription price from $N to $N starting [date]. [Optional sentence on what's changing or improving.] Thank you for being part of this. [CTA to subscription management or 'Got it' dismiss]."

Avoid vague language ("adjusting our pricing structure"), pure corporate framing ("due to increased operational costs"), or burying the actual dollar amounts. State the old and new price explicitly. Users who discover the real number from Apple's email—after your messaging has been evasive—feel deceived, and that translates directly into negative reviews and cancellations.

Phase 3: The follow-up reminder

This phase is often skipped, but for consent-required price increases it can recover 10–20% of subscribers who missed the original notification. Many users don't open Apple's automated emails: they get filtered to promotions tabs, missed in a high-volume inbox, or skimmed without action. Your follow-up puts the consent action back in front of them inside the app, where they're already engaged.

Make the action one tap. A deep link to the subscription management page removes friction. On iOS you can open the App Store subscription management screen directly:

UIApplication.shared.open(URL(string: "https://apps.apple.com/account/subscriptions")!)

Keep the follow-up message brief and non-pressuring: "A quick note: our subscription price is changing on [date]. Tap here to review the details and confirm your subscription." Don't repeat the full pre-announcement copy—that risks feeling like harassment. Just surface the action.

Localization: your messaging needs translation too

Apple's emails are localized automatically—they arrive in the user's device language and display currency correctly for the subscriber's region. Your in-app pre-announcement almost certainly isn't localized unless you've specifically built that, and a price increase is the wrong moment to deliver a machine-translated message.

At minimum, localize the pre-announcement and follow-up reminder into your app's top five markets by subscriber count. For many subscription apps this is US English, Japanese, German, French, and Brazilian Portuguese—but verify against your territory data in App Store Connect's Sales and Trends reports before assuming. The guide to IAP localization fields covers the full set of surfaces to review.

Handling subscribers who don't consent

For consent-required increases, a portion of your subscriber base will neither consent nor explicitly cancel—they'll simply not respond. At the renewal date, Apple cancels their subscription rather than charging the new price. They enter an expired state, not a cancelled one, which matters for how you treat them downstream.

Three practical considerations:

Don't immediately strip all access. If a subscriber's plan expires due to non-consent, consider whether to show a targeted win-back offer before removing features. Apple's win-back offer system can present promotional pricing to lapsed subscribers through the same introductory-offer infrastructure—this is a separate flow from the price increase itself. The iOS subscription win-back guide covers configuration and timing for this.

Track non-consent as a distinct churn cohort. Non-consent churn is behaviorally different from involuntary churn (payment failure) and deliberate cancellation. These users may be price-sensitive, or they may have simply missed the email. They warrant different reacquisition messaging—specifically, messaging that surfaces the new price clearly and gives them a reason to reconsider rather than offering a generic discount.

Expect delayed reactivation. Developer community data shared across iOS forums suggests a meaningful fraction—estimates range from 15% to 25%—of non-consent churned subscribers resubscribe within 90 days, often at the new price, once they realize they've lost access to features they relied on. Don't write them off as permanently lost at the moment they lapse.

Managing the review spike

Even well-executed price increases generate some negative App Store reviews. This is normal and predictable. The risk is an unmanaged spike—ten or more one-star reviews in a 48-hour window citing the price change—which can depress your rating and create a visible signal problem for prospective users during a period when your existing base is already re-evaluating the relationship.

Prepare a response template before the increase goes live. A strong response acknowledges the frustration, briefly restates the value rationale in one sentence, and offers a support contact for users with specific questions. Apple's response interface is public, so your reply is visible to prospective subscribers as well as the reviewer. Measured, empathetic responses to pricing complaints often do as much for conversion reassurance as the review itself would have harmed it.

Monitor review volume in the two weeks following the Apple email. A spike concentrated among users who appear to be lapsed (no recent app opens before the review) often indicates that those users received Apple's email without having seen your pre-announcement first. This is a diagnostic signal: it means your pre-announcement reach was lower than expected, and you should investigate notification permission rates or your push delivery logs before the next price change.

Sources and further reading

• Apple Developer: Auto-renewable subscriptions overview and pricing guidance
• Apple App Store Connect Help: Managing subscription pricing and territory settings
• Apple Developer Documentation: App Store Server Notifications (including PRICE_INCREASE and REFUND notification types)
• RevenueCat Blog: Subscription analytics, pricing strategies, and cohort modeling for iOS developers
• Phiture Mobile Growth Stack: ASO and subscription retention research and playbooks
• AppFollow Blog: App Store review management and reputation during pricing events