How to Estimate a Shopify Store's Revenue: A Working Formula

Why you'd even want to know

The question usually shows up in a specific moment. You're about to pitch an agency's services to a brand and want to know if they can afford you. You're an app developer deciding which stores to cold-email. You're sizing up a competitor before a meeting. In every version, the honest answer is the same: Shopify doesn't publish store-level revenue, and there's no public API that hands it to you. What you can do is build an estimate from what's visible, and be upfront about how rough that estimate is.

This post walks through the formula nearly every guide on this topic leans on, where its three inputs actually come from, what a storefront's tech stack and catalog can add to the picture, and where the exercise falls apart if you push it too far.

The formula, and why it's smaller than it looks

Every methodology for this question reduces to the same three-variable equation:

Traffic x Conversion Rate x Average Order Value = Revenue

A worked example from WinningHunter's write-up on the topic shows the mechanics plainly: 20,000 monthly visitors at a 3% conversion rate is 600 orders a month, and 600 orders multiplied by the average order value is the monthly revenue estimate.

StoreCensus runs a similar calculation at a larger scale: 100,000 visitors a month at a 1.5% conversion rate is 1,500 orders, which it multiplies by an average order value and then adjusts upward for repeat purchases.

Those are clean numbers on purpose. Real stores rarely hand you round figures for any of the three variables, and each one is a separate estimation problem in itself. That's the part most short explanations skip past.

Where the three numbers actually come from

Traffic

You don't get a store's real analytics. You get a third-party estimate of traffic from a tool that models it off indirect signals, and that estimate carries its own error bars before you've multiplied anything.

Traffic quality matters as much as traffic volume. StoreCensus's research found organic traffic converts around 3.6%, compared with 0.8% to 1.2% for paid social traffic. A store pulling 50,000 visitors mostly from paid social ads is not comparable to a store pulling 50,000 visitors mostly from organic search and email, even though the top-line traffic number looks identical.

Conversion rate

This is the variable with the widest range of plausible values, and it's also the one you can least verify from outside. StoreCensus puts the median conversion rate for Shopify stores at 1.4% to 1.8%, though this varies by category. Gift-category stores, in their data, hit as high as 4.9%.

Without access to the store's own analytics, you're picking a number from a benchmark range and hoping the store in front of you sits close to average. It usually doesn't, in one direction or the other.

Average order value

AOV is the easiest of the three to approximate, because you can often see product prices right on the storefront. It's also the easiest to get wrong, because listed prices don't account for bundling, discounts, or the fact that bulk buyers skew the real average upward. Treat a visible price scan as a starting estimate, not the final number.

If you want a fast read on a store's price range and product count without clicking through every collection page by hand, a product exporter pulls the catalogue into a spreadsheet, which makes it much quicker to compute a rough average across the whole product line instead of eyeballing a handful of items.

Reading the store itself

Traffic, conversion, and AOV get you a number. The storefront itself gives you context for whether that number is believable, and this is the part most guides underweight.

App stack. StoreCensus's data puts the average Shopify store at 6.4 installed apps. A store running well past that, especially with apps for enterprise inventory sync, loyalty programs, or subscription management, is signaling a larger operation than a store running the default theme with two or three basic apps. An app detector matches the scripts and assets a storefront loads against known app signatures, so you can see which of the apps it recognises leave a trace in the page without digging through the page source yourself. Treat what it finds as a lower bound: apps that run only in the admin, the checkout, or on Shopify's servers leave nothing in the page, so a short list does not mean a small operation.

Catalog growth. StoreCensus also tracked SKU count rising 14% year over year across the stores in their sample, from an average of 278 to 316 products. A growing catalogue isn't proof of growing revenue on its own, but a store that keeps adding products is behaving differently than one that's been static for a year.

Theme and checkout customization. Which theme a store runs, and how far it has been customized, is a weaker but still useful signal, particularly for Shopify Plus stores where checkout.liquid customization, custom scripts, or a B2B storefront usually mean the merchant had the budget and the reason to pay for that work. A theme detector tells you the theme a storefront declares, which is the quickest first step. It cannot tell you how heavily that theme was modified or what was done to the checkout; judging that means looking at the store yourself, and a store that looks stock from outside may not be.

Repeat purchase behavior. StoreCensus's research found repeat purchases account for over 40% of total revenue at the stores they studied. You can't observe this directly from outside a store, but it's worth remembering when a single traffic snapshot looks low: a good share of a healthy store's revenue isn't coming from the visitors you're counting that month at all.

