Shopify Multi-Channel Reporting in Google Sheets

The Master SKU Is What Stops One Product From Becoming Two

I would not start a multi-channel report with Amazon revenue or Shopify revenue. I would start with the product.

The same product can have one Shopify SKU, one Amazon seller SKU, one ASIN, and maybe a bundle SKU on top of that. The mistake is letting each platform name the product differently with no master SKU tying it together. Without that mapping, your formulas treat the same physical item as two separate products.

The master SKU is what keeps one product from becoming two different stories in your data. If your SKU structure is already messy across platforms, Shopify SKU management covers the cleanup before you try to build anything on top of it.

200 Orders on Amazon. 20 on Shopify. Which One Is More Work?

I can do 200 orders a day on Amazon FBA. My main job for those orders is sending pallets to the fulfillment center. Amazon picks, packs, ships, handles customer service, and processes returns. Twenty Shopify orders a day at a similar revenue number means someone at my 3PL or local warehouse is picking, packing, and shipping every single one of them.

Same line on your revenue report. Completely different operational reality.

That difference matters when you decide where to grow. Double your Shopify volume and your fulfillment workload doubles with it. Double Amazon and your workload is one more pallet. A report showing only revenue per channel hides that cost entirely, and you can end up investing in the channel that looks good on a dashboard while your ops team is drowning.

For each product, here is what I want to see across channels:

If product cost changes your channel decision, Shopify COGS tracking brings gross margin per channel into the same workbook. Revenue without cost can make the wrong channel look like the winner.

Why the Price Gap Between Channels Cannot Be Reconciled

Customers use AI to compare prices across channels before they buy. Someone finds your product on Amazon, the AI surfaces your brand website, and they check whether the direct price is better. That path happens constantly now.

So I deliberately price Shopify a few points below Amazon on purpose. The math: capturing a direct sale eliminates the Amazon referral fee, which means the discounted price can actually net more than the Amazon sale at full price. It is a strategy for pulling customers off-platform and keeping more of the margin.

When both channels are in separate reports, the different average order values look like a data error. Someone on your team will try to reconcile them. They cannot be reconciled: that gap is intentional.

When both channels sit in the same sheet with fees applied, you can see whether the strategy is working. If your Shopify net after the discount and your own fulfillment cost is higher than Amazon net after fees, the direct-capture play is correct. If it is not, you are discounting without capturing the benefit.

The 12-Unit Problem and Why Inventory Is Where Channels Collide

And if your Amazon FBM and Shopify both pull from the same local warehouse, the stock count has to be accurate at the warehouse level. Say the warehouse shows 12 units. Seven Amazon orders come in and five Shopify orders come in. On paper, that works.

If the real count is 10, two of your customers have a problem: cancel, delay, or backorder. That is an embarrassing situation that feels entirely preventable, and it happens because neither platform could see what the other was doing.

Your Shopify inventory management tab pulls available units from Shopify's API. Amazon inventory comes in separately. Both sitting in the same workbook, joined by master SKU, is what gives you a combined stock position before orders start coming in from both sides.

Amazon Destroys Returns. Shopify Sends Them Back.

When a customer returns a product through Amazon FBA, I have the setting to destroy it rather than have it shipped back. The reason is practical: an open or damaged product coming back risks getting accidentally resold. Amazon destroys returned items and the transaction is closed.

A Shopify return comes back to my warehouse or 3PL. Someone physically checks it, decides if it is resellable, and either puts it back in stock or disposes of it.

Those are two completely different return flows with two different effects on your inventory position. Neither channel's report shows you the other. Your Shopify returns data and your Amazon FBA returns data need to sit together for the reorder number to actually mean anything.

The Monday Morning Problem

You want one number: what did the business make last week?

Amazon's revenue figure does not include the full fee breakdown unless you pull a settlement report. Your Amazon seller fees live in a completely different export. Shopify's revenue figure has payment processing netted against it but pending returns still included. Your ad spend is in a third platform. Your 3PL invoice for Shopify orders arrives at the end of the month on its own cycle.

None of those are on the same screen. Getting to your real net number means logging into each platform, reading each number, and doing the subtraction yourself. Amazon's settlement cycle runs on a biweekly schedule while Shopify reports on transaction date, so the timing is mismatched on top of everything else.

That rebuild currently takes your team 90 minutes every Monday.

How the Workbook Is Structured

When your Shopify data connects through our Shopify to Google Sheets connection and your Amazon data connects through the Amazon seller data connection, they land in separate source tabs. If your team has been using Shopify order exports manually, this replaces that workflow. Keep them separate: the platforms use different date structures and fee timing. The reconciled view is built on top of those source tabs.

Your product_channel_view tab is where the business reads the product. Use order date as the join field, not Amazon's settlement date. Amazon settlements land two weeks late and will throw off any period comparison if you build on settlement timing.

For daily monitoring after a change to one channel, the Shopify sales tracker covers the comparison window that makes channel changes visible at the day level before you wait a full week.

The Decisions the Sheet Makes Faster

Your multi-channel sheet does not need to answer every ecommerce question. It needs to make a few product-level calls easier:

Should Shopify get the better discount because you want the direct sale? Should Amazon get more inventory because FBA handles the fulfillment work? Should a product get pushed on the channel where it already converts? Should a product stop getting inventory because it looks weak on both channels? Should a higher return rate on one channel change how you judge that channel's revenue?

That is enough. The joined tab is where your business reads the product. Start there.

When a Unified Sheet Doesn't Help

Single-channel sellers do not need this. If you only sell on one platform, combining data adds structure for a problem you do not have.

We are the wrong call if you need real-time inventory sync across platforms. Our connection pulls on a schedule. The allocation decision is still yours. If you need a system that automatically shifts stock between Amazon FBA and Shopify fulfillment based on velocity, that is a dedicated inventory management tool.

Your sheet earns its cost when the gap between what each platform shows and what the business actually made is large enough to change a real decision, and when closing that gap currently takes your team 90 minutes every Monday.

If Walmart becomes your third channel later, the same tab structure extends: add a Walmart source tab, add Walmart to the channel column in the SKU map, and product_channel_view picks it up. The Shopify and Amazon integration article covers the master SKU structure that keeps all three channels joinable on the same product identifier.