Is BYOM pricing worth it for a growing Shopify brand?

The price on an app's page is rarely the price you end up paying. A flat fee, a usage charge, a fee per resolution and a share of your revenue all look affordable in a pricing table and behave very differently once your store grows. This post sets out the four common models, how Shopify's billing rules apply to them, what published per resolution prices cost at scale with the maths shown, and how to work out a payback period you can defend to yourself.

Four ways an app can charge you

Most Shopify apps use one of four models, and many mix them. A subscription charges a fixed amount each billing period. A usage charge counts something, such as messages, orders or AI actions, and bills for it. A per resolution or per outcome charge bills only when the software completes a task, such as answering a support ticket without a human. A revenue share takes a percentage of the sales the app is credited with.

Each one moves risk in a different direction. With a subscription the supplier carries the risk of a quiet month and you carry the risk of paying for software you do not use. With a usage charge you carry the volume risk, so a good month costs you more. A per outcome charge looks like the fairest model, because you pay for results, and it is only as fair as the definition of a result. A revenue share grows with your store whether or not the app is the reason the store grew.

Shopify's own developer terms show how much of a price is the platform's take. The revenue share page says developers keep 100% of their first $1,000,000 in gross app revenue earned from 1 January 2025, and 85% of earnings above that. It adds that all billing is subject to a 2.9% processing fee and applicable sales tax. A developer's price therefore has to cover those costs as well as hosting and support, and it is a reason not to expect prices to fall to nothing.

An independent count gives a sense of the field. A statistics roundup from Uptek, drawing on the App Navigator database, reports 11,905 apps in the Shopify App Store as of 14 November 2024, and says 47.01% of them, 4,560 apps, offer at least one free plan or trial. The same page quotes a blog's figure of $58.49 for the average monthly cost of an app across all plans. The page says the method behind that average is not disclosed, so treat it as a rough anchor and not a benchmark. The most expensive apps it identifies cost $999.99 a month.

What usage based means on the Shopify invoice

Shopify's developer documentation defines a usage based subscription as a pricing model that charges merchants continuously based on app use during Shopify's 30 day billing cycle. The merchant has to accept the pricing plan before charges begin. After approval, the app creates usage records, each of which documents a billable action and its cost.

The protection for you is the capped amount. It sets a maximum charge for each 30 day cycle, and the documentation says merchants can adjust the threshold themselves in the Shopify admin. Developers get a webhook when a merchant changes the cap, and another when usage approaches 90% of it, so the app is expected to be able to tell you. Ask any supplier what it does at 90% and what happens at 100%. Does the service stop, queue the work or carry on and bill the difference? Each answer is a different invoice.

Free trials work the same way. The developer sets the number of trial days on a plan, and billing starts when the trial ends. Shopify says it tracks trial days over a 180 day period to stop merchants from reinstalling an app repeatedly to get new trials. If a merchant uses 12 of 15 trial days, uninstalls and returns 90 days later, they still have three trial days left. That rule works in your favour as well as the developer's. A trial you started and forgot about is still counting down.

One more rule affects what you see. Shopify's app requirements tell developers to charge through Shopify's own billing, so a merchant can change plan from the admin without contacting support. The charge then appears on your Shopify bill. Billing outside that system means a separate invoice, a separate contract and a separate way to cancel.

Per resolution pricing at scale

Three helpdesk vendors publish a price per automated resolution. The table shows what each page said when we read it on 2 October 2026. Currencies are as published. Intercom and Gorgias quote in US dollars and Zendesk's UK page quotes in pounds.

Multiply the unit price by volume and the scale becomes visible. At 500 resolved conversations a month, Intercom's $0.99 comes to $495. At 2,000 it is $1,980, and at 5,000 it is $4,950, which is $59,400 over twelve months. On Gorgias's annual rate of $0.90, 5,000 interactions come to $4,500 a month, before the helpdesk plan and before the ticket count that each automated interaction also adds. At Zendesk's committed £1.30, 500 resolutions cost £650, 2,000 cost £2,600 and 5,000 cost £6,500, or £78,000 over twelve months.

