Plans in the Purchasely Console
To create a
Plan, click on the button
+ Add new plan
Plan is composed of the following parameters:
Plan name: This parameter is used to display the
Planin the Purchasely Console, but is also displayed to the user in the section "My Subscriptions" (which allows users to manage their subscription directly in the Mobile App).
Plan Vendor ID: This parameter allows you to set your own identifier for the
Plan. When receiving
Eventsof a particular
Plan Vendor IDcorresponding to the
Subscriptionwill always be present. It will inform you about the
Planassociated with the subscription allowing you to define the matching entitlements. The
Planhas a common identifier for all the
Platformsto which it is distributed.
Plan type: This parameter allows you to define the type of in-app item corresponding to the Plan. If a plan is mapped with several In-App purchases from several stores, it should be consistent and have the same type across all the stores.
Level: This parameter allows you to organize
Product. Subscriptions should be arranged in descending order, starting with the option that offers the highest level of service. This order defines the migration policies (see below)
Binding Store Product ID together
To bind the Plan with the Store Product ID, you must first ensure that the Application has been correctly plugged with the Stores.
Check the Stores on which your Plan is distributed.
Product IDfrom the corresponding in-app purchase retrieved from the App Store Connect Console in the field
App Store Product idApp Store Connect Console > My Apps > [YOUR APP] > In-App Purchases > Manage > In-App Purchases > [YOUR IN-APP PURCHASE]
Product IDfrom the corresponding in-app product retrieved from the Play Store Console in the field
Play Store Product idPlay Store Console > [YOUR APP] > Store presence > In-App products > Subscriptions > [YOUR IN-APP SUBSCRIPTION]
Ordering Plans inside a Product
Level parameter is used to rank
Plans inside a
On iOS, the App Store Connect Console provides the
Subscription Groups, which are the exact equivalent of
Products in Purchasely. The order in which
Subscriptions are organised inside a
Subscription Group defines the migration policies (up-sell | down-sell | cross-sell). The policies are managed directly by the App Store.
Plans inside a
Product should be organised in the same order as Subscriptions inside a Subscription Group. If they are ordered differently, the Subscription Group ordering will prevail over the
Product ordering in the Purchasely Console.
On the Play Store,
Subscription Groups do not exist. Therefore, this is the order in which
Plans are organized inside a
Product in the Purchasely Console, which will define the migration policies between the
Plans. The policies are thus managed by the Purchasely Cloud Platform.
About migrations policies
When a subscriber changes his subscription from (A) to (B), a migration is applied. The migration results in the auto-cancellation of subscription A when subscription B is purchased.
On iOS, the migration is directly applied by the App Store. The condition to meet is to have the two
in-app purchases belong to the same
Three different policies can be applied by the App Store:
Downgrade: If subscription A has a higher rank than subscription B in the
Subscription Group, the migration will be considered a downgrade. In this case, subscription A will remain active until the end of the current billing period, and subscription B (with its own price and periodicity) will be replaced automatically and become active only for the next billing cycle. Subscription A will then be automatically resigned. Example: a migration from a Yearly plan to a Monthly plan (screenshot above 👆) or from a Gold plan to a Silver plan in a multi-tiers subscription group. Inside the app, the user flow looks like this:
User flow on iOS when
Upgrade: If subscription A has a lower rank than subscription B in the
Subscription Group, the migration will be considered an upgrade. In this case, subscription B will immediately replace subscription A a new billing cycle will start right away. Subscription B will be refunded pro rata temporis (for the time remaining before the end of the current billing period) to the user.
Crossgrade: If subscription A has the same rank as subscription B in the Subscription Groups, the policy applied will depend on the duration of each subscription. If they have the same duration, the policy applied will be the same as an upgrade (effective immediately + pro-rata refund), and the user flow will be the one of an upgrade. If they have different durations, the policy applied will look like a downgrade (subscription B will become effective at the next renewal date).
More information about all this is accessible directly on Apple Help Center.
On the Play Store, since Subscription groups do not exist, migration is directly managed by the Purchasely Cloud Platform. To achieve this, it relies on
PlansA & B belong to the same Product, Purchasely will apply a migration.
For simplicity for users, the exact same rules as on iOS have been implemented (downgrade/upgrade & crossgrade). Purchasely Cloud Platform relies on the parameter
Levelto determine which Plan has the highest rank and apply the corresponding migration policy.
Plans in the Purchasely Console
To edit a
Plan, click on the
Edit button in the upper right corner.