Shopify ERP Integration: Connecting NetSuite, SAP and Odoo Without Data Mess

The first sign is usually small. A customer orders the last two units of a bestseller, the warehouse has already sold them to a wholesale account, and nobody finds out until the pick ticket comes back short. Then finance notices that Shopify shows one refund total for the month and the ERP shows another, and nobody can explain the gap.

A Shopify ERP integration exists to stop exactly that. Done properly, it moves orders, inventory, products, customers, fulfillments and refunds between Shopify and NetSuite, SAP, Odoo or Business Central on rules everyone agreed in advance. Done badly, it moves the same records twice, overwrites good data with stale data and fails quietly. Below is what we actually configure on these projects: field ownership, sync timing, connector choice, failure handling and a year-one cost model.

What a Shopify ERP integration actually has to do

A Shopify ERP integration has one job: keep both systems agreeing about stock, orders and money, closely enough that nobody fixes things by hand. Shopify is where customers buy; the ERP is where the books, purchasing and fulfillment planning live.

Shopify’s own ERP integration page describes four ways to wire this up: native vendor connectors, iPaaS platforms, custom builds, and older ESB or ETL tooling. Its Global ERP Program lists five certified partners: Microsoft Dynamics 365 Business Central, Oracle NetSuite, Infor, Acumatica and Brightpearl by Sage. SAP is not on that list, which matters later.

Every approach uses the same two mechanisms: the Admin API to read and write records, and webhooks such as orders/create and inventory_levels/update to push events. A connector is mostly a set of opinions about using those two. When the opinions match your business, connectors are cheap and dull. That’s what you want.

What syncs, and in which direction

Six record types carry almost every integration: products, inventory, orders, customers, fulfillments and refunds. Payouts are a quiet seventh that finance cares about. This is our starting default for direct-to-consumer stores.

Two rows cause most of the trouble. Refunds, because they arrive days after the order, often partial, sometimes as an exchange. And B2B, because company records, payment terms and price lists live in the ERP and have to land in Shopify’s B2B objects in a shape Shopify accepts. If wholesale is in your plan, read our guide to Shopify B2B store development before you map anything.

Source-of-truth rules: settle these before you buy anything

Every field needs exactly one owner, and the other system must never overwrite it. Obvious on paper. It usually breaks in week two, when a merchandiser fixes a price in Shopify admin and the next product sync from the ERP quietly puts the old price back.

We write the rules as a one-page table and get ops, finance and ecommerce to sign it. The ones we reach for most:

• The ERP owns anything with a cost attached. SKU codes, unit cost, base price, tax class, weight and stock. Shopify displays them and never edits them.
• Shopify owns anything a shopper reads. Titles, descriptions, images, SEO fields and most metafields. ERP text fields will mangle your product copy. Our metafields guide covers how to structure the fields that stay on the Shopify side.
• Orders are immutable once accepted. After the ERP creates a sales order, edits in Shopify become flagged exceptions, not silent updates.
• The SKU is the join key. Not the title, not the Shopify ID. If your SKUs aren’t unique and stable, fix that first. No connector will.

Microsoft’s connector shows the immutable-order rule in action. Its order sync documentation says that when an order changes in Shopify after Business Central has processed it, the connector flags a conflict instead of pushing the change through. That’s the right default for any ERP, and we build it into custom work too.

Connector vs iPaaS vs custom: three ways to do ERP ecommerce integration

Use a vendor connector if your flows look like everyone else’s. Use an iPaaS if you need to bend the flows or add more systems. Write custom code only for the parts neither can express. Most ERP ecommerce integration projects we see would have been fine with the first option, and a fair number were sold the third.

Custom middleware is right when your ERP has no maintained connector, or when one flow (say, a made-to-order bundle that explodes into twelve component lines) can’t be modelled anywhere else. It’s wrong when the reason is “we want control.” You’ll get control. You’ll also get on-call duty.

NetSuite, SAP and Odoo: what each one needs

The ERP you run shapes the plan more than the tool does. NetSuite has two mature packaged options, SAP depends on which SAP you mean, and Odoo modules vary wildly.

NetSuite Shopify integration

For a NetSuite Shopify integration, start with Oracle’s own connector and move to Celigo only if you outgrow it. The NetSuite ERP Connector listing shows four tiers: B2C Standard at $199.92 a month, POS and B2C Premium at $249.92, and B2B at $916.58. Orders, price and quantity sync, full product sync and coupons are in every tier. B2B customer sync appears only on the B2B tier, so price that in if you sell wholesale.

The connector still runs on what used to be FarApp, and you’ll see that name in the settings. Real-time price and quantity sync is on by default; you switch it off in NetSuite under Setup > Company > General Preferences > Custom Preferences, in the FarApp group. Oracle’s help page on that preference says that with real-time off, item changes are picked up on a cycle that typically runs every 45 minutes, and a separate push to the storefront runs every 60 minutes by default. Leave real-time on unless you have a specific reason not to.

Celigo is the step up. Its App Store listing shows a Starting package at $7,800 a year with 2 endpoints and 10 integration flows, and a Standard edition at $18,900 a year with 3 endpoints, 20 flows and 24/7 support. Count your flows before choosing. Orders, fulfillments, inventory, products, customers, refunds, cancellations and payouts make eight, which fits the Starting package. Add a 3PL as a third endpoint and you’re on Standard.

SAP Shopify integration

SAP Shopify integration splits in two. For SAP Business One there are packaged apps: eShopSync’s SAP Business One Integration lists a Standard plan at $99 a month or $1,070 a year, syncing B1 items to Shopify products and item groups to categories. It has two reviews, so pilot it with your own order types before trusting it with live volume.

