What are Shopify integration tools?

Shopify integration tools are the platforms that move orders, customers, products and inventory between Shopify and the rest of your stack by calling the Shopify Admin API or reacting to webhooks. They fall into four groups: Shopify-owned mechanisms such as Flow and the Admin API, App Store connectors built for one destination, general iPaaS vendors such as Celigo, Workato and Zapier, and warehouse-focused ELT vendors such as Fivetran, Airbyte and Adapters.

How much does Shopify integration cost?

Shopify charges nothing extra for Admin API access, so the cost is whatever you put in front of it. App Store connectors typically run $20 to $200 a month per destination. ERP connectors and iPaaS vendors bill per order, per task or per connection, which is the number that grows with you. Adapters is flat at $49 to $399 a month regardless of order volume.

Does Shopify have an API?

Yes. The GraphQL Admin API is the primary one and is where Shopify puts new functionality. There is also a Storefront API for customer-facing surfaces, a Customer Account API, and a REST Admin API that has been legacy since 1 October 2024. Since 1 April 2025 all new public apps must be built exclusively on the GraphQL Admin API.

What are the Shopify API rate limits?

The GraphQL Admin API meters calculated query cost in points per second: 100 on Standard, 200 on Advanced, 1,000 on Shopify Plus and 2,000 on Enterprise. A single query may not exceed 1,000 points. The legacy REST Admin API uses a leaky bucket of 40 requests that refills at 2 per second, raised by a factor of ten on Plus.

How do I integrate Shopify with QuickBooks?

Pick a destination for each money movement first, then wire it. Orders become sales receipts or invoices, Shopify Payments fees become an expense against a merchant fee account, refunds become credit memos, and the payout becomes the bank deposit those items clear against. Get the mapping right and the deposit reconciles. Get it wrong and every month closes with an unexplained variance.

How do I integrate Shopify with Xero?

The same design decisions apply as with QuickBooks, plus one Xero-specific constraint worth planning around: the Xero API allows 5 concurrent calls, 60 calls per minute and 5,000 calls per day per connected organization. A tool that writes one invoice per order will hit the daily ceiling on a store doing more than roughly 5,000 documented events a day, so summarized daily journals are usually the correct design.

Does Shopify integrate with NetSuite?

Not natively. NetSuite integration runs through a connector, either an App Store listing, an iPaaS vendor such as Celigo or Boomi, or a custom build on SuiteTalk. The hard part is never the order sync, it is item and inventory master data: which system owns the SKU, how kits and bundles map, and how fulfillments flow back to Shopify.

Does Shopify integrate with Salesforce?

Through connectors rather than a first-party build. Most teams sync Shopify customers and order history onto the Salesforce contact or account so sales sees purchase behavior. If the requirement is reporting across both rather than record-level sync, landing Shopify and Salesforce in a warehouse and joining them there is cheaper and far less fragile.

How do I export all Shopify orders to a database or warehouse?

Use a bulk operation rather than paginated queries. Bulk operations run asynchronously, return JSONL, are not subject to the normal cost limits, and from API version 2026-01 you can run five at once per app per shop. The result URL expires after one week, so download it as soon as the job reports complete.

What is the best Shopify accounting integration?

It depends on whether you need document-level detail or reconciled summaries. A2X and similar tools produce summarized journals that tie to the payout, which is what most accountants want. Order-level connectors give you every transaction in the ledger, which suits stores that invoice B2B. Warehouse-first tools give you neither ledger entry, but they give you the numbers to audit both.

Shopify Integration Tools - API, Cost, ERP, Accounting

Which Shopify integration tool should you use?

Match the tool to the destination. If the destination is accounting, the question is whether your accountant wants summarized journals that tie to the payout, which is what A2X and similar tools produce, or order-level detail in the ledger, which is what a direct connector gives you. If the destination is an ERP such as NetSuite, buy a connector built for that route, because item and inventory master data is the hard part and Celigo and Boomi have spent years on it. If the destination is a warehouse, that is ELT and Fivetran, Airbyte or Adapters do it. If the workflow never leaves Shopify, use Shopify Flow, because it is already included. And for a store with two or three routes that simply have to run, a mapped scheduled sync on a flat price beats a task meter that grows every time you have a good month.

The correction worth making early: almost every published comparison of this category ranks apps by install count and star rating, and none of them mention the two constraints that actually decide the project. The GraphQL Admin API meters calculated query cost in points per second, which is 100 on a Standard plan and 1,000 on Plus, so the same connector behaves like a different product on a different plan. And a tool that posts your net payout as revenue will never reconcile, no matter how many stars it has. For the wider category outside Shopify, start with best data integration tools.

