Subscription price increase consent review checklist
A subscription price increase is not just a finance update. It can require subscriber consent, change renewal behavior, and create support load if the app's entitlement logic is not ready.
Before raising prices, classify whether subscribers need to consent, when Apple notifies them, what happens if they do not consent, and how the app handles entitlement states. Apple App Store Connect guidance says some price increases require consent before the next renewal for the subscription to renew. AppReviewReady interpretation: build a consent-risk calendar before scheduling the change.
Classify the price change before scheduling
List current price, new price, storefronts, subscriber cohorts, billing periods, introductory offers, promotional offers, and grandfathering decisions. A global increase can have different user impact across markets.
Do not treat consent as a vague legal issue. It affects whether a subscription renews, whether access continues, and how support explains the outcome to subscribers.
Build a consent-risk calendar
- Date price is scheduled in App Store Connect.
- Date Apple begins notifying subscribers where consent is needed.
- Next renewal windows for affected cohorts.
- In-app messaging dates and support staffing.
- Date entitlement logic is verified for non-consent, canceled, expired, and active states.
Make app behavior match subscriber state
If a subscriber does not consent, the app should not show a confusing mix of active plan copy, expired access, and upgrade prompts. Server entitlement logic should distinguish active, pending consent, expired, canceled, billing retry, and grace states.
AppReviewReady interpretation: price increases expose weak entitlement code. Test all subscription states before the business announces the change.
Coordinate App Store and in-app messaging
- Use App Store Connect as the source of truth for price and effective date.
- Avoid telling users to manage a subscription outside Apple's subscription management flow.
- Update paywalls, FAQs, support macros, and renewal explanations before notifications land.
- Check localized currencies, taxes, and duration wording.
- Track support questions and refunds after the change.
Document the price-change review packet
This packet usually stays internal, but it lets the team answer review or support questions with facts instead of reconstructing the decision after subscribers are already affected.
If the increase is paired with new features, make the feature availability date separate from the price effective date. Users should not be asked to consent to a higher price based on functionality that is not yet live in their storefront or subscription tier.
After rollout, compare cancellations, failed renewals, support tickets, and refund requests by storefront. A price change can expose localization or value-proposition problems that were invisible when only one market was tested.
Keep historical screenshots of the old and new paywall copy. They help support explain the transition and prevent the team from accidentally reverting to stale pricing language in a later release.
Subscription price change packet: Products: [ids] Storefronts: [list] Consent needed: [yes/no by cohort] Effective dates: [dates] Entitlement states tested: [list] User messaging: [screens/support] Rollback plan: [owner]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check subscription change risk
Review pricing, consent, entitlement states, and user messaging before rollout.
Open the tool