Skip to content
Tutorials Center
My learning

Topics

Lesson 39 of 55 ยท Billing

App Pricing Models and Billing Options

Compare free, recurring, usage-based and one-time pricing for Shopify apps, learn how trials and managed pricing work, and try a runnable pricing simulator.

An app that merchants love but cannot pay for is a hobby. Shopify gives you a built-in way to charge: merchants approve a charge inside their admin, and the amount appears on their normal Shopify invoice. You do not collect card numbers, run a payment form or chase failed payments. In exchange you accept the platform's rules about what you may charge for and how.

This lesson is about the decisions that come before any code: which pricing model fits your app, how trials work, and whether to let Shopify host your plan page (managed pricing) or build the flow yourself with the Billing API. The API calls are covered in Implementing Billing with the Billing API. All platform code and numbers shown here are read-only or illustrative: billing needs a real app and a real shop, so the runnable parts are plain JavaScript stand-ins that model the arithmetic.

The four building blocks

Every Shopify app price is made from a small set of pieces. You can combine them.

Building block What the merchant sees Typical use
Free No charge Lead generation, a companion to a paid product, or an app funded elsewhere
Recurring subscription A fixed amount every billing period (every 30 days, or yearly) Ongoing features: a review widget, a reporting dashboard
Usage-based charge An amount that grows with what the app did Per SMS sent, per label printed, per 1,000 products synced
One-time charge A single payment A migration, a setup service, a lifetime unlock

Two ideas sit on top of those blocks:

  • A free trial delays the first recurring charge by some number of days.
  • A usage cap is a maximum the merchant agrees to for usage charges in a billing period. The merchant sees it on the approval screen, so they are never surprised.

Charges are made in a currency Shopify supports for apps, which for most apps means US dollars, regardless of the merchant's store currency. Think about that when you price: a merchant in another country sees a converted amount on their invoice.

flowchart LR
    A["Free"] --> M["Your plan"]
    B["Recurring<br/>subscription"] --> M
    C["Usage-based<br/>charge"] --> M
    D["One-time<br/>charge"] --> M
    M --> T["Optional free trial<br/>and usage cap"]

Plans are combinations of a few simple building blocks.

Choosing a model

Ask what the merchant gets more of when they pay you more.

  1. Value grows with time and features. Use tiered recurring plans: Basic, Growth, Advanced. Plans are easy to explain and give you predictable revenue.
  2. Value grows with volume. If your costs rise with usage (an SMS provider, a shipping-label vendor, a heavy AI call), a flat price either loses you money on big merchants or overcharges small ones. A usage-based charge, often with a small monthly base fee, keeps your margin steady.
  3. Value is delivered once. A data migration or custom setup fits a one-time charge.
  4. You are validating an idea. Start free or with a long trial, learn what merchants use, then add a paid tier. Gating is easier to add than to remove.

A hybrid is very common: a monthly base fee that includes a quantity, plus a usage charge beyond it. This is what the pricing simulator below models.

Keep plans few. Merchants compare you against several alternatives in the App Store and rarely read a five-column pricing table. Three plans, named for the merchant's stage (Starter, Growth, Scale), is a good default.

Trials

A free trial lets a merchant try the app before the first recurring charge. You pass a number of trial days when you create the subscription. Two practical points:

  • Trial days count down over time, not over days when the merchant uses the app. A trial is not paused when the merchant ignores it.
  • Shopify remembers trial days that a shop already used on your app. If a merchant uninstalls on day 5 of a 14-day trial and reinstalls later, the remaining days are what they get, not a fresh 14. This stops the same shop from restarting trials forever. Verify the exact current behavior in Shopify's billing documentation when you design a trial offer.

During a trial a merchant can still use the usage-based part of your plan if you built one, so decide whether trial users get usage charges or a free allowance. Many apps give a small free allowance during the trial.

JS Timeline of a trial and the first bill

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The 30 here matches the usual EVERY_30_DAYS billing interval. Notice that a 30-day interval is not "one calendar month": charges drift against the calendar, which matters if you promise "billed on the 1st".

Managed pricing or the Billing API?

You can let Shopify run the plan flow, or you can run it yourself.

Managed pricing. You define your plans in the Partner/Dev Dashboard (names, prices, intervals, trial days). Shopify shows a plan-selection page to merchants, handles upgrades and downgrades, and creates the subscriptions. Your app just needs to check which plan the shop is on and unlock features accordingly. It is the fastest route and removes a lot of billing code, but you accept Shopify's flow and its limits on plan structure (for example, usage-based charging is not part of the plain managed plans at the time of writing; check the current docs, because this changes).

