Shopify growth agency · Working with stores worldwide
Start a project
Home/Services/Shopify Store Development/App/API Integration
App/API Integration

Shopify API Integration for ERP, 3PL, PIM and Back-Office Systems

Shopify API integration connects your store to the systems that run the rest of the business: the ERP that owns stock and pricing, the warehouse that ships orders, the PIM that holds product data, the CRM, the accounting package and the marketplaces you sell on. When those connections are missing or fragile, staff re-key orders, stock goes out of date, and nobody trusts the numbers. We choose and configure the right connector app where one fits, and build custom middleware on the Admin GraphQL API where it does not. You get data that moves on time, a written map of what syncs where, and alerts when something fails.

0Steps from audit to launch
0Of changes previewed before they go live
0Free audit before any quote
Free audit firstStaged changesYou approve every changeShopify and Shopify Plus

Integration projects are part of our Shopify store development service and are often scoped alongside a new build, a redesign or a Plus upgrade.

01

What an integration project covers

An integration defines which system is the source of truth for each type of data, how that data moves between Shopify and the other system, how often, and what happens when a sync fails. The deliverable is a working connection plus the documentation to maintain it.

Every project we run answers four questions before any code or app is chosen:

  1. Which system owns each field? Price might live in the ERP, descriptions in the PIM, stock in the warehouse system, and SEO fields in Shopify.
  2. Which direction does it flow? One way, both ways, or one way with exceptions.
  3. How fast does it need to arrive? Orders to a 3PL within minutes, product enrichment overnight, accounting daily.
  4. What happens on failure? Retry, alert, queue for review, or block the order.
02

Systems we connect to Shopify

SystemExamplesWhat usually syncsTypical direction
ERPNetSuite, Microsoft Dynamics 365 Business Central, SAP Business One, OdooProducts, prices, stock, orders, customers, B2B termsBoth ways
PIMAkeneo, Salsify, PlytixTitles, descriptions, specs, images, variant options, metafieldsPIM to Shopify
3PL and WMSWarehouse and fulfilment partners with an API or EDIFulfilment requests, tracking, stock levels, returnsBoth ways
CRMHubSpot, SalesforceCustomers, orders, lifetime value, B2B accountsShopify to CRM
POSShopify POS, third-party in-store systemsStock by location, in-store sales, customersBoth ways
AccountingXero, QuickBooksOrders, refunds, payouts, fees, taxShopify to accounting
MarketplacesAmazon, eBay and others via Marketplace Connect or a dedicated connectorListings, stock, ordersBoth ways

Brand names above are examples of systems stores commonly run. We scope each integration against the specific system and version you use.

03

Connector app, integration platform or custom middleware

There are three ways to connect Shopify to another system, and the cheapest one to build is not always the cheapest one to run.

OptionGood forWatch out for
Connector app from the Shopify App StoreCommon systems with standard data, fast setupFixed field mappings, limited error visibility, monthly app fees
Integration platform (iPaaS)Several systems, moderate customisation, in-house ops teamPlatform licence cost, logic spread across many flows
Custom middleware on the Admin GraphQL APIUnusual data models, high order volumes, strict timing, legacy systemsNeeds hosting, monitoring and an owner

We start by testing whether a connector covers your real data. If it maps nearly all of your fields and the gaps can be handled in metafields or a small extension, that is usually the right answer. When a connector would force you to change how the business works, we build custom.

04

How we build custom Shopify integrations

Custom integrations run as a custom app installed only on your store, with access scopes limited to what the integration needs. The technical choices below are where most fragile integrations go wrong.

Admin GraphQL API first

Shopify now treats the REST Admin API as legacy and puts new capability into the Admin GraphQL API. We build on GraphQL so the integration does not need rewriting when older endpoints are retired, and so we can request exactly the fields we need in one call.

Webhooks with verification and reconciliation

Webhooks tell the middleware the moment an order is created, a product changes or stock moves at a location. They can be delivered to an HTTPS endpoint, Amazon EventBridge or Google Cloud Pub/Sub. We verify each webhook's HMAC signature, process events idempotently because the same event can arrive more than once, and do not rely on arrival order. A scheduled reconciliation job compares both systems and repairs anything a missed webhook left behind.

Bulk operations for large data sets

Initial loads and nightly catalogue syncs use bulk operations rather than thousands of paged calls. A bulk query exports products, variants or orders to a JSONL file that the middleware processes. Bulk mutations import changes from a staged upload. This keeps large catalogues in sync without hitting rate limits.

Rate limits and throttling

The GraphQL Admin API limits apps by calculated query cost, not request count, and Shopify Plus stores get higher limits. The middleware reads the throttle status returned with each response, backs off before it is blocked, and queues work during flash sales so orders still reach the warehouse in order.

Data mapping

