I would like a feature that allows the user of the extension to format which decimal seperator they should use for pricing. Because I am from europe, and we are mostly using comma instead of america who are using decimal point. Ofc I could use euro as base price and hopefully let it sorted itself out, but it would be a quality of life feature if it was an option if I want to use USD base price while it generated the correct pricing with the correct decimal seperator.
it works great and i want to recommend to all my dev friends they will love it but we need it to be able to adjust pricing for promotional offers too. i assume this will be easy to modify the extension to work like this. just need the extension to be triggered.
When recommending prices, allow to only select some countries to update, ie I like some stuff for euro different than Americas etc
I would like more flexibility, like allow specifying price per currency, all prices end in .00
On Play Console, Mongolia uses MNT, not USD. But the tool suggests a price in USD.
On 2026-01-01, Bulgaria switched from the lev to the euro. It would be terrific if you could update that in the tool.
Hi, I have a one time product which is priced 499$ but extension doesn’t allow me to select a price over 399 and i can not edit the dropdown value either. How can i do this?
Summary: When editing prices for an in-app product in Google Play Console, the extension doesn’t show up at all. This seems to be related to Google’s recent update of the IAP pages — the new layout isn’t supported by the extension yet. Expected behavior: The extension should load on the updated IAP pricing pages and detect the price editor the same way it does for apps and subscriptions.
In App Store Connect, the extension fails to detect the price dialog for app prices, subscriptions, and in-app purchases. The UI doesn’t respond even though the dialog is clearly open. Expected behavior: The extension should consistently recognize the price dialog across all App Store Connect pricing surfaces (apps, IAPs, and subscriptions).
Opening the extension in one Chrome tab also triggers it to open in another Chrome window. Closing the extension is inconsistent — the Close button closes the wrong instance (the one in a different window). Expected behavior: Extension should open only in the active tab/window, and the Close button should close the instance where it was clicked.