Integrations

Shopify ERP integration in Australia: what Business Central, NetSuite, and Odoo buyers should test for B2B in 2026

A practical Australian guide to Shopify ERP integration for B2B and wholesale teams comparing how Business Central, NetSuite, and Odoo handle connector depth, pricing sync, inventory ownership, and rollout risk in 2026.

This is a timely ERP topic in Australia because Shopify materially changed the B2B buying conversation on 2 April 2026. Shopify announced that foundational B2B features are rolling out to Basic, Grow, and Advanced plans at no extra cost, which means more wholesale and trade sellers can now run B2B and DTC in one storefront without first moving to Shopify Plus.

For most Australian teams, the real decision is not "can these systems connect?" It is whether the integration model fits the operating complexity of B2B catalog pricing, customer-specific terms, stock ownership, finance reconciliation, and support accountability after go-live.

Why this topic matters more now

• Shopify now positions B2B as a mainstream capability across all plans rather than a niche Plus-only conversation, so more SMB and lower-mid-market buyers can justify testing Shopify-led commerce in an ERP shortlist right now.
• Shopify's current B2B help also points users toward catalogs, pricing, checkout, orders, reporting, automations, and integrations to ERPs and external systems. That makes ERP integration part of the core design, not an optional afterthought.
• For Australian distributors, importers, wholesalers, and hybrid DTC+B2B brands, that shifts the pressure onto ERP design choices: who owns product truth, which system owns customer-specific pricing, where invoices live, and how warehouse and payment exceptions are handled.

Business Central: strongest native product story, but upgrade discipline matters

• Microsoft's current Shopify Connector documentation says the connector is available only for Business Central online, is preinstalled for new environments, and requires both a Business Central licence and a Shopify licence.
• Microsoft also documents broad native capability: multiple Shopify shops, bidirectional sync of products, customers, companies, orders, inventory, fulfilments, and posted sales invoices, plus B2B company mapping and Shopify Payments payout information.
• For Australian buyers, that is the cleanest first-party product story in this comparison. If Business Central is already shortlisted, the Shopify path is easier to validate through standard Microsoft documentation than the alternatives reviewed here.
• The caution point is release discipline. Microsoft says Shopify API versions change every quarter and that if a Business Central environment falls behind the required major release, Shopify API calls can be blocked. In practice, that means the integration operating model needs owner accountability for major updates, not just initial setup.
• Another practical limit matters for B2B teams: Microsoft's FAQ still lists draft orders as unsupported. If your wholesale process depends heavily on negotiated draft-order flow in Shopify, test that gap directly before assuming the connector fits your commercial model cleanly.

NetSuite: richer B2B order and catalog flow, but connector setup is more commercial and procedural

• Oracle's current help says you must add the Shopify connector through your NetSuite account manager, then authorize it in NetSuite Connector before mapping fields and testing data flow. That is a real product path, but it is less "already there" than Business Central's preinstalled connector model.
• Oracle also documents a substantive Shopify B2B capability set: B2B order synchronisation, company sync, payout sync, order sync, reverse order edits, fulfilment sync, product sync, refunds and adjustments sync, inventory sync, reverse payment sync, and catalog and price-list sync.
• For buyers running wholesale terms, staged fulfilment, and customer-specific pricing, Oracle's catalog and payment sync story is commercially important. The docs also describe invoice posting, customer deposits, and payment handling aligned to B2B workflows rather than only DTC checkout.
• The trade-off is implementation shape. Oracle documents prerequisites such as enabling the Shopify B2B allotment, installing and authorizing the NetSuite Connector SuiteApp, configuring the connector, and creating custom records for catalog sync. That is not a reason to reject NetSuite, but it does mean partner capability and configuration discipline matter more than a simple "native integration" label suggests.
• NetSuite looks strongest here when the buyer genuinely needs a deeper B2B order-to-cash model and is willing to govern a more structured connector setup.

Odoo: viable, but the current source set points to app-marketplace connector dependency

