MYOB EXO runs your business. We connect it to everything else.
We integrate MYOB EXO / Exonet with retailers, 3PLs, banks, eCommerce, and eInvoicing. Managed end to end, not handed back to your IT team.
MYOB EXO is one of the largest ERP clusters in our customer base. Not because operators haven’t moved on. Because EXO works for the way the business actually runs. Flow has been integrating EXO since 2006. We know the Narratives table. We know how DR_TRANS, DR_ACCS, and SALESORD behave. We know the custom fields on debtor and stock master that hold trading-partner branch codes and SKU mappings. The integration sits on top of that, not around it.
EXO connects to everything. It just doesn’t talk to everything natively.
EXO is a strong ANZ mid-market ERP. It wasn’t built to integrate with every retailer EDI spec, every 3PL portal, every eCommerce platform, every eInvoicing network on its own. That’s the gap. Most integration vendors don’t know EXO at the table level. They push you to a generic adapter or quietly recommend migrating off. Neither answer is what you needed.
EXO’s structure is specific
Custom fields on debtor accounts that hold trading-partner branch codes. Custom fields on stock master that hold partner SKU mappings. Narratives table for line-item instructions. DR_TRANS, DR_ACCS, SALESORD, STOCK_ITEMS. Naive mapping loses business logic that lives in those structures and has been built up over years.
Multiple integration patterns
Some integrations write directly to the EXO database. Some use ODBC. Some use newer APIs. The right pattern depends on the integration: performance, transaction volume, schema stability. Most platforms only offer one of these.
Trading partners expect more than EXO ships
EDIFACT, XML, fixed-length, REST/cXML, B2BE VAN, SFTP, SPS Commerce, Coupa, FremanWeb. EXO doesn’t carry any of this natively. The integration layer has to bridge every one of them.
“Just migrate” isn’t the answer
You’re on EXO for a reason. The reports work, the customisations work, the team knows it. Replacing the ERP to fix an integration gap is a $500K+ project to solve a $50K problem. Integration is the right layer to fix at.
We connect MYOB EXO to anything your business needs.
Flow runs the integration layer that sits between EXO and the outside world. EDI to retailers. APIs to 3PLs and eCommerce. eInvoicing networks. B2BE and other VANs. Whatever your business runs on, we connect EXO to it and manage the integration ongoing, so your team doesn’t carry the EDI knowledge or the platform expertise.
Retailer EDI
Bunnings, Mitre 10, PlaceMakers, Carters, ITM, The Warehouse, Briscoes, Harvey Norman, Foodstuffs, Woolworths, Coles. EDIFACT, XML, fixed-length, custom. We’ve integrated EXO with all of them.
3PL and logistics
Mainfreight FremanWeb consignment with SSCC labels. Carrier APIs. Warehouse handoff. We tie EXO sales orders through dispatch and back into ASN where the retailer expects it.
eCommerce and channel
eCommerce platforms including Shopify, BigCommerce, marketplaces, and B2B portals. Inbound orders into EXO, outbound stock and pricing back out. Multi-channel running off a single ERP source of truth.
eInvoicing (Peppol)
Peppol-compliant eInvoicing out of EXO for both ANZ networks. Inbound supplier invoices into EXO accounts payable.
VAN and gateway connections
B2BE, SPS Commerce, Coupa, EDIS. Whichever network your retailers or your group is on. EXO doesn’t need to know which VAN the document came through; we handle that layer.
EXO-specific handling
Custom fields on debtor and stock master for branch codes and SKU mappings. Narratives for line-item instructions. Direct DB write or ODBC where API isn’t an option. The integration respects what your EXO already does. It doesn’t try to flatten it.
EXO integration patterns we run.
Different partners need different patterns. We choose the right one per integration. Not one-size-fits-all.
| Pattern | When We Use It |
|---|---|
| Direct DB write | High-volume, low-latency writes to EXO. Stock updates, sales order creation, invoice extraction. Where ODBC and direct SQL give the right performance and the schema is stable. |
| ODBC connectivity | Read-side queries for customer master, stock master, transaction extraction. The standard Flow pattern for batch and near-real-time reads from EXO. |
| EXO Business REST API | Newer integrations where MYOB API endpoints are available and the volume profile suits. Cleaner contract, version-safe. |
| Custom fields and Narratives | Where the integration needs to write or read business data that lives in EXO custom fields or Narratives table. Common for retailer branch codes, panel cut instructions, line-item notes. |
| Staging-layer validation | Inbound EDI documents validated against the EXO customer master and product master before being created as sales orders. Errors caught before they hit production. |
| EDI document handling | EDIFACT, XML, fixed-length, custom. Translated to EXO sales orders, invoices, ASNs. Retailer-specific spec preserved. |
Built for ANZ mid-market businesses running EXO who’d rather extend it than replace it.
Flow’s MYOB EXO integration service is designed for NZ and Australian manufacturers, distributors, FMCG suppliers, and trade-retail operators who run EXO as their core ERP and need it connected to the outside world without rebuilding the back office.
You run MYOB EXO or Exonet
Current EXO Business, legacy Exonet, or somewhere mid-upgrade. We work with all of them.
You need integrations EXO doesn’t do natively
Retailer EDI, 3PL portals, eCommerce, eInvoicing, VAN connections. EXO is the system of record; we handle everything that talks to it.
Your IT team is small
One to three people stretched across ERP, security, infrastructure. Can’t absorb EDI specs, retailer onboarding, or VAN troubleshooting on top of everything else.
You want it run, not just set up
A managed integration partnership. We run the integration ongoing, handle the changes, watch the flows. Not a build-and-walk-away project.
We know MYOB EXO. We’ve been integrating it since 2006.
Flow started in New Zealand in 2005 building integration software for ANZ businesses. EXO integrations have been part of that work since 2006. We’re not a global platform with a generic EXO adapter. We’re an NZ-founded operator with two decades of EXO integration experience and a customer base where EXO is one of the largest ERP clusters.
Deep EXO expertise
Custom fields, Narratives, DR_TRANS, DR_ACCS, SALESORD, ODBC, REST. We’ve integrated EXO with dozens of trading partners across NZ and Australia. The tribal knowledge is in the platform, not in one person’s head.
We run it. You don’t have to.
We build it, operate it, and keep it running. You don’t need EDI or EXO integration expertise on your team.
NZ founded. ANZ operated.
Started in Auckland. AWS ANZ hosting keeps your data in-region. Support from people in your timezone.
Fewer customers. Deeper responsibility.
We stay accountable for outcomes, not just uptime. Post go-live is where most integration relationships fall apart. It’s where ours start to prove themselves.
Get your MYOB EXO integrated properly. Talk to us.
Tell us about your EXO setup and what you need it connected to. We’ll come back to you within 2 business days with an initial assessment.