Running one Shopify store into QuickBooks is already a reconciliation exercise — see why Shopify payouts don't match QuickBooks deposits if you haven't dealt with that yet. Running two or three stores means doing that same exercise multiple times over, with no built-in way to see the combined picture without building it yourself.
Here's why that's a real structural problem, not just "more of the same work," and how to consolidate it by hand until it isn't.
Why multiple stores don't just add up
Each store has its own payout batches
Every Shopify store settles independently. Store A's payouts land on their own schedule; Store B's land on a different one, even if both process transactions on the same day. There's no combined payout — you're reconciling two (or more) separate streams of deposits against two separate sets of orders, on two separate timing cycles.
Fee structures can differ between stores
Different Shopify plans, different card-mix, different countries, or a store that's grown into a different pricing tier all mean the processing fee percentage isn't guaranteed to match across stores. You can't apply one blended assumption across both — each store's fee reconciliation has to be worked out on its own terms.
QuickBooks Online's native Shopify connection is one store per company file
QuickBooks Online's Shopify integration connects to a single Shopify store per QuickBooks company file. There's no native setting to point two Shopify stores at one QBO file and have both feed in cleanly. In practice, merchants running multiple stores either keep separate QuickBooks files per store (which means your combined P&L and balance sheet don't exist anywhere until someone builds them) or connect one store natively and bring the other store's data in manually — through a CSV export, a journal entry summary, or a third-party consolidation app.
Intercompany noise, if stores share inventory or fulfillment
If the same warehouse or supplier serves both stores, or inventory moves between them, you also need to make sure that movement isn't double-counted as revenue in one store and cost in the other, or missed entirely. This is easy to get wrong quietly — it doesn't throw an error, it just quietly overstates or understates a number until someone notices the margin looks off.
Consolidating it by hand
If you're managing this manually today, here's the actual workflow:
- Pull each store's payout and sales data separately, using the reconciliation process from the payouts post above — per store, not combined. You need each store's Total Sales, payout totals, fees, and refunds cleanly broken out before you try to combine anything.
- Normalize the categories. Make sure "Shopify processing fees," "refunds," and "product revenue" mean the same thing and hit the same GL accounts across both stores' exports — it's common for one store's chart of accounts to have drifted slightly from the other's if they were set up at different times.
- Check for shared inventory or intercompany movement between the stores before combining. If goods moved from Store A's warehouse to fulfill a Store B order, that needs an explicit intercompany elimination, not just addition.
- Combine into one set of totals, keeping a per-store breakdown alongside the combined number — you'll need both when something looks off and you have to figure out which store it came from.
- Repeat every reconciliation period. This is the part that turns into "the CSV mess": without a system doing this automatically, it's a recurring manual merge, and it scales linearly with the number of stores you add.
The automated version
This is exactly what ClairFlo's multi-store consolidation does natively: connect more than one Shopify store to a single ClairFlo account and every order rolls into one set of books, tagged by store, with both a consolidated view and per-store drill-down available without any manual merging. It builds directly on the same Shopify payout reconciliation mechanism described in the payouts post, applied per store automatically. See Multi-Store Accounting Consolidation in the glossary, or the full feature reference at /features.