Google Play In-App Purchase Options Announced at I/O 2021
The 2021 Google I/O sessions sketched a broader menu for Play billing: carts that hold more than one consumable, subscriptions assembled from several products, fixed-term prepaid access, and a client version that unlocks the set. This guide restates those announcements as a working checklist. Treat every configuration here as dated 2021 announcement material rather than a description of current Play behavior, and confirm details against Google's own documentation before you plan a release.
What changed in Play purchase configuration
Three configuration changes were presented. Each one changes what a customer can assemble in a single purchase, so the practical question for a team is which of them matches an existing product catalog.
Multi-quantity purchases. A store can offer several consumable products at the same time. Which products are eligible is configured in the Google Play console, and once a customer selects eligible items they pick the quantity they want directly from their cart. The design consequence is that quantity becomes a customer-facing choice rather than something your app has to infer or bundle.
Multi-line subscriptions. A single subscription can now contain more than one product. Customers can add, remove, upgrade, or downgrade those products at sign-up and at any later point in the subscription lifecycle. The design consequence is that a subscription is no longer a fixed bundle chosen once; your entitlement logic has to tolerate a changing set of products under one subscription.
Prepaid plans. A prepaid plan grants access to content for a fixed period, and Google Play notifies users as the plan approaches expiry. The announcement compares this to Apple's non-renewing subscriptions, which is a useful mental model: access ends at a known point unless the customer acts again.
A quick way to map the three against a catalog:
- Selling several consumables in one checkout → multi-quantity purchases.
- Letting one subscription carry a changing set of products → multi-line subscriptions.
- Selling fixed-length access with an expiry reminder → prepaid plans.
Worked example. Suppose a game sells three consumables — extra lives, a coin pack, and a boost — and a player wants two coin packs and one boost. Under the multi-quantity model, all three are eligible products configured in the console, and the player sets the coin-pack quantity to two in the cart before confirming. Your fulfillment path therefore has to read a per-line quantity, not assume one unit per product.
The billing client gate
The configurations above are not free. The announcement states that taking advantage of the new features requires updating the app to Play Billing Client 4.0, and it points readers to the version 4.0 release notes for the details.
This creates a distinction worth keeping straight when something does not work as expected:
- A product configuration problem means the eligible products, quantities, or plan terms are not set up as intended in the console.
- A client version problem means the app is still on an older billing client and therefore cannot reach the new purchase types at all.
If a new configuration is invisible to testers, check the client version before reworking the catalog. If the configuration appears but behaves wrongly, the catalog is the better place to look first.
The original post also said the publisher's own tooling was being updated for Play Billing Client 4.0 and the new features, described as coming soon at the time. No rollout evidence accompanies that statement here, so it is recorded as a 2021 intention rather than a current capability claim.
Decision checklist before you commit to a release:
- Confirm which of the three configurations, if any, your catalog actually needs.
- Confirm the app can move to Play Billing Client 4.0, and read the release notes for that version.
- Decide how entitlement logic will handle a changing product set within one subscription.
- Decide how fulfillment will read per-line quantities for multi-quantity carts.
- Plan how prepaid expiry will be surfaced to customers alongside Play's own reminder.
- Re-check every assumption against current Google documentation, since this material dates from 2021.
Adjacent Play announcements
Three further items from the same sessions are relevant to teams that ship billing, even though none of them is a purchase configuration:
- New engagement metrics and benchmarks, intended to show developers how their apps perform relative to similar apps.
- The Digital Goods API, which lets progressive web apps built with Trusted Web Activities sell digital items through Google Play Billing.
- The Google Play SDK Console, which gives SDK developers visibility into an SDK's usage and crash statistics and a way to report known issues, while giving app developers more information about the SDKs they integrate.
For a billing team, the SDK Console item is the one with the most direct operational value: it is a channel for learning about problems in the SDKs your purchase flow depends on.