Shopify integration tools compared

Billing units rather than price tags, because most of this category is quote-based, per-order or task-metered and any number we print goes stale. The one flat published figure below is ours. Verify current pricing with each vendor before you sign anything.

Comparison of 12 Shopify integration and data integration tools by owner, approach, best fit, pricing model and main caveat
Tool	Owner	Approach	Best for	Pricing model	Watch out for
Shopify Flow	Shopify	First-party automation inside Shopify, triggered by store events	Tagging, inventory rules and internal notifications that never leave Shopify	Included with the plan	It automates inside Shopify. It is not a data pipeline to another system
App Store connectors	Third-party developers	Single-purpose apps that link Shopify to one named destination	One well-trodden route such as Shopify to a popular accounting package	Monthly subscription per app, often tiered by order volume	One app per destination adds up fast, and each has its own support queue
Celigo	Celigo	iPaaS with prebuilt Shopify to ERP integration apps	Shopify to NetSuite or Dynamics with order, item and inventory flows	Subscription plus per-flow or per-endpoint licensing	Strongest where NetSuite is the destination, heavier than you need if it is not
Workato	Workato	Recipe-based enterprise automation with a wide connector catalog	Multi-system workflows crossing commerce, finance and support	Annual contract metered on recipes and tasks	Entry pricing is aimed at enterprises, so it rarely fits a single Shopify route
Boomi	Boomi	Established iPaaS with an ERP-heavy connector library	Teams already standardized on Boomi for other integrations	Per-connection licensing plus platform subscription	Connection-based licensing punishes adding sources one at a time
Zapier	Zapier	Trigger-and-action automation a non-engineer can build	Alerts, handoffs and low-volume record creation owned by marketing or ops	Metered on tasks per month	A task meter and order volume grow together, which is the wrong shape for commerce
Make	Make	Visual scenario builder with branching and iteration	Multi-step logic that would be awkward in a linear trigger-action tool	Metered on operations	Every step in a scenario burns an operation, so cost scales with complexity
A2X	A2X	Summarized accounting journals reconciled to the Shopify payout	Stores whose accountant wants clean payout-level entries, not order noise	Monthly subscription tiered by order volume	Deliberately summarized. If you need order-level detail in the ledger, look elsewhere
Fivetran	Fivetran	Managed ELT replication of Shopify into a warehouse	Analytics teams that want Shopify tables in Snowflake or BigQuery	Monthly active rows	An MAR bill on a store with heavy customer updates is hard to forecast
Airbyte	Airbyte	Open-source ELT you can self-host or buy as a managed cloud	Engineering teams comfortable operating the pipeline themselves	Credits on cloud, infrastructure and time if you self-host	Self-hosting is free until you count the engineer who maintains it
Hightouch	Hightouch	Reverse ETL from the warehouse back onto business tools	Pushing modeled segments and lifetime value out to marketing systems	Tiered, with limits on active syncs	It is the return leg. You still need something to fill the warehouse
Adapters	Adapters	Visual field mapping and scheduled sync between Shopify, databases, warehouses and finance tools	One to a dozen routes that have to run reliably without a metered bill	Flat $49 to $399 a month, no per-order or per-row meter	Smaller catalog than the enterprise iPaaS vendors. If you need forty sources, say so early

The column a table cannot show you is how a tool handles the awkward parts of a Shopify catalog: variants, metafields, bundles, multi-location inventory and the difference between an order and its fulfillments. Two vendors will both list Shopify and only one will bring across the metafield your merchandising logic depends on. During the trial, sync the exact objects you need and read what landed rather than trusting the logo on the connector page. If you are evaluating against a specific vendor, we keep honest write-ups of Celigo, Workato, Zapier and Fivetran.

What Shopify already gives you before you buy anything

Six integration mechanisms ship with the platform. Knowing which one fits changes the shortlist, because a vendor that pages through orders one screen at a time is spending your points allocation on a job a single bulk operation would finish while nobody is watching.

