Shopify Amazon Integration in Google Sheets: Run Both Channels From One Workbook

Shopify & Amazon Integration for the Full Picture

I had 12 units in my local warehouse. Seven orders came through Amazon, five through Shopify. The software was not syncing correctly. What I actually had was 10. So I had to go back to two customers for a cancel or backorder conversation. That is an embarrassing thing to admit, and it is entirely avoidable when both channels draw from one accurate count instead of two separate ones that do not talk.

That is the inventory version of the problem I described.

And I sell products that barely move on Shopify but do well on Amazon.

I sell others that do the opposite.

If I am looking at each channel separately, I see average performance in one place and strong performance in another. What I am actually missing is the same product across both channels at the same time: which channel is pulling faster, whether I am allocating inventory to match it, and whether the next purchase order reflects real combined demand.

The SKU Map Comes First

Your first problem is almost always identity. Shopify has one SKU, Amazon may have another, FBA and FBM can use different codes, and bundles or multipacks make it messier.

Your platforms do not need to match. Your business needs a master SKU.

On Amazon a listing might be WIDGET-BLU-LG. On Shopify that same product is SHP-WDG-BL-L. Same unit. In your data without a mapping table, they are two separate products. A SUMIF on SKU returns zero and the pivot shows them as strangers.

Your master SKU fixes this: every formula references it, platform-specific codes stay native, and your sheet sees one product instead of two.

If your SKU structure needs deeper cleanup first, Shopify SKU management covers the variant-level structure.

Inventory Allocation Is the First Real Use Case

If you run Amazon FBM and Shopify from the same physical stock, the count has to be accurate where the product ships from. Both channels drawing from the same pool without a shared count is where the 12-unit problem lives.

If your Shopify inventory management tab is already pulling available units per location, that is the Shopify side of the combined count. Amazon FBA inventory comes from your Amazon connection. Together they give you a stock position that reflects what both channels can actually fulfill.

Channel Performance: Same Product, Different Story

This is where a Shopify Amazon integration workbook earns its keep beyond inventory.

Take a product that sells well on Amazon but has worse return rates than Shopify. Your net revenue looks different once refunds are in. A product does better on Shopify because the brand story matters there and Amazon is price-competitive. A product is slow on both channels, which means the next purchase order is a bad idea regardless of what either platform shows individually.

Your Shopify sales report gives you the Shopify order rows with refund amounts per SKU. Your Amazon seller data gives you the equivalent from Seller Central. Joined by master SKU in the same workbook, the comparison is one row per product: Amazon net revenue, Shopify net revenue, which channel is growing, which is slowing, and whether cost data changes the picture.

If product cost affects your allocation decision, keep Shopify COGS tracking close. Channel revenue without cost can make a product look stronger than it is.

Keep Raw Tabs Separate, Then Join

Do not dump both platforms into one raw tab. Their fields, timing, order structures, refund handling, and fulfillment paths are all different. Keep your source data separate, then join by master SKU.

Raw data stays raw. Your business comparison happens in product_channel_view, built on top of the SKU map. That structure scales cleanly if Walmart gets added: one more source tab, same mapping approach. The Shopify to Google Sheets hub covers how the Shopify side of this workbook is structured.

The Purchase Order Gets Easier to Trust

Under-ordering across two channels is expensive in a specific way: emergency shipping, an earlier container than planned, higher storage and holding costs, more duties and landed fees than budgeted. It happens when you look at one channel's velocity without the other and place an order based on half the demand picture.

A combined sheet gives you a cleaner read before committing to the next buy. Same product, both channels, current velocity, days of supply, reorder flag. That saves the team from logging into Shopify, Seller Central, your shipping software, and three spreadsheets just to answer whether to place an order this week.

When This Sheet Adds No Value

Single-channel sellers do not need this. If you only sell on Amazon or only on Shopify, the unified view adds structure for a problem you do not have.

If ShipStation or NetSuite already syncs inventory across your channels and you trust the counts, the inventory reconciliation piece is redundant. The remaining case for the combined view is performance analysis, but only if you are actively making allocation calls based on channel performance. If the data sits in the sheet and nobody acts on it, the build was not worth it.

We do not automatically sync inventory or push purchase orders. Our connection pulls the data on a schedule. A person reviews the combined view and pulls the trigger. If you need that loop automated, it is a different tool.

Before You Build

Do Shopify and Amazon SKUs need to match?

‍No. Plenty of brands use different SKU syntax per channel. The master SKU mapping table connects them: platform codes stay native, business reporting uses the master.

What if a product only exists on one channel?

‍The master SKU still lives in the mapping table with a blank for the missing platform. Combined velocity for that SKU is just the single-channel number. The formula handles it.

Does this work for three channels?

‍Yes. Add a Walmart source tab and a walmart_sku column to the mapping table. The product_channel_view picks up the third channel. Same structure, same master SKU logic.