ERP, CRM, PIM and 3PL integrations
Shopify commerce integrations
For brands whose orders, stock, prices and customer records live in an ERP, CRM, PIM or 3PL as well as in Shopify, OUXP builds the connections so each record is entered once and matches everywhere – no re-keying, no overnight CSV files. Senior engineers map every data flow first, use a maintained connector when one fits, build custom when it doesn’t, and alert you when a sync fails.
Where disconnected systems cost you orders and hours
Your Shopify store shouldn’t be an island. These are the six problems that most often bring merchants to us – what you see, and what we do about each.
-
Your team re-keys data between systems
- What you see
- Orders copied into the ERP by hand, stock updated from spreadsheets, customer records typed twice.
- What we do
- Move the data through the APIs on both sides, so each record is entered once – in the system that owns it.
-
An overnight sync oversells stock
- What you see
- A nightly CSV job is the only link between warehouse and store. When it fails, nobody notices until orders arrive for stock you don’t have.
- What we do
- Push stock changes as they happen, per location, and run a scheduled reconciliation that flags any mismatch.
-
The connector covers 80% of your workflow
- What you see
- The off-the-shelf connector handles standard orders and breaks on your bundles, B2B pricing or split shipments.
- What we do
- Keep what works, then configure, extend or replace the part that breaks on your 20%.
-
Nobody understands the integration anymore
- What you see
- A developer who has since left built it, nothing is documented, and everyone is afraid to touch it.
- What we do
- Read the code and logs, document every flow and fix what is fragile – see taking over an integration.
-
B2B data lives in the ERP, not in Shopify
- What you see
- Company accounts, price lists and payment terms sit in the ERP, so wholesale buyers phone in orders or see the wrong price.
- What we do
- Sync companies, catalogs and payment terms into Shopify’s B2B features, so buyers order online at their agreed prices – catalogs assigned to specific companies, or more than 3, need Shopify Plus.
-
A platform move breaks every connection
- What you see
- You’re leaving Magento, Adobe Commerce, Salesforce Commerce Cloud, BigCommerce or WooCommerce, and every integration was built for the old platform.
- What we do
- Inventory each one, rebuild it against Shopify’s APIs and test it with real order scenarios before cutover.
Which systems can you connect to Shopify?
Any system with a usable API. These are the ones we connect most often, and the data that usually moves between them and Shopify.
| System | Platforms and apps we work with | What usually moves |
|---|---|---|
| ERP | NetSuite, SAP, Microsoft Dynamics, Acumatica | Orders and refunds to the ERP; stock, prices, products and B2B accounts back to Shopify; fulfillment and invoice status in return |
| CRM | Salesforce, HubSpot | Customers and orders, so sales and service teams see the full purchase history |
| PIM | Akeneo, Salsify | Product content, attributes, images and translations into Shopify products, metafields and metaobjects |
| Shipping, OMS, WMS and 3PL | ShipStation, EasyPost, ShipBob, Flexport, ShipperHQ and 3PL warehouses | Orders out for fulfillment; tracking numbers, fulfillment status and stock per location back; shipping rates and rules at checkout |
| Payments | Shopify Payments, Adyen, Authorize.net, PayPal, Stripe | Gateway setup where the provider is offered at Shopify checkout; payouts, fees and refunds matched in your accounting system or ERP |
| Tax | Shopify Tax, Avalara | Tax calculated at checkout, B2B tax exemptions, and tax data passed to finance |
| Subscriptions | Recharge, Skio, Shopify Subscriptions | Subscription orders into fulfillment and stock planning; skip, pause, swap and cancel in the customer account; failed payments routed to whoever follows up |
| Reviews | Yotpo, Okendo, Judge.me, Bazaarvoice | Review requests after fulfillment, ratings on product pages, review history imported during a migration |
| Search and merchandising | Shopify Search & Discovery, Algolia, Bloomreach, Klevu, Rebuy | Catalog, stock and prices indexed as they change; recommendation and merchandising rules your team controls |
| Email and SMS | Klaviyo, Attentive, Iterable | Customer events, orders and consent status, so messages reach only people who opted in |
Platforms and apps we work with – not formal partnerships. Not on the list? Tell us which system – we review its API documentation and test access before quoting, and never assume a ready-made connector exists.
Connector, middleware or custom build – which do you need?
There are three ways to connect a system to Shopify. Most stacks end up mixing them: a vendor’s app for email, middleware for the ERP, and a small custom service for the one rule nothing else handles.
| Approach | Fits when | Keep in mind | Ongoing cost |
|---|---|---|---|
| Maintained connector appThe vendor’s own Shopify app, or Shopify Flow for simple automations | Your workflow matches the connector’s – common for email, reviews, shipping and tax | You get the vendor’s idea of the workflow; edge cases may not be configurable | App subscription, billed by the vendor |
| Integration platform (iPaaS)Celigo, Boomi | An ERP needs several flows – orders, stock, prices, customers – and your team wants a visual tool to adjust mappings | Unusual rules still need custom scripting inside the platform, and someone has to own the flows | A subscription from the middleware vendor – usually billed yearly – plus maintenance |
| Custom integrationA custom app or middleware on Shopify’s Admin API and webhooks | Your processes, data model or volume go beyond what connectors handle – complex B2B pricing, an ERP with no Shopify connector, high order volume | The most control, and code you own and maintain – including Shopify’s quarterly API versions | Hosting and maintenance |
Honest note
A bigger stack is not automatically better. If a maintained connector covers your real workflow, use it – we’ll tell you so, because it costs less than a custom build and someone else keeps it updated. Custom code earns its place when connectors can’t follow how your business actually works.
Simple automations inside Shopify – tagging orders, notifying a supplier – often need no integration at all. Our app and automation development team builds those with Shopify Flow or a small custom app.
Before recommending any new tool, we check
- Business need: what problem it solves, for whom, and how you’ll know it’s working
- Native capability: whether Shopify, or a tool you already pay for, can do it without another app
- Ongoing cost: subscription fees, usage pricing and the time it takes to run – over years, not months
- Maintenance: who updates it when Shopify, the theme or the other system changes
- Ownership: whose account it is, who holds the credentials and the data, and what happens if you switch
What we settle before building anything
Every integration starts with a data-flow mapping session that answers four questions with you. The answers become a written map you keep, whoever builds the integration.
-
01
Where does each record originate?
Each field gets one system of record – often the ERP for price and stock, the PIM for product content and Shopify for carts and checkout. When two systems can edit the same field, data drifts, so we decide which one wins.
-
02
How, and how often, do updates move?
Orders and stock changes move as they happen, through webhooks. Catalogs and price lists can move in scheduled batches. Each flow gets the frequency the business needs, not the connector’s default.
-
03
What happens when a connection fails?
A stuck order can’t wait the way a product description can. For each flow we agree how long data may wait, which failures raise an alert and who receives it – the safeguards are set out below.
-
04
Who resolves exceptions?
An order with an unknown SKU, a customer record the ERP rejects, an address the 3PL can’t ship to. Each type of exception gets an owner – on your team or ours – and a documented way to resolve it.
Agreed in writing before the build
- The data-flow map: every field, its direction, frequency and system of record
- How access works and where credentials are stored – no shared passwords
- Validation rules for the data that moves
- Which failures raise an alert, and who receives it
- The documentation your team will get at handover
How we keep integrations from failing silently
Integrations rarely break on an ordinary order. They break on a missed webhook, a retried request or a Shopify API change nobody planned for. Every integration we build handles these five.
-
Shopify webhooks can be missed, repeated or arrive out of order
How we handle it
Shopify doesn’t promise that every webhook arrives, or arrives in order: a failed delivery is retried up to 8 times over 4 hours, and a subscription that keeps failing is removed. We acknowledge each webhook at once, process it from a queue, skip duplicates by their webhook ID and apply changes in timestamp order. A scheduled reconciliation job then compares both systems and corrects anything missed.
-
A retry creates a second order in the ERP
How we handle it
Every write is idempotent: it carries a unique key, such as the Shopify order ID, so a repeated request updates the record it already created instead of adding a duplicate. That is what makes automatic retries safe.
-
A failure nobody hears about
How we handle it
Records that still fail after retries go to a holding queue with the error attached – never deleted – and an alert reaches the person named in the mapping. Once the cause is fixed, the records are replayed. A monitoring dashboard, handed over with the documentation, shows the state of each flow.
-
Large syncs run into Shopify’s API limits
How we handle it
Full catalog and price-list loads use Shopify’s bulk operations, which aren’t subject to the normal rate limits. Everyday calls read the remaining API budget and slow down before Shopify refuses them. As of October 2026, the GraphQL Admin API allows Shopify Plus stores 1,000 points a second, against 100 on Basic and Grow and 200 on Advanced.
-
Shopify’s API changes every quarter
How we handle it
Shopify releases a new API version every 3 months and supports each for at least 12. An integration still calling a retired version is answered by the oldest supported one instead, so its behavior can change with nobody touching it. We pin each integration to a version, track deprecations and update on a schedule – under a retainer, that is routine maintenance.
How an integration project runs
Six steps from the first call to a monitored integration, with the approach, price and timeline in writing before any build work starts.
- 1
Strategy call
Which systems, what should move between them, and what goes wrong today. Bring connector names and any documentation you have.
- 2
Data-flow mapping
The four questions answered for every flow, the other system’s API reviewed and access tested.
- 3
Approach and quote
Connector, middleware or custom – with the reasons, the recurring costs, the price and the timeline.
- 4
Build and test
Against a development store and the other system’s test environment where one exists, with the awkward cases included: refunds, partial shipments, unknown SKUs.
- 5
Go live
Flows switched on one at a time, historical data backfilled where needed, and the first live orders followed from checkout to the ERP and back.
- 6
Handover and monitoring
Documentation and a monitoring dashboard. Ongoing maintenance can move to a monthly retainer.
How integration pricing works – build and running costs
Each build is quoted in writing after the mapping session, when its real size is known, with vendor licenses and hosting listed beside our price. Maintenance afterwards is optional: hand it to a retainer, or run the integration in-house with our documentation. Retainers run month to month with 30 days’ notice.
What moves the build price
- How many systems and flows are involved
- One-way or two-way sync – two-way needs conflict rules for every shared field
- Record volume, and how often the data moves
- Whether a maintained connector covers most of the workflow
- The quality of the other system’s API and documentation
- How many exceptions your process has: B2B pricing, bundles, split shipments
What is not in our price
- Connector app and middleware licenses – billed by their vendors and listed in the proposal, so you see them before you commit
- Work your ERP consultant or 3PL charges for on their side
- Hosting for custom middleware – agreed up front with the other recurring costs
| Option | Price | What you get |
|---|---|---|
| Growth retainer | $5,000/month | 45 engineering hours a month, integration maintenance included |
| Dedicated retainer | $9,500/month | 90 hours a month or a dedicated engineer, with integration maintenance and 24/7 emergency coverage included |
| 24/7 emergency add-on | +$500/month | Added to Growth: coverage around the clock, with a 2-hour first response outside business hours |
| One-time emergency fix | $250/hour | 2-hour minimum – for a broken integration when you’re not on a retainer |
On every retainer tier, first response comes within 30–60 minutes during business hours (Mon–Fri, 9 AM–9 PM ET), monitoring and reporting don’t use your hours, and unused hours roll over one month. The Essential tier ($2,500/month) covers fixes and theme work but not integration maintenance. See retainer and maintenance plans.
Taking over an integration someone else built
Taking over an integration nobody documented is common work for us. It starts by finding out what it actually does – which is often not what anyone remembers.
What we check first
- Where the code runs, and who holds the credentials and the accounts
- Every flow, against the four mapping questions
- Error logs, and records that failed or never arrived
- Which Shopify API version it calls, and how long that version is supported
- Webhook subscriptions Shopify may have removed after repeated failures
What you get
- Written documentation of every flow
- A list of risks, ranked by what they could cost you
- Fixes quoted separately, so you decide what to change
- Monitoring and alerts where they were missing
- A choice: hand maintenance to a retainer, or keep the documentation and run it in-house
Changing platforms? The free migration assessment includes an app and integration map: what has a direct Shopify equivalent and what needs a rebuild. See all migration paths to Shopify Plus.
What merchants say about our integration work
A central inventory system and two Recharge subscription projects, quoted word for word from the Shopify Partner Directory.
-
“Others told us it wasn't possible but Vitali created a central inventory system that works with our custom setup. Great work and communication.”
Dive Bar Shirt Clubvia Shopify Partner Directory (external site)Apps & integrations -
“…resolved the challenge that we were having with Recharge in a day - where other developers seemed to struggle to provide a resolution.”
Small Beervia Shopify Partner Directory (external site)Apps & integrations -
“Implemented a recharge shopify checkout conversion and I could not be happier with how smooth everything went.”
FANGORIAvia Shopify Partner Directory (external site)Apps & integrations
Reviews sometimes name our engineers – everyone named is part of the OUXP team.
Emergency support
Store down? Checkout broken?
- Store down or showing errors
- Checkout or payment failures
- A theme or app update broke something
- ERP, inventory or fulfillment sync stopped
Commerce engineers, not a help desk. Every request gets a first response within 30–60 minutes during business hours. Retainer clients with the 24/7 emergency add-on are covered around the clock. Not a client yet? Call anyway.
+1 (818) 651-3226 Emergency line 24/7 · Business hours Mon–Fri, 9 AM–9 PM ET
Commerce integration questions
Something else? Ask an engineer – first response within 30–60 minutes during business hours (Mon–Fri, 9 AM–9 PM ET).
Should we use a connector app, iPaaS middleware or a custom integration?
Use a maintained connector when it covers your real workflow – it costs less, and we’ll tell you so. Middleware such as Celigo or Boomi suits an ERP with several flows when your team wants a visual tool for mappings, at the cost of a vendor subscription. Custom code on Shopify’s Admin API wins when your processes, data model or volume go beyond what connectors handle. The data-flow mapping session decides before you pay for a build.
What happens when an integration fails?
Integrations we build retry safely, park failed records in a queue instead of losing them, and alert a named person. For integrations we maintain on a Growth or Dedicated retainer, failures get a first response within 30–60 minutes during business hours (Mon–Fri, 9 AM–9 PM ET). With 24/7 coverage – an add-on on Growth (+$500/month), included on Dedicated – that extends around the clock, with a 2-hour first response outside business hours.
Can you fix or take over an integration someone else built?
Yes – taking over undocumented integrations is common work for us. We find where the code runs and who holds the credentials, trace every flow, read the error logs and check which Shopify API version it calls. You get written documentation and a ranked list of risks, with fixes quoted separately. From there you can hand maintenance to a monthly retainer or keep the documentation and run it in-house.
How much does a Shopify ERP integration cost?
It is quoted after a data-flow mapping session, because the price depends on what the mapping finds: how many flows, one-way or two-way sync, record volume, whether a maintained connector covers most of the work, and how good the ERP’s API is. Connector and middleware licenses are billed by their vendors. Maintenance after launch is included in the Growth ($5,000/month) and Dedicated ($9,500/month) retainers.
How do you keep inventory in sync between Shopify and our ERP or 3PL?
One system owns stock – usually the ERP or the warehouse system – and Shopify follows it. Stock changes are pushed as they happen, per Shopify location, instead of in an overnight batch, and orders reach the ERP or warehouse as soon as they are placed. A scheduled reconciliation compares both sides and flags any drift before it turns into overselling.
Do we need Shopify Plus to integrate an ERP?
No. The Admin API and webhooks work on every paid Shopify plan, and core B2B – company accounts, up to 3 catalogs and payment terms – has been on all paid plans since April 2026. Plus matters at scale: as of October 2026 its Admin API allows 1,000 points a second (100 on Basic and Grow, 200 on Advanced), and it adds more than 3 B2B catalogs, catalogs assigned to specific companies, and checkout extensions on the information, shipping and payment steps. See Shopify Plus development.
Will our integrations carry over when we migrate to Shopify Plus?
Not as they are: integrations are built against a platform’s APIs, so each one is reconnected or rebuilt for Shopify. The free migration assessment includes an app and integration map showing what has a direct Shopify equivalent and what needs a rebuild. App mapping and configuration sit inside the migration quote; ERP middleware development is usually quoted as its own item, so you see it before you commit.
Connect your stack properly
Tell us which systems should talk to each other and what goes wrong today. An engineer replies within 30–60 minutes during business hours with questions and a suggested first step – usually a data-flow mapping session.