BeforeThe 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.
AfterYour 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.
BeforeAfterpay'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.
AfterYour 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.
BeforeAustralian 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.
AfterAfterpay 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.
BeforeWooCommerce 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.
AfterYour 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.
