Plan name: This parameter is used to display the Plan in 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 Events of a particular Subscription, the Plan Vendor ID corresponding to the Subscription will always be present. It will inform you about the Plan associated with the subscription allowing you to define the matching entitlements. The Plan has a common identifier for all the Platforms to 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 Plans within the 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)

Check the Stores on which your Plan is distributed.

Report the Product ID from the corresponding in-app purchase retrieved from the App Store Connect Console in the field App Store Product id App Store Connect Console > My Apps > [YOUR APP] > In-App Purchases > Manage > In-App Purchases > [YOUR IN-APP PURCHASE]

Report the Product ID from the corresponding in-app product retrieved from the Play Store Console in the field Play Store Product id Play Store Console > [YOUR APP] > Store presence > In-App products > Subscriptions > [YOUR IN-APP SUBSCRIPTION]

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:

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).

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 Products and Plans. If Plans A & 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 Level to determine which Plan has the highest rank and apply the corresponding migration policy.