Subscription + battle pass coexistence rules
Operator checklist for running an auto-renewable subscription alongside a seasonal battle pass without stacking claims that break store or ad parity.
Subscription perks that silently stack with battle-pass premium tracks confuse store reviewers and UA creative. This checklist separates product types using official billing docs.
Product definitions
Apple’s Auto-renewable subscriptions overview covers subscription products and programme context. Google Play Billing Library is the Android entry for one-time products versus subscriptions. Neither page defines “battle pass”, but both require clear product typing in the store console — operators must not market a pass as a subscription (or the reverse) in ads.
Checklist
| Check | Pass condition | Fail action |
|---|---|---|
| Product type | Pass = consumable/non-consumable/seasonal non-renewing; sub = auto-renewable | Fix store config |
| Perk matrix | Document which perks stack, replace, or mute when both owned | Economy design sign-off |
| Ad claims | Creative states which product grants the shown perk | Rewrite |
| Restore / revoke | Subscription lapse removes only sub perks; pass remains until season end | QA |
| Refund path | Sub refunds vs pass refunds use correct server handlers | Engineering |
| Pricing page | Store and web show both SKUs without implying one includes the other unless true | ASO / web |
Facts versus limits
| Field | Evidence |
|---|---|
| Apple subscriptions overview | developer.apple.com/app-store/subscriptions |
| Play Billing overview | developer.android.com/google/play/billing |
| Observed stacking titles | None here |