None of these signals convert into a number by themselves. They're there to tell you whether the number from the formula is in the right neighborhood.

What none of this proves

Brandsearch, which runs a revenue estimator tool, states that the estimates it marks high-confidence are typically within 15-25% of actual revenue. That is one vendor's claim about its best-case estimates from one tool, not an independently tested figure, and it says nothing about how close a hand-built formula will get. A formula built on estimated traffic, a benchmark conversion rate, and a scraped price list has no published error rate at all, and it can land far off for stores with unusual traffic mixes or heavy wholesale and B2B revenue that never touches the public storefront.

It's also worth being specific about what the exercise doesn't tell you. It doesn't tell you profit margin, ad spend, refund rates, or whether the number you calculated for one month resembles a typical month for that store. A single-month traffic estimate is a snapshot, not a trend. Brandsearch's own data notes that only 10-15% of new Shopify stores clear even a modest monthly revenue threshold within their first six months, a useful reminder that most stores you'll estimate sit on the low end of the range, not the high end.

If you're going to quote a revenue estimate back to a client, a prospect, or in a pitch deck, the responsible move is to present it as a range with the method attached, not a single confident figure. A low and a high monthly figure, with the date and the method ("based on traffic and average pricing") written beside them, is a defensible sentence. A single figure quoted to the dollar is not, no matter how precise the underlying spreadsheet felt while you were building it.

A repeatable way to size up a store before you pitch it

If you're doing this for agency or app-developer purposes, the useful version of this exercise isn't a one-off calculation. It's a checklist you run before deciding whether a store is worth pursuing:

1. Pull an estimated traffic range and note the source and date, since these estimates shift and go stale.
2. Apply a conversion rate from the middle of the published benchmark range for the store's category, not the high end.
3. Sample product prices across the catalogue rather than just the homepage featured items, to get a realistic AOV.
4. Check the visible app stack and theme for signals of scale, particularly Plus-tier indicators like custom checkout or multi-currency support.
5. Cross-check against hiring signals, like open roles on a careers page or LinkedIn, if you have time. None of the leading guides on this topic mention this step, but a store hiring three marketing roles is behaving like a bigger business than the revenue formula alone might suggest.
6. Write the estimate down as a range, with the date and the method attached, so anyone reading it later knows exactly how much to trust it.

That last step matters more than it sounds like it should. An estimate without a date and a method tends to get repeated as fact a few months later, once nobody remembers it was a guess to begin with.

FAQ

Is Shopify store revenue public information? No. Shopify doesn't publish per-store sales data, and there's no official way to look it up. Every method described here, including the traffic times conversion times AOV formula, is an estimate built from indirect signals, not a reported figure.

How accurate are Shopify revenue estimator tools? Brandsearch, one of the few tools that publishes an accuracy figure for its own estimator, states that its high-confidence estimates are typically within 15-25% of actual revenue. That is a self-reported figure for that one tool, and it covers only the estimates the tool itself is most confident in. There is no independent benchmark for formula-based estimation in general, and an estimate built from third-party traffic and a benchmark conversion rate can miss by more than that.

What is the average Shopify store's revenue? Published averages differ from source to source, and every one of them is pulled upward by a small share of very large stores. The typical store you look up sits well below the average, which is one more reason to write an estimate down as a range rather than a single figure.

What tech stack signals suggest a higher-revenue store? A larger-than-average app count (StoreCensus found the average sits at 6.4 apps), a growing product catalogue, and Shopify Plus indicators like checkout customization or multi-currency support are worth checking. None of them confirm revenue on their own, but together they tell you whether a formula-based estimate is plausible.

Where the estimator fits in

Running the formula by hand means pulling a traffic estimate from one place, a conversion benchmark from another, and averaging prices off the storefront yourself. It works, but it's three separate lookups for one number. Doing that lookup for every store on a prospect list adds up fast, and that's the actual point of the checklist above: know when a manual pass is worth the time and when it isn't.

For a first read on any specific store, try the Shopify revenue estimator. It works differently from the formula: it tracks a store's inventory over time rather than modeling traffic. For a store it has watched long enough, it shows a floor, what the store demonstrably took over the window, alongside a monthly projection, and it labels which is which; those two figures are the part that sits behind a plan. For a store it hasn't watched long enough yet, it tells you it is still gathering data instead of guessing, and how long it has been watching any store is free to see.