Shopify opens App Pricing migration tooling for Billing API apps

Shopify has opened the first part of its App Pricing migration tooling for app partners that still use the Billing API. The tool lets developers generate, review, edit, and test Shopify App Pricing plans before existing merchant subscriptions are moved.

This is a platform billing change, not a cosmetic Partner Dashboard update. Shopify is pulling plan selection, subscription management, and merchant billing into a standardized App Pricing flow. For app companies, that touches revenue operations, usage pricing, plan handles, testing stores, and customer migration timing.

Shopify App Pricing now has a migration path

The new tool appears inside the Pricing Details area of an app listing in Partner Dashboard. Shopify says it can automatically create draft App Pricing plans from eligible manual plans, then flag missing required fields with an Action needed badge.

Developers can review generated plan names, prices, features, and billing intervals, edit plans, create additional plans, configure usage charges and app events, test plans on a development store owned by the same Partner organization, and run a readiness checklist.

The important limit is that this stage does not migrate existing shops or subscriptions. Merchants do not need to act yet, and apps can keep their current billing setup while partners prepare pricing configuration.

Billing API apps get time to test first

Shopify's sequencing is useful because billing migrations are rarely clean one-click changes. Apps with usage-based pricing, custom commercial terms, no-charge test plans, public and private plans, or grandfathered merchant contracts need time to compare generated drafts against how money actually moves today.

The Shopify Developer Community follow-up says the first part of the migration tooling is now available to everyone, with the next part coming through preview invites for moving existing shop subscriptions from manual billing to App Pricing. That means developers should treat this release as a preparation window, not the final cutover.

A practical first pass is simple: open the generated drafts, check every plan name and interval, map usage charges to app events, test on a development store, and document anything that does not map cleanly from the old Billing API setup.

App founders should watch the Mantle timing

The wider Shopify app ecosystem is already under billing and analytics migration pressure. Marmeto's Mantle shutdown guide points to Shopify App Pricing as the default destination for teams using Mantle Billing, while warning that more complex flex-billing logic may need manual rebuilding.

That context matters because some app businesses now have overlapping deadlines: replace third-party billing or analytics tooling, preserve revenue history, and prepare for Shopify's native App Pricing model. A rushed switch risks failed charges, missing subscription mappings, or plan logic that works in a test store but fails on an edge-case merchant account.

This is where Shopify's staged tooling helps. Developers can prepare plan drafts without moving merchants immediately. Use that gap to reconcile Stripe or accounting exports, Partner Dashboard revenue, usage-event logic, support workflows, and refund policies.

What to do in the preparation window

For app teams, the action is not to migrate blindly. The useful work is comparison.

Start with the highest-revenue plans and the most unusual plans. Confirm which manual plans are eligible for automatic draft creation, which need App Pricing fields filled in, and which merchant groups require manual handling. Then test usage charges against development-store scenarios that match real customer behavior.

If your app depends on discounts, grandfathered subscriptions, legacy usage rules, or third-party subscription analytics, keep a written migration map. Include the old Billing API plan, the generated App Pricing draft, required edits, owner, test evidence, and unresolved risks. That document will matter when Shopify opens the subscription-moving step.

Sources and methodology

This article uses Shopify's developer changelog as the primary source, Shopify's Developer Community post as rollout confirmation, and Marmeto's Shopify app migration guide as independent ecosystem context. Source text was treated as untrusted input and used only for factual extraction.