When EDI only arrives through an adaptor: SYSPRO, MYOB Acumatica, Cin7 and the others
A large share of the ERPs run by Australian suppliers have no EDI translator of their own. SYSPRO, MYOB Acumatica, Cin7 Core, Unleashed, Jiwa, Attache, MYOB Exo, Sage 50 and Katana all get EDI the same way: a partner adaptor reads the retailer's documents and pushes them through whatever door the ERP offers. That is not a criticism. It is how most mid-market EDI works everywhere. But the adaptor's choice of door decides how upgrades behave, what the licence counts, what happens when a document fails, and how hard it is to leave. Those are the things to ask about before signing.
SYSPRO: three doors, and a clear preference from the vendor
SYSPRO is the best-documented case, because the vendor publishes its own rules. What SYSPRO calls native EDI is a set of fixed-format import and export programs: a sales order import that reads an EDI-standard file, an invoice export that writes one file per customer by sender code, and a back-order release import. Alongside them sit the Document Flow Manager, which auto-imports XML, and the business objects, a programming interface that any partner product can call.
The import program's validation rules are worth reading before any adaptor is chosen, because the adaptor cannot change them. The customer's sender code must match the file. The customer's part number is resolved through the customer stock-code cross-reference first, then the stock-code field, then the supplier catalogue number, and otherwise the line is treated as a non-stocked item. Lines for stock on hold or past its supersession date are not imported. There are error codes for a duplicate purchase order, an invalid unit of measure and an invalid warehouse. The order quantity is placed into back order regardless of stock on hand, which means the release step is part of the EDI process, not something that happens later. And the import only runs when every line is valid, so one bad line holds the whole order.
SYSPRO's 2023 connection guidance is unusually direct. Where possible, connect through the load-balanced business-object service and use business objects to query and post, because they stay forward compatible when the underlying tables change. Connecting to the database directly with SQL drivers is not advised, and often affects a customer's ability to upgrade, because version-specific tables and columns tie the solution to a release. Integrations that are not accredited by SYSPRO consume operator licences, and it is the customer's responsibility to have enough. The 2018 upgrade guide says the same from the other side: verify every third-party product before upgrading, expect the document-flow manager to have been re-architected, and re-test anything built in a version-dependent way.
The adaptors on the market attach through each of the three doors. One long-established translator runs as a menu option inside SYSPRO and emails errors to whoever is configured to receive them, which its partner recommends be the EDI team rather than sales. One newer connector goes through the web API over business objects, paces its posts to stay inside rate limits, quarantines unmapped products, routes unmapped customers to a house account, holds orders until credit clears, and holds the ASN until shipped quantities reconcile with pick and pack scans. Another lets the site choose the door per installation. The Australian case I found is instructive in the other direction. A Brisbane irrigation distributor was required by a large plumbing chain to integrate with its EDI system in 2009, and a partner built an application that polled the chain's system, converted orders to XML and auto-imported them through the document-flow manager. The distributor's finance lead praised how easy the database tables were to understand. That was a SQL-level build of exactly the kind the 2023 guidance now warns against. It worked; it would also have had to be revisited at every upgrade since.
MYOB Acumatica: no native EDI, and the details that bite
On the Acumatica community, which serves the same product sold here as MYOB Acumatica, the accepted answer is that native Acumatica does not have EDI functionality and a marketplace add-on is the route. The user threads are where the lessons are. One sellable unit shipped in two boxes reached the retailer's ASN as quantity two, and the only fix the network offered was to key the ASN in its portal; the community's answer was to model the boxes as stocked components of a non-stock kit and let automatic packaging fill the shipment's package tab, so the adaptor could build the proper hierarchy. A connector on one release logged itself out every thirty days, and it took ten months before the provider explained that the integration token expired. Every status line the network sends back counts as a transaction against the licence tier, so a document is metered going out and again when its status is confirmed. Change orders from a retailer are not applied automatically; one user built a comparison report for customer service to key the changes by hand, which is a reasonable design, not a workaround.
Cin7, Unleashed, Katana and the inventory apps
Cin7 is two products. The larger edition has built-in retailer connections, including the Australian majors; the smaller one must use partner integrations. A trade article quotes a buyer who found out six months after purchase that the edition they had bought could not trade with a large American retailer, and migrated. A consultant who works with both estimates middleware for the smaller edition and for Unleashed at a monthly fee plus per-document charges and says EDI mapping is one of the two line items that blow up statements of work. Unleashed attaches through a managed service on a per-connection fee or through an API key, and the API route warns that changes made after approval do not sync back. Katana only gained a retailer-network integration in 2025, and an independent review says anyone needing retail EDI will hit walls.
Jiwa, Attache, MYOB Exo and Sage 50
The Australian accounting-grade systems are pre-mapped by the local networks against the major retailers, which makes onboarding faster, and nobody has written a first-hand account of any of them, which tells me the pain is at the network rather than the ERP. Sage 50's integrators are frank that it cannot produce an order response or hold packing information, so the connector synthesises both. That is fine until a retailer asks for a pack level the system does not have.
The questions to ask any adaptor
Which door. Business objects or API, document import, or the database. Only the first survives upgrades without a project.
Which licence. Does the integration consume user or transaction licences, and is the provider accredited by the ERP vendor.
Which failures are visible. Where does a rejected line go, who is emailed, and can customer service see it without IT.
Which hierarchy. Can the adaptor build pallet, carton and item from what the ERP holds, or does it need a kit, a package tab or a portal.
Which exit. If you leave the network, which maps and labels have to be rebuilt per retailer. Those generated inside the network's platform usually do.