A final Shopify app usage charge can show $0 after uninstall because Shopify's billing finalization used the wrong cycle, even when it had recorded billable usage. Shopify says it fixed that specific bug on October 30, 2026, and adjusted affected earnings it identified. If your charge is still missing, reconcile the completed cycle against your usage ledger and take the evidence to Partner Support; resending events is not the recovery path. Shopify's account of the fix
Key takeaways
- The confirmed bug selected a newly opened cycle instead of the completed cycle when an uninstall scheduled cancellation at a billing-cycle boundary.
- Shopify says the fix is fully rolled out and that it adjusted previously affected earnings found in its review.
- A
202 AcceptedApp Events response proves receipt, not successful billing validation. - You have 24 hours after uninstall to submit remaining events for usage that occurred before uninstall, but that window does not repair an already finalized $0 charge.
What actually went wrong
In the reported case, a merchant generated billable usage, uninstalled the app, and later produced a CHARGE_USAGE event for zero units and $0.00. Shopify confirmed that, when uninstall scheduled cancellation exactly at a billing-cycle boundary, finalization could read the newly opened cycle rather than the cycle that had just ended. That distinction matters: this was not evidence that the merchant had failed to pay, nor necessarily evidence that the app had failed to report usage. The metered component of both usage-only and hybrid plans could be affected. Shopify reported on October 30 that it had corrected the cycle selection and verified the deferred-cancellation flow. Read the original report and Shopify's follow-up.
There are other ways to arrive at zero revenue, so diagnose the stage that failed before opening a ticket. Shopify App Pricing accepts events, validates them asynchronously, aggregates accepted usage by meter, calculates the charge, and ultimately pays earnings after collecting the merchant's invoice. Those are different states, not one successful API call. Shopify's usage-charge documentation and earnings documentation describe the separate steps.
| What you observe | Likely place to investigate | Next action |
|---|---|---|
API returned 202, but no billable event appears | Meter handle or asynchronous validation | Check Dev Dashboard billing-event logs |
Billing event has PERIOD_CLOSED | Event arrived outside the permitted billing period | Check occurrence and submission times |
Billing events show OK, then final CHARGE_USAGE is $0 | Finalization or an adjustment to usage | Compare the completed cycle with app history and your ledger |
| Charge exists, but payout does not yet show earnings | Merchant invoice or payout timing | Inspect charge details and payout status |
Prove which failure you have
I would build this investigation around immutable usage records, not around the current installation state. An exporter, for example, should record the completed export before it attempts to report its meter event. The record needs the shop ID, subscription or plan context, meter handle, quantity, occurrence timestamp, idempotency key, and submission result. Keep the evidence needed to audit a charge without putting customer identifiers in the App Events payload. Shopify's billing-event guide explicitly warns against sending identifying data.
For each affected shop:
- Identify the completed app billing cycle and total the underlying successful usage by meter. Apply that plan's actual fixed, graduated, or volume pricing; multiplying units by one rate is wrong for some plans.
- In Dev Dashboard, open Logs, filter Type to App billing event, and check that each relevant event has status
OK. An unmatched meter handle may appear only as an App event, not a billable event. - In Partner Dashboard, inspect the store's app history and charge details. Find the uninstall, scheduled cancellation, final
CHARGE_USAGE, and any subsequent adjustment. Compare gross charges with gross expected charges before comparing net earnings or payouts. - Check the payout separately. Shopify says a charge becomes an earning after it collects payment from the merchant, so an absent payout alone does not prove this $0 finalization bug.
The Dev Dashboard validation instructions explain why 202 is insufficient: billing errors have no synchronous error response or failure webhook. The charge and payout guide shows where to inspect individual charges.
Submit remaining usage without making the discrepancy worse
Shopify allows 24 hours after uninstall to submit billing events for usage that occurred before uninstall. After that, new events are rejected with PERIOD_CLOSED. On APP_UNINSTALLED, mark the installation inactive, stop generating new billable work, and promptly drain events representing work already completed. Preserve each event's original occurrence time and stable idempotency key. The usage-charge rules specify the window.
The billing outbox should be small and explicit:
- Commit the completed work and its pending billing event together, or use an outbox so a worker crash cannot erase one side of the transaction.
- Retry transport failures according to the App Events API response rules, using the same idempotency key for the same event.
- Record the API response, then verify the eventual billing result in Dev Dashboard. Alert when a submitted event is not
OK.
Do not resend already accepted usage with new keys to compensate for a final $0. That creates a distinct event, risks charging the merchant twice, and does not correct a finalized cycle. Shopify specifically advised against it. Nor should you force a merchant onto a free plan before uninstall: one reporter saw a positive charge on that path, but Shopify said no plan switch was required after the fix. Shopify's follow-up
Recover an affected charge
As of November 13, 2026, Shopify says it completed billing adjustments for previously affected earnings found during its review. That is not a promise that every disputed record was identified or that an app can issue its own replacement charge. Check the Partner Dashboard for an adjustment first. If the expected adjustment is absent, continue through an existing Partner Support case or open one with the shop and app IDs, subscription context, completed-cycle dates, uninstall and finalization timestamps, event idempotency keys, OK billing results, your calculated charge, and the $0 history entry. Keep account-specific identifiers out of public forum posts. Shopify's recovery guidance
The next technical step is a reconciliation job: for every uninstall with nonzero validated usage, compare the expected completed-cycle charge with Shopify's final charge and any later adjustment. A fixed platform bug prevents new instances of this failure mode; that comparison tells you whether old revenue was actually recovered.
Frequently asked questions
Does a 202 response mean Shopify will bill the usage event?
No. It confirms receipt by the App Events API. Check the event's billing result under App billing event logs in Dev Dashboard.
Can I send usage events after a merchant uninstalls my app?
Shopify allows 24 hours to submit remaining events for usage that occurred before uninstall. Events submitted after the period closes are rejected with PERIOD_CLOSED.
How do I recover a final usage charge that incorrectly became $0?
First check Partner Dashboard for a billing adjustment. If one is missing, give Partner Support the completed-cycle usage records, validated event results, final charge, and relevant identifiers; do not create replacement events with new idempotency keys.