A customer orders a part the website says is in stock, but it isn’t there. The stock number came from a feed that stopped running two days ago, and nobody noticed. Someone now has to call the customer and explain.

A Shopify Plus API integration has to prevent this kind of mismatch. The ERP, the PIM, and the CRM each hold a piece of the product, price, and customer data. And the store has to stay in step with all three.

Problems usually start when two systems disagree, and nobody has said which one to believe.

The fix starts with the connection layer itself.

What Is Shopify Plus API Integration?

Shopify Plus API integration is the work of connecting a Plus store to the systems behind it, usually an ERP, a PIM, and a CRM. Products, prices, stock, customers, and orders then move between them under rules you have agreed in advance.

Plus gives you more headroom on the same API. Access to company locations requires B2B access and the appropriate app permissions. Some operations have additional plan requirements.

For distributors starting Shopify Plus development, check both B2B pricing requirements and rate limits when choosing a plan.

Which Shopify APIs Carry ERP, PIM and CRM Data?

Shopify has a lot of APIs. Only a few of them matter for ERP, PIM, and CRM work.

API What it carries Role
GraphQL Admin API Products, inventory, customers, companies, orders Main read and write path
REST Admin API Legacy resources and endpoints; coverage differs Legacy, for an existing Shopify REST API integration
Storefront API Catalog, cart, checkout Headless storefronts
Webhooks Order, product and inventory events Near real-time triggers
Bulk operations Large asynchronous reads and writes Catalog loads, reconciliation

Example ownership of stock, content, customer records, and order capture across ERP, PIM, CRM, and Shopify.

Build anything new on GraphQL. Shopify marked REST as legacy on October 1, 2024, and since April 1, 2025, new public apps have to use GraphQL. Review existing REST integrations for migration to the GraphQL Admin API.

Your own systems and outside services connect in different ways. The ERP, PIM, and CRM can connect through an app configured for the integration, with access limited to the data they need.

A third-party service may connect through its own app. Shopify meters GraphQL Admin API capacity by app and store; integrations can still share downstream bottlenecks.

Which System Should Own Each Record?

Before anyone maps a field, answer three questions for each piece of data.

Which system owns it?

Which way does it move?

And if two systems disagree, which one wins?

A Shopify system integration that skips this can appear to work at launch while conflicts build up over time.

Object Owner Direction Rule
SKU and item identity ERP ERP to Shopify Shopify never creates a SKU
Descriptions, specs, media PIM PIM to Shopify ERP never overwrites content
List and contract pricing ERP or pricing engine ERP to Shopify One authority, documented fallback
Inventory by location ERP, WMS or OMS Back office to Shopify Send sellable stock, not total stock
Companies and contacts CRM or ERP Often both ways Agree on the matching key first
Orders Shopify Shopify to ERP Deduplicate by store and Shopify order ID
Fulfillment, invoices, credit ERP ERP to Shopify Expose only what buyers need

Inventory causes the most problems. The same item can be active at one branch and discontinued at another, so someone has to decide which locations the storefront number comes from. Confirm those rules for each branch before mapping Prophet 21 inventory.

Definitions cause problems too. If finance counts available stock one way and ecommerce counts it another, the sync just copies the disagreement across.

What Are the Architecture Patterns for ERP, PIM & CRM Data Sync?

A Shopify Plus API integration can combine four patterns. Which one a piece of data gets depends on how out of date it is allowed to be.

For an example of ERP pricing automation, see the Western Pacific build. The team saved 20+ hours a week on manual price updates. That build was on Adobe Commerce, but the same split applies on Shopify Plus.

1. Event-Driven Push for Orders and Status

Shopify sends a webhook when an order comes in, stock changes, or a fulfillment is recorded. For HTTPS webhook deliveries, your endpoint has one second to connect and five seconds to finish, and Shopify will delete an Admin API subscription after eight failed deliveries in a row. So acknowledge fast and queue the payload.

Do not mark an order synced based on HTTP status alone. Check the ERP’s application response and confirm the order was created. Store the Shopify order ID and shop identifier as the integration reference. If a call times out, you can look the order up instead of guessing whether to retry.

2. Scheduled Bulk Sync for Catalog and Pricing

Use GraphQL bulk operations for large catalog reads and supported writes. Bulk queries run in the background and return a JSONL file. Confirm that the selected pricing mutation supports bulk writes.

The bulk query itself does not consume the normal query-cost budget; the API request that submits it does. The trade-off is in how you write the query: five connections at most, and no more than two levels of nesting. Shopify’s bulk query guide notes that from version 2026-01 an app can run five bulk queries per store at once.

3. On-Demand Lookup for Contract Pricing

A few things are better left in the ERP. Contract pricing on configured items and credit holds both change too often to keep a copy in Shopify, so fetch them when the buyer needs them and cache the answer briefly.

If the ERP is down, the page still has to show something, such as a message asking the buyer to request a quote. Show a cached price only if the pricing policy permits it, and never bypass a credit hold.