Most sync errors are mapping errors. We document how Shopify objects relate to the other system:

  • SKU as the shared key, with Shopify variant IDs and inventory item IDs stored against ERP item codes.
  • External IDs stored in metafields, so records can be matched without guessing.
  • Locations mapped to warehouses, with fulfillment orders routed to the right 3PL.
  • Discounts, shipping, taxes, refunds and Shopify Payments fees mapped so accounting totals match payouts.
  • Currencies and prices per market when Shopify Markets is in use.

Sync monitoring

Every integration ships with logging, retries, a queue for failed records, and alerts to a named person by email or Slack. You can see what synced, what failed and why, without asking a developer.

05

Problems we fix

ProblemUsual causeFixMetric it moves
Overselling items that are out of stockStock syncs on a slow schedule or ignores some locationsEvent-driven stock updates plus reconciliationOversell and cancellation rate
Orders not reaching the warehouseSilent API failures, no retryQueue with retries and alertsOrder-to-ship time
Duplicate customers in ERP or CRMNo shared key, email changesMatching rules and stored external IDsData quality, support time
Accounting never reconcilesRefunds, discounts and fees mapped inconsistentlyExplicit financial mapping by transaction typeMonth-end close time
PIM overwrites SEO titles and descriptionsPIM set as owner of every fieldField-level ownership rulesSearch visibility of edited pages
Integration stalls during a saleRate limits hit, no backoffCost-aware throttling and queueingOrders processed per hour at peak

A PIM or ERP that creates or renames products can also change handles, create near-duplicate products or push thin content to live URLs. When that happens, our technical SEO for Shopify team checks redirects, canonicals and indexation so the sync does not quietly cost you search traffic.

06

Where integration stops and automation starts

Integration moves data between Shopify and another system. Automation decides what to do with it on a schedule or rule. We keep them separate so each has a clear owner:

07

Integrations on Shopify Plus

Plus stores tend to have more systems, more locations and more order volume. Higher API limits help, and B2B adds data that must come from the ERP: company records, catalogs, price lists and payment terms. Setting up B2B, expansion stores and checkout logic on Plus is handled by our Shopify Plus developers, and we connect those features to your back office.

08

How an integration project runs

  1. Audit and baseline. We map your current systems, data owners, manual re-keying and existing apps, and measure where time and errors go today. You receive a written integration audit.
  2. Strategy and scope. We produce a data mapping document and recommend connector, iPaaS or custom build. You agree a fixed scope and timeline.
  3. Build and fix. The integration is built against a development store or a sandbox of the other system first. You review test orders, product syncs and failure alerts before anything connects to live data.
  4. Launch and track. We switch the integration on in a planned window, watch the first live syncs closely, and hand over documentation. Ongoing clients get a private portal, monthly reporting and a monthly call.
09

Cost and timeline

Integration work is a fixed project fee, scoped after a discovery call, because a connector configuration and a two-way ERP build with B2B pricing are very different amounts of work. See how quotes are put together on our pricing page.

As a typical range, a connector setup takes one to three weeks and a custom ERP or 3PL integration takes six to twelve weeks. Timing depends on data quality, how many systems are involved, and access to the other system's API and test environment.

If you already know which system you need connected, book a Shopify integration scoping call and bring a sample of your data.

10

Who this service is for

  • Stores re-keying orders into an ERP, warehouse or accounting system by hand.
  • Brands moving to a new ERP, PIM or 3PL and needing Shopify connected on day one.
  • Stores whose current connector drops orders or stock updates without telling anyone.
  • Multi-location and wholesale brands that need stock and prices from one source of truth.
FAQs

Frequently asked questions

Often an app will do. We test your real data against available connectors first and only recommend custom middleware when a connector cannot handle your data model, volume or timing.

A custom ERP integration usually takes six to twelve weeks, depending on data quality and access to the ERP's API. A connector setup is much faster.

It is a fixed project fee quoted after a discovery call. The price depends on the number of systems, the direction of sync, data volume and whether a connector or custom build fits.

Failed records go to a queue, are retried automatically, and trigger an alert to a named person if they keep failing. A reconciliation job also compares systems on a schedule.

We build on the Admin GraphQL API, which is where Shopify adds new capability. It also lets us use bulk operations and cost-based throttling for large catalogues.

Yes. We sync companies, locations, catalogs, price lists and payment terms from the ERP so trade buyers see the right prices when they log in.

A staff account on Shopify with the right permissions, plus API credentials or a sandbox for the other system. Integration apps request only the access scopes they use.

Pairs well with

Related services

Scope your Shopify integration

Tell us which systems you run and where data gets stuck today. We start with a free audit of your current setup and send back a data mapping outline with a recommended approach. Scope your Shopify integration with us.

Chat on WhatsApp