QuickBooks Online ↔ Shopify integration

Shopify orders become sales in QuickBooks Online with the right items, taxes and payouts, and stock levels stay in step

A Shopify store produces hundreds of orders, each with items, discounts, shipping, taxes and a payout that arrives days later net of processing charges. Getting that into QuickBooks Online by hand means either one giant monthly entry nobody can audit, or a bookkeeper typing all week. The QuickBooks Online ↔ Shopify pair turns each order into a sales record in QuickBooks with the same lines the customer saw, books payouts and processing charges when they arrive, and keeps stock levels in step between the two systems. Below: what exactly moves, which scenarios we cover and which capabilities of both systems we rely on.

Request an integration System page: QuickBooks Online →System page: Shopify →

What moves between the systems

Shopify → QuickBooks OnlineA paid Shopify order becomes a sales record in QuickBooks Online with the same items, quantities, discounts, shipping and tax lines the customer saw at checkout.
Shopify → QuickBooks OnlineShopify products are matched to QuickBooks items by SKU, so sales land on the right item and revenue is reported by product, not as one lump sum.
Shopify → QuickBooks OnlineShopify payouts are recorded in QuickBooks as transfers with the processing charge booked separately, so the bank feed matches the payout and the sales total still matches the orders.
Shopify → QuickBooks OnlineA refund or cancellation in Shopify creates the matching refund in QuickBooks against the same order and customer.
QuickBooks Online → ShopifyStock levels kept in QuickBooks — after a purchase or a stock count — go back to Shopify, so the store does not sell what the warehouse no longer has.
QuickBooks Online ↔ ShopifyCustomers are matched by email: a new Shopify buyer is created in QuickBooks once, and a returning one is reused, so the customer list does not fill up with duplicates.

What we connect

We check the QuickBooks Online region and currency of the company file against the store's currency and the countries it sells to.
You install the integration in the Shopify admin as a custom app with access only to orders, products, inventory and payouts, and connect the QuickBooks company through Intuit's consent screen.
We build it on Shopify's current GraphQL interface, not the legacy one, so the pair keeps working as Shopify retires old versions.
We map products by SKU and agree how to handle Shopify products without a SKU or a QuickBooks item: create it, or send it to a “needs attention” list.
Together with the bookkeeper we choose the QuickBooks accounts for sales, shipping income, tax, Shopify processing charges and the clearing account for money before payout, and decide whether stock is kept in QuickBooks or in Shopify.
We run it on a Shopify development store against a QuickBooks test company, then switch to live starting from an agreed date so old orders are not doubled.

Automation scenarios

One giant monthly entry

Before the bookkeeper posts the whole month of Shopify sales as one summary entry, and nobody can say which product or which day the revenue came from.

After each order is a separate sale in QuickBooks with its items, so the reports break down by product and date.

Payout does not match the sales

Before the bank shows a Shopify payout that matches no order total, and the bookkeeper spends an hour finding which orders and charges it consists of.

After the payout is recorded as a transfer with its orders and processing charge attached, and the bank feed matches in one click.

Sold out but still on sale

Before the warehouse count in QuickBooks says zero, but Shopify keeps taking orders until someone updates the quantity by hand.

After the QuickBooks stock level goes to Shopify on every change, and the product shows as sold out on time.

Tax by state and country

Before Shopify calculated tax per order, but QuickBooks receives one summary amount, and the tax report has to be rebuilt by hand.

After the tax line of each order goes to QuickBooks as it was charged, and the tax report is built from real orders.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

In QuickBooks an invoice is a sales form where the customer pays for a product or service later — exactly what a CRM deal turns into.
Source: developer.intuit.com ↗ checked 2026-09-27
Items in QuickBooks are the products and services a company buys or sells; they become the lines of an invoice, which is why we build the CRM catalogue on them.
Source: developer.intuit.com ↗ checked 2026-09-27
QuickBooks notifies a connected application whenever data in the customer's company file changes — this is what keeps the CRM current without constant polling.
Source: static.developer.intuit.com ↗ checked 2026-09-27
The orders query returns the store's orders with status, customer and line items, and Shopify itself suggests using it to automate fulfillment workflows.
Source: shopify.dev ↗ checked 2026-09-27
An app can subscribe to store events (webhook topics) and receive data about them in near real time, instead of polling the store.
Source: shopify.dev ↗ checked 2026-09-27
The REST Admin API is legacy as of October 1, 2024; from April 1, 2025 all new public apps must use the GraphQL Admin API only.
Source: shopify.dev ↗ checked 2026-09-27

Limits

QuickBooks Online is built for the US, Canada, the UK, Australia and a few other markets; Intuit's materials show no Ukrainian version or Ukrainian reporting, so this pair is for stores that already keep their books in QuickBooks. On the Shopify side, new integrations are built on the current GraphQL interface because the old one is legacy, and request limits depend on the store's plan, so large catalogs are synchronized in batches. Which accounts sales, processing charges and tax go to is an accounting decision we set up the way your bookkeeper says.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Shopify has its own QuickBooks connector. Why a custom pair?

If a ready connector fits your accounts, tax setup and stock rules, use it, and we will say so after looking. A custom pair is for stores where the ready one posts summaries instead of orders, mishandles multi-currency, or does not keep stock in step the way the bookkeeper needs.

Where should stock be kept: in QuickBooks or in Shopify?

In one place only, and you choose it at the start. If purchases and stock counts happen in QuickBooks, it is the source and Shopify follows. If the warehouse works in Shopify, orders reduce stock there and QuickBooks only receives the sales.

What happens to orders placed before the launch?

Nothing, unless you ask. The pair starts from an agreed date so the bookkeeper's earlier entries are not doubled. Older orders can be loaded separately for a chosen period after checking that they are not already in QuickBooks.

Does it work with several currencies?

Yes, if multi-currency is enabled in the QuickBooks company file. Each order is recorded in the currency the customer paid in, and the payout is recorded in the currency it reached the bank in. We check this setting at the start because it cannot be switched off later.