How to Update App Prices in Bulk on the App Store and Google Play (2026)

Changing one price is easy. Changing it everywhere is the problem.

Say you want to raise your subscription by a dollar, launch in twenty new countries, or fix prices that have drifted out of line. In the standard consoles, that is not one change. It is a change per country, per product, per store, done by hand, one click at a time. On the App Store alone, every product has 175 storefronts behind it, and Google Play has its own list of countries on top. For a single app with a couple of products, a small pricing decision turns into hundreds of edits, with a real chance of a typo going live to a whole country.

A bulk app price update is the fix: make the pricing decision once, then apply it across every country and both stores in a single pass. I have priced apps since 2012 and done this both the slow way and the fast way, so here is what a bulk update actually involves, the moments you need one, how to do it without breaking a live price, and the part most bulk tools get wrong.

Why updating prices is a grind by default

The stores are built to change one price at a time. On the App Store, a subscription price is set per territory, so a single product already has up to 175 numbers behind it. Each in-app purchase and extra subscription adds its own set. Google Play is much the same, with its own console and its own per-country pricing. Change your strategy once and you are looking at hundreds of individual edits, spread across two dashboards that do not talk to each other. Even changing a single price in App Store Connect has more moving parts than people expect; multiply that by every country and product and you see the problem.

That is why anyone past a handful of products ends up in a spreadsheet, copying numbers between tabs and consoles, and why "I need to update my prices" quietly becomes a task people avoid for months. The prices sit wrong not because the developer does not care, but because fixing them by hand is genuinely tedious.

What the stores give you for bulk changes in 2026

Less than you'd hope, and less than a year ago.

On the App Store, prices are set one product at a time. Apple's help pages walk you through it per in-app purchase and per subscription, and I haven't found a screen in App Store Connect that edits the prices of several products at once.

Google Play used to have two bulk tools, and it removed both in 2025. CSV import and export of products stopped on May 19, 2025. Pricing templates, which let you link many products to one price, stopped managing prices on October 27, 2025. Since then, in Google's words, "all pricing adjustments must be made at the individual product level." The alternative Google points to is its API.

So on both stores, a real bulk update today goes through the API: either your own script, or a tool that calls it for you.

What a bulk price update actually does

A bulk update collapses all of that into one operation. In practice it is three steps.

First, connect the stores, so one place can read and write your App Store Connect and Google Play prices. Second, choose the scope: which apps, which products, which countries, and what change you are making, whether that is a flat increase, a new base price, or a full per-country recalculation. Third, push once. The tool applies your decision to every storefront and both stores in a single run, instead of you doing it a few hundred times.

Click to enlarge

The important part sits between steps two and three: a preview. A good bulk update shows you the full diff before anything goes live, old price and new price, per country, per product, so you approve the whole change with your eyes open. Price changes are metadata, not a new build, so they take effect without an app release or App Review, which is exactly why a preview matters. There is nothing between your click and a live price in front of real users.

The four moments you actually need it

Bulk updates are not an everyday thing. They matter at a few specific moments.

Annual price increase. You decide to raise prices across the board. Doing it in one pass, with the same logic applied everywhere, is the difference between an afternoon and a quarter of procrastination.

Launching into new countries. You expand your storefronts and suddenly have dozens of new markets that need prices. Setting them all at once, correctly, beats leaving them on whatever the store auto-filled.

Cleaning up drift and legacy prices. Exchange rates move, old plans pile up, and prices you set two years ago no longer make sense. A bulk pass resets them to current, coherent numbers. This is especially true on the App Store, which never updates subscription prices for exchange rates on its own, so they drift until you step in.

Coordinated campaigns. A launch, a sale, or a repricing test that has to hit every market at the same time, cleanly, then roll back cleanly afterward.

In every one of these, the value is not only speed. It is consistency: the same decision applied the same way everywhere, instead of a hundred slightly different manual edits.

Doing it without breaking a live price

The flip side of changing every country at once is that a mistake also reaches every country at once. Under-price a market by a wide margin for a day and even a quick fix can leave you honoring a bad price for a while.

So a bulk update is only as good as its safety rails. You want a full preview of the diff before the push, a record of what changed, and a one-step way to roll back if a number was wrong. I covered that in detail in how to change app prices safely with versioning and rollback. Treat a bulk push like a deploy, not a spreadsheet edit.

The part most bulk tools get wrong

A lot of bulk pricing tools skip the part that matters: doing it fast is not the same as doing it right.

Most bulk updates are really a bulk copy. You set one base price and the tool pushes a currency conversion of it to every country. That is fast, and it is still wrong, because a converted price ignores what people in each market can actually pay. A $9.99 subscription pushed to India or Brazil as a straight conversion lands two or three times too high for the local economy, in bulk, in one click. You just made the same mistake everywhere, faster.

Click to enlarge

A bulk update earns its value when what you are pushing is localized pricing: a price set to each country's purchasing power, not a raw conversion of your home number. That is the difference between updating 175 prices and updating 175 correct prices. The evidence that it moves revenue is in whether parity pricing grows app sales.

Bulk updates, done right

A bulk update that applies purchasing-power prices across every country and both stores in one pass, with a preview and a rollback, is exactly what PricePush does. It calculates purchasing-power-aligned prices for 190-plus countries, not raw conversions, snaps each one to a price the store actually allows, and pushes them to the App Store and Google Play together, showing you the full diff first. Every push lands in your price history, and on the Pro plan you can restore an earlier push with one button. You can see your own per-country prices free, no login, before you change anything, or try it on one app.

The point of a bulk update is not to make a bad pricing decision faster. It is to make one good decision, once, and have it land correctly in every country.

Quick answers

Can you bulk update prices in App Store Connect? Not across products in the web interface. Prices are set per in-app purchase and per subscription. To change many at once you need the App Store Connect API, or a tool built on it.

Does Google Play still have pricing templates? No. Since October 27, 2025 pricing templates no longer manage prices, and every price change happens at the product level, in Play Console or through the API.

Can you still import in-app product prices by CSV on Google Play? No. Google stopped CSV import and export of products in Play Console on May 19, 2025.

Do price changes need a new app version? No. Prices are store settings, not part of your build, so you can change them without a release.