Pricing template (Google Play)

What a pricing template was

A pricing template was a Google Play Console feature that let developers define one localized price set (a base price plus per-country overrides) and reuse it across many in-app products and subscriptions. Instead of editing 175 country prices on every new SKU, you applied a template and inherited the whole set.

For apps with dozens or hundreds of SKUs (large game catalogs, content marketplaces, multi-tier subscription apps), templates were the only way to keep cross-product pricing consistent without painful manual editing.

Why Google deprecated pricing templates

In 2023, Google rolled out the new subscription architecture: base plans, offers, and a redesigned price-setting flow. Pricing templates were deprecated as part of that migration. The Play Console removed the create-template UI; existing templates still worked for legacy products but new ones could not be made.

The official replacement guidance from Google:

• Set prices per product or per base plan directly
• Use the new Pricing tab on each subscription to manage per-country prices
• Use the Google Play Developer API to script bulk changes if you have many products
• Third-party tools (PricePush, others) handle the bulk operation that templates used to handle in the UI

The deprecation moved the consistency-across-products problem out of Google's UI and into the developer's tooling. For most indie devs, that meant either accepting per-product manual editing or adopting a pricing tool.

How the migration affected indie devs

The practical pain points after templates were removed:

• New IAPs no longer inherit pricing from existing ones automatically
• Adding a new subscription tier means re-entering all 140+ country prices
• Keeping cross-product pricing parity now requires scripting or an external tool
• The Google Play Developer API exposes per-product price endpoints, so automation is possible but requires real engineering

For solo indie devs shipping one or two subscription tiers, the templated-vs-not difference is small. For apps with many products or frequent pricing changes, the loss of templates was significant.

What replaces pricing templates on Google Play?

No direct replacement in the UI. Google's official path is: set prices per product or per base plan, use the API for bulk operations, and rely on third-party tooling for cross-product consistency. PricePush and similar tools fill the gap that templates used to fill.

Do legacy pricing templates still work?

Existing templates created before deprecation continue to apply to existing products that reference them. You cannot create new templates, but old ones still work for backwards compatibility. Eventually Google may sunset them fully; treat them as a deprecated dependency.

How PricePush handles the template gap

PricePush keeps your pricing strategy at the app level, not the SKU level. Define your strategy once (PPP blend, Big Mac, custom), apply it across every product, push to Google Play through the Developer API. The result is what pricing templates used to do in the UI: one source of truth for per-country prices, applied consistently across every SKU.