Track this on a live dashboard
Connect your store and watch these numbers update themselves — no spreadsheets.
No commitment until you’ve seen your own numbers
If you sell on Amazon and Shopify, you already know the shape of the problem: Amazon sales never show up in Shopify's revenue, and Amazon ad spend never shows up in Shopify's marketing reports. Each platform is confidently reporting a fraction of your business as though it were the whole thing.
So the weekly question — how is the business actually doing? — becomes a manual job. Two logins, two exports, a spreadsheet, and a number that is already a few days old by the time anyone looks at it.
This guide covers the four ways sellers actually solve this, what each one costs in time and money, and the three traps that make combined numbers wrong in ways that are hard to spot.
It is tempting to assume this is an oversight that Shopify or Amazon will eventually fix. They will not, and the reason is structural: each platform's analytics exist to show you performance *on that platform*. Shopify has no commercial reason to surface how well you are doing on Amazon, and Amazon has considerably less.
Even if they wanted to, the data does not line up. A "sale" on Shopify is an order at checkout. On Amazon it is an order that may be cancelled before dispatch, may be returned within a long window, and carries referral and fulfilment fees deducted at different points. Currencies, timezones and refund handling all differ. Stacking the two revenue numbers on top of each other produces a figure that is wrong in a direction you cannot predict.
This is why the combining has to happen somewhere else, and why doing it carelessly is worse than not doing it at all.
Export each platform's sales report, paste both into a sheet, and reconcile by hand. Almost every multichannel seller starts here, and it works: it is free, you control every assumption, and building it forces you to understand exactly how each channel reports.
The costs are time and staleness. Half an hour a week is twenty-six hours a year, and the number is only correct on the day you build it. More subtly, a manual process gets skipped in exactly the weeks you are busiest — which are usually the weeks something interesting is happening.
Worth doing once, deliberately, even if you later automate it. The reconciliation teaches you where the two platforms disagree, and you will need that knowledge to sanity-check any tool you buy.
Shopify's analytics are genuinely good for Shopify. Amazon's Business Reports are genuinely good for Amazon. Neither can see the other, and no amount of configuration changes that.
The trap here is subtle: because each report looks complete, it is easy to make decisions on a partial view without noticing. A product that looks like a poor performer in Shopify may be your best seller overall. An ad campaign that looks unprofitable on Shopify's attribution may be driving Amazon searches you never see.
Pipe both platforms into a warehouse — BigQuery, Snowflake — with an ELT tool, then build reporting on top. This is what larger operations do, and it is the most powerful answer: full history, arbitrary joins, blended CAC and LTV models, no vendor limits on what you can ask.
It is also the most expensive in both money and skill. You need the pipeline, the warehouse, a BI layer and someone who can write SQL and maintain all three. For a business doing seven figures across several channels with an analyst on staff, this is the right answer. For a seller doing the reporting themselves on a Sunday evening, it is a project that never quite finishes.
Connect each channel's API once, and a dashboard tool normalises them into one view: a combined total, the per-channel split beneath it, and ad spend alongside the sales it drove. No exports, no SQL, and it stays current on its own.
This is the middle path, and it is where most multichannel sellers land. The trade-off against a warehouse is depth: you get the numbers a dashboard can express rather than any question you can imagine. The trade-off against a spreadsheet is control: you inherit the tool's definitions of revenue and fees, so it matters a great deal whether the tool is honest about what it is showing.
That last point deserves more weight than it usually gets. A dashboard that quietly displays a stale figure, or fills a gap with an estimate, is more dangerous than a spreadsheet you know is a week old — because you will trust it.
Double-counting ad-driven sales. If you run Amazon Ads and Meta ads that both influence the same purchase, adding each platform's reported attributed revenue produces a total larger than your actual revenue. Attribution windows overlap and platforms all claim credit. Use blended metrics — total ad spend against total revenue — as the honest top-line, and treat per-platform ROAS as directional rather than additive.
Comparing gross to net. Shopify revenue is typically gross of payment fees; Amazon revenue as sellers usually see it is already net of referral and FBA fees. Comparing them directly makes Amazon look worse than it is, sometimes dramatically. Decide whether you are comparing gross revenue or contribution margin, and apply the same definition to both.
Ignoring the refund lag. Amazon's return window means a strong month can lose several percent of its revenue weeks later. A combined dashboard that reads today's numbers will overstate recent Amazon performance relative to Shopify. If you are making inventory decisions on it, look at a period old enough to have settled.
Seeing the numbers together is not the point. The point is the decisions that only become possible once you can: which channel deserves the next tranche of inventory, which products earn their shelf space on which platform, and where the next advertising pound does the most work.
Those are the questions a per-channel view cannot answer, because every one of them is a comparison. A seller looking only at Shopify cannot tell that a product's margin is twice as good on Amazon after fees; a seller looking only at Amazon cannot tell that their brand site converts the same traffic at a higher contribution margin.
So when you evaluate any of the four options above, judge it on whether it makes those comparisons easy and honest — not on how many charts it produces.
Dash Captain is option four: connect your channels and see sales, ad spend and profit across all of them on one board, with what changed flagged for you. Tiles state plainly when data is live, stale or missing, which matters most exactly when you are combining sources that can each fail independently.
Being straight about status: Google Analytics and Search Console are live today. Shopify is in early access. The Amazon Seller API connector is still in the approval queue, so the full Amazon-and-Shopify-in-one-board promise is not something you can switch on this afternoon. If that is what you need working today, one of the warehouse tools or an established multichannel analytics vendor will serve you better, and we would rather say so here.
What you can use right now, with no connector and no signup, are the calculators — the FBA fee calculator, contribution margin, blended ROAS and break-even tools all work on numbers you paste in, and they encode the fee and margin logic this guide describes.
Four ways, in ascending order of cost and power: export both to a spreadsheet and reconcile manually; use each platform's native reports separately and accept the blind spots; pipe both into a data warehouse and build BI on top; or connect both to a dashboard tool that normalises them into one view. Most sellers doing their own reporting land on the dashboard option; teams with an analyst tend toward the warehouse.
Because Shopify only knows about orders placed through Shopify. Amazon is a separate marketplace with its own checkout, and unless you are using a listing integration that writes orders back into Shopify, those sales are invisible to it. The same applies in reverse, and to ad spend on both sides.
Not safely. Amazon revenue as sellers usually see it is already net of referral and fulfilment fees, while Shopify revenue is typically gross. Adding them mixes two different definitions and understates how Amazon is really doing. Pick one basis — gross revenue, or contribution margin after fees — and apply it to both channels before comparing anything.
It depends on which problem you actually have. If you need listings and inventory synchronised across marketplaces, you want multichannel listing software — a different category entirely, and not what a reporting dashboard does. If you need to see performance across channels and decide where to invest, you want an analytics dashboard or a warehouse. Confusing the two is the most common mistake in this search.
Not yet — the Seller API connector is built but sitting in Amazon's approval queue, and we list it as "coming soon" rather than claiming it. Shopify is available in early access today, Google Analytics and Search Console are live, and the free calculators work with no account at all.
Connect your store and watch these numbers update themselves — no spreadsheets.
No commitment until you’ve seen your own numbers
Revenue is vanity; profit is sanity. Walk the profit ladder — gross, contribution and net — learn which costs belong where, how discounts, shipping and returns bite, and how to find the numbers that tell you if you're actually making money.
Amazon's referral fee runs from 5% to 45% by category, and the FBA fee is set mainly by size and weight. What each fee costs, and how to work out what you keep per unit.
Blended ROAS — also called MER — divides total revenue by total ad spend across every channel. Learn the formula, why it's lower (and more honest) than per-platform ROAS, and what a good number is.
Amazon and Shopify charge completely different fees, so comparing their revenue tells you nothing about which one actually makes you money. Here's the contribution-margin method that compares them fairly, a worked example, and three ways the comparison quietly goes wrong.