WOOCOMMERCE DEVELOPMENT

Australian WooCommerce stores built in 2016 are not the same performance or security liability today that they were then — here is what the audit typically finds

Ignited Nepal builds and audits WooCommerce stores for Australian SMEs. We fix performance debt on ageing WooCommerce installations, connect Xero and MYOB for Australian GST accounting, configure Afterpay correctly on product pages, and develop custom extensions for B2B pricing and industry-specific integrations.

Request a WooCommerce Development Brief → View the evidence →
This is for you if

WooCommerce development for Australian businesses is relevant to you if any of the following applies.

You have a WooCommerce store that was built between 2015 and 2020 and has been maintained irregularly. You have plugins that have not been updated in over a year, a theme that may not be compatible with the current PHP version your hosting provider is running, and you are uncertain whether your store has known security vulnerabilities.

You are an Australian SME that needs WooCommerce connected to Xero or MYOB for GST-compliant accounting. Orders are currently being entered manually into your accounting software, or you have a connector installed that is not syncing correctly.

You are using Afterpay on your WooCommerce store but the instalment widget is not appearing on product pages in the right position, or the minimum and maximum order display thresholds are not configured correctly for your product range.

You are considering migrating from WooCommerce to Shopify and want an objective assessment of what the migration involves, what you would gain, and what you would lose — particularly if you have complex B2B pricing or custom integrations on WooCommerce that do not have direct Shopify equivalents.

You are an Australian B2B business using WooCommerce for wholesale or trade customer ordering and need account-level pricing, PO payment terms, or a customer-specific catalogue.

What's broken

Four WooCommerce problems that appear consistently in Australian store audits

WooCommerce running on unmaintained plugins

The average Australian WooCommerce store that has been live for five or more years has between 20 and 35 plugins installed. Of those, several are typically unmaintained: the developer has abandoned the plugin, the last update was over two years ago, or the plugin has known security vulnerabilities documented in the WordPress vulnerability database that have not been patched. Unmaintained plugins create two categories of risk. The first is security: a plugin with a known exploitable vulnerability is an active attack surface, and WooCommerce stores are targeted because they hold customer payment data and personal information. The second is PHP compatibility: when your hosting provider upgrades the PHP version on your server — which they do periodically, and often with limited notice — plugins built for older PHP versions can fail silently or generate fatal errors that take part of your store offline. An audit of your plugin stack, cross-referenced against the WordPress vulnerability database and PHP compatibility data, typically identifies three to six plugins that need immediate replacement or removal in a store that has been running for five-plus years without regular maintenance.

Afterpay integration not showing the instalment amount on product pages

Afterpay's official WooCommerce plugin places the instalment widget in a default position that is typically below the product short description, which means a customer reading a product page does not see the BNPL option until they scroll past the price and add-to-cart button. The widget also uses default minimum and maximum display thresholds that may not match your product price range: if your products are predominantly under $35 or over $2,000, the default configuration either shows the widget on products Afterpay does not actually support or hides it on products it does support. Moving the Afterpay widget to appear inline with the product price — which is where it has the greatest influence on purchase decisions — requires either a plugin configuration change or a short code adjustment, depending on your theme. Configuring the minimum and maximum display amounts requires editing the plugin settings to match your catalogue's actual price range and Afterpay's current merchant limits for Australian accounts.

Xero or MYOB not syncing with WooCommerce for Australian GST

Australian WooCommerce stores need their accounting software connected to WooCommerce so that orders create invoices automatically, GST is recorded correctly, and customer records are maintained without manual re-entry. The most common connectors — Xero for WooCommerce (by Woo) and WooCommerce MYOB Exo or AccountRight connectors — work correctly in straightforward configurations but break down in several common Australian scenarios. Stores with mixed GST and GST-free products need the connector configured to pass the correct tax class for each product line rather than applying a blanket GST rate. Stores with a combination of shipping-taxable and shipping-exempt scenarios need the shipping tax handling configured correctly at the connector level. Stores that process refunds in WooCommerce need the connector to create credit notes in Xero or MYOB rather than leaving the original invoice outstanding. Each of these requires configuration beyond the default connector setup, and in some cases requires custom hooks in WooCommerce to pass the correct data to the connector's API.

No page caching causing slow load on Australian hosting

