Skip to content

How-to

How to bulk change in-app purchase and subscription prices

App Store Connect changes prices one product at a time. Here is how to change ten, fifty or two hundred in-app purchases and subscriptions at once without losing a weekend or leaving half your catalog at the old price.

Updated 9 min read

Can you bulk change in-app purchase prices in App Store Connect?

Not in one step. App Store Connect has no screen that changes many in-app purchases or subscriptions together: you open each product, plan its change and confirm it. To change many at once you either repeat that per product, script the App Store Connect API, or use a tool that drives the API for you with one review.

Why App Store Connect makes this slow

Three things multiply the clicks. First, every in-app purchase and every auto-renewable subscription has its own price schedule, reached from its own page. Second, prices live per storefront: Apple generates comparable prices for all 175 countries and regions from a base country (set a price for an in-app purchase), but any storefront you have set by hand stays as you set it until you change it again. Third, subscriptions are scheduled per storefront too, with a choice about existing subscribers on each change (manage pricing for auto-renewable subscriptions).

So “raise everything by 10 %” across three apps with eight products each is 24 separate flows, each with a review of up to 175 rows. That is where mistakes creep in: a product skipped, a custom price in one country overwritten, a subscription left at the old price because its group was collapsed.

The manual path, product by product

If you have a handful of products, the built-in screens are fine. Apple distinguishes three kinds of in-app purchase price change: global (a new base price, comparable prices everywhere else), temporary (a start and end date in chosen countries) and custom (prices you manage yourself in some or all countries). Effective dates can be set from today up to the end of the next calendar year (schedule price changes for in-app purchases).

  1. In Apps, select the app, then In-App Purchases in the sidebar (non-renewing subscriptions sit under Subscriptions).
  2. Open the product, and next to Price Schedule click the add button (+).
  3. Choose Global, Temporary or Custom, pick the date and the base-country price, and review the comparable prices.
  4. Confirm, then repeat for the next product.
  5. For each auto-renewable subscription: open it, go to Subscription Prices, choose Plan Subscription Price Change, pick countries, date and price, decide what happens to existing subscribers, and confirm.

Before you start, export what customers pay today: each subscription’s pricing page has an Export as CSV option for current and upcoming prices. Keep that file. It is your undo list.

The API path: what the work looks like

The App Store Connect API can do everything the screens do, and a script can loop over products. You need a team API key with the App Manager or Admin role (role permissions); setting one up is covered in creating an API key for pricing. The shape of a bulk job:

StepEndpointNotes
List productsGET /v1/apps/{id}/inAppPurchasesV2, GET /v1/apps/{id}/subscriptionGroups, GET /v1/subscriptionGroups/{id}/subscriptionsOnce per app; in-app purchases, subscriptions in a group.
Find price pointsGET /v2/inAppPurchases/{id}/pricePoints, GET /v1/subscriptions/{id}/pricePointsFilter by territory; Apple says the subscription filter will be required (subscription price points).
Apple’s equivalents elsewhereGET /v1/subscriptionPricePoints/{id}/equalizations, GET /v1/inAppPurchasePricePoints/{id}/equalizationsThe matching point in other currencies (equalizations).
Write an in-app purchase changePOST /v1/inAppPurchasePriceSchedulesRequires baseTerritory, inAppPurchase and manualPrices; each price has startDate and optional endDate (docs).
Write a subscription changePOST /v1/subscriptionPricesOne per territory, with startDate and preserveCurrentPrice (docs).
Cancel a pending subscription changeDELETE /v1/subscriptionPrices/{id}Only before it starts.

The arithmetic matters. A subscription is written one storefront at a time, so 20 subscriptions in 175 storefronts is 3,500 writes before you count price-point lookups. Apple limits requests per API key over a rolling hour, reports the remainder in the X-Rate-Limit header, and rejects excess calls with HTTP 429 and RATE_LIMIT_EXCEEDED; its own example shows 3,500 requests an hour and notes that actual limits vary (identifying rate limits). A loop that ignores this stops half-way, and you are left with some products changed and some not.

  • Read the header on every response and slow down before you hit zero; queue 429s and retry later rather than in a tight loop.
  • Cache price points per product and territory. They are the bulk of your reads.
  • Expect per-item errors (a price point that does not exist in one storefront, a date that is too soon) and record them per product and country so you can resend only the failures.
  • Tokens are valid for at most 20 minutes, so a long job has to mint new ones.
  • For in-app purchases, read the current schedule first and build the new one from it, so countries you priced by hand are kept on purpose rather than by luck.
  • Changes can take up to an hour to show in the sandbox, so test purchases right after a write may still show the old price.

Our API pricing guide walks through one product end to end; the comparison with maintaining your own script is on RepriceCat vs API scripts.

A spreadsheet workflow for many products

Whether you click or script, a spreadsheet keeps a bulk change honest. One row per product and storefront, with today’s price beside the new one, lets you sort, filter and eyeball the whole change before anything is sent.

  1. Export current prices: one row per product × storefront with product ID, type, territory, currency, current price and any scheduled change.
  2. Add columns for the rule (for example “+10 %”), the raw target price and the snapped price, the nearest price Apple actually offers in that currency.
  3. Filter for rows where the snapped price equals the current price, or moves much more than you intended. Fix those by hand.
  4. Add a start date column and, for subscriptions, an existing-subscribers column (keep or apply).
  5. Feed the finished sheet to your script, or re-enter it product by product, and keep the sheet with the date as your record.