S/4HANA and older ECC systems we treat as iPaaS or custom projects from day one. With SAP outside Shopify’s Global ERP Program there’s no certified one-click app, and large SAP shops usually have middleware they’ll want you to use anyway. The hard part is rarely the Shopify side. It’s getting a test client, a change window and one named owner for the sales order interface.

Odoo Shopify connector

Choosing an Odoo Shopify connector mostly means reading module pages carefully. As one example, the eCommerce Shopify module by Odoo IN for Odoo 19 is listed at $198.63 and says plainly that it uses no webhooks. Orders and fulfillments sync on a 10-minute scheduled job. Products come across from Shopify only on demand, each variant becomes a standalone product, and metafields aren’t mapped. Refunds arrive as credit notes linked to the original invoice.

Fine for simple variants, poor for a fashion brand with 40 size and colour combinations per style. The listing also notes that stores created on or after 1 January 2026 must connect through OAuth rather than a custom-app token, which ties into the changes in our explainer on expiring offline access tokens. Ask every connector vendor how they handle that.

Sync frequency: how fresh does each record need to be?

Inventory and orders need minutes or less. Almost everything else can wait an hour or a day. We often find every flow set to the fastest schedule “to be safe,” so product updates fight order imports for API capacity during a sale.

Ask what the worst gap is that you can live with. For stock, that depends on how fast a SKU sells against the buffer you hold. A hero product selling 30 units an hour can’t sit on a sync that might be 105 minutes stale (our worst case from adding the 45-minute check and the 60-minute push above). A slow-moving accessory can.

Our rules of thumb:

1. Orders: event-driven, from the orders/create webhook or the connector’s real-time option, with a 15-minute sweep to catch anything missed.
2. Inventory: on change from the ERP, plus a full reconcile nightly. Hold a safety buffer on fast sellers instead of chasing instant sync.
3. Fulfillments: every 15 to 30 minutes. Late tracking emails get noticed.
4. Products and prices: on change, or hourly. Big catalog loads go through Shopify’s bulk operations, never a loop of single calls.
5. Payouts: once a day, after Shopify settles.

Failure handling: what breaks and how to catch it

Every Shopify ERP integration fails sometimes. The good ones make a failure visible within minutes and fixable without a developer. That needs retries that can’t create duplicates, a place where failed records wait, and a reconciliation job that trusts none of it.

Know the platform limits. Shopify’s webhook troubleshooting docs say your endpoint must respond within five seconds, failed deliveries are retried up to eight times over four hours with growing gaps, and if failures persist the subscription is removed. A deploy that breaks the endpoint over a weekend means events you will never receive. Shopify’s advice is to backfill the gap from the API afterwards.

What we put in place on every build:

• Acknowledge, then process. Return 200 straight away, queue the payload and process it from there. Slow ERP calls inside the webhook handler are the usual cause of timeouts.
• Idempotency on the Shopify order ID. Webhooks can arrive twice. The ERP should refuse a second sales order for an order ID it already has.
• A dead-letter queue with a human owner. Records that fail mapping (an unknown SKU, a missing tax code) go to a list someone in ops checks every morning. Not a shared inbox. A named person.
• A nightly count check. Orders, refunds and units shipped per day in Shopify against the ERP. If the numbers differ, alert. On the integrations we support, this is the check that catches problems first.
• Subscription health checks. A daily job confirms the expected webhook subscriptions still exist and recreates any Shopify removed.

Read your connector’s failure states before go-live. Business Central, for instance, marks a failed shipment sync with a Fulfillment ID of -1 and retries only when someone resets it to 0, per the Microsoft page above. Every connector has quirks like that. Get the list in writing and decide who handles each case by hand.

What a Shopify ERP integration costs: a worked example

For one store on a mainstream ERP, expect year one somewhere between roughly $10,000 with a well-fitting connector and $40,000 or more with custom middleware, once implementation and support hours are counted. Hours, not licences, drive the total.

A clearly hypothetical example: say you run a homeware brand on NetSuite doing about 3,000 Shopify orders a month from two warehouses, with 900 SKUs and no B2B. We price three approaches at a blended partner rate of $90 an hour. Licence prices come from the listings above; the hours are our planning estimates, not quotes.

Note the year-two row. Custom middleware is barely cheaper to run than Celigo, because the licence saving goes into support hours, so the case for custom is fit, not savings. And the connector stays cheap only while your flows fit its model. Spend 30 hours a quarter on workarounds and Celigo looks cheap.

ERP licensing, 3PL connectors and pre-launch data cleanup sit outside this table. Cleanup is the line people forget: duplicate SKUs, inactive items with stock, customers with three “primary” addresses. If you want this model run on your own numbers, our enterprise integration team does that as the first step of a project.

Frequently asked questions

What we’d do first

Don’t start with a vendor demo. Start with a spreadsheet: one row per field, then columns for owner, direction and how stale it may get. Get ops and finance to agree on it. That page settles about half the tool decision by itself.

Then run your 200 messiest real orders through the cheapest option that might fit, usually the ERP vendor’s own connector. If it handles nearly all of them, buy it. If not, you have the evidence to justify an iPaaS. Either way, build the nightly count check before go-live. Six months from now, it’s the thing that tells you everything above still works.

We’ve built for brands like Delsey, EcoFlow and Medcline. If you want a Shopify ERP integration that finance will actually trust, look at our enterprise solutions and tell us what you’re connecting.