Shopify app pricing strategy comes down to three decisions: which model (free, freemium, tiers, usage, or revenue share), how long the trial runs, and how tiers map to merchant size. Each has known failure modes. This guide covers the patterns that show up across the App Store and how to change prices without a churn spike.
The Five Pricing Models in the Wild
Browse any App Store category and five models account for nearly everything you see:
| Model | Typical shape | Wins when | Fails when |
|---|---|---|---|
| Free | $0 forever | You monetize elsewhere (ecosystem, lead gen, acquisition target) | You need the app itself to be a business |
| Freemium | Free tier + paid plans | Free users feed ranking, reviews, and word of mouth | Free tier satisfies most of the market |
| Flat tiers | 3 plans, e.g. $9 / $29 / $79 | Value is predictable and merchants want a known bill | Value scales 100x across your merchant base |
| Usage-based | Per order, message, or credit | Costs and value both scale with activity | Merchants cannot predict their bill and resent it |
| % of revenue | Cut of GMV the app generates | The app visibly makes money (upsells, recovery) | Attribution of "generated" revenue is arguable |
The deciding question is how your value scales with merchant size. An upsell app delivering 100x more revenue to a 10,000-order store than to a 100-order store leaves most of its value on the table with flat pricing; that is why revenue-share and usage models cluster in upsell, recovery, and checkout categories. A utility that does the same job for everyone (a redirect manager, a metafield editor) has no such gradient, and flat tiers are exactly right.
Blends are common for good reason. Flat tiers with usage allowances ("Pro: $29/month, up to 2,000 orders") give merchants a predictable bill and give you protection from whales. Shopify's billing system supports combining recurring and usage charges natively, per its billing documentation, so the constraint is strategy, not plumbing.
One model deserves a warning label: percentage-of-revenue pricing converts beautifully ("we only make money when you do") and generates the angriest churn, because sooner or later a merchant does the multiplication on a good month and concludes you are their most expensive vendor. If you price this way, cap it, or add a flat-fee alternative at the top end before your best customers do the math.
Trial Length: Match It to Time-to-First-Value
Across top listings, 7-day and 14-day trials are the overwhelming pattern, with occasional 30-day trials on apps whose value takes time to accumulate. Treat those as observations from browsing the store rather than official statistics; Shopify publishes no aggregate trial data.
The right way to choose is empirical and specific to you: measure how long a new merchant takes to reach first value in your app.
- Same-session value (page builders, bulk editors, badges): 7 days is plenty, and shorter trials pull revenue forward and shorten CAC payback. The payback math that governs merchant acquisition applies to your app economics too: a week less of free usage across every cohort is not nothing.
- Accumulating value (analytics, surveys, email automation, anything needing traffic to prove itself): a 7-day trial shows the merchant an empty dashboard and asks them to pay for it. Use 14 or 30 days, and spend the trial emailing the merchant every time the app produces something worth seeing.
Two implementation notes that punch above their weight. First, onboarding should be designed against the trial clock: whatever your time-to-first-value is, your setup flow's job is to shrink it. Second, extend trials generously on request. A merchant asking for more time is a merchant still deciding, and the marginal cost of a week is zero.
Anchoring Tiers to Merchant Revenue Stage
The most common tiering mistake is segmenting by feature list ("Starter gets 3 templates, Pro gets 10") when the real segmentation variable in this ecosystem is merchant size. Shopify hands you a natural ladder: hobbyists on the entry Shopify plan, growing brands in the middle, and Plus merchants processing serious volume. Your tiers should climb that ladder.
Practical anchors, in rough order of usefulness:
- Order volume. The cleanest proxy for merchant size and, usually, for the value your app delivers. "Up to 500 orders/month" segments honestly.
- Usage of the thing you do. Emails sent, surveys collected, pages published.
- Team and workflow features. Multi-user, permissions, audit logs; these map to organizational maturity, which maps to budget.
- Shopify plan detection. Charging Plus merchants more via a Plus-specific tier is standard practice; a Plus store's tolerance for a $199/month tool is categorically different from a hobbyist's.
Sanity-check each tier against the merchant's own economics. A store doing $2,000 a month in revenue experiences a $29 app as a real decision; a store doing $200,000 does not notice it. Price each tier at a level its target merchant would describe as obviously worth it, and let the tier above capture the merchants for whom your value is 10x bigger.
Avoid more than three or four public plans. Every additional option slows the pricing-page decision, and the App Store listing displays your pricing prominently enough that confusion costs installs, not just conversions.
When Freemium Wins Installs but Kills Revenue
Freemium in the App Store is really a distribution strategy wearing a pricing costume. The distribution side is real: free installs feed the install velocity that App Store ranking rewards, free merchants leave reviews, and both compound the organic flywheel that Built for Shopify and the store's discovery surfaces amplify. Some of the biggest apps in the store climbed exactly this way.
The revenue side is where it goes wrong. Widely cited freemium conversion benchmarks across SaaS sit in the low single digits, and free merchants file support tickets at close to the rate paying ones do. Run the numbers on a freemium app with 5,000 installs: at a 3% conversion to a $29 plan, that is roughly $4,350 in MRR carrying the support, infrastructure, and roadmap weight of 5,000 accounts.
Freemium earns its keep only when the free tier has a mechanism, not just a hope:
- A growth ceiling. The free tier genuinely serves small stores and genuinely runs out as the store grows (order caps are the classic version). The merchant's success upgrades them, no sales motion required.
- A flywheel contribution. Free users visibly strengthen ranking, reviews, or network effects that paid acquisition would otherwise have to buy.
- Low marginal cost. If each free account carries real infrastructure or support cost, the model bleeds.
If none of those describe your app, skip freemium and use a good trial instead. A trial is freemium with a deadline, and the deadline is what converts.
Raising Prices Without a Churn Spike
Every successful app underprices v1, so plan for the increase before you need it. The mechanics matter here: in Shopify's billing system a subscription price change is a new charge the merchant must explicitly approve. There is no silent repricing of an existing subscriber. A forced migration is therefore a re-selling event for every affected merchant, which is why the standard playbook leans on grandfathering:
- New installs first. Raise prices for new merchants immediately. They never knew the old price; you will see the effect purely in listing conversion, which you should watch for two to four weeks.
- Grandfather existing merchants for a defined window (six to twelve months is common) or indefinitely for early cohorts. Legacy pricing for loyal merchants is cheap goodwill, and the cost declines as the cohort naturally churns down over time.
- If you must migrate everyone, give 30 to 60 days notice, pair the increase with shipped improvements you can point at, and write the email like a founder, not a billing system. Surprise, not price, drives most increase churn.
- Instrument it. Track cohort churn and downgrade rates around the change so you learn your merchants' actual elasticity rather than guessing. This is also a moment to make sure your subscription analytics stack is stable; plenty of developers had to rethink theirs when Mantle announced its shutdown, and running a price migration without reliable MRR and churn dashboards is flying blind.
Managed Pricing vs the Billing API, Strategically
You can run billing two ways, and the choice quietly shapes your pricing strategy's flexibility.
Shopify App Pricing (the evolution of managed pricing) means you define plans in the Partner Dashboard and Shopify operates the machinery: trials, recurring charges, proration, upgrades and downgrades, and price updates. Per Shopify's changelog, it now supports usage charges, recurring charges, or both together, which removed the last big reason most apps needed custom billing code. Shopify positions this as the default and recommended path, with the Billing API as legacy.
The Billing API hands your code full control: create charges, manage subscriptions, implement whatever logic you can imagine. The price is that you own the edge cases (declined charges, frozen stores, plan-change proration) forever. It remains the right choice for genuinely bespoke needs, such as negotiated enterprise contracts or billing logic no plan matrix can express. If you go this route, get comfortable with the underlying APIs; our Admin API guide covers the foundation that billing work sits on.
The strategic read: for a new app in 2026, use the managed path unless you can name the specific deal structure it cannot express. Standardized billing is faster to ship, easier for merchants to trust, and keeps your engineering time on the product. Custom billing code is technical debt you take on deliberately, for a reason you can articulate, or not at all.
Annual Plans: Cheap Retention, Underused
Shopify's billing supports annual intervals, and yet annual plans remain rare in the App Store relative to the broader SaaS world. That is an opening. An annual plan at a 15 to 20% discount does three things at once: it pulls a year of cash forward, it removes twelve monthly cancellation decisions from the merchant's calendar, and it drops measured churn, because prepaid merchants stop re-evaluating you monthly.
The caveats are real but manageable. Merchants uninstalling mid-term will expect refunds, so decide your refund policy before the first request rather than during it. And annual pricing amplifies whatever your product is: a year of prepayment for an app that stops improving becomes a year of accumulating resentment, delivered in one review.
Offer annual on your middle and top tiers once monthly retention is proven, not before. Selling a year of something you have not yet kept people paying for monthly is a bet you do not have the data to make.
Price Localization
Listing localization gets you found in non-English markets; price localization decides whether those merchants convert. A $49/month plan is background noise for a US brand and a genuine budget line for a merchant in Southeast Asia or Latin America, and a single global price quietly forfeits markets where your translated listing is winning attention.
Full per-country price books are usually overkill for an indie app. Lighter options: a cheaper entry tier that emerging-market merchants self-select into, regional discount codes offered through partners, or simply revisiting the decision when your Partner Dashboard geography data shows a market with high installs and low conversion. That pattern, lots of interest and few buyers, is the signature of a price-to-market mismatch.
Run the Repricing Audit This Month
Block two hours and answer four questions with data, not memory: What is your actual time-to-first-value, and does your trial length respect it? What share of your MRR comes from merchants whose value from your app is 10x your top plan? What would happen to listing conversion if new-install pricing rose 25%? And if you run freemium, what is your real conversion rate and cost per free account? Two hours on those four questions finds money for almost every app older than a year, because pricing set at launch encodes what you knew at launch, and you know more now.