WooCommerce MYOB Integration.

Written by Nicholas Duell, founder of Duelling Pixels — 15+ years building WooCommerce stores and the integrations that run them. Last updated: June 2026.

The short version

MYOB runs the books for a huge share of established Australian businesses — often for a decade or more before the WooCommerce store ever existed. Then the store arrives, orders pile up, and someone inherits the job of re-typing them into MYOB. By the time stores call us, that job is usually costing a day a week, and the “temporary” spreadsheet has been temporary for two years.

The honest context: MYOB’s connector ecosystem for WooCommerce is thinner than Xero’s. There are fewer plugins, they assume more, and which MYOB product you run changes what’s possible. That’s not a reason to give up the books system your accountant knows — it’s a reason to scope the integration before buying anything. That scoping is what we do, and when no connector fits, we build against the MYOB API directly.

First question: which MYOB are you on?

MYOB Business (formerly Essentials)

Fully cloud-based, with a modern API — the easier integration target. Most off-the-shelf connectors support it well, and a properly configured sync can push orders, payments, and contacts through with little drama. If you’re on MYOB Business with a straightforward catalogue, a connector plus careful configuration is usually the right answer.

MYOB AccountRight

The desktop-heritage product with cloud-hosted company files. It’s deeper accounting software — inventory, jobs, categories — but integration depends on your company file being online and your version being current, and connector support is patchier. AccountRight stores are where we most often end up building custom: the business logic that justified AccountRight rarely fits a generic connector’s assumptions.

Everything below — what syncs, what breaks, what it costs — depends on this answer first. It’s the first thing we ask in a scoping call.

What a good WooCommerce–MYOB sync handles

Orders into invoices — with the right timing

Each WooCommerce order becomes an MYOB invoice with line items, freight, and discounts intact. The design decisions: create on order or on payment, how statuses map, and what happens to cancellations. These defaults are where cheap setups go wrong quietly.

Payments and gateway fees

Stripe, PayPal, and Afterpay deposit your takings minus fees, so payouts never match invoice totals — and the bank feed never reconciles. The fix is structural: payments to a clearing account, fees posted as expenses, deposits matching to the cent. If your bookkeeper dreads the bank feed, start here.

GST mapped for BAS

WooCommerce tax classes mapped to the right MYOB tax codes — GST, GST-free, and mixed carts — with the per-line rounding differences between the two systems handled. The goal is a BAS you review, not one you reconstruct.

Contacts without the sludge

Guest checkouts will happily create a new MYOB card for every order unless matching rules stop them. We match on email with sensible fallbacks so repeat customers stay one contact with their full history.

Items, SKUs, and stock

AccountRight users often run real inventory in MYOB, which forces the source-of-truth question: who owns stock levels — the store, the POS, or the books? We make that decision explicit and sync one-way wherever possible. Two systems editing stock is how phantom inventory happens.

Refunds done properly

Refunds — especially partial ones — should land in MYOB as credits against the original invoice with GST reversed. It’s the most commonly skipped part of off-the-shelf setups, and the one your accountant will find at the worst time.

Connector, middleware, or custom build

Off-the-shelf connectors

Connector services like Amaka offer WooCommerce–MYOB syncs that work well for simple, single-channel stores on MYOB Business — many on free or low-cost tiers, with paid plans for more volume and control. The catch is the assumptions: daily summaries vs per-order invoices, limited refund handling, and thin AccountRight support. Configured deliberately, they’re great value. Installed hopefully, they’re a mess you find at BAS time.

Custom integration against the MYOB API

When you run AccountRight, sell through multiple channels, or have rules no connector anticipates — wholesale pricing, job tracking, partial fulfilments — we build the integration directly. It does exactly what your workflow needs, runs on your infrastructure, and doesn’t depend on a third-party service’s roadmap or uptime. We’ve built these flows alongside Square, Lightspeed, Shippit, and Afterpay for Australian retailers.

And the question we get quietly asked in half these conversations: “should we just move to Xero?” Sometimes, honestly, yes — the connector ecosystem is richer. But it’s an accounting decision first, not a website decision, and plenty of businesses are better served keeping the MYOB setup their accountant runs well. If you’re weighing it up, we integrate WooCommerce with Xero too, so you’re not locked into either answer.

Inherited a broken MYOB sync?

We see the same patterns: a connector that duplicated every customer as a new card, six months of payouts sitting unreconciled, GST coded wrong since setup, or a sync that silently stopped when the MYOB company file moved and nobody noticed until the accountant did. The damage is rarely fatal — but it compounds monthly.

The repair is methodical: audit what actually synced, fix the mappings and the root cause, backfill the gap without duplicating what’s already there, and verify against the bank statements. Because we’re WooCommerce developers, the fix isn’t limited to what a connector’s settings page allows — when it needs code, we write it.

We’re based in Melbourne and work with stores across Australia. Local and want to talk it through across a table? Start with our Melbourne WooCommerce developer page.