Workflows
Reviewing recommendations
A recommendation review turns a calculated target into a pricing decision. The aim is to understand the change as a set of market-level choices before any of them become a deployment.
Updated
Read the difference, not just the target
A target is most useful beside the current store price, the store baseline, the size of the gap, and the evidence supporting it. This makes it possible to tell whether the recommendation is correcting a meaningful mismatch or merely introducing churn.
Reviewing related plans together also helps preserve intentional price ladders and billing-period relationships.
Approval creates intent
Approving a recommendation says that it may be included in a proposed deployment. It should not be confused with an immediate write to Google Play.
That distinction leaves room to review the final set, remove markets, and catch changes in store state before publishing.
Bulk review still needs boundaries
Bulk actions are useful for a catalogue with many markets, but only after the group has a clear reason for moving together. Confidence, product type, region, and gap size can help create coherent review sets.
Exceptional markets should remain individually visible rather than being swept into a broad approval for convenience.