WooCommerce on SiteGround, Kinsta, or WP Engine's Australian data centre performs well when caching is correctly configured. When it is not, the store runs uncached PHP and database queries on every page load. On a shared hosting plan, this is compounded by CPU and memory limits shared across multiple sites. The symptoms are product pages that take three to five seconds to load, checkout pages with noticeable lag, and sporadic timeouts during traffic peaks. These are not code problems. The store code may be entirely correct. The problem is that without page caching (WP Rocket, LiteSpeed Cache, or the hosting provider's built-in caching layer) and object caching, WooCommerce is doing far more work per page request than it needs to. Australian hosting providers vary in what caching is enabled by default versus what needs to be configured: SiteGround's SuperCacher, Kinsta's full-page cache, and WP Engine's EverCache all require WooCommerce-specific configuration to cache correctly without serving cached cart or checkout pages to logged-in users.

What we engineer

WooCommerce development services for Australia

WooCommerce store audit

We audit your WooCommerce installation against the WordPress vulnerability database, PHP compatibility data for your current hosting PHP version, and performance benchmarks. We produce a written report of findings prioritised by severity — security vulnerabilities, stability risks, and performance issues — with specific remediation steps for each finding.

Performance optimisation

We configure page caching and object caching for your specific hosting environment, optimise your WooCommerce database, review and rationalise your plugin stack, and address any theme-level performance issues identified in the audit. We measure load time before and after using GTmetrix and Lighthouse with consistent parameters so the improvement is documented.

Xero and MYOB integration

We configure the WooCommerce-to-Xero or WooCommerce-to-MYOB connector for Australian GST handling, including mixed-rate tax configurations, shipping tax, refund and credit note handling, and customer record sync. Where the standard connector does not handle your specific accounting configuration, we write custom hooks to pass the correct data.

Afterpay, Zip, and BNPL configuration

We configure Afterpay and Zip WooCommerce plugins for the correct position, display thresholds, and Australian merchant account settings. We test the complete payment flow from product page through to Afterpay/Zip confirmation and back to WooCommerce order creation.

B2B WooCommerce development

For Australian B2B businesses using WooCommerce for wholesale or trade customer ordering, we configure account-level pricing using a dedicated B2B plugin (WholesaleX or B2BKing), set up PO payment terms, create trade-only product catalogues, and configure minimum order quantities and account-specific shipping rates.

WooCommerce-to-Shopify migration

We assess the technical complexity of migrating your WooCommerce store to Shopify, identify what transfers directly (products, customers, orders) and what requires custom work (complex B2B pricing, custom plugins, accounting integrations), and provide a written migration scope with a realistic cost and timeline estimate. We execute the migration if you proceed, including data migration, redirect mapping, and post-migration testing.

Request a WooCommerce Development Brief →
What changes

What an audited and correctly configured Australian WooCommerce store looks like