Native Shopify integration mechanisms, what each is for, when to use it and what it costs against platform allocations
Mechanism	What it does	Reach for it when	What it costs you
GraphQL Admin API	Reads and writes orders, customers, products, inventory and fulfillment; where Shopify ships new functionality first	Any integration built today, including everything a connector does on your behalf	Calculated query cost in points per second, 100 on Standard up to 2,000 on Enterprise
Bulk operations	Runs a large query asynchronously and returns the whole result set as a JSONL file	Backfills and full exports, which is most of the work in week one	Exempt from the normal cost limits; five concurrent bulk queries per app per shop from version 2026-01
Webhooks	Pushes an event to your endpoint when an order, customer or product changes	You need reaction time in seconds rather than a scheduled poll	Free of the API allocation, but you own delivery failures, ordering and replays
Shopify Flow	Trigger and action automation that runs inside the Shopify admin	The whole workflow starts and ends inside Shopify, such as tagging or stock alerts	Included in the plan, but it is not a route to an external system
REST Admin API	The older resource-based API, still functional and still widely used	Maintaining something already built on it, not starting something new	Leaky bucket of 40 requests refilling at 2 per second; legacy since 1 October 2024
Storefront API	Public product, collection and cart data for headless storefronts and buyer surfaces	You are building a customer-facing experience, not moving records between back offices	No fixed per-minute limit for real buyers; unsigned anonymous bots get the strictest limits

The honest limit of the native route is not capability, it is ownership. A private app can do anything the Admin API exposes, but it does not ship with backoff you did not write, a per-record error log somebody can read, or an alert that reaches a human when last night's sync stopped at 3 AM. That gap is what you are buying when you buy a tool, and it is worth being explicit about it rather than discovering it during the first failed backfill. The same trade is covered generally in build versus buy for integrations.

Shopify API rate limits every integration has to live inside

The GraphQL Admin API does not count requests, it counts calculated query cost in points per second, and your plan sets the rate. Read from the Shopify developer documentation on 20 August 2026. If you take one table from this page, take this one.

Shopify API rate limits and allocations relevant to integrations, with the value and why it matters
Limit	Value	Why it matters
GraphQL Admin API, Standard plan	100 points/sec	The default ceiling most stores integrate against. Query cost, not request count, is what is metered
GraphQL Admin API, Advanced Shopify	200 points/sec	Double the Standard rate. Worth knowing before you blame a connector for being slow
GraphQL Admin API, Shopify Plus	1,000 points/sec	Ten times Standard. The plan upgrade changes what a nightly backfill can realistically finish
GraphQL Admin API, Enterprise	2,000 points/sec	Commerce Components tier. Rarely the constraint at this level; query design usually is
Maximum cost of a single query	1,000 points	A deeply nested query is rejected outright, not throttled. Flatten it or use a bulk operation
Cost fields on every response	requestedQueryCost, actualQueryCost, throttleStatus	A tool that reads throttleStatus can pace itself. A tool that ignores it will hammer into THROTTLED errors
Array input maximum	250 items	The cap on any list argument across the APIs. It sets your realistic page size
Pagination ceiling	25,000 objects	You cannot page past this. Beyond it you must filter, split by date, or use a bulk operation
Count accuracy	up to 25,000 items	Counts above this are not exact. Do not reconcile a load by comparing a Shopify count to a row count
REST Admin API bucket	40 requests, refills 2/sec	The classic leaky bucket. Bursts of 40 are fine, sustained throughput is 2 per second
REST Admin API on Shopify Plus	x10 multiplier	Plus raises the REST bucket by a factor of ten, which is why a Plus migration can hide a bad design
REST Admin API status	legacy since 1 Oct 2024	New public apps have had to be GraphQL-only since 1 April 2025. Ask any vendor which one they use
Concurrent bulk query operations	5 per app per shop	From API version 2026-01. Before that it was one bulk operation of each type at a time
Bulk operation result URL lifetime	1 week	The signed JSONL download expires. A pipeline that fails to collect the file has to rerun the whole job
Bulk query shape	5 connections, 2 nesting levels	Products to variants is valid; products to variants to images to metafields is not. Plan several jobs
New variants per day above 500,000 variants	10,000 per day	A hard ceiling on catalog loads for very large stores. It turns a one-day migration into a scheduled one
API version release cadence	every 3 months	New versions land 1 January, 1 April, 1 July and 1 October at 5pm UTC
Support window per stable version	minimum 12 months	At least nine months of overlap between consecutive versions. Ask a vendor which version it pins

One consequence of the points model that catches almost everybody. Because cost is calculated from the shape of the query rather than the number of calls, two integrations that both pull orders can differ by an order of magnitude in throughput on identical plans. The one that requests only the fields it needs, keeps nesting shallow and reads throttleStatus to pace itself will finish. The one that asks for every field on every connected object will spend the whole allocation on data it discards.

