MYOB Acumatica eCommerce Connector: Shopify and BigCommerce Without the Rekeying

When the Australian Bureau of Statistics published the final edition of its Retail Trade series, online retailing came in at $4.7 billion for the month of June 2025 alone, and the online share of total retail had climbed past 11 per cent the year before. Australians buy online as a habit now, which means wholesalers and retailers sell online whether their systems were built for it or not.

The gap usually shows up between the store and the books. Orders arrive in Shopify, someone rekeys them into the ERP, stock counts drift apart, and month end becomes archaeology. MYOB’s 2025 ERP Trends report found 45 per cent of Australian businesses saying disconnected systems limit their growth, and a storefront bolted onto an unconnected ERP is exactly that problem.

What the MYOB Acumatica eCommerce connector is

MYOB shipped native Shopify and BigCommerce connectors for MYOB Acumatica, built on the commerce framework the platform inherits from global Acumatica. Native matters here. The connector is part of MYOB Acumatica itself, configured on screens inside the ERP, not a third party tool holding the two systems together from outside.

The flow runs both ways. Orders come in from the storefront with their customer and payment details attached. Product details, price changes and inventory updates go out from the ERP to the store. You trigger a sync manually or put it on a schedule, and the ERP stays the single place where products and prices are actually maintained.

What syncs between your store and the ERP

MYOB’s consultant documentation lists the entities the BigCommerce connector carries: customers and customer locations, stock items and non-stock items, template items for products with variants, product images, and sales orders. The Shopify connector covers the same storefront ground.

In practice that means a new customer who checks out online exists in your ERP moments after the sync runs, their order sits in a queue as a proper sales order, and the fulfilment, invoicing and GST treatment all happen in MYOB Acumatica the way they would for any phone or email order.

The setup decisions that matter

Connecting the store is an afternoon. The decisions around it are what you live with, and MYOB’s own setup guide walks consultants through them:

• A customer class for online buyers. Every imported customer lands somewhere. A dedicated class keeps terms, tax settings and receivables accounts right by default.
• A guest checkout customer. Shoppers who do not create an account need a home in the ERP, and guest orders need numbering that will not collide with anything else.
• Dedicated order types. Separate types for online sales and online returns keep e-commerce volume visible and reportable instead of blended into the rest of the order book.
• Payment method mapping. Storefront payments have to land against the right cash account, or reconciliation gets worse rather than better.

MYOB is blunt about testing all of this in a sandbox tenant before it goes near live data. We agree, and that is the discipline on every connector project we run.

“The connector setup is the easy part. The decisions that come back to bite are the boring ones: which customer class online buyers land in, how guest orders get numbered, and whose job it is to read the sync log on Monday morning. Get those right and the integration disappears into the background, which is exactly what you want from it.”

Josh Craig, Director, Auboros

Sync schedules, and the drift between them

The connector syncs on demand or on a schedule, and that schedule is a design decision. Whatever window you choose is a window where the store and the ERP disagree: stock sold in the shop has not left the website yet, and a price updated in the ERP has not reached the storefront. On a quiet Tuesday that is trivial. During a promotion with thin stock it is how you oversell.

Run tighter schedules through busy periods, decide who checks failed syncs each morning, and treat the sync log as an operational report rather than plumbing. This is also where an AI channel sync agent earns a look for multi-channel sellers: it reads the drift between systems and drafts the fixes, with a person approving each one.

When the native connector is enough, and when it is not

If you sell through Shopify or BigCommerce, the native connector should be the default starting point. If your store runs on WooCommerce, Magento or a marketplace, there is no native path, and you are into certified integrations from the MYOB app marketplace or custom API work, which is a bigger scoping conversation. Complex B2B pricing can also stretch past what a standard sync handles well, and it is better to find that out on a whiteboard than mid-implementation.

Fairness note: if e-commerce is the heart of the business and you are still choosing an ERP, it is worth seeing how Odoo handles Shopify and WooCommerce, since it takes a different approach with its own connector set. And if you are a wholesale distributor weighing up MYOB Acumatica itself, the FastStart Wholesale Distribution program is the fixed scope way in.

Selling online next to MYOB Acumatica, or planning to?

We are a Brisbane based MYOB Acumatica partner working with wholesalers and retailers across Queensland and beyond. If you want the store and the ERP reading from the same page, book a free consultation and we will map what the connector covers for your setup before anyone commits to anything.