Here is what “raise by a percentage, rounded to the nearest .99 price” does to common US prices when the rounding is done naively. Note the rows that barely move, or could round back to today’s price:

Current priceRuleRaw targetNearest .99 priceActual change
$2.99+20 %$3.59$3.99+33 %
$4.99+10 %$5.49$4.99 or $5.99 (a tie)none, or +20 %
$4.99+20 %$5.99$5.99+20 %
$9.99+15 %$11.49$10.99+10 %
$49.99+10 %$54.99$54.99+10 %
Free+10 %$0.00skippednone

A careful checklist before you send

CheckWhy
Export today’s pricesIt is the only way back if a change goes wrong. Keep it with the date.
Dry runBuild every request without sending any; count products, storefronts and expected errors.
Review every rowProduct × country, old → new. Look for unchanged rows, big jumps and hand-set countries.
Pick a start dateA future date gives you time to cancel and lines the change up across storefronts. Start times vary by region (start times).
Decide on existing subscribersKeep their price or apply the new one; increases applied to existing subscribers follow Apple’s notice and consent rules.
Check what is already scheduledA new subscription change replaces the one already scheduled for that storefront.
Send in batchesPace against the rate limit; watch failures per product and country.
Verify and recordRead back the schedules, compare with your sheet, file the result.

Pitfalls that bite in bulk

  • Snapping. Small percentages on low prices can round back to today’s price (see $4.99 +10 % above), and rounding can turn +15 % into +10 % or +20 % into +33 %. Make sure a raise always lands above today’s price and a cut below it, and review the snapped price, not the rule.
  • Free products. A percentage of zero is zero. Skip free products in a percentage change, or set them a price on purpose.
  • Hand-set storefronts. If you set your own price in a storefront, Apple stops adjusting it for tax and exchange rates. A global change from the base country may not be what those storefronts get; decide per storefront.
  • Subscriptions are per storefront and per change. Apple allows one future price change at a time per storefront and billing plan type; scheduling another overwrites the first (Apple’s subscription pricing rules).
  • No undo once live. A subscription increase that has taken effect cannot be reversed, and a decrease always applies to existing subscribers; you can only schedule another change.
  • Subscription groups. Raising monthly but not yearly changes the yearly plan’s discount and can make an upgrade look worse than a downgrade. Change a group’s plans together and check their ratios.
  • Apple does not adjust subscription prices for tax or exchange rates, but it may adjust in-app purchase prices in storefronts it manages. Know which of your prices Apple can still move.

Raising subscription prices has its own rules on notice and consent; read how to raise an App Store subscription price before applying an increase to existing subscribers.

Doing it with RepriceCat

RepriceCat connects to your App Store Connect team key and runs this whole workflow with one review. “Change many prices” lets you pick up to 200 products across your apps, with quick picks for all subscriptions, monthly, yearly, in-app purchases or app prices, then raise or lower by a percentage or set one new price. Nothing goes to Apple until you have seen the review and confirmed.

  • Percent changes are rounded to Apple’s nearest .99 price, and a raise always moves to at least the next price up (a cut to at least the next one down), so nothing rounds back to today’s price. Free products are skipped, and every snapped row is marked in the review.
  • Regional tiers on or off: other countries get their tier’s price, or Apple’s own prices with your hand-set ones kept.
  • Now or on a date, and for subscriptions “existing subscribers keep their price” (Apple’s preserve-current-price).
  • A review table of product × country, today’s price → new price, and a dry run that sends nothing.
  • Spreadsheet round trip: export current prices to Excel, Numbers or CSV, edit, import; errors are listed first and imported rows become pending changes you review.
  • Activity logs every change per country, lists failed countries with Apple’s reason so you can resend only those, and can roll a change back.

See how it works on bulk change App Store prices, or start with a free month.

Frequently asked

Can I change all in-app purchase prices at once in App Store Connect?

Not from a single screen. App Store Connect changes prices one product at a time; to change many at once you script the App Store Connect API or use a tool built on it.

How do I update subscription prices in bulk?

Schedule a price change per subscription and storefront, either in App Store Connect or with POST /v1/subscriptionPrices in the API. Decide for each change whether existing subscribers keep their current price.

Will a bulk price change affect my existing subscribers?

Only if you apply it to them. For an increase you can keep the current price for existing subscribers; a decrease always applies to them. Increases applied to existing subscribers follow Apple’s notice and consent rules.

Why did my 10 % increase not change some prices?

Prices must land on one of Apple’s price points. A small percentage on a low price, such as $4.99 plus 10 %, can round back to the current price. Check the snapped price for each row before you send.

What rate limit applies to bulk price changes through the API?

Apple limits requests per API key over a rolling hour and reports the remainder in the X-Rate-Limit header. Its example shows 3,500 per hour but actual limits vary, so pace your job and retry 429 errors later.

Can I undo a bulk price change?

You can delete changes that have not started yet. Once a change is live you schedule another one back to the old prices, which is why exporting current prices first matters.

Try it

Reprice every territory from one base price

Tiers, price-point snapping, one review table, one confirmation — through the App Store Connect API. First month free, then $1 per app per month.