The store already takes orders. Acumatica already holds customers, stock, and price. The gap is SalesOrder, StockItem, and who owns warehouse quantity. We will tell you what the contract-based API will take, and what still lives in the ERP.
Australian ecommerce team. We look at the store and the Acumatica tenant before anyone talks about a connector.
01
What you have
02
What is safe to keep
03
Connect or leave
The store still takes orders. The ERP still holds account pricing. That is why the two have been left talking through a morning export, or through a project that stalled when someone said “MYOB” and meant the company-file line.
MYOB Acumatica is cloud ERP for mid-sized AU/NZ businesses: financials, inventory and distribution, CRM, payroll, projects. MYOB Advanced Business was renamed MYOB Acumatica. It is the ANZ localisation of Acumatica; MYOB is the sole exclusive ANZ provider. Native GST, BAS, STP in Australia and IRD in New Zealand. Industry editions include wholesale, distribution, and manufacturing.
MYOB cites the iStart ERP Buyer’s Guide 2025–26 as “#1 ERP platform in Australia and New Zealand” based on the upper range of each vendor’s declared installed base. That is iStart and vendor-declared, not an independent count. We will not repeat the rank as if we measured it.
You might recognise one of these:
You do not need a new storefront, or a “rip out the ERP” pitch. You need a clear read on the Acumatica company you already have.
Acumatica has a documented contract-based REST API. The stall is rarely “there is no API”. It is login, endpoint version, and the fact that AccountRight knowledge does not transfer.
This is the contract-based REST API (JSON). Login is POST /entity/auth/login, logout /entity/auth/logout. The default endpoint pattern is /entity/Default/{version}/ — docs exemplify 6.00.001. There is also OData on generic inquiries and DACs on the underlying Acumatica platform. None of that is api.myob.com/accountright/. Reusing an AccountRight key, cftoken, or Sale/Invoice path against Acumatica is a failed project, not a configuration tweak.
Documented work that looks like a store job: Customer, StockItem, SalesOrder (including Details / InventoryID / Quantity), SalesInvoice (for example ReleaseSalesInvoice), InventorySummaryInquiry, Shipment (ConfirmShipment). The usual direction is ERP → store for customers, stock items, warehouse qty and price; store → ERP as a SalesOrder with lines; invoice release and shipment confirm later. B2B account pricing often lives in the ERP. If the store invents a price, Acumatica will not agree at invoice.
InventorySummaryInquiry is there because warehouse quantity is an ERP question. A storefront cache that ignores location, allocation, or kit components will oversell. Pulling StockItem master and pulling available qty are different calls.
The documented pattern is login, work, logout. Long-running store jobs need a designed auth life-cycle, not a saved cookie from someone’s browser session against the tenant. Partners and customisations on the tenant also change which contract endpoint you should call.
None of that makes the catalogue or the ERP worthless. It does mean “use the MYOB connector we used on AccountRight” is the wrong first move.
We start with the tenant and the store, not with a rename announcement.
Store platform, Acumatica (or still-labelled Advanced) tenant, endpoint version, whether B2B pricing lives in the ERP, warehouses, and any existing middleware. We will tell you whether the first write is a SalesOrder or whether the store should only read stock.
There are three honest outcomes. We recommend one, not all three.
Customers and StockItems in, then SalesOrder out, then invoice release and shipment confirm if those are actually in scope. A non-production tenant beats a Friday ConfirmShipment.
Source, the endpoint version, and a short record of which contract entity creates which document.
We will not tell you NESS (Dynamics NAV) proves Acumatica delivery. We will not tell you AccountRight and Acumatica share an API. If you already have an Acumatica implementation partner who owns the commerce module, they may be the better first call. If you want an honest fork in the road on the store side, talk to us.
A store URL and which Acumatica tenant is enough to start.
The first call is 30 minutes. You leave with a recommendation you can take to a manager, not an ERP estimate pulled from thin air.
We have not published a MYOB Acumatica or MYOB Advanced ecommerce case. NESS Corporation is a published B2B nopCommerce store integrated with Microsoft Dynamics NAV 2018. That is NAV, not Acumatica, and not proof we have delivered this ERP.
CoSource is a Sydney software firm and a nopCommerce Gold Partner. Services include CRM & ERP integration on nopCommerce, AbleCommerce, and Shopify. That is a capability, not an Acumatica case study. An Acumatica tenant still starts with its own assessment.
Thirty minutes. Bring a store URL and the Acumatica (or Advanced) tenant. We will tell you whether to connect, fix the connector, or leave orders inside the ERP.
Book a free 30-minute discovery call