4. Reconciliation as the Backstop

Webhooks get missed. They turn up in the wrong order, and sometimes they do not turn up at all. Shopify’s webhooks documentation says so plainly and tells you to run a reconciliation job.

The job is simple. On a schedule, ask Shopify for everything that changed since the last run, compare it against your own records, and raise an alert on anything that does not match.

Four integration patterns matched to orders, catalogs, pricing and discrepancy checks.

How Do Shopify Plus API Limits Shape the Design?

Each query costs points. Your plan decides how fast you get them back.

Plan Restore rate
Standard 100 points per second
Advanced 200 points per second
Shopify Plus 1,000 points per second
Shopify for enterprise 2,000 points per second

Source: GraphQL Admin API rate limits. Shopify can temporarily reduce these rates.

Three limits apply on every plan. Shopify’s API limits page puts a ceiling of 1,000 points on a single query, caps array inputs at 250 items, and stops pagination at 25,000 objects. That last one is why long order exports have to move to bulk operations.

The GraphQL Admin API’s cost metadata includes a throttleStatus block telling you how many points you have left. A Shopify Plus API integration should read it and slow down when the number drops, rather than guessing.

How Does Shopify’s B2B Model Map to ERP and CRM Records?

In Shopify, a trade buyer is a Company, and each of their branches is a Company Location. Shopify’s companyLocations reference shows what sits on a location: its own addresses, tax settings, payment terms and catalogs. A catalog decides what that branch sees and what it pays.

For a distributor, a Shopify API integration usually maps it like this:

ERP customer account to Company

ERP ship-to and bill-to records to Company Locations

ERP contract pricing to the price list on that location’s catalog

ERP payment terms to Shopify payment terms; enforce ERP credit limits separately

CRM account and contacts to the Company and its contacts

A distributor can let the ERP own credit and terms, and leave relationship history to the CRM.

How Do You Plan a Shopify Plus API Integration?

This order works well on distributor projects:

List every field the storefront shows or captures, and write down which system owns it.

Decide how fresh each one needs to be: live, on a schedule, fetched on demand, or checked by reconciliation only. This choice affects integration cost and reliability.

Agree your identifiers before anyone writes code, including the shop and Shopify order ID you will use as a reference.

Build the hardest flow first. Contract pricing and split shipments are the usual candidates.

Give someone ownership of queue depth, webhook failures and reconciliation mismatches, and set alert levels for each.

Go live one region or customer group at a time, with reconciliation running from day one.

Replacing an old connector does not change the order. Run the first two steps against the mappings you already have, because some of them will be out of date.

Our ecommerce ERP integration overview goes wider on the ERP side.

Frequently Asked Questions

1. Is a Shopify API Integration Better Than a Connector App?

A connector comes with its mappings already set, which is fine if you have one ERP and standard flows. Building your own starts to pay off when your pricing, fulfillment or multi-entity rules are specific to your business.

2. Does a Shopify System Integration Need Middleware?

Not always. One ERP with standard flows can connect straight to Shopify. Once a PIM, CRM and WMS are in the picture, a single layer that handles the mapping, queuing and retries is usually easier to run than several direct connections.

3. How Often Do Shopify API Versions Change?

Every three months, and Shopify’s API versioning guide says each stable version is supported for at least 12 months. Name a version in every request and test against the newest one each quarter. If your version is retired, Shopify falls forward to the oldest supported stable version. Check the X-Shopify-API-Version response header.

4. How Do You Secure Webhooks in a Shopify Plus Integration?

Check the HMAC signature in the X-Shopify-Hmac-SHA256 header against the raw request body before you do anything with the payload. After that, use the X-Shopify-Webhook-Id header to spot repeats, because Shopify can send the same webhook twice.

Conclusion

Storefronts get redesigned every few years, and connectors get swapped out with them. The ownership rules and the reconciliation job are what survive those changes. Get them right and nobody has to re-key orders when the front end changes, which is why they are the part of a Shopify Plus API integration worth paying for first.

Klizer calls this Connected Commerce: Foundation, Storefront, Integration and Intelligence working as one system. The integration gets built alongside the ERP, not added once the store is already live.

For manufacturers and distributors, this means designing the storefront, ERP integration, and monitoring together.

If you are planning one of these, book a consultation with Klizer for your ERP setup.

Picture of Geetanjali Chauhan
BLOG BY

Geetanjali Chauhan

Geetanjali Chauhan is a content marketing and social media professional at Klizer with more than 10 years of experience across B2B technology and digital-first brands. Her expertise includes content strategy, copywriting, search-focused writing, social media campaigns, email marketing, brand messaging, and performance analysis. She holds a Ph.D. in Microbiology, which gives her a research-driven, analytical approach to complex subjects. At Klizer, she writes about ERP migration, Epicor and P21, Shopware B2B commerce, PIM integration, and AI in distribution, turning technical topics into clear guidance for business readers.
Scroll to Top