Before
After
Before The average Australian WooCommerce store that has been live for five or more years has between 20 and 35 plugins installed. Of those, several are typically unmaintained: the developer has abandoned the plugin, the last update was over two years ago, or the plugin has known security vulnerabilities documented in the WordPress vulnerability database that have not been patched. Unmaintained plugins create two categories of risk. The first is security: a plugin with a known exploitable vulnerability is an active attack surface, and WooCommerce stores are targeted because they hold customer payment data and personal information. The second is PHP compatibility: when your hosting provider upgrades the PHP version on your server — which they do periodically, and often with limited notice — plugins built for older PHP versions can fail silently or generate fatal errors that take part of your store offline. An audit of your plugin stack, cross-referenced against the WordPress vulnerability database and PHP compatibility data, typically identifies three to six plugins that need immediate replacement or removal in a store that has been running for five-plus years without regular maintenance.
After Your plugin stack is documented and maintained. You know which plugins are active, when each was last updated, and whether any have known vulnerabilities. You have a defined process for applying updates — staged to a test environment before production — and you are not running abandoned plugins that create security exposure.
Before Afterpay's official WooCommerce plugin places the instalment widget in a default position that is typically below the product short description, which means a customer reading a product page does not see the BNPL option until they scroll past the price and add-to-cart button. The widget also uses default minimum and maximum display thresholds that may not match your product price range: if your products are predominantly under $35 or over $2,000, the default configuration either shows the widget on products Afterpay does not actually support or hides it on products it does support. Moving the Afterpay widget to appear inline with the product price — which is where it has the greatest influence on purchase decisions — requires either a plugin configuration change or a short code adjustment, depending on your theme. Configuring the minimum and maximum display amounts requires editing the plugin settings to match your catalogue's actual price range and Afterpay's current merchant limits for Australian accounts.
After Your accounting integration works without manual intervention. WooCommerce orders create invoices in Xero or MYOB automatically with correct GST handling, customer records are maintained, and refunds create credit notes rather than leaving accounting entries unbalanced.
Before Australian WooCommerce stores need their accounting software connected to WooCommerce so that orders create invoices automatically, GST is recorded correctly, and customer records are maintained without manual re-entry. The most common connectors — Xero for WooCommerce (by Woo) and WooCommerce MYOB Exo or AccountRight connectors — work correctly in straightforward configurations but break down in several common Australian scenarios. Stores with mixed GST and GST-free products need the connector configured to pass the correct tax class for each product line rather than applying a blanket GST rate. Stores with a combination of shipping-taxable and shipping-exempt scenarios need the shipping tax handling configured correctly at the connector level. Stores that process refunds in WooCommerce need the connector to create credit notes in Xero or MYOB rather than leaving the original invoice outstanding. Each of these requires configuration beyond the default connector setup, and in some cases requires custom hooks in WooCommerce to pass the correct data to the connector's API.
After Afterpay appears in the right place on your product pages. Customers see the instalment amount at the point where they are deciding to add a product to their cart. The widget does not appear on products outside Afterpay's price range, which removes the confusion of a customer attempting Afterpay at checkout only to find it unavailable.
Before WooCommerce on SiteGround, Kinsta, or WP Engine's Australian data centre performs well when caching is correctly configured. When it is not, the store runs uncached PHP and database queries on every page load. On a shared hosting plan, this is compounded by CPU and memory limits shared across multiple sites. The symptoms are product pages that take three to five seconds to load, checkout pages with noticeable lag, and sporadic timeouts during traffic peaks. These are not code problems. The store code may be entirely correct. The problem is that without page caching (WP Rocket, LiteSpeed Cache, or the hosting provider's built-in caching layer) and object caching, WooCommerce is doing far more work per page request than it needs to. Australian hosting providers vary in what caching is enabled by default versus what needs to be configured: SiteGround's SuperCacher, Kinsta's full-page cache, and WP Engine's EverCache all require WooCommerce-specific configuration to cache correctly without serving cached cart or checkout pages to logged-in users.
After Your store loads at an acceptable speed. Product pages, category pages, and checkout are served from cache where possible. The performance gap between your store and competitors who are on more optimised configurations is closed.
How it works

How we work on Australian WooCommerce projects

  1. 01

    Store audit

    For existing WooCommerce stores, we start with a full technical audit. We review your plugin stack against the WordPress vulnerability database, test your PHP compatibility, run performance benchmarks from Australian server locations, audit your database, and document the complete configuration. For new build projects or migration assessments, we start with a technical scoping call to document requirements.

  2. 02

    Written findings and scope

    We produce a written audit report with findings prioritised by severity. For each finding, we describe the issue, the risk or impact, and the specific remediation. We then scope the development work based on the audit, with itemised tasks and time estimates. You review and approve before work begins.

  3. 03

    Staging environment setup

    All development work is performed on a staging environment that is a copy of your production store. For Australian hosting environments (SiteGround, Kinsta, WP Engine, Pantheon), we work within the platform's built-in staging tools where available. Changes are not pushed to production until fully tested on staging.

  4. 04

    Development and testing

    We execute the scoped work on staging, test the complete purchase path including all payment methods, accounting sync, and any custom functionality, and document any additional findings encountered during development. For Xero/MYOB integrations, we test with live sandbox credentials before moving to production API keys.

  5. 05

    Production deployment and documentation

    We deploy to production during a low-traffic window, monitor the store immediately after deployment, and provide written documentation covering what was changed, how to maintain it, and any ongoing maintenance tasks (such as the recommended plugin update process).

Request a WooCommerce Development Brief →
Common questions

WooCommerce questions from Australian businesses

Should I upgrade my Australian WooCommerce store or migrate to Shopify?

