Amazon Shopify Walmart Reporting From One Google Sheet

Amazon Shopify Walmart Reporting Integration

Amazon Shopify Walmart reporting gets messy when the same product sells on three channels and each channel gives you a different version of the answer.

Amazon shows one number. Shopify shows another. Walmart shows another.

We have been on Amazon since 2012, and every channel we added after that created the same reporting problem in a different costume. Amazon had settlement timing, FBA fees, ads, and inventory. Shopify had orders, payouts, discounts, refunds, and payment fees. Walmart had order status, WFS or seller-fulfilled stock, item IDs, and its own reconciliation flow.

A Shopify Community reconciliation thread described the exact problem: payout does not equal orders, fees and refunds do not line up cleanly, COGS has to be tracked by SKU, and Amazon plus Shopify need to land in one view before SKU-level profit makes sense. That thread is worth linking because it clearly shows that report breaks when payout, order, fee, refund, and COGS data live in separate places.

Your SKU mapping tab makes your spreadsheet more reliable

Amazon, Shopify, and Walmart reporting should start with a simple SKU mapping tab that connects each channel’s SKU to one internal SKU your team uses for reporting.

MASTER_SKU is the first tab to build

MASTER_SKU is the product translator.

Amazon may call the product BLK-MUG-12OZ. Shopify may call it Black-Mug-12. Walmart may use a seller SKU or item ID that does not match either one.

Your combined report needs one name for that product.

Use this structure:

Every combined formula should return internal_sku first.

Amazon SKU to internal SKU:

=XLOOKUP(B2, MASTER_SKU!B:B, MASTER_SKU!A:A, "")

Shopify SKU to internal SKU:

=XLOOKUP(B2, MASTER_SKU!C:C, MASTER_SKU!A:A, "")

Walmart SKU to internal SKU:

=XLOOKUP(B2, MASTER_SKU!D:D, MASTER_SKU!A:A, "")

If the formula returns blank, stop there. That SKU is not ready for the combined report.

A blank product key is not a small issue. It means the sale can disappear from the view your team trusts.

Keep the platform rows separate first

Amazon rows should land in Amazon tabs. Shopify rows should land in Shopify tabs. Walmart rows should land in Walmart tabs.

Do not squeeze all three into one import tab like what our competitors tryto do to nickel and dime you for the subscription.

I would start with:

• AMZ_ORDERS
• AMZ_INVENTORY
• AMZ_ADS
• AMZ_SETTLEMENT
• SHOPIFY_ORDERS
• SHOPIFY_REFUNDS
• SHOPIFY_PAYOUTS
• WALMART_ORDERS
• WALMART_INVENTORY
• WALMART_RETURNS
• WALMART_SETTLEMENT

Then use calculation tabs to translate them into the same product view.

Think of it like sorting receipts from three stores. You do not rewrite every receipt first. You keep each receipt clean, then total the parts you actually need.

For the Amazon-only source structure, use the Amazon seller data to Google Sheets guide. For Shopify source data, use the Shopify to Google Sheets guide. For Walmart source data, use the Walmart Seller Center guide.

Build the combined sales view before margin

CHANNEL_SALES_VIEW should be the first real combined report.

Start with these columns:

• internal_sku
• product_name
• amazon_units
• shopify_units
• walmart_units
• total_units
• amazon_sales
• shopify_sales
• walmart_sales
• total_sales

You can build the first version with SUMIF.

Amazon units by product:

=SUMIF(AMZ_CALCS!B:B, A2, AMZ_CALCS!D:D)

Shopify units by product:

=SUMIF(SHOPIFY_CALCS!B:B, A2, SHOPIFY_CALCS!D:D)

Walmart units by product:

=SUMIF(WALMART_CALCS!B:B, A2, WALMART_CALCS!D:D)

In these examples:

• Column B is internal_sku
• Column D is units_sold
• A2 is the product in your combined view

Then total the three channel columns:

=B2+C2+D2

This is plain, but that is the point. A combined view should be easy to audit.

If Amazon units look wrong, check the Amazon calculation tab. If Shopify units look wrong, check Shopify. If Walmart units look wrong, check Walmart. Do not hide all three inside one monster formula.

Inventory tells you whether the sales can continue

A product can be winning across all three channels and still be one week away from a stockout.

That is why the second combined view should be inventory.

Use:

• internal_sku
• Amazon available units
• Shopify available units
• Walmart available units
• total available units
• 30-day units sold
• average daily units
• days of supply
• reorder flag

Simple days of supply:

=IFERROR(Total_Available_Units / Average_Daily_Units, "")

Simple reorder flag:

=IF(Days_Of_Supply<30, "Reorder", "OK")

Change 30 to your actual lead time.

This is where the sheet becomes useful. You are no longer asking, “What sold on Amazon?” You are asking, “Can this product keep selling across Amazon, Shopify, and Walmart?”

According to Walmart’s Inventory API documentation, sellers and approved solution providers can retrieve and update current SKU inventory by ship node. That reinforces the same operating point: inventory needs to be tied to SKU before it belongs in any channel summary.

More docs if you want to take on the APIs directly yourself.

