CATEGORY

FP&A Strategy

WRITTEN BY

Fin

Your AI CFO

FP&A Strategy

Connect Shopify & Amazon Without a Data Engineer October 2026

Connect Shopify & Amazon Without a Data Engineer October 2026

FP&A Strategy

10 minutes

WRITTEN BY

Fin

Your AI CFO

SHARE BUTTONS

WRITTEN BY

Fin

Your AI CFO

SHARE BUTTONS

Shopify reports what a customer paid. Amazon reports what's left after it takes its cut, usually two weeks after the fact. Running a real channel comparison on top of that structure requires a few deliberate choices about how you define revenue, how you handle timing, and where fees actually belong in your P&L.

TLDR:

  • A product earning, say, 45% on Shopify may earn 18% on Amazon after FBA, referral fees, and ad spend. Blending them hides the gap.

Why Shopify and Amazon Reports Don't Add Up

Shopify reports revenue when an order is placed. Amazon reports it when a settlement pays out, typically every two weeks, net of fees it has already deducted. Pull both dashboards on the same day and you are looking at two different time periods, two different definitions of revenue, and two different treatments of cost. Founders piecing together numbers across channels rarely land on a single figure they can actually trust. Adding the two totals together does not produce a P&L. It produces a guess, and most CPG brands can't answer this for exactly this reason.

The Structural Differences Between Shopify and Amazon Financial Data

Shopify reports gross sales at order creation: full price, before any fees are taken out. Amazon works the opposite way. By the time a settlement hits your bank account, Amazon has already deducted referral fees, FBA fulfillment fees, storage charges, and any reserve amounts it's holding. The deposit is net, not gross.

That gap has real consequences for channel comparison. Shopify revenue is pre-fee and order-date-stamped. Amazon revenue is post-fee and settlement-date-stamped, arriving on a two-week lag. A CFO consolidating these has to decide: do you gross up Amazon to match Shopify's treatment, or net down Shopify? Either way, you need a methodology. Without one, the numbers will never line up.

The Fee Problem: What Amazon Doesn't Surface Clearly

Amazon's referral fee is calculated on the total sale price (item price plus shipping plus gift wrap), not the item price alone. Referral fees typically run 8 to 15% by category (though the full range spans 5% to 45%) with a $0.30 per-unit minimum floor. A $25 item with $5 shipping pays 15% on $30. That $0.75 difference per order compounds fast across a catalog.

On top of referrals, FBA fulfillment fees, monthly storage charges, and advertising cost of sales are all deducted before settlement. The fees most commonly missed in manual reconciliation are storage fees (billed on a separate monthly cycle) and ad spend, which many brands track in a separate dashboard and never tie back to per-order margin. The result: a brand that thinks it's running 40% gross margin on Amazon may land closer to 28% once all fees are counted. That is a common pattern instead of a precise figure, but the gap is real. This is one reason CPG brands get contribution margin wrong so consistently.

What a Unified Financial Report Actually Needs to Show

A revenue roll-up across two channels is not a financial report. It's a starting point. A real unified report shows gross sales by channel, channel-specific fees deducted at the line level, COGS matched to the same orders, and contribution margin per channel, all on a consistent time axis.

The accrual view tells you what you earned. The cash view tells you what actually landed in your bank account. Both matter, and they will rarely match on any given week. Understanding what sets the most profitable brands apart starts with having both views clean. A CFO needs to see:

  • Gross sales (Shopify at order date, Amazon grossed up to match)

  • Channel fees line-itemed, not bundled into a net figure

  • COGS by SKU, applied at the order level

  • Delivered gross profit and contribution margin per channel

  • Cash collected versus revenue recognized, with the settlement lag visible

Without that structure, you cannot compare Shopify margin to Amazon margin. You're comparing apples to a settlement statement.

The Three Approaches to Connecting the Channels

Three broad approaches exist, each with a different cost and ceiling.

Approach

Setup

Maintenance

Financial Depth

Manual exports + spreadsheets

Low upfront

High, renewed every settlement cycle

Revenue roll-up only; no order-level margin

Accounting-layer tools (e.g. journal entry sync to QBO)

Medium

Low

GL-accurate but summarized; no channel fee detail

FP&A-layer with raw order data

Medium-high

Low once connected

Full contribution margin, fee-level visibility, accrual and cash toggle

Spreadsheets are cheap until they aren't. One missed settlement cycle, one Amazon fee schedule change, and your numbers are wrong for the month. Accounting-layer tools solve the bookkeeping side but collapse order detail into summary entries: you get clean books, not actionable margin data. The FP&A-layer approach costs more to set up but gives you something the other two cannot: a live view of what each channel actually earns after every fee is accounted for.

