> 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-indexes.md). # Price indexes A **price index** is a table of per-territory multipliers. When you run a Base-price batch, Amply takes your base-country price and multiplies it by each territory's factor. Indexes come in two flavours — system (maintained by Amply) and custom (yours to edit). **Use this when** you want to reuse a pricing matrix across products or batches, import one from a spreadsheet, or inspect a system index. **Don't use this when** you only ever run Percentage-method batches — those ignore indexes. ## Prerequisites * Your plan includes custom price indexes. If the **Price Indexes** entry isn't in the left nav, check your plan. * The application is connected to App Store Connect or Google Play Console so territory codes resolve correctly in the factor table. ## Where to find it From the left nav under **Price Management**, click **Price Indexes**. The page heading reads **Custom Price Indexes**. The table lists every index available to the active project — both system and custom — with columns: Name, Countries, Created, Updated. Two controls above the list: * **Download template** — exports a blank CSV of every territory for a platform. Pick **All platforms**, **iOS only**, or **Android only**. * **New index** — choose **From CSV** (upload a filled-in template) or **Blank / manual** (open the editor). ## System vs custom | | System | Custom | | ------------- | --------------------------------- | -------- | | Maintained by | Amply | You | | Shown as | **System** label next to the name | No label | | Editable | No — view-only | Yes | | Deletable | No | Yes | | Duplicatable | Yes — creates a custom copy | Yes | Known system indexes in the dropdown include **Apple Store Matrix (IAP)** and **App Store**. Other system matrices may appear if Amply has provisioned them for your project — check the list. ## Managing custom indexes ### Create from scratch Click **New index** → **Blank / manual**. The editor opens with: * **Name** — a label you'll recognize in the dropdown later (for example, `2026 Q2 rollout — premium tier`). * **Platform** — All platforms, iOS only, or Android only. An iOS-only index is hidden when creating a batch for an Android product, and vice versa. * **Factor table** — one row per territory, pre-filled at `1.0`. Type a new multiplier: `1.5` means 50% above the base price, `0.8` means 20% below, `1.0` is parity. Every factor must be positive — saving is blocked until the warnings clear. Click **Create index** to save. ### Create from CSV 1. Click **Download template** and pick the platform. The CSV downloads as `amply-price-index-template--.csv`. 2. Fill in the factor column for each territory in a spreadsheet. 3. Back in the list, click **New index** → **From CSV** and upload. Amply parses the file and opens the editor with factors pre-filled — you can still tweak before saving. ### Duplicate Any row — system or custom — has a **Duplicate** action in its row menu. It opens the editor pre-filled with the original's factors and `(copy)` suffixed on the name. Use this to derive a custom variant of a system index. ### Edit Click the pencil icon on a custom row. System rows only offer a view-only dialog (the eye icon). The editor shows a **"referenced by N price changes"** banner when the index is currently used — edits to the index don't change prior batches, only future ones. Click **Save changes** when done. ### Delete Row menu → **Delete**. The request can fail — for example if the index is still referenced by a batch — and Amply surfaces the error in a toast. Rewrite or remove the offending batches first if that happens. ## Save a batch as an index Any Base-price batch with entries shows a **Save as custom index** button on its detail view. Amply derives an index from the per-territory prices the batch produced and opens the editor with: * A suggested name based on the product and date. * Platform compatibility inferred from the batch. * The factor table pre-filled. * Optional warnings if any territory couldn't be derived. Review, adjust, save. The result is a regular custom index you can use in future batches. Percentage-method batches don't produce an index — there's no per-territory factor matrix to derive. ## How factors are applied For a Base-price batch using index *I* in base country *C*: 1. Base price *P* is what you entered in the form. 2. For each territory *T* in *I*, the computed price is `P × I[T]`. 3. The result is rounded per your rounding settings (if any). 4. On iOS only, the result is snapped to the nearest valid Apple price point. Territories missing from *I* are skipped for that batch. The base country's own factor in *I*, if present, is ignored — the base price is used as-is. ## Common mistakes * **Wrong platform tag.** If an index doesn't show up in the dropdown, check its Platform — an iOS-only index is hidden for Android batches. * **Template mismatch.** Uploading an Android-only template into an iOS-only index produces rows the other platform doesn't support. Use **All platforms** if you want the index usable everywhere. * **Non-positive factor.** Zero or negative factors block saving. Keep every row at `1.0` or higher to include it at parity with the base; set lower (e.g. `0.9`) for a discount. * **Forgetting to update referenced batches.** Editing an index doesn't rewrite batches that already submitted — only future ones using it. ## Related * [Creating a price change](/price-management/creating-a-price-change.md) — where indexes are selected * [Comparing prices](/price-management/comparing-prices.md) — side-by-side view of current prices across products * [Price management overview](/price-management/price-management.md) — when to pick Base price vs Percentage