Most ANZ brands who ask us for an ERP integration do not have an ERP.

They have Xero or MYOB doing the ledger, an inventory system doing stock, a 3PL with its own portal, Shopify doing the storefront, and a spreadsheet somebody rebuilds every Monday to make the four agree. Collectively everyone calls that "the ERP", and the request that lands with us is "can you connect it".

Sometimes the answer is yes and it takes six weeks. Sometimes the honest answer is that the thing you are trying to connect is not the thing causing the problem.

Here is how we work out which.

What counts as an ERP in the ANZ mid-market?

Worth being precise, because the word covers three quite different tiers and the integration work is not comparable across them.

Ledger plus inventory. Xero or MYOB for accounts, with an inventory system on top. In this part of the world that usually means Cin7 Core, which was DEAR Systems before the rebrand, or Unleashed. Both started in New Zealand. Neither is a full ERP and neither pretends to be. For a brand doing NZ$5M to NZ$20M through Shopify and a bit of wholesale, this stack is often entirely adequate.

Mid-market operations platforms. Cin7 Omni, which is the original Cin7 product and a different system from Cin7 Core, Brightpearl by Sage, or MYOB Acumatica, which was MYOB Advanced until the 2024 rename and is the ANZ-localised version of Acumatica. More depth, EDI and 3PL handling, longer implementations.

Full ERP. NetSuite, Microsoft Dynamics 365 Business Central, SAP Business One. Finance, inventory, manufacturing and reporting in one platform, implemented over months rather than weeks, usually with a specialist ERP partner alongside the commerce team.

If someone has quoted you for "Cin7" without telling you whether they mean Core or Omni, that is worth clarifying before anything else. They are priced and scoped very differently.

The question that decides the whole project

Not which system. Who owns the truth.

For every object that exists in two places, one system has to be the source of record and the other has to accept what it is told. Products, inventory, customers, orders, pricing, returns. Six decisions. Make them explicitly, at the start, in writing.

Almost every failed integration we are asked to rescue failed here rather than in the code. Two systems both believing they own inventory will fight forever, and the fight shows up as oversells on a Saturday, not as an error in a log.

Our usual starting position for a Shopify brand:

  • Products and pricing – the ERP owns the data, Shopify owns the presentation.
  • Inventory – the ERP owns it, always. One number, pushed out.
  • Orders – Shopify creates them, the ERP fulfils and settles them.
  • Customers – messier, and it depends on whether retail is in the picture.

Defensible defaults, not rules. The point is that somebody decides deliberately rather than letting the connector decide by accident.

What actually breaks

The demo always works. These are the things that surface in month three.

Timing. Most connectors sync inventory on a schedule. If yours runs every fifteen minutes and you sell a one-off piece, you will oversell. Decide what the acceptable window is per product type, not globally.

Bundles and kits. Shopify and your ERP rarely agree on what a bundle is. This is the single most common source of stock drift we see.

Returns and credits. Order sync gets all the attention. Credit notes, refunds and exchanges get built last and then quietly do not reconcile.

Tax. GST-inclusive pricing in New Zealand and Australia, GST-free exports, and the difference between how Shopify and an ERP each calculate it. Get your accountant in the room during scoping, not after the first return.

Multi-currency. NZD and AUD through Shopify Markets, settled back into a ledger that may be running a single base currency. Entirely solvable, frequently forgotten.

Backorders and pre-orders. Shopify's model and most ERP models are different enough that this usually needs a deliberate decision rather than a default.

How to connect it, in order of what to try first

Start simple and escalate only when the business logic demands it.

1. The vendor's own connector. Cin7, Unleashed and most mid-market platforms ship a Shopify integration. If it covers your flows, use it. It is maintained by the vendor, it is cheap, and nobody has to support it at 2am.

2. An integration platform. When you need conditional logic, field mapping the native connector cannot do, or several systems in the same flow, an iPaaS like Celigo earns its licence. We work with Celigo for exactly this. You get a maintained, visible, debuggable layer rather than a black box.

3. Custom middleware. Last, not first, and only where the logic is genuinely specific to your business. Custom means you own it forever. Sometimes that is correct. It should be a decision, not a default because the first two were not properly evaluated.

Shopify Flow handles a surprising amount of the simple conditional work before you reach step two, and costs nothing extra.

Should you integrate before or after replatforming?

If you are moving to Shopify and connecting an ERP, do the platform move first and the integration second, with a deliberate gap between them.

Running both at once means that when something goes wrong, and it will, you cannot tell which project caused it. The gap is not wasted time. It is the thing that makes the second project diagnosable.

The exception is when the ERP is the reason for the replatform, as happens with brands whose current platform cannot support the integration at all. Then the sequencing gets decided for you, and the scoping needs to be unusually careful.

What we do not do

Worth saying plainly, because it saves everyone a discovery call.

We build native Shopify, and that includes native Shopify B2B. Where we are not the right call is complex B2B beyond what native Shopify supports: punchout catalogues, EDI, custom quoting engines, and ERP-driven pricing logic that native Shopify B2B cannot express. Some of that can be solved with integration. Some of it genuinely needs a different kind of platform and a different kind of partner, and you are better served by someone who will tell you that early.

We also do not implement the ERP itself. We connect it. On full ERP projects we work alongside the ERP partner rather than instead of them.

Frequently asked questions

What is the difference between Cin7 Core and Cin7 Omni?

They are two different products under one brand. Cin7 Core was DEAR Systems before the rebrand and targets SMB to lower mid-market. Cin7 Omni is the original Cin7 product, aimed at mid-market omnichannel brands, with native EDI, POS and 3PL handling. They differ substantially in price and implementation length, so confirm which one a quote refers to.

Do you need an ERP to sell on Shopify Plus?

No. Plenty of brands run NZ$20M-plus through Shopify Plus on an inventory system and a good ledger. An ERP becomes worth the overhead when manufacturing, complex purchasing or multi-entity finance enter the picture, not at a particular revenue number.

How long does an ERP integration to Shopify take?

With a vendor connector and clean data, a few weeks. With an iPaaS layer and moderate custom logic, six to twelve weeks. A full ERP implementation running in parallel is a different kind of programme and is measured in months. Data quality drives the timeline far more than the technology does.

What is an iPaaS?

An integration platform as a service: a hosted middleware layer that moves and transforms data between systems without custom code. Celigo is the one we most often use for Shopify and ERP work.

Can Shopify connect to NetSuite?

Yes, via connectors and integration platforms, and it is a well-established pattern. The work is in deciding ownership of each data object and handling the exceptions, not in the connection itself.

Where to start

Before you scope an integration, write down the six ownership decisions above and see how many your team disagrees on. That argument is the project. Everything after it is implementation.

And if the honest answer is that your inventory system is fine and your problem is that nobody owns the data, say so out loud before anyone writes a statement of work.

We are a Shopify Plus Partner and Klaviyo Master Gold agency in Takapuna, Auckland, running unified commerce projects for mid-market brands across New Zealand and Australia, including ERP and systems integration alongside commerce builds. If you want a straight read on what your stack actually needs, get in touch. We will tell you if the answer is that you do not need us.