Apple grandfathering rules for subscription price changes

Apple gives you three distinct paths when you raise a subscription price — grandfathering, consent-required increases, and automatic small increases. Understanding the churn math and LTV trade-offs of each prevents you from triggering a revenue loss larger than the gain you were chasing.

Every developer eventually faces the same dilemma: you launched at a price that made sense two years ago, but inflation, App Store commission changes, or a growing feature set make a price increase unavoidable. The good news is that Apple gives you structured options. The bad news is that picking the wrong one — or misunderstanding how grandfathering interacts with your subscriber cohorts — can trigger a churn wave that erases the revenue gain you were chasing.

This post walks through each price-change pathway Apple offers, explains when consent is legally required, models the LTV trade-offs of grandfathering, and gives you a practical decision framework before you touch App Store Connect.

The three price-change paths Apple gives you

When you update a subscription price in App Store Connect, Apple presents three distinct outcomes for your existing subscribers. Understanding them at a mechanical level is the foundation for every decision that follows.

The first option — preserving the price for existing subscribers — is what most developers mean when they say "grandfathering." Your existing subscriber base is protected; only new subscribers pay the higher price. Apple sends them an informational email confirming their subscription is unaffected.

The second option requires active consent. Apple emails subscribers with a call-to-action; if they do not respond before their next billing date, the subscription lapses. This is unavoidable for large increases that fall outside Apple's automatic threshold, and it is the highest-stakes option in your toolkit.

The third option — Apple's automatic price increase pathway, introduced in 2022 — lets developers make modest, periodic adjustments without forcing a consent moment. The thresholds Apple applies vary by currency and are documented in App Store Connect Help, but the general principle is that the increase must stay within a defined ceiling in both absolute and percentage terms. Apple documentation confirms the feature is designed to accommodate inflation-style adjustments.

When Apple requires subscriber consent

Apple's consent requirement is not arbitrary. It reflects consumer-protection obligations across dozens of jurisdictions, many of which mandate that subscription holders must affirmatively agree to a price change before they are charged the new rate.

Consent is required when:

• The new price exceeds Apple's automatic increase ceiling for that currency and subscription period.
• You are transitioning a subscriber from an introductory or promotional price to the standard price in a way that constitutes a material change.
• The price change affects markets where Apple's local regulatory obligations demand explicit consent.
• You make changes to a subscription group structure that alter the subscriber's effective pricing.

When consent is required, Apple controls the notification timing and the UI copy. You cannot customize the consent email subject line, body, or call-to-action text. What you can control is when you submit the change in App Store Connect — and therefore how much lead time subscribers have before their next billing date. Apple recommends giving subscribers at least 30 days of notice; most practitioners who have managed consent-required increases aim for 45–60 days ahead of the effective date to leave room for errors and to allow in-app communication to land first.

Consent flows carry a real cost. Analysis published by RevenueCat and discussed across indie developer communities consistently suggests that a meaningful share of subscribers who receive a consent-required notification do not take action — and therefore churn. The exact share varies by app category, price sensitivity, audience engagement, and the magnitude of the increase. Developers planning a consent-required change should model scenarios where 15–35% of their existing subscriber base does not re-consent.

For a mature app with a stable subscriber base, losing a quarter of existing subscribers to a price change is often worse than the revenue gain from the higher price — at least in the short term. Modeling this properly requires knowing your average subscription tenure and LTV, which is the subject of the next section.

Grandfathering math: what it costs you over 12 months

Grandfathering preserves subscribers, but it comes with a quiet long-term cost: you end up running two revenue tiers in parallel, and the old tier shrinks only as fast as subscribers voluntarily churn. For a sticky app with low natural churn, a large fraction of your subscriber base can remain at the old price for 18–24 months.

Consider a simplified model with a baseline of 1,000 existing subscribers, an old monthly price of USD 4.99, and a target price of USD 7.99:

This is a deliberately simplified illustration — real LTV math needs to incorporate reactivation rates, new subscriber acquisition at the new price, and the compounding effect of higher ARPU on future cohorts. But the directional conclusion holds: grandfathering preserves subscribers but delays ARPU improvement, while consent-required changes front-load churn but immediately raise ARPU for the surviving cohort. The automatic small-increase pathway often wins on 12-month math when the ceiling allows it, because you capture the full existing base at the new price with modest churn.

The math also looks meaningfully different by region. If you are working through whether a price increase makes sense in a specific territory, the AppsOps territories dashboard surfaces territory-level subscriber data, and the post on why iOS subscription churn is higher in low-PPP markets covers how price sensitivity varies across currency zones. A consent-required increase that is manageable in the US may be devastating to your subscriber base in Brazil or Turkey.

A practical framework before you submit the change

Before making any change in App Store Connect, work through these four questions:

1. What is the size of the increase? If the increase falls within Apple's automatic threshold for that currency, the automatic pathway is available. If it exceeds the threshold, you must choose between grandfathering and consent-required.

2. What is your subscriber tenure distribution? Pull your cohort retention data. If median subscriber tenure is under 6 months, grandfathering loses much of its protective value — those subscribers will churn naturally before the price gap matters significantly. If median tenure exceeds 18 months, grandfathering creates a meaningful multi-year ARPU drag. You can get a rough read from the AppsOps pricing tool by layering in cohort-level revenue data.

3. What is your likely re-consent rate? Look at your email open rates, push notification engagement, and historical voluntary upgrade behavior. Apps with highly engaged audiences tend to see better re-consent rates. Without a prior data signal, model conservatively: assume 25–30% non-consent churn as a baseline.

4. Can you sequence this increase? A large jump in one move — say, $4.99 to $9.99 — is much harder than two smaller increases spread 12 months apart. The automatic pathway can handle modest annual adjustments; reserving a consent-required event for a single larger jump, ideally timed to a major feature release, generally yields better outcomes than multiple consent events in a short window. For guidance on setting test prices and measuring subscriber response before committing to a change, see the post on how to A/B test iOS app prices safely.

What Apple communicates to subscribers — and what you cannot control

One aspect of the process that catches many developers off guard is how little control they have over subscriber-facing communication. Apple writes and sends the price-change notification emails. You cannot customize the subject line, the body copy, or the call-to-action wording. For consent-required increases, Apple sends a follow-up reminder if the subscriber has not acted. The timing of these reminders is Apple-controlled.

What you can do to soften the impact:

• Use in-app messaging — a modal or a banner — to explain the price change and its rationale before the Apple email arrives.
• If you collect email addresses directly (via your own account system), send a pre-announcement from your own CRM that frames the value of your app before subscribers receive a transactional Apple notification.
• Update your App Store listing and paywall copy to reflect the new price clearly, so subscribers who return to the app mid-consent window understand the context.
• Monitor your App Store reviews in the days following the notification. A spike in negative reviews tied to the price change is an early signal that your communication strategy needs adjustment — consider an in-app response or a temporary reactivation offer for churned subscribers.

Subscription analytics platforms like RevenueCat surface granular data on how subscribers respond to price-change events: consent rates, time-to-churn after notification, and reactivation rates for subscribers who initially did not re-consent. Instrumenting this before you initiate a price change gives you the baseline data you need to evaluate the outcome — and to plan the next price-change cycle with better information.

Sources and further reading

• Apple Developer — App Store subscriptions overview and pricing guidance
• Apple App Store Connect Help — Managing auto-renewable subscription pricing
• RevenueCat Blog — Subscription analytics, pricing, and churn research
• Phiture Mobile Growth Stack — App Store subscription monetization insights
• AppFollow Blog — App Store review monitoring and subscription strategy
• Apple Developer News — App Store policy updates and release notes