Most Australian WooCommerce stores should be upgraded rather than migrated to Shopify, unless they meet specific criteria where Shopify's strengths are directly relevant. Shopify is a better choice if you want a fully managed platform where hosting, security, and core software updates are handled for you; if your catalogue is straightforward (no complex B2B pricing, no custom integrations) and you want access to Shopify's ecosystem of apps and themes; or if you are planning significant international expansion and want Shopify Markets. WooCommerce is the better choice if you have complex B2B pricing (account-level discounts, PO payment terms, quote workflows) that WooCommerce handles natively and Shopify requires expensive third-party apps to replicate; if you have custom WooCommerce plugins for business-specific logic that do not have Shopify equivalents; or if your Xero/MYOB integration is deeply configured and the cost of re-integrating on Shopify is significant. The migration decision should be based on a technical assessment of what transfers and what does not — not on a general preference for one platform over the other.

How do I connect Xero or MYOB to WooCommerce for Australian GST accounting?

Connecting WooCommerce to Xero uses the Xero for WooCommerce plugin published by Woo (the company behind WooCommerce), which creates a OAuth connection between your WooCommerce store and your Xero organisation. After connecting, you configure the Xero account codes for sales, shipping, and each tax class your store uses — in Australia this typically means setting up the GST account code for taxable products and the correct code for GST-free products. For MYOB, the most commonly used connector for small Australian businesses is the WooCommerce MYOB AccountRight integration by Visser Labs. Both connectors require configuration beyond the default setup to handle Australian GST correctly for stores with mixed-rate catalogues or complex shipping tax scenarios. The most common failure mode is that the connector creates all invoices with the same tax treatment regardless of the product's WooCommerce tax class — fixing this requires mapping each WooCommerce tax class to the correct Xero or MYOB tax rate in the connector settings.

How do I move the Afterpay widget to the product price line in WooCommerce?

Afterpay's official WooCommerce plugin uses a hook to inject the instalment widget into the product page. By default, the hook is woocommerce_single_product_summary at priority 15, which places it after the product price (priority 10) but before the add-to-cart button (priority 30). To move the widget to appear directly after the price — which is typically priority 11 — you remove the default hook in a custom functions.php snippet and re-add it at priority 11. The exact implementation depends on your theme: some themes render the product summary using custom templates rather than the standard WooCommerce hooks, in which case the widget placement requires a template-level change rather than a hook priority change. After repositioning, verify the widget is displaying correctly across both desktop and mobile viewpoints and that it does not appear on products outside your configured minimum and maximum display amounts.

What hosting is best for a WooCommerce store in Australia?

Kinsta and WP Engine are the highest-performing managed WordPress hosting options for Australian WooCommerce stores, with Australian data centres (Sydney) and WooCommerce-specific caching configurations built in. Both handle server management, security patching, and daily backups. For the majority of Australian SME WooCommerce stores with up to 5,000 products and moderate traffic, SiteGround's GrowBig or GoGeek plans on the Australian data centre (Sydney) perform well when configured correctly with SiteGround's SuperCacher. Shared hosting on providers like Crazy Domains or VentraIP is adequate for low-traffic stores but typically does not provide the server-level caching and resource allocation needed for WooCommerce stores above a few hundred products or a few thousand monthly visitors. For high-traffic stores or stores with large catalogues (10,000+ products), a VPS or dedicated managed hosting plan is more appropriate than any shared or entry-level managed plan.

How do I audit and clean up outdated WooCommerce plugins?

Auditing WooCommerce plugins starts with three checks for each active plugin: when was it last updated (visible in the plugin details on WordPress.org or in your wp-admin Plugins screen), is it in the WordPress vulnerability database (check patchstack.com or wpscan.com), and does it have a known PHP version compatibility issue. Any plugin that has not been updated in over 18 months, has a documented unpatched vulnerability, or is listed as incompatible with PHP 8.0+ (the minimum version most current Australian hosts support) is a candidate for replacement or removal. After identifying problematic plugins, the remediation process is: find a maintained alternative where one exists, test the alternative on staging, replace the unmaintained plugin, and document the change. Avoid simply deactivating and deleting a plugin without testing the impact on store functionality first — some plugins add database tables or modify order data in ways that affect store behaviour after removal.

Start here

Start with a WooCommerce audit

If your WooCommerce store was built more than three years ago and has not had a structured maintenance and performance review, the audit is the right starting point. We document what is broken before scoping any development work.

Request a WooCommerce Development Brief →