Billing API. Your app calls the Admin GraphQL API to create subscriptions, one-time purchases and usage records, and it sends the merchant to a confirmation page. You control the plan page, the copy and the logic (custom plans per merchant, discounts, usage metering). You also own every edge case: handling declines, upgrades, uninstalls and a merchant who never approves.

Question Managed pricing Billing API
Who builds the plan page? Shopify You
Code you write Check the current plan Create, confirm, upgrade, cancel, meter
Custom or per-merchant prices Limited Yes
Usage-based charges Check current support Yes, with a cap
Best for Simple tiered plans Hybrid, usage or custom pricing

Pick managed pricing when it covers your plans. Move to the Billing API when you need something it cannot express. Either way, never trust a plan stored only in your own database: ask Shopify (or keep your copy in sync from billing webhooks), because merchants change plans outside your app.

What the merchant approves

Whatever route you take, a recurring or usage charge only starts after the merchant clicks Approve on a Shopify page that shows the price, the interval, the trial and any usage cap. The app cannot charge in secret. Until the merchant approves, the subscription is pending and you should not unlock paid features.

Merchants can also cancel from their admin, and an uninstall cancels active charges. So your app must keep working gracefully when a subscription disappears: downgrade to a free state, do not crash.

Revenue share and fees

Shopify keeps a share of the revenue your app earns through its billing system, and the exact percentages and any introductory allowance are set in the Partner Program Agreement, which Shopify updates from time to time. Rather than hard-code a number from a tutorial, read the current terms and keep the rate in one configuration value in your finance model. Two habits help:

  • Price on the amount the merchant pays, then compute your payout after Shopify's share and any processing or currency fees.
  • Keep money as integers (cents) in code to avoid rounding drift, as explained in Money as Integers. For wider pricing strategy, see Pricing Models; those ideas apply to your own SaaS pricing too.

A pricing simulator

This stand-in models a hybrid plan: a base fee that includes an allowance, a per-unit price beyond it, and a cap. The revenue-share rate is a made-up parameter (shareRate) for illustration only. Replace it with the rate in your current agreement.

JS Hybrid plan: base fee, included units, usage cap

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Look at the 5,000-unit row for each plan: the cap stops the usage part from growing without limit, which protects the merchant, and also caps your revenue from very busy shops. Choosing the cap is a pricing decision, not a technical one.

Real platform code: reading the plan

With managed pricing, the typical check is "what is this shop paying for right now?". The shape of the query is below. It is read-only here, and API versions change, so confirm field names against the version you target (2026-01 or the latest stable release when you build).

GRAPHQL
# Admin GraphQL (read-only example)
query CurrentPlan {
  currentAppInstallation {
    activeSubscriptions {
      id
      name
      status
      trialDays
      currentPeriodEnd
      lineItems {
        plan {
          pricingDetails {
            __typename
          }
        }
      }
    }
  }
}

In your app, turn that answer into a small object such as { plan: "growth", active: true } and make every feature check use it. The project lesson on a paid app builds this gate step by step.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Your costs rise with every SMS the app sends, and merchants send very different amounts. Which pricing fits best?

    When cost grows with volume, usage-based charges (often with a small base fee) keep your margin steady and let small merchants pay less.
  2. 2. When does a recurring charge or usage cap actually start for a merchant?

    A new subscription is pending until the merchant approves it. Until then you must not unlock paid features or assume you will be paid.
  3. 3. Which situation points to the Billing API rather than managed pricing?

    Managed pricing is best for simple tiers with the least code. Custom pricing and metering need the Billing API, where you own the flow.
  4. 4. Why should billing amounts in your own code be integers such as cents?

    Binary floating point cannot represent many decimal amounts exactly, so repeated arithmetic can be off by a cent. Integer cents avoid this.

Summary

  • Shopify app pricing is built from four blocks: free, recurring, usage-based and one-time, plus trials and usage caps.
  • Match the model to how value and your costs grow: tiers for features, usage for volume, one-time for a delivered service.
  • Charges start only after the merchant approves them; handle a missing or cancelled subscription gracefully.
  • Managed pricing means little code and a Shopify-hosted plan page; the Billing API gives full control and full responsibility.
  • Revenue share terms change, so keep the rate in one configuration value, and calculate money in integer cents.

Next: Implementing Billing with the Billing API