ERP for Shopify: What an Odoo Build Actually Involves

If you run a Shopify store and you are looking at ERP, the first thing to know is that Odoo is not one of the five ERPs Shopify certifies. The second is that a Shopify connector Odoo itself supports now exists on its App Store — third-party, not first-party — and its documented limits, not its feature list, are what should decide whether it fits you.

Odoo tends to get filed under “budget option” in ERP comparisons, which tells you nothing useful about whether it will work for your store. What decides that is narrower and more concrete: what the connector actually syncs, what it refuses to sync, and what your own team ends up owning.

That is what this piece covers.

Key takeaways

• Shopify certifies five ERPs. Odoo is not one of them. The Global ERP Program covers NetSuite, Brightpearl by Sage, Dynamics 365 Business Central, Acumatica, and Infor.
• Certification has a price. The certified NetSuite connector alone costs more per year than any Odoo connector costs once.
• A Shopify connector Odoo supports exists regardless, listed on Odoo’s App Store for version 19 at around $199 — categorised third-party, not first-party.
• That connector syncs on a ten-minute cron, not webhooks. There is no real-time sync. For most stores that is fine; for flash sales and tight stock it is not.
• Product data flows one way — Shopify into Odoo. You cannot push products from Odoo out to Shopify with that connector.
• Shopify variants do not import as Odoo variants. If your catalogue is variant-heavy, this is the line item that will define your build.
• Those limits are the $199 module’s, not Odoo’s. Connectors at $580–$640 claim webhooks, two-way product sync, variants, metafields and per-market pricing — so choosing your connector matters more than most buyers realise.
• If you sell configurable products, Shopify has a structural ceiling — three options per product and no nested bundles — and that is the clearest case for the storefront living in Odoo.

First: Odoo is not a Shopify-certified ERP

Shopify runs a curated programme of ERP integrations it has vetted itself. As of today the Shopify Global ERP Program lists exactly five certified apps: the NetSuite ERP Connector, Brightpearl by Sage, Dynamics 365 Business Central, Acumatica Cloud ERP, and the Infor eCommerce Connector.

Odoo is not on that list, and you should not let anyone tell you otherwise.

What that actually means is narrower than it sounds. Certification means Shopify has reviewed the integration and will vouch for it. It does not mean uncertified systems cannot connect, and it does not mean the certified five are better fits for your business.

It does mean one concrete thing: if your evaluation criteria include “Shopify itself stands behind this integration,” Odoo fails that test.

It is worth seeing what that assurance costs, though, because the gap is not small.

The certified connector alone costs roughly $2,400 a year. The Odoo ones cost between about $199 and $640, once. That is the actual trade you are making when you weigh certification.

There is a supported connector, and its limits are published

You may have read that connecting Odoo to Shopify means an unofficial module or a middleware layer. That is now only half right, and the distinction matters.

Odoo’s App Store lists a Shopify connector for Odoo 19 published by Odoo IN Pvt Ltd, built on Shopify’s GraphQL and OAuth standards, at around $199.

Be precise about what that is. The App Store categorises it as Third Party, and the listing describes it as the only third-party Shopify app Odoo supports. So it is not a first-party Odoo module in the way the Amazon connector is, and it is not a Shopify-certified integration either. What it is: a connector Odoo stands behind, with a support path, sold through Odoo’s own store. That sits somewhere between “official” and “some vendor’s module,” and anyone telling you it is either one is oversimplifying.

What makes it genuinely useful to evaluate is that its listing publishes its own limitations in unusual detail — including the ones that lose deals. Most connector marketing does the opposite.

Those limits are the most important information on this page, so here they are in full.

What the standard connector does and does not do

Read that table as a filter rather than a feature list. Four of those rows disqualify certain businesses outright, and it is much cheaper to discover that now than in week six of a build.

One distinction worth holding onto: these are the connector’s limits, not Shopify’s. Shopify’s API supports webhook-driven updates, writing products from an external system, creating variants, metafields, and per-market price lists. Every row above marked Not supported reflects a decision by the connector’s authors, not a wall in the platform. That matters when you are deciding whether to accept a constraint, pay to work around it, or take a different route entirely — and it is worth asking any partner which of the two they are describing when they tell you something cannot be done.

And they are not Odoo’s limits either

