Two-way QuickBooks sync for food distributors, explained

Minori Midori talks to QuickBooks Online in two ways, and they suit two different operations. The file-based export, on every plan, produces three CSV files you download and import yourself; nothing touches your QuickBooks company until you do. The API sync, on the Enterprise plan, replaces the files entirely: you connect once through Intuit's own sign-in screen, and from then on the books keep themselves. This piece explains what the sync moves in each direction, how you check on it, and what it refuses to do. The refusals are the part your bookkeeper will care about most.

The export path: three files you control

For many operations the export is the right relationship permanently. Pick a period in the admin and download three files: invoices in the exact layout QuickBooks Online's import expects, payments received for the reconciliation loop, and orders for the sales that never saw an invoice. Your bookkeeper imports them on their own schedule, reviews each upload screen, and stays in full control of what enters the company file. We wrote up both halves of that workflow in detail: importing invoices into QuickBooks Online covers the file layout and the upload settings that trip people up, and recording customer payments in QuickBooks Online covers where each kind of distributor money belongs. The export ships on every plan and stays available even after you connect the sync.

The sync exists for the operation where those monthly imports have become a job. Same records, same numbers, no files.

What flows out to QuickBooks

Once connected, four kinds of records move from the platform into your QuickBooks company on their own:

• Issued invoices. Every invoice the platform issues appears in QuickBooks as a real invoice: your invoice number, the customer, issue and due dates, line items with quantities and rates, discounts and tax, and a total that matches the platform exactly to the cent. That includes catch-weight invoices whose totals change after weigh-in; the update reaches QuickBooks too. Draft invoices never sync, because a draft is not an accounting record. Void an invoice on the platform and its QuickBooks counterpart is voided as well.
• Settled payments. Online invoice payments that settle, invoices your staff mark paid by check or cash, and money taken at checkout all post to QuickBooks and are applied against the specific invoice they pay, so accounts receivable clears correctly. An ACH debit still in flight is a promise, not a payment; it posts when it settles, and failed attempts never post at all.
• Sales receipts. Prepaid wholesale and retail orders never produce an invoice, so they sync as sales receipts, with line items and totals that match the platform to the cent. Revenue in QuickBooks matches revenue on the platform without a monthly journal entry.
• Customers and items, matched or created. The sync finds the existing QuickBooks customer or item where one exists and creates it where one does not, then remembers the pairing forever. You never pre-build lists, and re-runs, retries, and reconnects never produce duplicates.

What flows back

The return direction is narrow on purpose, and it exists for one scene every distributor knows: a paper check arrives, and your bookkeeper records the payment in QuickBooks against the customer's invoice, the way they always have. Without anyone touching the platform, the matching platform invoice becomes paid. The buyer's balance updates, reminder emails stop, and your staff see the invoice as settled. A partial payment updates the remaining balance without marking the invoice paid, and a payment the platform already recorded is never double-counted.

That is the whole inbound flow: payments, applied to invoices the sync itself created. Your bookkeeper keeps working in QuickBooks; the platform stops nagging customers who have already paid.

The activity log is the trust layer

An accounting integration you cannot inspect is worse than none, so the sync area shows its work. You see connection health, when the last run happened, and a per-record log: synced, pending, or failed, with the reason in plain language a bookkeeper can act on, such as "QuickBooks rejected invoice #114: the connected company requires a tax code." Fix the underlying issue and press retry on the record. A Sync now button runs everything on demand instead of waiting for the next scheduled pass. If the QuickBooks connection expires or is revoked, the admin area says so plainly and notifies you; records that accumulate while disconnected sync cleanly after you reconnect, with nothing lost and nothing duplicated.

What it deliberately does not do

The boundaries are as designed as the features, and they are worth knowing before you connect:

• It never imports from QuickBooks. Customers, items, and invoices created directly in QuickBooks stay in QuickBooks. The platform is the source of truth for its own records, and the sync will not pull someone else's data model into your catalog.
• Refunds and credit memos stay with the bookkeeper. Money going back out is recorded in QuickBooks directly, as a credit memo or refund receipt, where your accountant can see it for what it is. Refunded status is visible in the activity log so nothing gets missed.
• Guest orders are skipped. A guest checkout has no customer account to book against, so guest orders are left out rather than invented.
• It runs on a schedule and on demand, not on every keystroke. Records sync automatically at least daily, and a Sync now pass makes a new record visible in QuickBooks within a couple of minutes. Nobody closes books by the second, and the sync does not pretend otherwise.
• It never blocks commerce. A QuickBooks outage or rejection cannot stop an order, an invoice, or a payment on the platform. Sync is always downstream, and it retries on its own.

One QuickBooks Online company per store, in USD, and QuickBooks Online only: Intuit no longer sells Desktop to new customers.

Which path fits your operation

Both paths end in the same place: a QuickBooks company whose numbers match your order system to the cent. The export keeps a person in the loop; the sync removes the files and adds the return trip for payments your bookkeeper records in QuickBooks. Accounting is one corner of what produce distribution software should carry for you, but it is the corner where retyping hurts twice, once in labor and once in errors. The full capability rundown, including plan availability, is on the two-way QuickBooks sync page. If month-end at your operation still means moving numbers between systems by hand, book a demo and watch an invoice land in QuickBooks with nobody touching a file.