Shopify to QuickBooks or Xero: the eight rows that decide whether the payout reconciles

The most common Shopify integration is also the one most often built wrong, and it fails the same way every time: somebody books the bank deposit as revenue. The deposit is gross sales minus discounts, refunds, processing fees and adjustments, so posting it as a single revenue line understates revenue, hides every expense inside it and guarantees a variance nobody can explain in March. Here is what has to map where.

How Shopify order and payout components map into an accounting ledger, and the mistake associated with each
Component	Where it lives in Shopify	Where it belongs in the ledger	The mistake
Gross sales	Order line item totals before anything is deducted	Revenue	Booking the payout amount as revenue understates both revenue and expenses and never reconciles
Discounts	Order-level and line-level discount allocations	Contra revenue	Netting discounts into revenue hides the promotional cost your marketing team is being judged on
Shipping charged	Shipping lines on the order	Shipping income, separate from product revenue	Mixing shipping into product revenue distorts gross margin by category
Sales tax collected	Tax lines on the order, by jurisdiction	A liability, never income	Tax booked as revenue inflates the top line and leaves the remittance unfunded
Refunds	Refund records, which can arrive in a later period than the order	Contra revenue in the period the refund happened	Backdating a refund to the original order month reopens a closed period
Payment processing fees	Shopify Payments balance transactions	Expense against a merchant fee account	Fees deducted before payout are invisible in order data alone, so they simply go missing
Gift cards	Gift card sale and gift card redemption, two separate events	Liability on sale, revenue on redemption	Recognizing revenue when the card is sold books income you have not earned yet
Payout	The deposit Shopify Payments actually sends to the bank	Bank deposit the above items clear against	If the payout does not equal gross less fees, refunds and adjustments, one of the rows above is wrong

One Xero-specific constraint belongs alongside this table, because it changes the design rather than just the settings. The Xero API allows 5 concurrent calls, 60 calls per minute and 5,000 calls per day per connected organization, with a separate app-wide ceiling of 10,000 calls per minute across all tenants. A tool that writes one invoice, one payment and one fee per order consumes three calls per order, which puts a busy store into HTTP 429 territory well before the day ends. Summarized daily journals are usually the right answer, and they are also what most accountants prefer to read. The specific routes are covered on Shopify to QuickBooks and Shopify to Xero. QuickBooks runs a tighter allocation than most people expect, 500 requests a minute per company file and only ten concurrent connections to it, so if the ledger is the destination the numbers that govern the build are on QuickBooks integration tools.

Six numbers worth knowing before the first demo

1,000

Points is the ceiling for a single GraphQL query

Exceed it and Shopify rejects the query rather than throttling it. Deep nesting is the usual cause, and a bulk operation is the usual fix.

2/sec

Sustained REST Admin API throughput

The leaky bucket holds 40 requests and refills at 2 per second. On Shopify Plus that rate is multiplied by ten.

25,000

Objects is the hard pagination ceiling

You cannot page past it and counts are only accurate up to it, so never verify a load by comparing a Shopify count to a warehouse row count.

5

Concurrent bulk queries per app per shop

Raised from one per type in API version 2026-01. It changes how fast a first full backfill of a large catalog can finish.

12 mo

Minimum support window per API version

Shopify ships a version every three months with at least nine months of overlap. Ask any vendor which version its connector pins to.

1 Apr 2025

GraphQL became mandatory for new public apps

The REST Admin API has been legacy since 1 October 2024. A vendor still building new REST integrations is telling you something.

How to set up a Shopify integration that survives Black Friday

Step 01 / Scope

Decide what has to agree, and which system wins

Write down the objects that matter, usually orders, customers, products, inventory and refunds, then name the system of record for each one. Inventory is the fight worth having early: if Shopify and an ERP both think they own stock levels, you will oversell. Everything downstream is easier once that sentence exists in writing.

Step 02 / Backfill

Load history with a bulk operation, not paginated queries

A first load of several years of orders through paged queries burns your points allocation for hours and stalls at the 25,000 object pagination ceiling. A bulk operation runs asynchronously, ignores the normal cost limits and hands back JSONL. Download the file promptly, because the signed URL expires after a week.

Step 03 / Map

Map fields once, including the money and the tax lines

