CloudyWP is a WooCommerce developer for Australian stores. We fix stores that are losing money, and build the parts local retailers always end up needing: GST that reconciles, Australia Post rates that actually appear, accounting that syncs, and a checkout that works on a phone. WooCommerce support Australia-wide from a Melbourne team, open all week, 9 to 5 AET.
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
If your store cannot take orders, go straight to our emergency WooCommerce support page rather than reading the rest of this one. A store that cannot trade is an outage, not a support ticket. Same-day incident work is a fixed $449 AUD callout covering the first 2 hours, and we work on a copy with a rollback point so a fix never turns into a second problem.
Mostly, a WooCommerce developer keeps an existing store trading and makes it do one specific thing it does not do yet. Very little of our WooCommerce development work is building a store from nothing. It is a payment gateway that stopped creating orders, a checkout that needs an ABN field or trade pricing, a plugin conflict after an update, a supplier feed that should update stock overnight, or a catalogue of several thousand products that has become slow in the admin. Some of it is platform housekeeping, such as moving an older store onto High-Performance Order Storage, the dedicated order tables WooCommerce has used by default for new stores since version 8.2, once every plugin that touches orders has been checked for compatibility. If the store needs recurring orders or memberships, our subscription plugin development page explains when that is better than stacking extensions.
Most WooCommerce advice online is written for a US store. GST is not sales tax, an ABN is not a VAT number, and Australia Post is not a carrier most overseas plugin authors test against. We have separate pages for the problems Australian stores get stuck on most: GST setup and BAS reconciliation, MYOB integration, Australia Post rates that will not show, and automated inventory updates. Each one covers the settings and the reasoning rather than a generic checklist.
Most WooCommerce failures have one of a handful of causes, and they are usually recent. An update to a plugin, the theme or WooCommerce itself that no longer agrees with an extension or with outdated template overrides in the theme. A host moving the site to a newer PHP version that an old plugin cannot run on. Payment gateway webhooks that stop reaching the site after a security plugin or firewall change, leaving paid orders stuck at Pending payment. WP-Cron not firing, so the Action Scheduler queue that runs scheduled sales, renewals and emails quietly backs up. A page cache that has been allowed to cache the cart or checkout, so customers see each other's carts or stale totals. And order emails that never arrive because the site sends mail without SPF and DKIM authentication. Each of these leaves evidence in the logs, which is why we start there.
WooCommerce suits a store that needs control: a checkout with custom fields or logic, trade and retail pricing side by side, unusual shipping rules, deep integration with accounting or warehouse systems, or a lot of content alongside the products. Shopify suits a store that wants a standard checkout and would rather pay a platform than look after software. Neither is better in general, and we build on both; a store inside a larger site is custom WordPress development work. If you are already on Shopify and feeling its limits, our Shopify to WooCommerce migration page sets out what moving actually involves and when it is not worth it.
A diagnosis starts at $249 AUD, quoted before we start, and you get the cause in writing as well as the fix. Ad-hoc WooCommerce support is $100 AUD an hour, or $500 AUD for a prepaid five-hour block. Larger builds, such as an accounting integration, a custom checkout or a migration, are fixed-quoted to scope after a short call; a typical custom build sits between $2,500 and $5,500 AUD. Ongoing cover runs from $159 AUD a month with no lock-in.
We back the site up first, make the change on a staging copy, and keep a rollback point in place. One detail matters more on a store than on any other site: orders keep arriving while we work. Pushing a staging database over the live one would delete every order placed in between, so we move code and configuration changes across, never a whole database. After a change we run a test order through the real gateway in test mode where it has one, then check the next live orders as they land. You get a short written note of what changed and why.
If your store is stable and changes rarely, pay for fixes as they come up; there is no reason to carry a monthly cost for a store that does not need it. Ongoing cover, our WordPress maintenance, earns its keep when the store depends on many plugins, takes enough revenue that a bad update is expensive, or needs small changes most months. Our Essential plan at $159 AUD a month covers updates, monitoring, weekly off-site backups and a monthly report. The Dev plan at $700 AUD adds 10 developer hours a month, which suits stores that always have something on the list.
Almost always. Most of what we do is inherited stores: someone else built it, or a plugin update broke it, or the person who set it up is gone. We do not require a rebuild before we will help.
Yes. We are often brought in for a specific problem (a payment gateway, a shipping integration, an accounting sync) alongside an in-house team or another agency, and we hand back documented work rather than something only we can maintain.
No. We are a Melbourne team providing WooCommerce support Australia-wide, and we work with stores wherever they are. Our hours are 9 to 5 AET, open all week, which lines up with when most Australian stores are trading.
We update on a staging copy first and read the changelogs for anything that alters templates or payment handling. WooCommerce lists outdated template overrides in your theme under WooCommerce > Status, and that list is one of the first things we check, because an override that has fallen behind is a common reason a checkout breaks after an otherwise routine update.
Yes, fixed-quoted after a scoping call. A typical custom build sits between $2,500 and $5,500 AUD; large catalogues, integrations and custom checkout logic take it higher, up to around $15,000 AUD for complex builds. You know the number before any work starts.
Stripe, PayPal, Square, Afterpay and Zip are the ones Australian stores ask about most, and we work with most gateways that have a maintained WooCommerce plugin. The common faults are similar across all of them: webhooks not arriving, API keys that were rotated or expired, and test mode left switched on after a change.
High-Performance Order Storage moves orders out of the general WordPress posts tables into tables built for orders, which makes order queries faster on busy stores. New stores use it by default. An older store can switch once every plugin that reads or writes orders declares compatibility; WooCommerce can keep both storage methods in sync during the change, so it can be done in stages and reversed if something misbehaves.
Usually because the site sends email straight from the web server without authentication, so the receiving mail provider treats it as suspect and drops it or files it as spam. Routing WooCommerce email through an authenticated SMTP or transactional email service, with SPF and DKIM records set on your domain, fixes most cases. We also check that the emails are enabled in WooCommerce and that a stalled scheduled-actions queue is not holding them back.
Tell us what is happening and we will come back with a fixed quote and a timeline, usually within one business day.
Get in touchWooCommerce developers fixing and extending Australian stores: GST, Australia Post, MYOB, payments, updates. Fixed quotes, Melbourne team, 9 to 5 AET all week.
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
