# Guideline 3.1.2(a) - Subscriptions: Removing Features Existing Subscribers Paid For

**Guideline:** 3.1.2 · **Store:** Apple App Store · **Severity:** medium · **Fix difficulty:** hard · **Typical turnaround:** 1-3 days

Canonical URL: https://appstorereject.com/rejections/apple/3/guideline-312a-subscriptions-removing-features-existing-subscribers-paid-for

## Description

Apple is rejecting your app update because it removes or downgrades features that existing subscribers are currently paying for, or moves previously included features to a higher-priced tier. Apple considers this a violation of the subscription value promise -- users subscribed based on a specific feature set, and reducing that set while maintaining the price is not acceptable. This rejection typically occurs during major app redesigns, tier restructuring, or when features are moved from a lower tier to a higher one. The key issue is retroactivity: new subscribers can be offered different tiers, but existing subscribers must retain access to what they paid for at the price they agreed to. The compliant approach, and best for maintaining user trust, is to grandfather existing subscribers into their current feature set while offering the new tier structure only to new subscribers. This requires server-side logic to track when each subscription was initiated and what features were available at that time.

## Common variations

- Updated version removes features from existing subscription tier
- Features moved from lower tier to higher tier retroactively
- Subscription value reduced without corresponding price reduction
- Existing subscribers lose access to previously included features

## Example rejection email

```
Guideline 3.1.2(a) - Business - Payments - Subscriptions

We found that the updated version of your app removes features that are currently included in the active subscription tier. Specifically, the 'Cloud Backup' and 'Priority Support' features previously included in the Standard plan ($4.99/month) are now only available in the new Premium plan ($9.99/month).

Existing subscribers should retain access to features they are currently paying for. Changes to subscription tiers should not retroactively reduce the value of existing subscriptions.

Next Steps:
Please revise the app to ensure existing subscribers retain access to all features included in their current subscription plan at the price they are paying.
```

## Resolution steps

## Quick Assessment
- **Risk level:** Medium
- **Resolution path:** Fix & Resubmit
- **Typical turnaround:** 1-3 days

## The Fix

1. **Grandfather existing subscribers** -- Implement server-side logic that identifies subscribers who were active before the tier change and maintains their access to all features they had.

2. **Track subscription start dates** -- Your backend should record when each subscription began and what features were available in that tier at that time.

3. **Only apply new tiers to new subscribers** -- New users see the updated tier structure. Existing subscribers keep their current deal until they change plans.

4. **Communicate changes transparently** -- If you must restructure tiers, notify existing subscribers in advance and explain how they are grandfathered.

5. **In Review Notes, explain the grandfathering** -- Tell Apple's reviewers exactly how existing subscribers retain their features. Provide test accounts that demonstrate the grandfathered experience.

## Prevention
- Plan tier changes with grandfathering from the start
- Never remove features from an active tier without a corresponding price reduction or migration path
- Track feature-to-tier mappings per subscription cohort on your server

## Appeal guidance

Appeal if the feature changes are due to external factors (API deprecation, legal compliance) that make the previous feature set impossible to maintain. Provide documentation of the external constraint.

## Before / after examples

**Before:** App update moves 'Cloud Backup' from Standard ($4.99/month) to the new Premium tier ($9.99/month), causing all Standard subscribers to immediately lose cloud backup access
**After:** Standard subscribers who subscribed before the change retain cloud backup access; new Standard subscribers see the updated feature set; Premium tier is available as an upgrade option
**Why it works:** Existing subscribers must be grandfathered into their current feature set when tiers are restructured.

## Common questions

**Can you appeal a 3.1.2 rejection?**

Appeal if the feature changes are due to external factors (API deprecation, legal compliance) that make the previous feature set impossible to maintain. Provide documentation of the external constraint.

**How long does this typically take to fix?**

Typical turnaround is 1-3 days (difficulty: hard). After resubmission, most re-reviews complete within 24-48 hours.

---
*Machine-readable source: https://api.appstorereject.com/api/rejections/detail?slug=guideline-312a-subscriptions-removing-features-existing-subscribers-paid-for*