Shopify ERP Integration: The Operator’s Guide for $5M+ DTC Brands

For most operators, the ERP arrives after Shopify. Inventory has been living in Shopify, finance has been living in QuickBooks (or a spreadsheet), and the team has been reconciling weekly.

Then a milestone — a 3PL onboarding, a B2B channel launch, a fundraise — surfaces the fact that the data spread across systems no longer agrees. Orders are missed. Inventory shows stock that shipped. Revenue gets restated.

The integration project that follows is rarely about features; it’s about restoring a single source of truth that the operations and finance teams can both work from.

The failure modes are repeatable. Inventory diverges because Shopify’s allocation logic and the ERP’s reservation logic were never reconciled. Refunds and exchanges land in different reconciliation buckets on the two sides.

Sales tax flows correctly until a new state nexus opens and the SKU master breaks. Multi-currency works until Markets adds a second region.

None of these are surprises to specialists who have shipped this work — they’re scoping conversations that should happen before the first integration flow is built, not after the third escalation.

A Shopify ↔ ERP integration is not a single connection — it is five separate flows, each with its own failure profile.

Get all five right and the integration disappears into the background; get any one wrong and your team will blame the integration for problems that are actually scoping gaps. We size every project against this list.

Orders: Shopify → ERP, near-real-time. Includes refunds, partial refunds, gift cards, and B2B net-terms orders if applicable. Most integration mistakes hide here.

Inventory: ERP → Shopify, on every change. The hard cases are multi-location, safety stock, and Shopify Markets routing. Wrong inventory shows up as oversells.

Customers: Bidirectional. Shopify is usually the source for DTC; ERP is usually the source for B2B. Wrong customer mapping shows up as duplicate accounts and broken net-terms invoicing.

Items/SKUs: ERP → Shopify, on every change. Bundles, kits, and configurable products are where mappings break. Get the SKU master design wrong and every downstream flow inherits the issue.

Fulfillments: 3PL/WMS → ERP, with optional pass-through to Shopify. Tracking, partial shipments, and returns reconciliation all live here.

Not every Shopify brand needs an ERP, and not every ERP-using brand needs a real integration.

The signal that you do: month-end close takes longer than five business days, inventory disagreements between Shopify and your finance system require a person to chase, or you’ve had to apologize to a customer because two systems disagreed on whether their order shipped.

If none of those are true today, the integration project can usually wait.

The signal that you can’t wait: a 3PL onboarding, a Markets/multi-region launch, a B2B channel turning on, a finance team that has to restate revenue more than once a year, or a fundraise where due diligence will reveal the spreadsheet-glued reconciliation.

Each of those changes the math because the cost of *not* integrating shows up as a discrete event with a deadline.

There are four common integration patterns at this scale. The right one depends on your ERP, your operational complexity, and how much in-house engineering you want to own.

iPaaS with prebuilt connectors (Celigo, Boomi, Workato): the dominant pattern for NetSuite, Business Central, and Acumatica. Pre-built flows cover 80%+ of the standard catalog.

Trade-off: you trust the connector’s assumptions about how SKUs and orders map, and customization happens inside the iPaaS rather than in your stack.

ERP-vendor native connector (NetSuite SuiteApps, Acumatica Commerce Edition, BC marketplace apps): tighter coupling, often cheaper to license, but customization is constrained to what the vendor exposes. Best when the vendor’s connector matches your edge cases out of the box.

Specialist app on the Shopify App Store (Connex, Patchworks, DCKAP, FarApp): purpose-built for a specific ERP pairing.

Often the right choice at the small end of the scale where iPaaS is overkill, or at the large end where deep ERP-specific functionality matters more than middleware flexibility.

Custom build (Node/Ruby/Python on top of Shopify API + ERP API): the right call only when standard connectors fail your edge cases AND you have in-house engineering capacity to maintain the integration for years.

Usually the wrong answer at $5M+; sometimes the right answer at $25M+ with B2B + DTC + marketplace complexity.

Implementation cost varies more by scope than by ERP, but the ERP sets the price floor.

Realistic 2026 ranges across the engagements we ship: NetSuite $30K–$200K (Celigo is the dominant iPaaS); Acumatica $20K–$120K (often via Kensium A+ Commerce or Celigo); Business Central $25K–$150K (Suite Engine, Dynamicweb, or Sana common); SAP B1/S4 $50K–$300K (more variance because partner quality dominates); QuickBooks $5K–$45K (light-touch ERP, lighter integration); Xero $5K–$30K; Brightpearl $15K–$60K (often includes its own warehouse + retail layer).

License and platform fees sit on top: $5K–$30K/year for iPaaS, $5K–$60K/year for ERP-native connectors.

The honest expectation: total first-year cost is 1.4–1.8× the implementation quote once you include iPaaS subscription, internal operator hours, and the integration partner’s post-go-live support.

The structured-shortlist approach beats freeform vendor calls every time.

Pick three integration approaches before talking to vendors, scope your actual problem on paper, and score each option against the five data flows above plus implementation timeline, license cost, partner availability, and exit cost.

Reference-check at least two operators at comparable scale per option; vendor-supplied references skew toward enthusiasts.

The whole process should take two to three weeks, not two to three months — if it’s taking longer, you don’t have a shortlist problem, you have a scoping problem.