Every year we watch a handful of Shopify brands under $100M sign an ERP contract they didn’t need. Six months later they’re on a call explaining to us why their “unified system” still can’t do something Shopify handled for free.
Here’s the blunt version: if you’re under $100M a year, an ERP is probably the wrong purchase. Shopify, extended properly, gets you further than most people expect.
The problem isn’t the idea. It’s the fit.
ERPs are built to be generalists. They handle finance, manufacturing, inventory, and commerce for companies that look nothing like a DTC apparel brand or a made-to-order furniture shop. That generalism is the whole pitch: connect everything, one source of truth, no more spreadsheets. It sounds right in the sales deck.
Then reality hits. The ERP turns out to have its own opinion about how orders, products, and inventory should work, and that opinion rarely matches how Shopify actually works. Every gap gets patched by hand. A year later those patches are the job. The tool that was supposed to remove complexity is now generating it.
We’ve watched this play out in a few recognizable ways.
One brand had an ERP specialist on a client call who couldn’t answer a basic question about tags versus metafields, something any Shopify developer answers without thinking.
Another spent months in onboarding and never went live. They gave up and moved to a tool built natively for Shopify instead.
A third spent 12 weeks waiting on their ERP vendor to work out how to split inventory between DTC and wholesale across multiple warehouses. Twelve weeks in, the vendor was still “investigating technical complexities,” with no timeline in sight. That’s not an edge case. That’s a config screen in a Shopify setup done right.
Why this keeps happening
Shopify wasn’t designed to be a spoke feeding data into an ERP hub. It’s opinionated about products, inventory, and orders in ways that make sense for commerce but confuse systems built around traditional accounting logic. Getting an ERP to speak Shopify’s language means building a translation layer, and translation layers break. They break on bundles. They break on multi-location inventory. They break the moment you do something Shopify-specific that the ERP’s data model never anticipated.
None of this is a knock on the merchants who sign these contracts. The pitch is convincing and the fear behind it is real. Nobody wants to be the ops team running a growing business off a spreadsheet with fifteen tabs. But reaching for an ERP to fix that is reaching for a hammer when what the job actually needed was picking the right tool: something closer to a precision instrument, with processes refined for exactly that kind of work.
What actually works
Most of what people buy an ERP to solve is solvable inside Shopify, with the right apps layered on top. Production tracking, supplier and inventory management, order routing: all of it can live close to the platform instead of fighting it. Focused tools that speak Shopify’s language natively beat one large system that has to be taught it after the fact.
There’s one real exception worth naming. Tools built Shopify native from the ground up, like Goodday for inventory and supplier management or Orderkraft for production, don’t hit the same translation problem, because there’s no translation happening. That’s a different category from bolting a general purpose ERP onto a Shopify store and hoping the API bridges the gap.
When an ERP actually earns its keep
ERPs earn their place somewhere. Past a certain size, the math changes. Multi-entity accounting, high volume wholesale and EDI, several sales channels that genuinely need one financial source of truth: that’s where an ERP starts paying for itself. Complex manufacturing is the exception already mentioned above, that’s a Shopify-native production platform problem, not really an ERP one. $100M isn’t a hard line, but it’s a reasonable one. Below it, the complexity an ERP adds usually outweighs the complexity it removes.
If you’re below that line and already fighting your ERP, it’s worth asking honestly whether the fight is necessary. Most of the time it isn’t. Most ERP fights are self inflicted. If you want a second opinion on yours, that’s the kind of thing we do.