This is the part most comparisons miss. The $199 module is not the only Shopify connector for Odoo, and the more expensive ones claim precisely the capabilities it lacks. VentorTech’s Shopify Connector PRO ($578.49) and Emipro’s Shopify Odoo Connector ($636.46) both advertise webhook-driven order import within seconds, two-way product and variant sync, metafield mapping, and per-market pricing exported from Odoo pricelists.

So the four constraints below are real, but they are a property of one specific $199 module rather than of running Odoo behind Shopify. If a limitation in the next section would disqualify you, the first question is not “do we need custom development?” — it is “are we looking at the right connector?” Spending another $400 is a great deal cheaper than either building around a limit or changing ERP because of one.

Those claims are the vendors’ own, and we have not tested them, so treat a demo on your actual catalogue as non-negotiable before you buy. We compare the options properly in our guide to Odoo Shopify connectors compared.

The four constraints that decide whether this fits

There is no real-time sync

Synchronisation runs on a scheduled job every ten minutes. Nothing is webhook-driven.

For a store shipping a few hundred orders a day across one or two channels, a ten-minute lag is invisible. For a store running flash sales, drops, or genuinely scarce inventory across multiple channels simultaneously, ten minutes is long enough to oversell — and overselling is the specific failure that pushes most merchants toward ERP in the first place.

If you came to ERP because you oversold something, ask specifically whether a ten-minute sync window solves your problem or reproduces it — and price a webhook-capable connector before you accept it.

Products only flow one way

The connector imports products from Shopify into Odoo. It does not push products from Odoo out to Shopify.

That matters more than it first appears, because it fixes where your catalogue is mastered. If you want Odoo to be the single source of truth for product data — the usual reason for buying an ERP — this connector will not deliver that for the storefront. Your team keeps creating and editing products in Shopify.

Accept Shopify as your product master, buy a connector that syncs both ways, or budget custom development to reverse the flow. Those are the three honest options, and only one of them is priced into a $199 module.

Variants do not map to variants

Shopify product variants are not imported as Odoo product variants.

For a catalogue of simple, single-SKU products this is irrelevant. For apparel, footwear, or anything sold in a size-and-colour matrix, it is the single largest piece of scope in the project. In our experience variant-heavy catalogues are where under-scoped ERP integrations come apart, and this is a documented limitation rather than a surprise — which is the good news, because you can price it before you start.

If your catalogue is variant-heavy, either start with a connector that maps variants natively, or treat variant mapping as the main line item in your quote.

Settings are locked while connected

Account settings — warehouse, journals, taxes — cannot be changed while the connector is active. Changing one means disconnecting, changing it, and reconnecting.

This is a minor operational annoyance rather than a blocker, but it shapes how you sequence a build: get your warehouse, journal, and tax configuration right before you connect, because changing them afterwards is a controlled procedure rather than a quick edit.

The decision nobody frames properly

It is usually assumed that Shopify stays exactly where it is and an ERP slots in behind it. That is usually the right answer. But it is an assumption, not an analysis, and Odoo is the one system where it deserves examining — because Odoo has its own ecommerce module, which means “keep Shopify” is a genuine decision rather than a default.

Keep Shopify as the storefront when your customer-facing experience is a competitive asset — conversion-optimised theme, an app stack you rely on, a checkout that performs. Shopify’s storefront and checkout are hard to beat, and rebuilding them inside an ERP to save a connector is a bad trade.

Consider moving the storefront when your complexity is operational rather than presentational — freight-rated shipping, trade pricing by customer account, B2B and retail from one catalogue.

Configurable products are the clearest case

Configurable products deserve their own mention, because this is where Shopify has a structural ceiling rather than a difficulty you can work around with effort.

Shopify raised its variant limit to 2,048 per product in October 2025. But options are still capped at three. A configurator with six independent choices cannot be expressed at all — not because 2,048 combinations is too few, but because you cannot declare six axes of choice in the first place.

Shopify’s bundle support has its own walls, and Shopify documents them itself: bundles cannot contain other bundles, they are incompatible with subscriptions and pre-orders, they do not support import, export or bulk editing, and if a component’s SKU changes you must delete and recreate the whole bundle. Mix-and-match bundles need either a third-party app or the Shopify Plus plan and the Bundles API. If you sell a kit assembled from sub-kits, that structure has no native representation.