Order totals, discount allocations, shipping, tax by jurisdiction, refunds and processing fees each need a destination. Currency needs a decision if you sell in more than one. Timestamps need a timezone that matches your accounting calendar, or a December 31 order lands in the wrong fiscal year.

Step 04 / Schedule

Poll on a schedule, react on a webhook, and pace against throttleStatus

Most commerce data is fine on a schedule. Reserve webhooks for the events where minutes matter, such as fulfillment or fraud holds. Whatever runs it should read the throttleStatus block on every response and slow down before Shopify returns THROTTLED, rather than retrying into the same wall.

Step 05 / Reconcile

Prove the payout balances before you call it done

Take one Shopify Payments payout and check that gross sales less discounts, refunds, fees and adjustments equals the deposit that reached the bank. If it balances for one payout it will balance for all of them. If it does not, one row in the reconciliation table on this page is mapped wrong, and it is nearly always the fees.

What teams actually connect Shopify to

Orders into the accounting ledger

Shopify orders, refunds and Shopify Payments fees posted into QuickBooks or Xero so the payout reconciles to the deposit without a spreadsheet at month end. This is the single most common Shopify integration and the one most often built wrong.

Orders and inventory into an ERP

Orders into NetSuite for fulfillment and billing, with stock levels and fulfillment status flowing back to Shopify. The order sync is easy. Item master and inventory ownership are where these projects actually succeed or fail.

Store data into a warehouse

Orders, customers, products and inventory replicated into Snowflake, BigQuery or Postgres so analytics can join commerce data to marketing spend and support tickets without hammering the Admin API for every dashboard refresh.

Multi-store and multi-channel consolidation

Several Shopify stores, or Shopify alongside Amazon and a wholesale channel, unified into one set of tables where revenue by SKU actually means something across all of them.

Customer history onto the CRM record

Purchase history, lifetime value and product mix written onto the Salesforce or HubSpot record so sales and support see what somebody bought without switching tabs into the Shopify admin.

Modeled segments back to marketing

Lifetime value tiers, churn risk and next-best-product computed in the warehouse and pushed back onto customer records or ad audiences. That is the return leg, with its own failure modes around rate limits and matching.

The accounting case has a dedicated walkthrough in syncing Shopify orders to QuickBooks, the ERP case is covered on Shopify to NetSuite, and the last one, pushing modeled segments back out of the warehouse, is covered on reverse ETL tools.

When another Shopify integration tool is the right answer

We would rather you buy the correct thing than churn in month three. Five situations where Adapters is not what you want.

Your accountant wants summarized journals

If the requirement is one clean journal entry per payout that a bookkeeper can tie out in thirty seconds, buy a tool built specifically for that, such as A2X. It is a narrower product than ours and that is exactly why it is better at this one job.

NetSuite is the destination and item master is the project

Shopify to NetSuite with kits, bundles, multi-location inventory and fulfillment writeback is a category of its own. Celigo and Boomi have spent years on that surface. If that is the whole scope, buy the specialist.

The workflow never leaves Shopify

Tag a customer after a third order, alert someone when stock drops below a threshold, hold an order for review. Shopify Flow does all of that, it runs inside the admin, and it is already included in what you pay Shopify.

You want a marketer to own the automation

Zapier and Make are genuinely better than us at letting a non-engineer wire up a notification or a form handoff without filing a ticket. If the workflow changes weekly and lives with the marketing team, buy that instead.

Your volume genuinely is enormous

Flat pricing is a bet that most stores move a predictable amount of data. If you are moving hundreds of millions of records a month, negotiate a volume contract with a metered vendor and you will likely beat our list price. Our advantage is the middle, where a per-order bill is unpredictable during a peak season and a hand-built integration is a permanent staffing cost nobody put on the budget.

Four questions to ask on every Shopify integration demo

Question 01

GraphQL or REST, and which API version do you pin?

REST has been legacy since October 2024 and new public apps have been GraphQL-only since April 2025. A vendor still building on REST, or pinning a version near the end of its 12 month support window, is telling you about its roadmap.

Question 02

Do you use bulk operations for the initial backfill?

Paging through several years of orders stalls at the 25,000 object ceiling and burns your points allocation for hours. Bulk operations are asynchronous and exempt from the normal cost limits. The answer tells you how long onboarding really takes.

Question 03

Does the payout reconcile, line by line?

Ask them to walk one Shopify Payments payout through to the bank deposit on screen, including fees, refunds and gift cards. If the demo cannot do it with real data, month end will not either.

