Connecting WooCommerce to MYOB is easy. Connecting it so that the figures in MYOB match the figures in WooCommerce, month after month, without someone manually fixing entries, is the actual job. Most off-the-shelf connectors get orders across and leave the reconciliation to you. We build and repair WooCommerce MYOB integrations for Australian stores, starting from what your books need to look like.
Send enquiryAustralian team
Based here, working your hours, not a timezone away
projects delivered
Over 10+ years building and maintaining sites for Australian businesses
One developer, start to finish
The same person every time: no re-explaining your site
Straight answers, on your terms
We only take work we can finish. Ask us anything first: no obligation
A reliable sync does the same five things for every order. It waits for a defined trigger, usually the order reaching a paid status. It finds the customer card in MYOB, creates one, or posts to a single shared card for retail customers. It creates the sale with one line per product, the shipping as its own line and any discount shown, each line carrying the right MYOB tax code. It records the payment against a clearing account rather than straight to the bank. And when the order is refunded in WooCommerce, it creates the matching return or credit in MYOB instead of leaving the original sale untouched. Each step has a failure mode, and the integration should log which step an order stopped at.
WooCommerce thinks in tax classes; MYOB thinks in tax codes: GST, FRE, N-T, EXP. A connector that maps everything to GST will import a GST-free product as taxable, and the error compounds silently across every order until a quarter of entries need correcting by hand. The mapping has to be explicit, per class, both ways.
MYOB has renamed and reorganised its products more than once, so "we use MYOB" can describe several different setups: AccountRight with its company file online, AccountRight on a file kept on a local computer, or one of the MYOB Business plans. The edition decides whether there is API access at all, whether inventory items are available to sync against, and how the connection is authorised. A cloud integration generally needs the company file to be online. We confirm the edition and where the file lives before quoting, because a connector set up against one arrangement will not simply point at another.
If MYOB tracks your stock, each order line has to land on an inventory item, and the link between the two systems is the SKU in WooCommerce matching the item number in MYOB exactly. A product with no SKU, a variation that shares its parent's SKU, or an item renamed in MYOB without the SKU being changed in the store will all make that line fail or post to the wrong item. Before switching a sync on we compare the two lists and fix the mismatches, which is tedious work and the reason most integrations behave on day one instead of month three. If MYOB does not track stock for you, sales can post without items and most of this problem disappears.
An order can land in MYOB as an invoice, a sale, or a journal entry, and the right answer depends on whether you are tracking inventory there, whether payment is captured at checkout, and how you want deposits and part-payments handled. Choosing wrongly is the reason so many stores end up with a duplicate-looking ledger.
Two-way stock sync sounds obviously desirable and frequently is not. If MYOB is not your source of truth for stock, syncing it back will overwrite good WooCommerce data with stale figures. We normally establish one authoritative side and push in a single direction unless there is a real reason not to.
A hundred-dollar order does not arrive in your bank as a hundred dollars. Gateway fees, payouts batched across several days, and refunds issued against an earlier period all break naive matching. We map the settlement side as well as the sale, typically through a clearing account for each gateway with the fees posted as an expense, so the bank feed actually reconciles rather than leaving a monthly residue for someone to chase.
WooCommerce and MYOB each calculate GST for themselves, and they do not always round the same way. If WooCommerce rounds at the order subtotal and MYOB calculates per line, or the other way round, a scattering of sales will differ by a cent. One cent is harmless; hundreds of them make the GST reconciliation look wrong and waste your bookkeeper's afternoon. The fix is deciding which side owns the calculation, sending amounts in the form MYOB expects for that choice, and aligning the WooCommerce rounding setting to match.
Expired authorisation, a changed company file, an API limit hit during a sale: connectors tend to fail quietly, and the first sign is a gap in the ledger discovered weeks later. We add failure alerting so a broken sync tells you on the day it breaks, and a daily summary of how many orders went across so a quiet failure is just as visible as a loud one.
Choose the simplest option that handles your mapping. A maintained connector plugin is the cheapest route for a store with standard products, standard GST and one payment gateway, and we will tell you if that is all you need. An automation platform such as Make.com or n8n suits stores that need a few extra rules, such as routing wholesale orders differently from retail. A custom integration earns its cost only when the logic is genuinely unusual: several gateways, split shipments invoiced separately, deposits, or multiple MYOB files. Small builds start at $300 AUD and everything is fixed-quoted after we have seen both systems. If you would rather not watch the connection yourself, website maintenance covers updates, backups and monitoring on the store it runs on.
Usually yes. Most of the integrations we are asked to look at are working in the sense that data moves, and broken in the sense that the data is wrong. Correcting the tax mapping and the record type is often enough, and is far cheaper than a rebuild.
Not necessarily. For a straightforward store a well-configured connector is the cheapest route, and we will tell you if that is your situation. Custom middleware only earns its cost when the mapping is genuinely non-standard: multi-currency, unusual tax treatment, or a workflow no connector exposes.
We build the same integration against Xero, and the underlying decisions are identical: tax code mapping, record type, settlement handling. The MYOB specifics on this page are about the API and the tax codes, not about which package we prefer.
Only if you need it. Trade customers who buy on account need their own card so their balance and statements work. For retail, a single shared cash-sales card keeps the card file from filling with thousands of one-off shoppers, and keeps personal details in one system instead of two. Many stores use both: individual cards for trade, one shared card for retail.
For most stores that take payment at checkout, syncing at payment is right, because that is when the sale and the money exist. Syncing at completion suits stores whose orders change between payment and dispatch, such as substitutions or partial shipments. The one thing to avoid is triggering on both, which is a common cause of every order appearing twice in MYOB.
Yes, as a one-off batch, but only after deciding a cut-over date. If someone has been keying sales into MYOB by hand, pushing the same orders automatically will duplicate them. We agree the first order the integration owns, send everything from that point, and leave earlier periods as they are in your books.
You should not have to check. Every integration we build sends an alert when an order fails and a short daily summary of what went across, so a quiet day and a broken sync look different. Failed orders are kept in a queue to retry once the cause is fixed, rather than being dropped.
Tell us what is happening and we will come back with a fixed quote and a timeline, usually within one business day.
Get in touchConnect WooCommerce to MYOB with correct tax codes, SKU matching, gateway clearing and failure alerts. Fix an existing sync or build a new one. Fixed quotes.
Get in touchEvery CloudyWP project runs the same way, whether it is a one-page site or a store with a thousand SKUs. Here is exactly what happens.
A single scoping call, then a written plan: what gets built, what it costs, and when it ships. No discovery-phase invoices, no moving targets.
48 hrs to your quote
Custom WordPress or Shopify on clean code you own outright. Every build ships fast, passes Core Web Vitals, and is handed over documented.
95/100 average PageSpeed
Your site talks to the tools you already run: CRM, invoicing, email, stock. The repetitive admin stops being someone's job and starts running itself.
15 hrs saved every week
