Moving Play subscription management from InAppProducts to monetization.subscriptions
Google Play now separates a subscription from the terms used to sell it. A subscription contains at least one base plan, and a base plan can carry offers. The newer monetization.subscriptions endpoints manage that structure, while InAppProducts remains for one-time purchases.
What changed in the subscription model
At Google I/O 2022, Play Billing Library 5 introduced a clearer division of responsibilities. The subscription identifies the product family. A base plan defines the recurring terms, such as billing period and renewal behaviour. An offer adds promotional or targeted terms, including trial phases. This separation supports multiple base plans and offers, prepaid plans, and more granular pricing and packaging tests.
Programmatic catalog management is most relevant when an app creates many subscriptions, such as access to individual creators, or frequently changes pricing and packaging. If those changes are made only in Play Console, the deprecated API may not be involved.
Which endpoint handles which job
Use monetization.subscriptions for subscription-level operations: list, get, create, patch, archive and delete, with batchGet and batchUpdate for groups of subscriptions. Creating or updating a subscription can also create or update its base plans.
Use monetization.subscriptions.basePlans to control which base plans are active. Its operations include activate, deactivate and delete, plus batchUpdateStates for several plans and migratePrices or batchMigratePrices for moving users from legacy pricing.
Use monetization.subscriptions.basePlans.offers for offer details and targeting rules. It supports list, get, create, activate, patch, deactivate and delete, with batchUpdate and batchUpdateStates for bulk changes.
Decide whether migration is required
Check whether your own backend, scripts or platform tooling call InAppProducts for subscriptions. The warning in Play Console is a prompt to investigate, not proof of current use. Before May 2022, subscriptions converted to the newer structure were made read-only in Console because editing them there would break later InAppProducts management. If no active API use exists, those subscriptions can be made editable and the warning can be disregarded.
If ownership is unclear, ask the Android or platform team whether any service still calls the API. Existing subscriptions converted by Google generally have one backwards-compatible base plan and offer, which gives a practical starting point for a like-for-like migration.
Field mapping and regional pricing
Map packageName to packageName and sku to productId. Map status to basePlans[0].state. Map prices to basePlans[0].regionalConfigs.price, listings to listings, subscriptionPeriod to basePlans[0].autoRenewingBasePlanType.billingPeriodDuration, trialPeriod to basePlans[0].offers[0].phases[0].regionalConfigs[0].free, gracePeriod to basePlans[0].autoRenewingBasePlanType.gracePeriodDuration, and subscriptionTaxesAndComplianceSettings to taxAndComplianceSettings. The old defaultPrice has no equivalent.
The regional-pricing change is the main operational difference. Play Console can apply a checked price across regions, but API-driven setup must provide pricing for each country or region where the product will be sold. A basic migration preserves the older structure with one compatible base plan and offer; it does not by itself unlock the fuller benefits of multiple plans, offers or prepaid terms.
Migration checklist
Before switching, inventory every InAppProducts subscription call and confirm that one-time purchases remain on the existing path. Replace subscription references with the mapped fields, add regional prices, test create, update, activation and deactivation flows, and verify that converted subscriptions remain readable and editable as intended. Keep the old integration available until the new endpoints have been exercised against the real catalog structure.
| Legacy InAppProducts field | monetization.subscriptions equivalent |
|---|---|
| packageName | packageName |
| sku | productId |
| status | basePlans[0].state |
| prices | basePlans[0].regionalConfigs.price |
| listings | listings |
| defaultPrice | No longer available |
| subscriptionPeriod | basePlans[0].autoRenewingBasePlanType.billingPeriodDuration |
| trialPeriod | basePlans[0].offers[0].phases[0].regionalConfigs[0].free |
| gracePeriod | basePlans[0].autoRenewingBasePlanType.gracePeriodDuration |
| subscriptionTaxesAndComplianceSettings | taxAndComplianceSettings |
Basic like-for-like migration using one backwards-compatible base plan and offer.
Frequently asked questions
Does the deprecation warning mean I must migrate?
Only if your code calls the InAppProducts API to manage subscriptions remotely. Managing products only through Play Console does not use that API. A warning can appear because older subscriptions were converted and left read-only, even when the API is no longer used actively.
What stays on InAppProducts after migration?
Keep using InAppProducts for consumables and one-time purchases. Move subscription catalog management to monetization.subscriptions, its basePlans endpoint, and its offers endpoint.
What replaces the old default price?
The single default price is no longer available. Set pricing for each country or region through the regional configuration for the relevant base plan.