What to integrate with Shopify before your store starts scaling
The order to connect Shopify to payments, tax, inventory, 3PL, ERP and marketing before you scale, what Shopify does natively and which plan limits matter.
Quick answer
Before a Shopify store scales, integrate in this order: payments and tax, then the inventory system of record, then fulfilment (including any 3PL and cash on delivery), then ERP and accounting, then marketing and customer data, and finally Shopify Flow automations on top. Each step depends on the one before it being right. Use what Shopify already does natively first, check which plan limits affect your design, and only build custom where connectors don't fit.
Key takeaways
- Sequence matters: fix money and stock before automating anything.
- Name one system of record for each type of data before connecting anything.
- Shopify Flow is free on Basic and above, but calling external systems with it needs Grow or above.
- API capacity depends on your plan, and new public apps have had to use GraphQL since 1 April 2025.
- Payments and tax plumbing differ by country; Shopify Payments isn't available in India.
Integration is a business problem before it's a technical one
The hardest part of most Shopify integration projects isn't the API call. It's agreeing on what data means the same thing across two systems that were built independently. A CRM's definition of "customer" and Shopify's definition rarely match exactly, and that mismatch, not the connection itself, is usually where a project's time goes.
This article covers what to connect, in what order, and how a project like this runs. For the technical building blocks, such as the Admin API, GraphQL and webhooks, see our guide to how Shopify app and API integrations work.
What to integrate first: a sequencing checklist
Work through these in order. A later step built on a wrong earlier one multiplies the error: automating order routing on top of inaccurate stock just oversells faster.
- 1. Payments and tax. Confirm your payment gateways, payout reconciliation and how tax is calculated for every market you sell to. Mistakes here touch every order and are slow to unwind.
- 2. Inventory system of record. Decide which system owns stock levels (Shopify, an inventory tool, a warehouse system or the ERP) and how often the others are updated. Add a guard against overselling, such as safety stock on fast sellers.
- 3. Fulfilment, 3PL and COD. Connect orders to whoever picks and ships them, and return tracking and fulfilment status to Shopify. If you offer cash on delivery, decide where collected cash and returned parcels are reconciled.
- 4. ERP and accounting. Post sales, refunds, fees and tax to your finance system, usually as daily summaries rather than order by order. Agree how invoices are produced where local rules require them.
- 5. Marketing and customer data. Sync customers, consent and orders to your email, CRM and analytics tools, respecting the consent customers gave.
- 6. Shopify Flow automations. Once data is reliable, automate tagging, alerts and routine tasks, and add alerts for failed syncs.
| Step | System of record | Direction | Trigger | If it fails | Plan dependency |
|---|---|---|---|---|---|
| Payments and tax | Payment provider for payouts; Shopify or a tax app for tax | Provider to Shopify and accounting | Event, plus a daily payout check | Payout mismatches flagged in reconciliation | Shopify Payments and tax service vary by country |
| Inventory | One named system: Shopify, inventory tool, warehouse system or ERP | Owner to Shopify | Event, plus scheduled reconciliation | Alert below safety stock; stop selling if sync stops | API capacity depends on plan |
| Fulfilment, 3PL, COD | 3PL or warehouse system for shipment status | Orders out to 3PL; tracking back to Shopify | Event | Alert on orders not acknowledged in time | Check the 3PL's connector requirements |
| ERP and accounting | ERP or accounting system for ledger and invoices | Shopify to finance system | Scheduled daily summary | Failed posts queued and retried | API capacity depends on plan |
| Marketing and customer data | Shopify for customers and consent | Shopify to email, CRM and analytics | Event | Consent mismatches reviewed | Usually none |
| Flow automations | Shopify | Within Shopify; outbound calls via HTTP | Event | Alert on failed workflow runs | Send HTTP Request needs Grow or above |
Pro tip
Use the table as a worksheet. The entries are a typical starting point, not a recommendation for your store: replace each one with your own systems before you talk to vendors, and name a person who is alerted when each sync fails.
What Shopify already does natively
Check what Shopify covers before buying a connector or commissioning custom work. Native features are maintained by Shopify and don't add another vendor to monitor.
| Need | Native option | Check before relying on it |
|---|---|---|
| Workflow automation | Shopify Flow, a free app on the Basic, Grow, Advanced and Plus plans | Send HTTP Request needs Grow or above; tasks from custom partner apps need Plus |
| Tax calculation | Shopify Tax (US, EU, UK, Canada) or Basic Tax (Norway, Switzerland, Australia, New Zealand, Singapore) | Elsewhere you set rates manually or use a third-party tax app |
| Card and wallet payments | Shopify Payments, in supported countries | Not available in every country; India is not on the supported list |
| Selling in several countries | Shopify Markets | See our guide to Shopify Markets for the set-up decisions |
Plan limits that change the design
Flow's external calls. Shopify Flow is free on Basic, Grow, Advanced and Plus, but the Send HTTP Request action, which lets a workflow call another system, is only available on Grow, Advanced and Plus. On Basic, an integration that needs to reach an external system has to come from an app instead.
API capacity. The GraphQL Admin API limits apps by query cost. Shopify lists restore rates of 100 points per second on standard plans, 200 on Advanced, 1,000 on Plus and 2,000 on Shopify for enterprise (Commerce Components), and a single query can't cost more than 1,000 points. High-volume syncs, such as frequent full inventory updates, need to be designed around those limits with webhooks, bulk operations and incremental updates.
GraphQL, not REST. Shopify's REST Admin API has been legacy since 1 October 2024, and since 1 April 2025 all new public apps must be built exclusively with the GraphQL Admin API. Ask any connector vendor or developer which API their integration uses. How the APIs, webhooks and limits work in practice is covered in our technical guide to Shopify APIs and webhooks.
Market notes: payments and tax
- India. Shopify Payments is not on Shopify's list of supported countries, so card and UPI payments go through a third-party payment provider. Tax rates are set manually, because India isn't covered by Shopify Tax or Basic Tax. Plan GST invoicing and posting to your accounting system as part of step 4.
- UAE. Shopify Payments lists the United Arab Emirates as a supported country; check the eligibility requirements for your business. Tax rates are set manually.
- UK, EU, US and Canada. Shopify Tax is available.
- Australia and Singapore. Basic Tax is available.
Worth noting
Sources: Shopify Payments supported countries and Shopify tax services by country, checked 14 October 2026. Coverage changes, so check both pages for your markets, and take tax advice on what you must collect and invoice.
The systems Shopify stores most commonly connect to
A handful of categories cover most integration needs: ERP systems like Odoo, SAP Business ByDesign or Microsoft Business Central for financials and inventory at scale; CRM platforms like HubSpot or Salesforce once customer data needs to live in one place across marketing, sales and support; accounting tools like QuickBooks or Xero, typically fed through a connector that posts summarised daily entries rather than every order; and shipping, fulfilment systems and 3PLs that need timely inventory and tracking sync to avoid overselling. For the ERP side in more depth, see how ecommerce ERP integration works, and for warehouses and 3PLs, connecting your store with 3PL partners.
How an integration project actually runs
A well-run integration starts with mapping: what data exists in each system, which fields correspond to which, and what happens when they conflict. From there, most projects move through a connection phase (via an existing connector or custom API work), a testing phase against real data, and a monitored rollout before fully relying on the sync.
- Map how each system defines shared concepts: customer, order, inventory item, status
- Decide which system is the source of truth for each data type
- Connect via an existing app where one exists, or scope custom work where it doesn't
- Test against real data, including edge cases like returns, partial fulfilments and cancellations
- Monitor closely for the first weeks, because integration issues often surface under real volume, not in testing
Connector app or custom integration?
| Factor | Connector app | Custom integration |
|---|---|---|
| Fit | Standard workflows | Business-specific rules and data |
| Speed to launch | Faster | Slower |
| Ongoing cost | Subscription | Maintenance and hosting |
| Control | Limited to app settings | Full control over logic |
| Risk | Vendor changes | Your team owns fixes |
Data ownership rules to agree early
Decide which system owns each data type: product information, prices, stock levels, customer records, orders and refunds. Write the rules down, including what happens when records conflict. Most integration bugs trace back to two systems both believing they own the same field.
Hypothetical example: a growing homeware brand sells online and through two wholesale accounts. The warehouse system owns stock, Shopify owns orders and customers, and the accounting system owns invoices and refunds once posted. Because the rules are written down, a refund issued in Shopify flows one way to accounting, and nobody edits stock by hand in Shopify.
Where integrations commonly break
Beyond data mapping, the most common failure points are authentication expiring silently, webhook events arriving out of order or more than once, and one system's edge case (a partial refund, a merged customer record) not having a clear rule in the other. A properly built integration verifies webhook signatures, handles duplicate events gracefully, and reconciles periodically rather than trusting real-time sync alone to stay accurate.
Heavier integration needs, such as several systems, high volume or multiple linked storefronts, are also one of the more common reasons businesses evaluate Shopify Plus, since its API restore rate is higher than on other plans.
For related guides, see ecommerce API integration and inventory integration.
Pro tip
Treat the first month after an integration goes live as a monitoring period, not a finished project. Most real issues surface under actual volume, not in testing.
When not to integrate yet
If order volume is low and one person reconciles everything in an hour a week, a full ERP integration may cost more to run than it saves. A good spreadsheet process plus Flow alerts can be the right answer for a while. Equally, don't connect a system you're about to replace: integrate the new one once, not both.
The sequence above also assumes Shopify is your main sales channel. If most orders come from marketplaces or wholesale, the order management or ERP system may need to sit at the centre instead, with Shopify as one channel feeding it.
Sources
Shopify Help Center: Shopify Flow; Shopify.dev: GraphQL Admin API rate limits; Shopify.dev: REST Admin API (legacy notice); Shopify Help Center: tax services; Shopify Help Center: Shopify Payments supported countries.
Accessed 14 October 2026. Plan features, API limits and country coverage change; check Shopify's current documentation before you design around them.
Conclusion
Integrate in the order your money and stock flow: payments and tax, inventory, fulfilment, finance, then marketing data, with automation last. Use native Shopify features where they fit, design around your plan's limits, and write down which system owns each piece of data before anything is connected. Our Shopify development services and automation work cover integration projects end to end.
Planning which systems to connect first?
ZSpace Labs is a remote-first technology studio that works with clients globally on Shopify integrations and workflow automation. If useful, we can talk through your sequencing worksheet and where a connector, Flow or a custom app fits.
Common questions.
Payments and tax first, because errors there affect every order and are expensive to correct later. Then decide which system owns inventory, then connect fulfilment, then accounting or ERP, then marketing and customer data, and automate last with Shopify Flow.