When does an Australian store actually need a WooCommerce developer?
You need a WooCommerce developer when the fix involves code, data or the way plugins interact, rather than a setting in the dashboard. If a product price is wrong, you can change it. If every price in the cart is out by a tenth because a tax class was set up backwards, that is developer territory.
WooCommerce is a free plugin that turns WordPress into a shop, which is why so many Australian retailers chose it: no monthly platform fee, full control of the code and a huge library of extensions. The same freedom creates the typical trouble. Stores grow by adding a plugin for every new need, each one updated on its own schedule, until one update knocks over the checkout on a Saturday morning.
These are the signals we hear most often from owners who end up hiring a WooCommerce developer:
- Orders sit on “pending payment” even though the customer was charged
- The GST figure on invoices does not match what your bookkeeper sees in Xero
- Australia Post rates show as zero, or a label fails to generate for certain postcodes
- The dashboard takes ten seconds to load the orders screen
- A plugin update produced a critical error and you rolled back without knowing why
- You want a feature, such as trade pricing, that no single plugin does properly
If none of these apply and you are starting fresh, our WordPress website design for Australia page covers the build side.
Should a WooCommerce developer fix your store or rebuild it?
Fix it when the product data and customer records are sound and the problems sit in a handful of plugins or templates. Rebuild when the theme is so modified that nobody can update it, or when the store runs on an old PHP version that the host is about to retire.
The honest answer comes from an audit, not a sales call. When you send us admin access to a staging copy, one of the three of us lists every active plugin, checks which ones are still maintained, reads the theme's functions file for custom code, and looks at the database size and the order table. That takes a short, quoted block of time and gives you a written list of what to keep, replace or remove.
Most Australian stores we look at land in the middle. The catalogue and customers are worth keeping, the theme can stay with some clean-up, and three or four plugins need replacing with something maintained or a small custom plugin. A full rebuild is rarely the cheapest route, and a WooCommerce developer who recommends one before seeing the store is guessing.
Signs a fix will do
Recent WooCommerce and WordPress versions, a child theme rather than edits to the parent, fewer than a few dozen plugins, and a working staging site.
Signs a rebuild is due
Edits made directly to a commercial theme, PHP well behind what the host supports, checkout templates overridden years ago, and no one able to explain what half the plugins do.
How should a WooCommerce developer set up GST tax classes for Australia?
Use one standard rate of 10% for taxable goods, a separate class at zero for GST-free products, and enter prices inclusive of tax so shoppers see the full amount. Then test a mixed cart before you trust it.
WooCommerce ships with “Standard”, “Reduced rate” and “Zero rate” tax classes. Australian stores rarely need a reduced rate, but plenty need the zero class: a grocer selling basic food alongside gift hampers, a pharmacy-style shop with some GST-free health products, or a bookshop that also sells gift cards. Which products are GST-free is a question for your accountant; our job is to make the store apply whatever answer they give.
The settings we check on every store:
- Prices entered with tax set to yes, so the figure you type is what the shopper pays
- Calculate tax based on the shop base address for a domestic-only store, or the customer address if you ship overseas
- Shipping tax class matched to the items in the cart, so postage on a mixed basket is handled consistently
- Display prices including tax in the shop and cart, with a “includes GST” suffix
- Rounding at subtotal level, which avoids one-cent differences when your bookkeeper reconciles
A wrongly configured class is the single most common reason a store's GST report disagrees with the accounting file. We fix the class, then re-check a sample of past orders so you know how far back the problem reaches.
Tax invoices with your ABN: what the ATO lists and how WooCommerce produces them
If you are registered for GST, the document a customer downloads should be titled “tax invoice” and carry the details the ATO lists. WooCommerce does not create a compliant PDF on its own, so a WooCommerce developer adds an invoice plugin and configures it.
According to the ATO's tax invoices guidance, a tax invoice shows the seller's identity and ABN, the date it was issued, a brief description of what was sold and the GST-inclusive price, with the GST shown separately or as a statement that the total includes GST. Sales of a thousand dollars or more also need the buyer's identity or ABN, and where a basket mixes taxable and non-taxable items, the invoice has to make clear which is which. The ATO also confirms an emailed PDF counts; paper is not required.
On a WooCommerce store that translates into a few concrete tasks. We add your legal name and ABN to the invoice template, number invoices in sequence, print a per-line GST marker for mixed carts, and add an optional ABN field at checkout for trade buyers so larger orders carry it automatically. Refunds generate a matching credit note. We set up the template; your accountant confirms it meets your obligations.
Australia Post, eParcel and courier plugins on WooCommerce
Start with an Australia Post plugin from one of its listed platform partners, connect it to your own MyPost Business or eParcel account, and let it pull live rates and print labels. Avoid hand-typed rate tables unless your catalogue is tiny.
Several WooCommerce plugin makers describe themselves as official Australia Post platform partners and support MyPost Business, eParcel contract rates, StarTrack and label printing. Which one suits you depends on volume and on whether you also use a courier or a shipping hub. A WooCommerce developer's job is to choose one, connect it with your credentials, and map every product to real dimensions, because live rates are only as good as the box sizes you give them.
The problems we fix most in this area are dull but expensive: products missing weights, so rates return zero; satchel products set as parcels; free-shipping rules that ignore remote postcodes; and label plugins still pointing at an expired API key after a staff member left. Each gets a short test plan, including a Tasmanian and a remote Northern Territory postcode, before we sign it off.
- Product weights and dimensions filled in for every shippable item
- Shipping zones split for metro, regional, remote and overseas where rates differ
- A packing rule so several small items are quoted as one satchel, not three parcels
- Tracking numbers written back to the order and included in the completed-order email
Afterpay, Zip and card payments on an Australian WooCommerce checkout
Add buy-now-pay-later as its own payment method alongside your card processor, install each provider's plugin against your own merchant account, and test a purchase, a partial refund and a full refund for every method before launch.
Afterpay and Zip both publish WooCommerce plugins that add their option at checkout and can show instalment amounts under prices on product, category and cart pages. Those messages help conversion, but every widget loads its own scripts. We usually keep them to product and cart templates and leave category grids clean, which keeps the listing pages fast on mobile data.
Card payments, Apple Pay and Google Pay come through whichever card processor you already hold a merchant account with. We do not resell gateways or take a cut; the accounts are yours, the fees go straight to the provider, and we only configure and test. When checkout fails, the cause is usually one of four things: a caching plugin serving a stale checkout page, a currency mismatch between the store and the BNPL account, a security plugin blocking the provider's callback, or two payment plugins loading conflicting scripts. A WooCommerce developer should rule out each of these in order rather than reinstalling everything.
HPOS migration: should your WooCommerce store switch now?
Yes, for most stores, once every plugin that touches orders declares HPOS compatibility. Test the switch on staging, run in compatibility mode until the tables are in sync, and only then make HPOS authoritative.
High-Performance Order Storage moves orders out of the general WordPress posts tables into dedicated order tables. WooCommerce's developer documentation says HPOS became stable and the default for new installations from version 8.2, released in October 2023, and describes keeping the old and new tables synchronised during the move, with a command-line sync for larger stores. Older stores that were installed before then are often still on legacy storage.
Our HPOS routine for an Australian store looks like this:
- List every plugin that reads or writes orders and check its HPOS compatibility notice
- Replace or patch any plugin that still queries orders as posts
- Clone the live store to staging and turn on synchronisation
- Run the sync from the command line for stores with a large order history
- Compare order counts, totals and GST figures between the two storage modes
- Switch the live store in a quiet hour, keep sync on for a period, then turn it off
The payoff is a faster orders screen and quicker order searches, which matters most to stores with years of history and busy sale periods.
Why is my WooCommerce store slow, and what does a WooCommerce developer do about it?
Most slow WooCommerce stores are slow for three reasons: too many plugins loading on every page, cheap shared hosting with no object cache, and large unoptimised images. Fixing those three usually matters more than any caching plugin setting.
We measure before touching anything. That means Google's PageSpeed Insights for the storefront, a query monitor on the admin, and a look at which plugins load scripts on pages where they do nothing. A BNPL widget on the blog, a slider library on checkout, and a form plugin on product pages are typical finds.
Then the fixes, roughly in order of impact:
- Remove or replace plugins that duplicate each other or are no longer maintained
- Load scripts only on the templates that use them
- Add an object cache and a page cache that excludes cart, checkout and account pages
- Serve images in modern formats at the size they display
- Clean expired transients, old sessions and orphaned order metadata
- Move to hosting with a data centre in Australia if yours is overseas and slow
Speed also feeds search. For the ranking side of a store, see ecommerce SEO services for Australia, and for a site-wide crawl and performance check our technical SEO audit page explains what gets tested.
Syncing WooCommerce orders to Xero or MYOB without double handling
Decide first what should land in the accounting file: one invoice per order, or a daily summary. Then map payment methods, tax codes and fees before connecting anything. Most sync problems are mapping problems, not software problems.
Australian retailers mostly run Xero or MYOB. Both can receive WooCommerce data through maintained connectors or through a small custom integration against their APIs. A connector is cheaper to start with; custom code makes sense when you need rules a connector cannot express, such as splitting a mixed GST basket across accounts, posting BNPL settlements net of fees, or syncing stock back from the accounting file.
What we map with you before any order moves:
- Which WooCommerce tax class becomes which GST tax code
- Clearing accounts for each payment method, including Afterpay and Zip settlements
- How refunds and partial refunds post as credit notes
- Where shipping income goes, and how discounts appear
- Whether customer contacts sync, or only a single cash-sale contact
For deeper accounting integrations, including inventory and multi-channel sales, read our dedicated Xero integration developer guide. Your bookkeeper signs off the mapping; we build it.
Custom WooCommerce plugins versus buying another extension
Buy the extension when a maintained one does exactly what you need. Write a custom plugin when you would otherwise stack three extensions and still end up editing theme files to glue them together.
A WooCommerce developer who writes everything from scratch costs you money, and one who installs a plugin for every request leaves you with a fragile store. The middle path is to use WooCommerce's hooks and filters in a single site-specific plugin that holds all your custom rules, kept in version control and separate from the theme, so a theme update never wipes your business logic.
Custom plugins we are asked for most by Australian retailers:
- Trade and wholesale price tiers visible only to approved accounts, shown ex-GST behind the login
- Restrictions on shipping certain products to particular states or territories
- Click-and-collect slots tied to store opening hours
- Order export files formatted for a third-party warehouse
- Reorder buttons and saved lists for repeat business customers
Custom plugin work is quoted from US$900 when it is a full integration, and per task when it is a single rule. The code sits in a repository you own.
Privacy, customer data and security on an Australian WooCommerce store
Keep only the customer data you need, lock down admin access, and keep software patched. Whether the Privacy Act applies to your business is a separate question to confirm with your adviser, but good data handling is sensible either way.
The OAIC explains on its small business privacy page that businesses with annual turnover of 3 million dollars or less are generally exempt from the Privacy Act, but that some are covered regardless, including health service providers and businesses that trade in personal information. Many online stores sit near that line or grow past it, so we build as if the rules apply.
On a WooCommerce store that means individual admin accounts instead of a shared login, two-factor authentication for anyone who can see orders, a security plugin configured so it does not block payment callbacks, automatic backups stored off the server, and a privacy policy page that matches what the store actually collects. We also remove old customer exports sitting in the uploads folder, which is a surprisingly common leak. This supports your obligations; it is not legal advice.
Working with a WooCommerce developer in India from Australia
It works best with a shared written task list, a short video call in your afternoon, and a staging site where changes wait for your approval. You do not need to change how you run the shop.
India is four and a half hours behind Sydney and Melbourne on standard time and five and a half hours behind during daylight saving. So our 9 am lands in your early to mid afternoon on the east coast, Brisbane stays on the same gap all year because Queensland skips daylight saving, and Perth is only two and a half hours ahead of us, which gives the longest overlap of any Australian city.
Here is what the first two weeks with a WooCommerce developer on our side usually look like:
- Days 1–2: you share admin and hosting access through separate user accounts; we create a staging copy and read the plugin list
- Days 3–4: a written audit arrives with each problem priced as its own line
- Day 5: a 30-minute call in your afternoon to agree which lines go first
- Week 2: fixes land on staging overnight your time, you check them next morning, and approved changes go live in a quiet hour
Quotes are in USD. You can pay in AUD through Wise, or by bank wire; invoices come from India. Code, hosting, domain and plugin licences stay in your name from day one. Terms are set out in your written quote and our terms.
How to vet a WooCommerce developer before you hand over admin access
Ask how they will work on a copy rather than your live store, who will hold the code, and what they would check first given your symptoms. A good WooCommerce developer answers those three questions specifically, without needing a long sales call.
Access is the real risk. Anyone with administrator rights can change prices, read customer details and install code. So give each developer their own user account with only the access they need, never share your own password, and remove the account when the work ends. Hosting access should be a separate login too, ideally with a staging environment the host provides.
Questions worth asking any WooCommerce developer, including us:
- Will you fix things on staging first, and how do changes get to the live store?
- Where does custom code go: the theme, a child theme or a site plugin?
- Will you raise tickets with plugin authors when their code is at fault?
- What will you document when the job ends?
- How do you handle an update that breaks checkout on a weekend?
- Which parts of this job would you not take on?
That last question matters. We do not do on-site work, product photography, paid ads management or hardware such as POS terminals, and we say so up front.
Red flags when hiring a WooCommerce developer
Walk away from anyone who wants your personal admin password, edits the live store without a backup, or cannot explain in plain English what they changed. Those three habits cause most WooCommerce disasters we are asked to clean up.
Other warning signs are subtler. A developer who installs a nulled copy of a premium plugin to save you the licence fee is exposing your store to malware. One who registers the store's hosting or domain under their own account holds your business hostage the day you part ways. A quote that says “WooCommerce fixes” with a single figure tells you nothing about what is included.
- No staging site, or “we'll just be careful on live”
- Premium plugins installed from unofficial sources
- Accounts, licences or hosting registered in the developer's name
- Edits made to the parent theme or to WooCommerce core files
- Promises of guaranteed rankings or instant speed scores
- No written record of changes at the end of the job
Nobody can guarantee search rankings, and a speed score on one test run is not the same as fast pages for real shoppers. We will tell you what we changed and how we measured it, and leave the judgement to you.
A worked example: fixing and extending a Geelong homewares store
Here is a hypothetical to show how a WooCommerce developer would approach a typical Australian job. Say a homewares shop in Geelong runs WooCommerce on shared hosting. Its owner reports three things: the orders screen crawls, Afterpay disappeared from checkout after an update, and the bookkeeper says GST in Xero never matches the store's report.
Day one, we clone the store to staging. The plugin list shows 58 active plugins, two of which are old shipping calculators nobody uses. Afterpay is missing because a caching plugin is serving a cached checkout to logged-out visitors. The GST mismatch comes from gift cards set to the standard tax class, which adds GST at sale and again when the card is redeemed.
The itemised quote might split into five lines the owner can approve separately: checkout cache exclusion and Afterpay retest; gift card tax class correction plus a list of affected past orders for the bookkeeper; removal of unused plugins; HPOS migration with synchronised tables; and a mapping review of the Xero connector. A sixth, optional line adds an ABN field at checkout for interior designers who buy in bulk.
None of this is a real client or a real result. It is the order of work we would follow, and the reason for each step.
WooCommerce developer checklist for an Australian store handover
Before you sign off any WooCommerce job, run through this list. If a WooCommerce developer cannot tick every line, ask why before you pay the final invoice.
- Admin, hosting and plugin licence accounts all registered to you
- Developer user accounts removed or downgraded after the job
- Custom code in a child theme or site plugin, with a copy of the repository
- GST classes tested with a mixed cart; prices display inclusive of GST
- Tax invoice PDFs showing your name, ABN, date, description and GST
- Australia Post or courier labels tested with metro, regional and remote postcodes
- Afterpay, Zip and card payments tested for purchase, partial refund and full refund
- Order sync to Xero or MYOB checked against a week of real orders
- HPOS status recorded, with any incompatible plugins listed
- Off-site backups scheduled and one restore tested
- A written change log of everything touched
Keep this list with your store's documents. Next time you hire anyone, freelancer or agency, hand it over on day one. For longer-term upkeep, our website maintenance services page explains monthly care.