The definition of a resolution is worth reading on each page. Zendesk says paying per automated resolution means you pay only for customer requests that were successfully resolved by the AI agent, without any escalation to a human agent. Intercom's page gives a minimum monthly commitment when Fin runs on an existing helpdesk, with an example of 50 outcomes. A minimum turns a variable price back into a fixed one for low volumes, and it is easy to miss in a table.

A flat fee and a per resolution fee cross over at a predictable volume. Divide a £200 monthly fee by Zendesk's £1.30 and you get 154 resolutions. Below that volume the per resolution price is cheaper than a flat £200. Above it, the flat fee wins. Most stores do not know their monthly count of conversations a tool could resolve, so measure it for a month before you pick a model.

Compare that with a salary. ONS figures for April 2025 put median gross annual earnings for full time employees who had been in their jobs for at least a year at £39,039. One person cannot handle 5,000 conversations a month, so the comparison is not with a single hire. Per resolution pricing is a variable cost with no ceiling unless you set one. A busy season, a product recall or a shipping delay multiplies the bill in the weeks you can least afford it.

Revenue share has the same shape. Suppose a tool takes 1% of the sales it is credited with. On £1,000,000 of annual sales credited to it that is £10,000. At £3,000,000 it is £30,000, for the same software doing the same work. The figures are hypothetical. Ask what is credited, over what window, and whether refunded orders are netted off.

• $0.99

  Intercom's published price per Fin outcome

  Intercom pricing page, read 2 October 2026

• £1.30

  Zendesk committed rate per additional automated resolution

  Zendesk UK pricing page, read 2 October 2026

• £19.67

  Median hourly earnings, full time employees, excluding overtime, April 2025

  ONS, Employee earnings in the UK, 2025

How to work out payback

Payback is the monthly cost divided by the monthly value, and the value has to be something you can count. Start with hours. ONS reports median hourly earnings of £19.67 for full time employees in April 2025, excluding overtime. That is wages before employer costs, so the real cost of an hour is higher, but it is a published figure you can use without argument.

For a flat £200 a month plan, the break even is £200 divided by £19.67, which is 10.2 hours. If the software saves your team ten hours a month, you are roughly level. If it saves thirty, the saving is about £590 against a £200 fee. Both numbers assume that the hours are released and used on something else. Ten minutes saved in forty scattered places is not ten hours, and a tool that saves time nobody redeploys saves nothing in cash.

For a per resolution price, divide the price by the hourly cost. Zendesk's £1.30 divided by £19.67 is £0.066 of an hour, which is just under four minutes. If a human takes more than about four minutes to resolve the same conversation, the automated price is lower on wages alone. If a human takes two minutes, the human is cheaper. A reasonable assumption for a typical order status question is that it takes a few minutes, so the maths is close, and the decision turns on quality and on what happens when the software is wrong.

Billing period changes the sums as well. Zendesk's UK page lists Support Team at £15 per agent per month on annual billing and £20 on monthly, and Suite Team at £45 against £59. For one agent that is a difference of £60 a year on Support Team and £168 on Suite Team. It is real money for a small team, and it comes with the commitment described earlier: you pay for twelve months to get it.

Count the cost of errors too. A wrong refund, a wrong promise about a delivery date or a wrong stock figure has a cost that the unit price does not cover. Ask whether a resolution that the customer reopens within a day is billed twice. Ask whether a resolution counts when a human steps in to finish the job. The definitions in the vendor's terms decide the real unit cost far more than the headline number does.

Review the number again after the first full billing cycle, using the invoice and not the plan page. Usage charges, overage and tax show up on the invoice and nowhere else. If the real figure is more than a fifth above what you expected, find out which line caused it before the second cycle starts, while the trial and the cap are still the easiest things to change.

A simple template keeps the decision honest. Write down the monthly price at your current volume and at double it. Write down the hours it replaces and the hourly cost. Write down the cap or the exit. If you cannot fill in all five numbers from the vendor's published terms, ask the vendor for the missing ones before you start the trial.

Questions that expose the real price

Run the table against every shortlisted app and keep the replies with the date. The vendor that answers all six without a sales call has priced the product in a way you can plan around.

What BYOM charges

Explore is £200 a month, with no revenue share, no transaction fees and no fees per resolution.