### Fix expired authorisation and Shopify rate limits When a run fails, it shows which step died, its input and output JSON, and an error ID. Read the output first: a 401 means authorisation, a 429 means throttling. The ceilings differ by plan. Per [Shopify's rate limit documentation](https://shopify.dev/docs/api/admin-rest/usage/rate-limits), Standard allows 2 requests per second and Advanced 4, so a flash sale on either plan means [Shopify](https://www.shopify.com/news/shopify-announces-fourth-quarter-and-full-year-2019-financial-results) reads are your bottleneck. On QuickBooks Online the limit is 8.3 requests per second. Shopify Plus allows 20 and Enterprise 40, both well above QuickBooks, so on those plans QuickBooks writes become the bottleneck and a naive burst gets throttled there. Queue the writes and back off on 429. If both systems write to each other, an edit in one fires a change in the other and back again. Pick one system of record per field. Treat edits after sync as new events: an order edited or refunded in Shopify after the invoice exists won't fix itself, so match on order number and update, never create. ## Build a custom Shopify to QuickBooks workflow with Activepieces I'm ready to add the missing consequences to sentences containing numbers. Please provide the sentences you'd like me to complete, one per line, with the numbers whose meanings need explanation. A replayed event then hits `Duplicate Document Number` or an update instead of a second receipt. That's the one design decision that keeps edits and retries from doubling your revenue. Read the list as the order of operations; the duplicate check sits before the write, because a check after it only reports damage. The trigger comes from the [Shopify piece](https://www.activepieces.com/pieces/shopify) and the write goes through the [QuickBooks piece](https://www.activepieces.com/pieces/quickbooks). 1. Trigger on a paid order in Shopify. 2. Look up the QuickBooks customer by email, and create one if none exists. 3. Map line items, tax and shipping. 4. Check whether a receipt with this order number already exists. 5. Create the QuickBooks sales receipt, or update the existing one. Step 4 is what the previous section's edit-and-refund rule depends on. You can [start the flow free](https://cloud.activepieces.com/sign-up). ### Map Shopify order fields to QuickBooks sales receipts Map the Shopify order number to the receipt's document number and the customer lookup result to the customer reference. Send each line item as its own line, with tax and shipping as separate lines tied to their own QuickBooks items. If shipping is folded into a product line, your shipping income report is wrong from the first order. Size the plan by runs. [Activepieces](https://www.activepieces.com/pricing) [Free gives 1,000 credits a month](https://www.activepieces.com/pricing), and the paid tiers (Plus, Team, Ultimate) add more credits on top of that. Every plan has unlimited flows, so credits are the figure to size against. If a five-step run spends one credit per step (confirm that on your account), **Free covers about 200 orders a month**. Plus is $20 a month and Team is $200 a month; take the credit allowance listed for each on the pricing page and divide by five for your order ceiling. A store past 200 orders a month will outgrow Free within the month, so budget for Plus first. ### When each integration method works best On a good day, all four sync fine. The differences are about what you can see and change on a bad one. | | Setup time | Pricing model | Mapping control | Error handling | |---|---|---|---|---| | Native connector | Shortest; install and authorize | Usually a flat app fee | Fixed to what the vendor exposes | Vendor's own sync log | | Zapier | Short | Per task | Field-level, inside Zapier's steps | Replay failed runs | | n8n | Longer | Per execution on cloud, or self-hosted | Full, including code | Error workflows you build | | Activepieces | Moderate | Monthly credits by plan | Field-level, with custom steps available | Failed runs you inspect and retry | Pick the native connector if its mapping already matches your chart of accounts. Pick a builder when you need the duplicate check in step 4, and expect to spend your time on the error path, not the happy path. ## Shopify QuickBooks sync setup checklist for week one Spend Monday choosing the route, fixing the sync start date, and proving that one order and one refund land correctly. The error path you just read about only matters once real money is flowing through it. Below is the whole job in order, and each item can be finished and checked without waiting on the next. - Pick the route: vendor connector, or a custom build if a documented limit blocks you - Set the sync start date - Test one order and one refund end to end - Set failure alerts - Reconcile a week of payouts against the Shopify payout report - Diary a re-check of the vendor docs Day one covers the first four; the last two close out the week. ### Choose your Shopify QuickBooks sync route Look for the one thing in the connector's docs that would stop your accounting job, such as how it handles refunds or multiple currencies, and let that choose the route. If nothing blocks you, take the connector and spend your effort on mapping. **Set the sync start date before you switch anything on.** Leave it unset and the connector may try to backfill history into books your accountant has already closed. You'll be reading a rejection like "Duplicate Document Number" on orders that were never meant to sync. Start from the first day of an open period. Then push one ordinary order and one refund through. The order shows you whether tax and shipping map to the accounts you expect. The refund shows whether the credit lands against the right sale or floats loose in the ledger. Fix the mapping now, while a single record is the only thing to clean up. Last come failure alerts, and they should go somewhere a human actually reads. A sync that fails silently looks identical to a sync that works until month-end, and by then you're untangling weeks of gaps. ### Reconcile Shopify payouts in QuickBooks after week one Take a full week of payouts and reconcile them against the Shopify payout report. Each payout should equal sales minus refunds minus fees, and it should match what QuickBooks shows as deposited. When a payout is off, the cause is almost always fees or a refund mapped to the wrong place. It's far cheaper to find in the first week than in the first quarter. Finally, put a date in your calendar to re-read the vendor docs. Connector limits and supported fields change, and the page that said your case was fine at setup isn't a promise about next quarter. Nothing here is automated by the connector or by any protocol layer on top of it, so the diary entry is your only guard against that drift. ## Frequently asked questions By month-end the drift shows, and these are the questions people ask once it does. ### Does Shopify integrate with QuickBooks Desktop? Not through the usual vendor connector, which is built around QuickBooks Online. Desktop stores generally need a third-party tool that goes through a local connector on the machine running Desktop, or a scheduled file import. Either way, the company file has to be reachable when the sync runs. If your bookkeeper's machine is asleep at 1am, your sync is too, and you find out when orders are missing. Check that before choosing a tool. If you can, moving to Online removes the whole problem. ### Is there a free Shopify QuickBooks integration? On some connectors there is a free tier or a trial, but the QuickBooks subscription itself is never free, and free tiers usually cap what you can do. The limits tend to show up as missing features, such as no refund handling or only a summary sync. Read the documented limits against your accounting job before you trust a free plan with real books. A free connector that silently skips refunds costs more than a paid one. ### Can I sync historical orders from before I connected? Usually only if the tool has an explicit backfill, and even then it may cap how far back it goes. Most connectors start from the connection date. For older orders, import them as a one-off, either through the tool's backfill or as summarized journal entries from an export. If you turn on live sync before the backfill, you risk duplicates where the two overlap. Pick a clean cutover date and write it down in the diary. ### Should I sync every order or a daily summary? If volume is high and you don't need customer-level receivables, sync a daily summary. If you do need them, sync every order. Per-order sync gives you traceability: you can match a QuickBooks entry to a Shopify order number. It also gives you more records to fail, retry and duplicate. Keep the ledger small with a summary, but you must reconcile it against payouts, because one wrong total hides inside the sum. The accounting job decides this. A tool's convenience should not. ### What happens to my sync if I change my Shopify plan? Nothing automatic should break, but verify instead of assuming. A plan change can alter which apps, payment settings or tax setups are available, and any of those can change what lands in your books. After a change, place a test order, refund it, and confirm the connector still maps the sale and the refund. Then log the change date in your diary so any shift in numbers has a documented cause. ## Related reading - [Stripe QuickBooks Integration: How to Connect (2026)](https://www.activepieces.com/blog/stripe-quickbooks-integration-how-to-connect-2026) - [Shopify HubSpot Integration vs Zapier or n8n in 2026](https://www.activepieces.com/blog/shopify-hubspot-integration-vs-zapier-or-n8n-in-2026) - [Klaviyo Shopify Integration: Setup and Pricing (2026)](https://www.activepieces.com/blog/klaviyo-shopify-integration-setup-and-pricing-2026) ## References - [Shopify](https://shopify.dev/docs/api/admin-rest/usage/rate-limits) - [CFOpresso](https://cfopresso.com/blog/quickbooks-vs-netsuite) - [Activepieces](https://www.activepieces.com/pricing)A payout isn't a sale. Shopify deposits revenue minus fees and refunds, so an invoice that books only gross sales will never match the bank line.