• In the official sources reviewed for this article, Odoo does not present a comparable first-party Shopify core connector page. The clearest Odoo-owned evidence is its Apps marketplace, where Shopify connectivity is offered through third-party connector modules.
• That matters because the integration question becomes less about "does Odoo support Shopify at all?" and more about which connector vendor, support model, and upgrade path the buyer is actually buying into.
• One current Odoo Apps listing for Odoo 18 and 19 positions Shopify sync around orders, products, customers, inventory, fulfillment tracking, queue jobs, field mapping, and inventory reports inside Odoo. That is enough to show a workable route exists, but it is a different risk profile from a first-party Microsoft or Oracle connector path.
• For Australian teams, Odoo can still be attractive when flexibility and lower software entry cost matter, but the buying team should be stricter about support ownership, webhook reliability, connector version compatibility, and what happens when the Shopify or Odoo release cadence changes.
• The safest interpretation is not that Odoo is weak. It is that Odoo's Shopify answer is partner-and-app dependent in a way buyers should price and govern explicitly.

The buyer questions that matter most in B2B and wholesale

• 1. Which system owns customer-specific catalog pricing and payment terms once Shopify B2B is live?
• 2. Which system owns available-to-sell inventory by location, and how quickly do stock changes flow back to Shopify?
• 3. Can the integration handle B2B realities such as company accounts, partial fulfilment, deposits, Net terms, refund handling, and payout reconciliation without manual side processes?
• 4. What breaks if Shopify changes its API or if the ERP environment falls behind major upgrades?
• 5. If something fails at 4:30 p.m. on a weekday, who owns support first: the ERP partner, the connector vendor, the ecommerce agency, or the internal operations team?

Where shortlists usually go wrong

• Teams confuse "integration exists" with "integration fits our operating model".
• Commerce leaders optimise for storefront speed while finance and warehouse teams discover later that pricing, stock, refund, or payout controls are underdesigned.
• Buyers test one happy-path order but skip catalogs, wholesale terms, partial shipments, draft-order workarounds, and exception handling.
• Odoo and NetSuite buyers sometimes underestimate connector governance because the project conversation starts with ecommerce momentum rather than support ownership and release management.
• Business Central buyers can go wrong in the opposite direction by assuming the first-party connector removes the need for an update cadence and process design discipline.

What to do before approving a project

• Run one real B2B scenario end to end: customer-specific catalog, negotiated pricing, one payment-term variation, one partial fulfilment, one stock exception, and one refund or adjustment.
• Force the partner or vendor to show where catalog rules, customer master ownership, inventory truth, invoice creation, and payout reconciliation actually live.
• Separate software capability from support model. Document who patches the connector, who watches sync failures, who approves mapping changes, and who owns upgrade rehearsals.
• If Shopify is being introduced because B2B is now available on the current Shopify plan, confirm that the ERP and connector economics still work once transaction volume, wholesale customer count, and warehouse complexity rise.
• Use this topic alongside a platform pricing guide and a warehouse or integration guide before final software selection.

What Australian buyers should conclude now

• Shopify becoming more B2B-accessible in April 2026 makes ERP integration a sharper shortlist question for Australian growing businesses now, not later.
• Business Central currently offers the clearest first-party Shopify path, NetSuite offers a strong but more procedurally managed B2B connector model, and Odoo remains viable through its app ecosystem but with more connector-governance dependency.
• The best choice depends less on headline feature count and more on how much B2B pricing complexity, payment-term complexity, inventory pressure, and support discipline the business is genuinely ready to carry.

Sources used

• Shopify newsroom announcement dated 2 April 2026 on B2B features rolling out across Basic, Grow, and Advanced plans.
• Shopify Help Center B2B documentation for current B2B areas including catalogs, pricing, checkout, orders, reporting, automations, and ERP integrations.
• Microsoft Learn Shopify Connector overview and Shopify Connector technical FAQ for Business Central capability, support model, online-only scope, quarterly Shopify API cadence, and unsupported draft orders.
• Oracle NetSuite Help for integrating Shopify B2B with NetSuite and the Shopify B2B sync documentation covering catalog, pricing, payment, fulfillment, refund, and inventory flows.
• Odoo Apps marketplace listing for a current Shopify connector module showing the app-led integration model and operational scope reviewed for this article.