Three workarounds exist, and they fail in different ways. A headless storefront that calls your ERP for pricing, or a quote-then-pay flow using Shopify’s Draft Orders API, both cost you something visible — the standard cart, the theme ecosystem, or both. The third keeps your storefront intact: a Shopify Function with network access, where a fetch target declares an HTTP request, Shopify executes it against your ERP, and the response feeds your pricing or validation logic at checkout. That is the cleanest fit for freight-rated shipping and trade pricing — and for most stores it is unreachable. Discount Functions and Cart and Checkout Validation are gated to Shopify for enterprises with custom apps, it has to be switched on by Shopify, and it is not available on development stores, so you cannot prototype it before committing. Shopify’s own documentation steers you toward metafields instead.

If a configurator is central to how you sell, that is the clearest argument for the storefront living in Odoo, where it is native and single-sourced. We worked through exactly this in our WooCommerce to Odoo migration case study, where a product configurator and trade pricing were the deciding factors.

The question to ask is not “which ERP” but “where does my complexity actually live?” If it lives in the storefront, keep Shopify. If it lives in operations — or in a configurator — the storefront is negotiable.

What it costs, and how long it takes

Here are our numbers.

In our experience Odoo ecommerce implementations run from roughly $5,000 to $100,000 (USD), and the variable with the widest effect is not your size — it is how much of the configuration your own team does. Teams that learn Odoo and configure it themselves, with an agency bridging gaps, typically sit at $5,000–$10,000 and land in roughly four to eight weeks. Teams that hand the project over entirely typically sit at $10,000–$100,000 and run three to six months, because discovery becomes a real project phase rather than a kickoff call. We break down why in what an Odoo ecommerce implementation actually costs.

All four figures above assume a catalogue that does not need variant remapping. If yours does, treat that as additive to both the cost and the timeline.

For a Shopify-specific build, the items that move the number are:

1. Variant mapping, if your catalogue needs it and your connector does not do it — usually the largest single line.
2. Reversing the product flow, if you want Odoo to master the catalogue and your connector only reads.
3. Catalogue and order history migration, driven by data quality rather than volume.
4. Custom code, which forces you off Odoo Online and onto Odoo.sh or on-premise — a hosting consequence most buyers discover late, and one with a licensing cost attached.

Notice that the first two disappear if you pick the right connector. That is the cheapest decision on this page and the one most often made by default.

The last point is worth pinning down before you sign anything. Odoo’s own hosting documentation states that Odoo Online does not run third-party modules containing Python code, which is what every Shopify connector here is. Ask any prospective implementer which hosting that requires, which plan tier that hosting sits on, and what the per-user rate is on that tier in your country. Odoo runs IP-detected regional pricelists, so a figure pulled from the wrong country can be out by 3× or more — check odoo.com/pricing yourself rather than taking a number from a quote or a blog post, this one included. The same caveat applies to every connector price above.

Plus the connector itself, somewhere between about $199 and $640 — a rounding error against the build, which is exactly why you should buy on capability rather than price.

What your team actually has to do

This gets less attention than platform selection, and it decides whether a project lands more reliably than the platform does.

One person on your side has to know all your workflows. Not a project sponsor, not a committee — one individual who can answer “why is that customer group priced differently?” definitively rather than convening a meeting.

If you have that person, a large share of configuration can sit with your team and the cost lands near the bottom of the range. If you do not, your partner fills the role, and the cost moves toward the top — not because the software is harder, but because someone has to assemble a picture of how your business works that does not currently exist in one place.

Concretely, expect your team to own:

• Deciding where each object is mastered — products, customers, inventory, pricing. Your connector’s defaults make some of these decisions for you; the rest are yours.
• Cleaning the catalogue before migration. Migration cost tracks data quality, not row count.
• Configuring warehouses, journals, and taxes before connection, because changing them afterwards means disconnect-and-reconnect.
• Testing the edge cases you actually hit — partial fulfilments, refunds against split shipments, the SKU that oversells.
• Owning the sync after go-live. Something has to happen when the job fails at 2am, and “we’ll notice” is not a plan.

If a partner has not asked who your system administrator is, they have not scoped your project.

When an ERP is the wrong answer

Gartner projects that by 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business use-case goals, with as many as 25% failing catastrophically (Gartner). In our view, a meaningful share of those are projects that should never have started.