Common Mistakes That Break Multi-Channel Financial Reports

Most brands hit the same failure modes when consolidating these two channels:

  • Recording Amazon's net deposit as revenue instead of grossing it back up to match Shopify's treatment

  • Using order date for Shopify and settlement date for Amazon in the same report, which mismatches two weeks of sales

  • Mixing cash and accrual accounting across channels without flagging which is which

  • Pulling contribution margin from channel dashboards that exclude ad spend entirely

  • Treating Amazon storage fees as a period expense instead of tying them to the orders that drove the inventory

That last one quietly destroys margin accuracy for any brand running substantial FBA volume. Storage is billed monthly on a separate cycle, so it never appears in a settlement report. Most founders never see it in their channel P&L at all.

How to Align Shopify and Amazon Sales Accurately

Pick one revenue treatment and apply it to both channels. Gross up Amazon's settlement data to remove the pre-deducted fees, then run both channels through the same line item structure. A Shopify payout and an Amazon settlement are not reconcilable until they speak the same language.

Here's the structure that works:

  • Start with gross sales at order date for both channels

  • Subtract discounts and refunds at the order level, not as a period adjustment

  • Pull channel fees as their own line (referral fees, FBA fees, merchant processing) separately from COGS

  • Apply COGS against the same orders, not as a monthly upload averaged across volume

  • Arrive at delivered gross profit, then subtract ad spend to get contribution margin by channel

The most common error at the reconciliation layer is timing. Shopify refunds can be issued weeks after the order; Amazon credits them against the next settlement. Match refunds to the original order date, not the date they appear in a settlement report.

Amazon settlements should never be booked as a single line of net revenue. Each settlement contains multiple fee categories. The settlement is a cash event. The revenue was earned weeks earlier.

Tracking Unit Economics by SKU Across Both Channels

Blended contribution margin at the brand level tells you if you're profitable. SKU-level economics tell you why, and what to do about it.

A product that earns, say, 45% on Shopify might earn 18% on Amazon after FBA fees, referral fees, and sponsored product spend. Both numbers are real. Running them into a single gross margin figure hides the gap entirely.

To track unit economics by SKU across both channels, you need:

  • Gross revenue per SKU, per channel, at order date

  • Channel fees applied at the SKU level, not averaged across the catalog

  • COGS per unit matched to actual orders instead of uploaded monthly

  • Ad spend attributed per SKU where possible, or allocated by channel if not

  • Fulfilled gross profit and contribution margin, per SKU, per channel

The fee allocation step is where most brands break down. Amazon referral fees vary by category, and FBA fulfillment fees vary by unit size and weight. A heavy item costing $7 or more to fulfill via FBA looks fine when blended with a lightweight SKU at $3 to $4. Pull them apart and one is underwater.

The output worth building toward: a SKU-by-channel margin table, refreshed at least weekly, showing which products deserve more inventory and which are quietly eroding margin with every unit sold. That view pairs naturally with gross margin return on inventory (GMROI) benchmarks.

How to Connect Your Accounting System to Both Channels

Your accounting system is the record of what happened, usually 15 to 30 days after it happened. That lag is something the founder's guide to omnichannel CPG finance covers in depth. Understanding that distinction prevents a lot of bad decisions about what to connect and why.

QuickBooks, Xero, and NetSuite each have native Shopify and Amazon connectors that sync data in as journal entry-level summaries: revenue, refunds, fees, and payouts collapsed into periodic entries. Accurate enough for tax compliance. Not granular enough for channel-level margin analysis or daily plan versus actual tracking.

What the accounting system captures well:

  • Recognized revenue by period, by channel

  • Fees as a summarized expense line

  • Cash received from settlements

  • COGS when tied to an ERP with inventory

What it does not produce is order-level contribution margin, real-time accrual visibility before the books close, or any comparison of actual versus planned performance by day. The GL closes when your bookkeeper closes it. Your business runs every day.

The architecture that works connects raw order data from Shopify and Amazon into a reporting layer above the GL. The accounting system stays as the source of truth for the balance sheet. The reporting layer handles real-time P&L, channel margin, and variance tracking from live order feeds without waiting for month-end close.

Building a Scalable Reporting Stack Without a Data Engineer

The classic data engineering path goes: stand up Fivetran, connect Snowflake, hire someone who knows Looker, wait 3 to 6 months, pay $200K in headcount, maintain it forever. For a brand doing $10M across Shopify and Amazon, that's a data warehouse project when you needed a financial report.

A lean stack for a brand in the $5M to $50M range starts with one question: what decisions do I need to make weekly, and what data do I need to make them? That answer evolves as you scale; see scaling your CPG tech stack.

