A pricing schedule pending status in App Store Connect means a price change you set is scheduled but not yet applied everywhere, either because it is waiting for its scheduled start date or because it is propagating across storefronts, which can take up to 24 hours. This is normal rather than stuck. Timezones matter, because the start time is region-based and the moment a change takes effect varies by country, so a pending change on your clock may simply mean the start time has not arrived yet in that region or the change is still rolling out. It can also reflect Apple's periodic tax and currency adjustments, and it is separate from app review, so resubmitting your app does not help and is not needed.
Short answer
In short, pending means the change is scheduled or propagating, not stuck. Per Apple's pricing help, App Store Connect schedules price changes by time zone, and a change can take up to 24 hours to display for all users, so a recent or future-dated change shows as pending normally. It is separate from App Review, so do not resubmit your app; wait for the schedule to complete.
What pricing schedule pending means
Under Price Schedule in App Store Connect you see your upcoming price changes with their start and end dates, and a pending state means a change on that schedule has not fully taken effect yet. It is not an error or a review verdict; it is the normal state of a price change between the moment you set it and the moment it is live for every user in every affected storefront. So seeing pending is expected right after you schedule a change.
There are two ordinary reasons a change sits pending. The first is that you scheduled it for a future date, so it is simply waiting for that date to arrive. The second is that its start has been reached but the new price is still propagating across the App Store's many storefronts, which is not instantaneous. In both cases the system is working as intended, and the pending label is telling you the change is queued or rolling out rather than failed.
Why it is pending: scheduling and propagation
When you set a price change, App Store Connect determines the soonest it can be scheduled based on time zones, generally a day or two ahead, and a change set for later stays pending until that time. So part of the answer is simply that a scheduled change waits for its scheduled moment, and until then pending is exactly what you should see.
The other part is propagation. Once a change's start time is reached, the new price does not appear for everyone at the same instant, because the App Store applies it across its storefronts over a short window. A price change can take up to 24 hours to display for all users, so a change that has technically started can still show as not fully applied while it rolls out. Both the wait for the start time and the propagation window are normal, and together they explain almost every pending pricing schedule.
Do time zones affect it?
Yes, time zones are central to how price changes take effect, which is why a pending status can look confusing on your local clock. The time of day your price change goes into effect varies by region, so the same change starts at different local moments around the world rather than all at once. App Store Connect schedules based on time zones, and the soonest available start reflects that, which is why you cannot always set a change for right now.
This has a practical consequence for a pending status. If you scheduled a change for a date and time that has already passed in some countries, it takes effect immediately in those regions but can take up to 24 hours to display for all users elsewhere, so it legitimately shows as pending while other regions catch up. So a pending change is often just the world's time zones and the propagation window working through, not a problem, and checking the exact scheduled start against the region you are looking at usually explains it.
Do tax and currency adjustments cause it?
Yes, Apple's automatic tax and foreign-exchange adjustments can produce pending pricing changes that you did not set by hand. When you choose a base price, Apple uses it to generate comparable prices across the other storefronts, and as taxes and exchange rates change, Apple periodically updates those storefront prices for you. Your Price Schedule indicates whether Apple may make such adjustments in certain countries due to tax or currency changes, so a pending entry can be one of these automatic updates rather than your own change.
There is an important caveat to know. If you schedule a custom price change that includes your base country, Apple stops automatically updating prices across the storefronts, so you take over responsibility for those regional prices. That is worth understanding when you see pending adjustments, because it changes whether Apple will keep managing tax and currency shifts for you. Either way, a tax or currency adjustment showing as pending is Apple maintaining comparable pricing, and it resolves on Apple's schedule like any other change.
Does resubmitting the app reset anything?
No, and this is the key thing not to do. A price change is independent of App Review, because pricing does not go through the review process and does not require a new build or a new app version. So resubmitting your app, or submitting a new version, does nothing to move a pending pricing schedule along and only adds unnecessary work. The pricing system processes the change on its own timeline regardless of your app's review state.
This separation is helpful once you internalize it. Because pricing and review are different systems, a pending price change is not blocked by anything in review, and a live app is not affected by a pending price change beyond the price itself updating when it applies. So the correct response to a pending pricing schedule is to let it complete, not to touch your app binary. Resubmitting is the reflex to resist here, since it cannot speed up pricing and can complicate your release.
Normal versus abnormal at a glance
Matching how long a change has been pending to whether it is expected tells you whether to wait. The table below maps it.
| State | Normal? | What it means |
|---|---|---|
| Pending before the scheduled start | Normal | Waiting for the date you set |
| Pending within 24 hours of start | Normal | Propagating across storefronts |
| Some regions updated, others not | Normal | Time-zone and rollout differences |
| Pending days after start with no effect | Investigate | Check schedule, time zone, and agreements |
| Unexpected pending adjustment | Usually normal | Apple tax or currency update |
Read the first three rows as reassurance: a change that is before its start, within a day of it, or partway across regions is behaving exactly as designed.
When to act or escalate
Most pending pricing resolves on its own, so action is only warranted once it is genuinely overdue. If a change is still pending well beyond 24 hours after its scheduled start, with no effect in any region, first re-check the schedule itself: confirm the start date and time, remember that the effective time varies by region, and make sure you are not reading a future-dated change as a stuck one. Also confirm your Paid Apps agreement is active, since pricing depends on it.
If the schedule looks correct, the agreement is active, and a change remains unapplied long past its start, that is when contacting Apple through App Store Connect is reasonable. Before doing so, note the exact price change, its scheduled start, and the regions affected, so you can describe it precisely. The order is to verify the schedule and time zone, rule out the base-country custom-price caveat and an inactive agreement, and only then treat a truly overdue change as a support case rather than normal propagation.
What to check
Working through these steps explains almost every pending pricing schedule. The checklist below covers them.
| Step | Action | Done? |
|---|---|---|
| Read the schedule | Note the change's start and end dates | [ ] |
| Account for time zones | Effective time varies by region | [ ] |
| Allow propagation | Give it up to 24 hours to apply | [ ] |
| Check for tax adjustments | See if Apple is updating for tax or currency | [ ] |
| Do not resubmit the app | Pricing is separate from App Review | [ ] |
| Confirm your agreement | Ensure Paid Apps is active before escalating | [ ] |
The step teams skip most is accounting for time zones, since a change can be perfectly on schedule while looking stuck against your own local clock.
Where a scan fits
Pricing is an App Store Connect and account matter, so a security tool has no role in whether a price change has applied, and it is worth being clear about that boundary.
A scanner like PTKD.com analyzes your app build for security issues such as exposed keys, over-broad permissions, and risky third-party code, mapped to OWASP MASVS. To be clear about the boundary: PTKD does not manage or apply your pricing, which lives entirely in App Store Connect and your agreements. It is useful for the security side of shipping an app, which is separate from your pricing schedule.
What to take away
- Pricing schedule pending means a price change is scheduled but not yet applied everywhere, either waiting for its start date or propagating, and it is normal.
- Price changes can take up to 24 hours to display for all users, so a recent change showing as pending is expected while it rolls out.
- Time zones matter, since the effective time varies by region, and a change can be live in some countries while still pending in others.
- Apple periodically adjusts storefront prices for tax and currency changes, so a pending entry you did not set may be one of those automatic updates.
- Pricing is separate from App Review, so do not resubmit your app to fix it; wait out the schedule, and a tool like PTKD.com is for your build, not your pricing.
