Start here
Your first pricing matrix
A first pricing review should answer a simple question: where do the app's current regional prices differ meaningfully from a purchasing-power-informed target?
Updated
Begin with the live catalogue
The starting point is the app as Google Play currently represents it: products, base plans, offers, availability, currencies, and regional prices. Reviewing the live catalogue prevents a pricing exercise from being built on an old spreadsheet or an assumed product structure.
Once imported, the catalogue becomes a regional matrix that makes differences visible across markets without changing the store.
Read the matrix before choosing changes
Compare the current price, the store's regional baseline where available, and the proposed parity target. Large gaps deserve attention, but the size of a gap is not enough on its own; data confidence, local billing currency, product position, and existing customers also matter.
A useful first pass identifies markets to investigate, markets to leave alone, and the strategy that best matches the app's pricing posture.
Move from analysis to a controlled update
Select only the markets you are prepared to change and inspect the proposed before-and-after values as a set. The detailed dashboard guide covers connection permissions, validation, and the publishing workflow.
The public takeaway is simpler: establish the current state first, understand why a target differs, and approve a bounded change rather than treating the whole catalogue as one switch.