You probably do not need an ERP yet if you are on a single sales channel, your fulfilment is straightforward, your catalogue is simple, and your reconciliation is a monthly task rather than a daily one. Shopify plus a competent inventory app will carry you further than most ERP conversations suggest.

The honest trigger is not revenue. It is when reconciling between systems becomes somebody’s actual job.

Frequently asked questions

Is Odoo a certified Shopify ERP?

No. Shopify’s Global ERP Program certifies five ERPs — NetSuite, Brightpearl by Sage, Dynamics 365 Business Central, Acumatica, and Infor. Odoo is not among them. A Shopify connector Odoo supports does exist on the Odoo App Store, but that is not the same as Shopify certification.

Does Odoo have an official Shopify connector?

Not in the strict sense. The Odoo App Store lists a Shopify connector for version 19 published by Odoo IN Pvt Ltd at around $199, but the store categorises it as Third Party and the listing describes it as the only third-party Shopify app Odoo supports. So it is a connector Odoo stands behind and sells through its own store, rather than a first-party module — and it is not a Shopify-certified integration either.

Is the $199 connector my only option?

No, and this is the most consequential thing to know before you scope a build. Independent vendors sell Shopify connectors for Odoo 19 at higher prices — VentorTech’s Shopify Connector PRO at $578.49 and Emipro’s Shopify Odoo Connector at $636.46 — and both advertise the capabilities the $199 module lacks, including webhook-driven order import, two-way product and variant sync, metafield mapping, and per-market pricing from Odoo pricelists. Those are vendor claims we have not tested, so demo them against your own catalogue, but the practical point stands: several limits people attribute to Odoo belong to one specific module.

Does the Odoo Shopify connector sync in real time?

The $199 connector does not — synchronisation runs on a scheduled job approximately every ten minutes, with no webhook-based sync. This is a limitation of that connector rather than of Shopify, whose API supports webhook-driven updates, and rather than of Odoo, since higher-priced connectors advertise webhook order import within seconds.

Can I sell configurable products on Shopify with Odoo behind it?

Not straightforwardly. Shopify caps products at three options regardless of the 2,048-variant limit, and its own documentation states that bundles cannot contain other bundles, so a configurator with several independent choices or a kit built from sub-kits has no native representation. Workarounds exist — a headless storefront, a quote-then-pay flow via Draft Orders, or a Shopify Function with network access calling your ERP at checkout. The first two cost you the standard cart or the theme ecosystem; the third preserves both but is gated to enterprise plans with custom apps and cannot be tested on a development store. If the configurator is central to how you sell, running the storefront in Odoo is usually the cleaner answer.

Can I push products from Odoo to Shopify?

Not with the $199 connector, where product data flows from Shopify into Odoo by manual fetch. Higher-priced connectors advertise two-way product sync, and Shopify’s API permits writing products from an external system — so this is a connector choice rather than a platform limitation.

Do Shopify variants import as Odoo variants?

Not with the $199 connector; this is a documented limitation of that module. Other Odoo Shopify connectors advertise variant sync in both directions. For variant-heavy catalogues — apparel, footwear, anything sold in a size-and-colour matrix — this single question should drive your connector choice, because remapping variants by hand is usually the largest line item in a build.

Should I keep Shopify as my storefront or move it to Odoo?

Keep Shopify when your storefront is a competitive asset — a conversion-optimised theme, an app stack you depend on. Consider moving when your complexity is operational rather than presentational: freight-rated shipping, trade pricing by account, B2B and retail from one catalogue — or when you sell configurable products, which Shopify structurally cannot model well.

How much does an Odoo build on Shopify cost?

In our experience $5,000 to $100,000 (USD), driven mostly by how much configuration your own team absorbs rather than by your size. Variant mapping, reversing the product flow, and catalogue migration are the items that move the number most on a Shopify-specific build — and the first two largely disappear if you choose a connector that handles them natively.

Working out whether this fits

The connector limitations are published, which means this is a decision you can make on evidence rather than on a vendor’s feature list. What it takes is someone looking at your catalogue, your channels, and where your complexity actually sits.

Talk to us about your Shopify and Odoo build →

About the author

Nguyen Tran is the founder of Ministers.io. He has worked on Odoo ERP implementations — five delivered directly and more than twenty advised on — across ecommerce, retail, manufacturing, and maintenance, repair and operations (MRO).

Connect on LinkedIn