Platform guide — Operations, Inventory & Finance
Most eCommerce accounting problems are integration problems.
The disagreement between what the store says you sold and what the books say you earned is rarely an accounting error. It's a mapping decision nobody made — about fees, refunds, gift cards, discounts, tax and timing.
QuickBooks is the accounting system most brands at this stage already own. The work is almost always in how orders reach it.
Partner disclosure: Gapstow may receive referral compensation if you sign up or purchase through links on this page. This does not change what you pay or how we evaluate the platform.
What it does
QuickBooks in one paragraph
QuickBooks handles the general ledger, bank reconciliation, accounts payable and receivable, sales tax and financial reporting. In an eCommerce context it becomes the destination for order revenue, payment processor fees, refunds and cost of goods.
The eCommerce-specific question is granularity: whether orders post individually, as daily summaries, or as payout-level journal entries — and what that choice does to reconciliation effort.
Notable capabilities
General ledger and reconciliation
The authoritative record. Everything else in the stack is a management report by comparison.
Sales tax handling
Liability tracking and filing support, typically alongside a dedicated tax engine for multi-state complexity.
COGS and margin visibility
Where product profitability becomes real, provided cost data is actually maintained upstream.
Multi-channel consolidation
Marketplace, wholesale and DTC revenue landing in one ledger with consistent mapping.
Where it fits
Every platform decision is a decision about who owns a stage.
- Storefront
- Customer
- CRM & Retention
- OperationsQuickBooks
- Fulfillment
- ReportingQuickBooks
Accounting is downstream of everything. It's also the only system where the numbers are eventually audited, which makes it the best forcing function for clean data upstream.
Commonly touches
- Shopify
- Payment processors
- ERP
- Inventory
- Sales tax
- Marketplaces
Judgment
Two lists, and the second one matters more.
When we’d look at it
- Store revenue and booked revenue disagree and nobody can explain the gap quickly.
- Month-end close involves manual CSV exports and spreadsheet reconciliation.
- You sell across DTC, wholesale and marketplaces and each is booked differently.
- Product-level margin is unknown because COGS isn't consistently captured.
- Payment processor fees, refunds and chargebacks are being absorbed into a single unexamined line.
When we’d question it
- The books are already clean and reconciled. Changing accounting systems to solve a reporting question is an expensive detour.
- The real need is operational or merchandising reporting. Accounting answers a different question, on a different timeline.
- An ERP already handles financials. Adding a second ledger creates a reconciliation problem rather than solving one.
- The problem is that nobody maintains cost data. No accounting platform can compute margin from costs that don't exist.
- You're syncing every order individually at high volume — that's usually a summary-level design problem, not a platform problem.
Before you implement
Questions to answer first
- 01
At what granularity should orders post — per order, daily summary, or payout?
- 02
Who owns the chart of accounts mapping for fees, discounts, refunds, gift cards and shipping?
- 03
How are gift cards and store credit treated as liabilities?
- 04
Where does COGS come from, and how often is it updated?
- 05
Which system is the source of truth for sales tax, and how are marketplace-facilitated sales handled?
- 06
What is the reconciliation routine when the connector fails for a day?
Implementation
What tends to go wrong
- Payout-level posting reconciles more cleanly to the bank than order-level posting, at the cost of order-level detail in the ledger.
- Refunds and partial refunds are the most commonly mismapped transactions in eCommerce accounting.
- Multi-currency and international sales need a decision on rate handling before the first sync.
- Whichever connector is used, agree with the accountant on the mapping before go-live rather than after the first close.
The finance team is usually the first to notice that the data model is wrong, and the last to be consulted when it's designed. Bring them into the integration conversation early — the mapping decisions are theirs to make.
Adding a platform is the easy part.
If QuickBooks is on the table, the useful conversation is about the process and architecture around it — not the software itself.