Shopify + QuickBooks Integration

Per-order sync suits stores with modest volume, B2B customers paying on terms, or an accountant who wants customer-level detail inside QuickBooks. A daily summary journal suits everyone else. One entry per day carries gross sales, discounts, refunds, shipping, taxes, gift cards, and fees as account-level lines, and order-level detail stays in Shopify, where it is searchable anyway. The practical test: once nobody opens individual sales receipts in QuickBooks any more, the summary is the better design, and it removes the API throttling and file bloat problems at the same time.

Because a payout is not a day of sales. It is gross sales minus processing fees, minus refunds, minus adjustments, and the orders inside it usually span more than one calendar day. If sales post straight to the bank account, nothing will ever tie. The fix is structural: sales post to a clearing account, and each payout posts as its own entry that moves the net amount to the bank and books the fees. After that, every deposit on the bank feed matches one payout entry exactly, and reconciliation stops being detective work.

Yes, but it is a genuinely different project, not a checkbox. QuickBooks Online has a modern REST API that a cloud service calls directly. Desktop and Enterprise integrate through the QuickBooks Web Connector, where the machine running QuickBooks polls for queued work, or through a hosted environment. That polling model changes latency, error handling, and who maintains the connection, so we scope Desktop work separately and price it honestly. Intuit’s investment is visibly in Online, so if you are choosing a version today rather than living with an existing file, integrate Online.

Technically in a limited way, practically usually no. Inventory tracking is edition-gated in QuickBooks Online and exists to value stock for accounting, not to run multi-location, multi-channel operations. We treat QuickBooks as the financial record and leave stock control to Shopify or a dedicated inventory system. If inventory operations are the actual problem you are trying to solve, you are shopping for an ERP or an IMS rather than an accounting sync, and we will tell you that in the first call instead of selling you the wrong project.

Shopify is authoritative for the tax charged at checkout, and the integration never lets QuickBooks recalculate it. US editions of QuickBooks Online prefer to compute sales tax themselves, so per-order documents need the charged tax passed through explicitly, and where that fights the automated behaviour, the cleaner pattern is posting tax to a liability account in the daily summary. In VAT and GST regions, Shopify tax lines map to the corresponding QuickBooks tax codes. Either way, the number the customer paid is the number in the books, reconciled at line level.

Often an app is enough and we say so. Mature connector apps handle straightforward per-order sync, and payout-summary tools such as A2X exist precisely because the payout is the hard part. Custom work earns its keep when you run multiple stores or currencies into one QuickBooks file, sell B2B on terms with real customer records, take payments through gateways beyond Shopify Payments, or have a posting scheme your accountant has already defined that no app can express. A short audit is cheap compared with discovering mid-quarter that an app cannot fit your chart of accounts.

Not if the sync is designed rather than defaulted. B2C checkouts consolidate behind a single web customer, so ten thousand one-time buyers do not become ten thousand QuickBooks records that slow the file and mean nothing to your accountant. Genuine B2B accounts map one to one with their terms and contact details. QuickBooks Online also requires display names to be unique across its name lists, so a naive per-customer sync eventually collides with an existing customer or vendor name and stops. Deduplication rules are set before the first sync, not discovered after it.