• Amazon Orders API documentation
• Shopify Order documentation
• Shopify Inventory Level documentation
• Walmart Orders API documentation
• Walmart Inventory API documentation

Stabilize your input data

Margin should come after sales, inventory, refunds, fees, ad spend, and COGS are clean.

I would not start with margin. It is the most tempting view and the easiest one to fake.

Use a formula like this only after the inputs are ready:

=Gross_Sales - Refunds - Platform_Fees - Ad_Spend - (Units_Sold * Unit_COGS)

That formula is simple. The hard part is making sure each part uses the same product key and the right time window.

If sales use order date and payout uses settlement date, label those separately. Do not blend them into one clean-looking number.

For Amazon fee data, use the Amazon seller fees into Google Sheets article. For dashboard layouts after your data is already connected, use the Amazon seller dashboard in Google Sheets guide.

Keep the sheet read-only for decisions

A shared Google Sheet can be your review file without becoming the system that changes live stock, prices, or listings.

I would use the sheet to answer:

• What sold?
• What came back?
• What stock is left?
• Which channel is carrying the product?
• Which SKU needs attention?
• Which margin number deserves a closer look?

Then I would make account changes inside Amazon, Shopify, Walmart, or a dedicated inventory tool.

Changing live stock, pricing, or listings from a shared reporting workbook is a different risk level. Keep this workbook downstream unless your team has intentionally built and tested write-back controls.

You'll begin to see why for 99 out of 100 sellers, it's not worth the time and hassle to transform yourself into a software development company. Do what you do best, which is marketing and selling your products. Not getting sidetracked into thinking you can save $100/mo and end up spending 6k/mo to build a broken side project software.

How to use Gorilla ROI

Our software fits when your team wants Amazon, Shopify, and Walmart data in one Google Sheet without rebuilding exports from three platforms.

Gorilla ROI is a Google Sheets data connector and hub for ecommerce operations, so Amazon, Shopify, and Walmart live data can load in the same workbook that your team already uses.

Gorilla ROI quick start guide shows how you can use our add-on to pull data from Amazon Seller Central, Amazon Ads, Shopify, and Walmart.

The workflow is:

1. Pull each channel into its own source tabs.
2. Map channel SKUs to internal_sku.
3. Build CHANNEL_SALES_VIEW.
4. Add inventory coverage.
5. Add refunds, ads, and margin after the first view works.

For ad fields like ACoS, ROAS, TACoS, clicks, and impressions, use the Amazon advertising metrics guide.

Video showing Shopify to Google Sheets integration

This is just one of the many video tutorials on integrating all ecom platforms we support. Go to our Gorilla ROI channel for more videos.

Use separate reports if the problem is still small

Use separate reports if three-channel reporting is not a weekly pain yet.

Gorilla ROI is the wrong fit if your team does not use Google Sheets for review, if one channel still does almost all the revenue, or if a few manual exports answer the question in under 30 minutes a week.

I would also slow down if you need write-back inventory syncing, custom Shopify metafields, or detailed Walmart Connect attribution. Confirm those needs separately before treating a reporting sheet as the answer.

Build this in order

Use this order before you trust the combined view.

1. Build MASTER_SKU.
2. Confirm every channel SKU maps to internal_sku.
3. Keep Amazon, Shopify, and Walmart source tabs separate.
4. Pick the date rule for CHANNEL_SALES_VIEW.
5. Keep payout and settlement views separate from order-date views.
6. Build one calculation tab per platform.
7. Build CHANNEL_SALES_VIEW.
8. Test one product across all three channels.
9. Add inventory coverage.
10. Add margin after COGS, refunds, fees, and ad spend are clean.
11. Keep decisions in notes or action tabs, not source rows.

Amazon Shopify Walmart reporting FAQ

What is Amazon Shopify Walmart reporting?

Amazon Shopify Walmart reporting means joining sales, inventory, refunds, ads, fees, and margin data from all three channels into one review system. In Google Sheets, I would use separate source tabs, one MASTER_SKU map, calculation tabs, and combined views.

Can I manage Amazon, Shopify, and Walmart reporting in one Google Sheet?

Yes, if every channel maps back to one internal SKU. Start with sales and order data first, then add inventory, refunds, ads, COGS, fees, and margin after the SKU map is clean.

What should I build first?

Build MASTER_SKU first. It should include internal_sku, amazon_sku, shopify_sku, walmart_sku, product name, and unit COGS. Every cross-channel formula depends on that map.

Why do my Amazon, Shopify, and Walmart totals not match?

They may use different date fields, payout timing, refunds, discounts, fees, and settlement rules. Use order date for sales movement and payout or settlement period for cash. Keep those views separate.

Where should ad data fit?

Ad data should live in its own source tab and join to the combined view by SKU, ASIN, channel, or date range. Keep campaign management inside the ad platform or PPC tool.

Does Gorilla ROI replace Amazon, Shopify, or Walmart?

No. You still use each platform for account work, order exceptions, listing changes, and channel-specific troubleshooting. Gorilla ROI helps your team review the data together in Google Sheets.

When should I avoid this setup?

Avoid this setup if you only sell on one channel, your team does not use Google Sheets, or a few manual exports still answer the question quickly. A combined workbook earns its place when the channel matching work keeps repeating.