> For the complete documentation index, see [llms.txt](https://docs.amply.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amply.tools/price-management/price-management.md). # Price management Plan, preview, and submit price changes for your in-app subscriptions and one-time products across every country your app sells in, from the dashboard. **Use this when** you want to change what users pay in one or many territories — a new base price plus an index, or a single ± percentage applied to current prices. **Don't use this when** you want to change a single product's price in a single country — do that directly in App Store Connect or Google Play Console. ## Prerequisites * The application is connected to App Store Connect or Google Play Console, and its products and current prices are visible in Amply. * Your plan includes Price Management. If you don't see the **Price Management** entry in the left nav, check your plan under [Billing](/user-guide/dashboard-tour.md#upgrade-the-plan). * For Android subscriptions, products must have a single base plan — multi-base-plan subscriptions aren't supported yet. ## Find it in the dashboard From the project sidebar, open **Price Management**. The landing page is **History** — every price change for the active application, drafts included. The page auto-refreshes every ten seconds while any batch is still in progress. Two buttons at the top right of History: * **New Price Change** — open the three-step form to create a draft. * **Compare** — inspect current prices across up to three products side by side. A third entry sits in the left nav under Price Management: * **Price Indexes** — manage reusable pricing matrices. ## Pricing method, in one sentence Two methods are available when you create a change: * **Base price** — set one price in one country, multiply by a price index for every other country. Best for a structured update. * **Percentage** — apply a single ± percentage to every current store price. Fastest for a uniform bump or cut. If you're not sure which to pick, open **Compare** first to inspect current prices side by side. See [Comparing prices](/price-management/comparing-prices.md). For the full wizard, draft workflow, and recovery actions, see [Creating a price change](/price-management/creating-a-price-change.md). ## Status reference A **price change** (a *batch* in the UI) goes through these states: | Status | What it means | | ---------- | -------------------------------------------------------------- | | Draft | Saved but not submitted. Edit or delete at any time. | | Pending | Submitted; queued for send. | | Sending | Actively pushing territory-by-territory updates. | | Completed | Every territory synced successfully. | | Incomplete | Some territories synced, others failed or were deferred. | | Failed | Every territory failed. | | Cancelled | You cancelled it while in flight, or it aged out. | | Deferred | Some territories are waiting on the store's rate-limit window. | **Completed**, **Incomplete**, **Failed**, and **Cancelled** are *terminal* — no more automatic retries. You can still act manually: retry failed entries, resume deferred ones, or derive a custom index from the matrix. Each territory inside a batch carries its own status: Pending, Sending, Completed, Failed, Skipped, Deferred, Cancelled, or Unchanged. **Unchanged** means the calculated new price matched the current store price — no write was needed. ## Store-specific behavior **App Store (iOS)** * Earliest start date is tomorrow — Apple rejects same-day changes. * Base price must match an **Apple price point** (a tier price Apple accepts). The form's autocomplete restricts you to valid points for the selected base country. * For subscriptions, you also choose an **audience**: "New subscribers only" (existing subscribers keep their current price) or "All subscribers." Price decreases apply to everyone regardless of the audience setting. **Google Play (Android)** * The change is accepted immediately, but can take several hours to propagate to the listing. * Subscriptions must have a single base plan. ## Who can use it Price Management is a dashboard-only feature — no SDK integration involved. The creator of every batch is recorded and shown in the **Created By** column of the history table. ## Related * [Creating a price change](/price-management/creating-a-price-change.md) — full walk-through of the wizard, draft workflow, and recovery actions * [Price indexes](/price-management/price-indexes.md) — system and custom indexes, and the CSV flow * [Comparing prices](/price-management/comparing-prices.md) — inspect current prices side by side * [Dashboard tour](/user-guide/dashboard-tour.md) — how to find Price Management and upgrade your plan if it's missing --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.amply.tools/price-management/price-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.