Question 04

What happens on a THROTTLED response, and during a sales peak?

You want the tool to read throttleStatus and pace itself, then back off exponentially and resume, not retry immediately into the same wall. Peak season is when this stops being theoretical.

Where Shopify data usually goes next

Most Shopify integration projects end up as one of these specific pairs. Each page covers the field mapping, the type conversions and the failure modes for that route.

→ Shopify to QuickBooks → Shopify to Xero → Shopify to NetSuite → Shopify to Snowflake → Shopify to BigQuery → Shopify to Postgres → HubSpot integration tools → Salesforce integration tools → Best iPaaS platforms

Questions buyers ask about Shopify integration tools

What are Shopify integration tools?: Shopify integration tools are the platforms that move orders, customers, products and inventory between Shopify and the rest of your stack by calling the Shopify Admin API or reacting to webhooks. They fall into four groups: Shopify-owned mechanisms such as Flow and the Admin API, App Store connectors built for one destination, general iPaaS vendors such as Celigo, Workato and Zapier, and warehouse-focused ELT vendors such as Fivetran, Airbyte and Adapters.
How much does Shopify integration cost?: Shopify charges nothing extra for Admin API access, so the cost is whatever you put in front of it. App Store connectors typically run $20 to $200 a month per destination. ERP connectors and iPaaS vendors bill per order, per task or per connection, which is the number that grows with you. Adapters is flat at $49 to $399 a month regardless of order volume.
Does Shopify have an API?: Yes. The GraphQL Admin API is the primary one and is where Shopify puts new functionality. There is also a Storefront API for customer-facing surfaces, a Customer Account API, and a REST Admin API that has been legacy since 1 October 2024. Since 1 April 2025 all new public apps must be built exclusively on the GraphQL Admin API.
What are the Shopify API rate limits?: The GraphQL Admin API meters calculated query cost in points per second: 100 on Standard, 200 on Advanced, 1,000 on Shopify Plus and 2,000 on Enterprise. A single query may not exceed 1,000 points. The legacy REST Admin API uses a leaky bucket of 40 requests that refills at 2 per second, raised by a factor of ten on Plus.
How do I integrate Shopify with QuickBooks?: Pick a destination for each money movement first, then wire it. Orders become sales receipts or invoices, Shopify Payments fees become an expense against a merchant fee account, refunds become credit memos, and the payout becomes the bank deposit those items clear against. Get the mapping right and the deposit reconciles. Get it wrong and every month closes with an unexplained variance.
How do I integrate Shopify with Xero?: The same design decisions apply as with QuickBooks, plus one Xero-specific constraint worth planning around: the Xero API allows 5 concurrent calls, 60 calls per minute and 5,000 calls per day per connected organization. A tool that writes one invoice per order will hit the daily ceiling on a store doing more than roughly 5,000 documented events a day, so summarized daily journals are usually the correct design.
Does Shopify integrate with NetSuite?: Not natively. NetSuite integration runs through a connector, either an App Store listing, an iPaaS vendor such as Celigo or Boomi, or a custom build on SuiteTalk. The hard part is never the order sync, it is item and inventory master data: which system owns the SKU, how kits and bundles map, and how fulfillments flow back to Shopify.
Does Shopify integrate with Salesforce?: Through connectors rather than a first-party build. Most teams sync Shopify customers and order history onto the Salesforce contact or account so sales sees purchase behavior. If the requirement is reporting across both rather than record-level sync, landing Shopify and Salesforce in a warehouse and joining them there is cheaper and far less fragile.
How do I export all Shopify orders to a database or warehouse?: Use a bulk operation rather than paginated queries. Bulk operations run asynchronously, return JSONL, are not subject to the normal cost limits, and from API version 2026-01 you can run five at once per app per shop. The result URL expires after one week, so download it as soon as the job reports complete.
What is the best Shopify accounting integration?: It depends on whether you need document-level detail or reconciled summaries. A2X and similar tools produce summarized journals that tie to the payout, which is what most accountants want. Order-level connectors give you every transaction in the ledger, which suits stores that invoice B2B. Warehouse-first tools give you neither ledger entry, but they give you the numbers to audit both.

The rate limits above have a dedicated walkthrough in the Shopify API rate limits guide. For the categories around this one, see iPaaS software when the job is keeping business applications in agreement, and ETL software for how our own pipeline works end to end.

Shopify integration tools compared: the Shopify integration API, integration cost, and ERP, accounting and data integration software