The integration sequence that holds:

  • Sales channels first (Shopify, Amazon): raw order data, fees, settlements

  • Advertising next (Meta, Google, Amazon Ads): spend tied to the same periods so you can calculate true contribution margin

  • Accounting third (QBO, Xero, NetSuite): recognized revenue and COGS

  • Banking last (via Plaid or direct): cash position and settlement reconciliation

Each layer depends on the one before it. Connecting banking before your fee structure is clean means your cash numbers will mislead you on timing.

Where automation genuinely replaces manual effort is in settlement-to-revenue translation and fee categorization. Done manually, those two tasks consume hours every two weeks and introduce errors every time Amazon changes its fee schedule. A reporting layer that ingests raw settlement data and maps fees to orders automatically removes that problem entirely.

Starting Small: A Crawl, Walk, Run Integration Sequence

Start with Shopify and Amazon connected (see Iris Finance's CPG & ecommerce integrations for the full channel list). That alone gives you gross sales by channel, fee-level deductions, and contribution margin per channel before ad spend. Useful on day one.

Add your accounting system next and COGS becomes accurate. Add ad spend data after that and you get true contribution margin. Add banking last for cash flow visibility.

Each layer adds precision to what the previous one already built. Waiting until every system is ready means waiting indefinitely.

How Iris Finance Connects Shopify and Amazon Into a Live Financial Model

Iris Finance connects directly to Shopify and Amazon at the order level and replaces the ETL pipeline, the BI build, and the spreadsheet model with a single live financial model. Gross sales, channel fees, ad spend, and COGS are matched automatically, refreshing every one to two hours. Based on Iris Finance's current customer base of roughly 500 brands and approximately $20 billion in GMV processed, contribution margin by channel is live before your books close, not 15 days after.

The daily P&L runs in both accrual and cash basis simultaneously, with every metric automatically paced against plan and flagged as on pace, watch, or off pace. When contribution margin moves, Finn, our AI copilot, surfaces the ranked variance drivers in under 90 seconds, without a finance analyst pulling exports.

On managed plans, the 13-week cash flow forecast layers in banking data via Plaid and purchase orders from connected inventory systems, extending the model from daily P&L to working capital visibility. No data engineer. Live in weeks.

Final Thoughts on Tracking Revenue Across Shopify and Amazon in One Report

You can't manage margin you can't see clearly. Gross up Amazon, net down your fees at the line level, and stop letting settlement timing distort your channel comparison. The brands that get this right stop arguing about the numbers and start using them. Contact the Iris Finance team if you want to see how that setup works.

FAQ

How do I track unit economics by SKU across Shopify and Amazon without a data engineer?

Apply channel fees at the SKU level, not averaged across your catalog. Amazon referral fees vary by category and FBA fulfillment fees vary by unit size, so blending them across SKUs hides the products that are quietly underwater. Connect raw order data from both channels into a reporting layer above your accounting system, match COGS to actual orders instead of uploading monthly averages, and output a SKU-by-channel margin table that refreshes at least weekly.

Can I connect Shopify and Amazon to one financial report without building a data warehouse?

Yes. A brand doing $5M to $50M across both channels does not need Fivetran, Snowflake, and a Looker developer to get there. Iris Finance connects directly to Shopify and Amazon at the order level, matches fees automatically, and delivers a live contribution margin view with accrual and cash basis. No SQL, no data engineer, no pipeline to maintain.

What is the right order of integrations when building a multi-channel financial report from scratch?

Sales channels first, then advertising, then accounting, then banking. Each layer feeds the next; banking before clean fee data will distort your cash timing. COGS becomes accurate once your accounting or ERP system is in, and true contribution margin only appears after ad spend is tied to the same periods.

Shopify and Amazon in the same P&L: how do you handle the timing mismatch between order date and settlement date?

Pick one revenue treatment and apply it to both channels. Gross up Amazon's settlement data to remove pre-deducted fees, then run both channels through the same line item structure starting at gross sales at order date. Amazon settlements are cash events; the revenue was earned weeks earlier. Booking a settlement as a single net revenue line collapses fee detail you need for channel margin comparison and mismatches the period against Shopify's order-date reporting.

How do I automate variance analysis for a CPG brand without hiring a dedicated finance analyst?

The prerequisite is structured data: contribution margin, ad spend, and channel fees mapped to orders before any analysis runs. Once that layer is in place, AI can surface ranked drivers behind a margin shift in seconds, not hours. Iris Finance's Finn copilot does this directly off live order data: ask why contribution margin dropped and it returns a ranked variance breakdown in under 90 seconds, without a finance analyst manually pulling exports.