Store IAP price-tier changes that force first-purchase pack redesign
Apple’s equalised price points and auto FX/tax adjustments break hard-coded first-purchase tables. Record the documented mechanics, not a rumour.
Hard-coded first-purchase pack tables fail when storefront prices move underneath them. This change log records the documented Apple pricing mechanics operators must design for — not an invented tier retirement date.
What changed / what is documented
Apple’s Set a price for an In-App Purchase (source read 20 September 2026) states developers choose from up to 800 default price points (with a path to request 100 higher points up to $10,000). You set a base country or region; Apple uses it to provide comparable prices on the other 174 storefronts. Apple will never change the price in your base country or region via automatic tax/FX updates, and will notify in advance of automatic changes on other storefronts. You may instead manually manage storefronts, in which case you own tax and FX maintenance.
Sandbox note from the same page: product metadata changes may take up to 1 hour to appear in sandbox.
Operator action for first-purchase packs
| Field | Evidence |
|---|---|
| Document checked | Apple ASC IAP pricing help |
| Price point count (default) | Up to 800 |
| Higher points (request) | Additional 100 up to $10,000 |
| Auto-adjust scope | Non-base storefronts for tax/FX |
| Base country auto-change | Never (per this page) |
| UA implication | Ads and client strings must read live localised price APIs, not a hard-coded USD table |
Facts vs limits
| Fact | Limit |
|---|---|
| Equalisation and base-country rules are documented | This is not a dated “tier chart vN retired on DATE” bulletin |
| Google Play pricing objects differ | Android one-time product offers are a separate change record |
| Advance notice of auto changes is stated | Exact future FX moves are not listed here |
