HUB · 3 GUIDES

E-commerce platforms

Compare Shopify, WooCommerce and custom builds, and see where Australian retailers need integration or custom software development instead.

Quick answer: Shopify and WooCommerce handle most of an Australian e-commerce store; custom development pays off closing the inventory, freight and accounting integration gaps around them.

Last updated 29 September 2026

Quick answer

Should a growing retailer build a custom e-commerce platform or use Shopify or WooCommerce?

High confidenceVerified 29 Sept 2026

Most Australian retailers should run on Shopify or WooCommerce and reserve custom software development for the inventory, freight and accounting integrations the platform can't handle at scale.

Additional Context

The platform layer - checkout, catalogue, payments - is a solved problem for the vast majority of retailers. The integration layer around it usually isn't, and that's where custom development earns its cost.

Sources

ACCC - Australian Consumer Law guarantees for online sellers
Consumer guarantees under the Australian Consumer Law apply the same way regardless of which platform a business sells through.
OAIC - Privacy Act small business exemption
Businesses above the small business exemption threshold pick up full Privacy Act notification and data handling obligations.

Platform Strategy

Shopify, WooCommerce or a custom build

Retailers turning over several million dollars a year rarely need to rebuild the storefront from scratch. Shopify and WooCommerce handle checkout, catalogue and payments capably, and the app ecosystems around both cover a wide range of standard retail needs. The decision that actually matters for operations managers is what happens once an order is placed - how stock, freight and the ledger stay in sync as volume grows.

Most teams hit this the first time they attempt WooCommerce customisation that goes beyond a plugin's intended scope, or when a Shopify app that worked at fifty orders a day starts silently dropping updates at five hundred. The platform hasn't failed - it's being asked to do a job it wasn't built for.

Where off-the-shelf platforms hit their limit

Three points tend to break first, and in a consistent order: stock counts across channels, freight calculation at checkout, and the reconciliation between orders and the accounting ledger. Retailers running Xero or MYOB alongside a platform-native inventory app often discover the two disagree on stock-on-hand within weeks of adding a second sales channel, because neither system was designed to be the single source of truth.

Solving this rarely means replacing the platform. It usually means building the layer between the platform and the systems on either side of it - multichannel inventory sync that treats the warehouse as the source of truth, and carrier API integration that pulls live rates instead of static flat fees. That's the specific, narrow work custom development is good for: an integration layer, not a rebuild.

Build vs Buy

The Integration Gap Behind Most Platform Complaints

Problem

Retailers blame the platform when Shopify or WooCommerce app data disagrees with the warehouse, a freight quote at checkout doesn't match the carrier invoice, or Xero and the storefront show different stock counts. The platform is rarely the problem. The missing integration layer between it and the rest of the stack usually is.

Common Pain Points:

Stock counts disagree across channels Warehouse, storefront and marketplace each show a different number, and nobody's sure which is right.
Freight quotes don't match invoices Checkout shows a flat rate while the carrier bills actual weight and zone, eating into margin on every order.
Month-end reconciliation takes days Finance re-enters order data into Xero or MYOB because the platform and the ledger were never properly connected.

Business Impact:

Time Wasted: Recurring hours each week on manual stock and order reconciliation

Cost Implication: Ongoing cost of overselling, refunds and freight under-recovery

Opportunity Cost: New sales channels delayed while staff manage data conflicts by hand

Solution

An audit of the platform, accounting system and fulfilment tools already in place, followed by targeted integration or custom development only where a genuine gap exists.

Our Approach:

1Map the current stack(Early phase)
Document every system touching an order - platform, accounting, freight, CRM - and pinpoint exactly where the data currently disagrees.
2Build the integration layer(Delivery phase)
Connect inventory, freight and accounting systems so stock and order data reconcile automatically instead of by hand.

Expected Outcome: Stock counts, freight costs and ledger entries that reconcile automatically, freeing staff from manual cross-checking as order volume grows.

Key Takeaways

What Actually Decides Platform vs Custom Build

Off-the-shelf platforms handle checkout and catalogue well; the integration layer is usually the real gap.Important
Shopify and WooCommerce rarely need replacing. The work worth paying for sits in connecting them properly to inventory, freight and accounting systems.
Stock disagreements across channels are a data ownership problem, not a platform bug.Important
Warehouse, storefront and marketplace apps each keep their own count; without one designated source of truth, they will always drift apart.
Freight and accounting integration pay back faster than a full platform rebuild.Important
Connecting live carrier rates and ledger sync addresses the two costs operations managers notice first: margin leakage and reconciliation time.
Custom development should target the specific gap, not the whole platform.Important
A narrow, well-scoped integration is cheaper to build and maintain than a ground-up replacement, and keeps the parts of the platform that already work.

The platform choice matters less than the integration decisions around it: get inventory, freight and accounting talking to each other before considering a rebuild.

E-commerce Platform Obligations and Trends

Growth in online trade brings regulatory and operational obligations that most retailers only notice after they've already crossed the relevant threshold.

Structurally higher since 2020

Online retail's share of total trade

Significance: medium

The ABS Retail Trade series has tracked online retail turnover holding a structurally higher share of total retail sales since the 2020 shift in shopping behaviour, rather than reverting to pre-2020 levels.

Source: ABS Retail Trade, Australia (abs.gov.au)

Apply regardless of platform

Consumer guarantee obligations

Significance: high

The ACCC confirms Australian Consumer Law guarantees on refunds, faulty goods and accurate advertising apply the same way to a Shopify storefront, a WooCommerce store or a fully custom build.

Source: ACCC - Australian Consumer Law (accc.gov.au)

$3 million annual turnover

Privacy Act small business threshold

Significance: medium

The Privacy Act's small business exemption applies only below $3 million annual turnover; e-commerce growth can push a retailer past that line and trigger full data handling obligations.

Source: Office of the Australian Information Commissioner

Methodology

Compiled from published Australian Bureau of Statistics retail trade data and current regulatory guidance from the ACCC and OAIC, current as at publication.

Integration in Practice

Connecting the accounting system and CRM

Xero and MYOB both offer native e-commerce connectors, and for a single-channel store they're usually enough. The trouble starts once a retailer sells through a second or third channel - a marketplace, a wholesale portal, a point-of-sale terminal in a physical store - and each one pushes orders to the ledger on its own schedule. Finance ends up reconciling by hand at month end, checking which system's version of an order is correct.

The same pattern shows up with HubSpot or another CRM: marketing wants a single customer record with full purchase history, but that record is split across the platform, the accounting system and sometimes a loyalty app. This is the kind of problem bespoke application development is suited to - building the layer that keeps those systems talking on one schedule instead of three, without replacing any of them.

When a custom build earns its cost

A fully custom platform earns its cost in a narrower set of cases: multi-vendor marketplaces with commission splits and payout logic no off-the-shelf platform handles cleanly, or a product catalogue and pricing model that's genuinely unusual - configurable products, trade pricing tiers, regulated categories. National Digital's build for Gratofy is one example: a custom marketplace development project where vendor payouts, inventory and multi-seller logistics needed to work as one system rather than a patchwork of plugins. For most retailers, though, the platform stays, and the effort goes into the handful of integrations that make it behave like one coherent system instead of five disconnected ones.

E-commerce Platform Questions, Answered

What's the difference between custom software development and an off-the-shelf platform?

Off-the-shelf platforms like Shopify or WooCommerce provide pre-built checkout, catalogue and payment features that suit most retailers out of the box. Custom software development means building specific functionality - an integration, a workflow, a data model - that no existing product handles for your particular combination of systems. Most Australian retailers use both: a standard platform for the storefront, and custom development for the integrations the platform can't cover.

When does a Shopify or WooCommerce store actually need custom development?

The signal is usually operational, not technical: stock counts across channels stop matching, freight quotes at checkout don't reflect what carriers actually invoice, or finance spends days each month manually reconciling orders against Xero or MYOB. Those are integration gaps rather than platform failures, and that's the point where a purpose-built connector or data layer typically pays back faster than switching platforms entirely.

Is custom development worth it, or should we manage inside the platform's app store?

App store plugins solve common problems well but were built for a generic use case, not your specific stack. They tend to break down once order volume grows or a business adds a second sales channel, because most weren't designed to reconcile data across systems. A narrowly scoped custom integration, built to solve the exact gap causing manual work, is usually cheaper to run long-term than layering several plugins that each own a slightly different version of the truth.

How long does building a custom e-commerce integration usually take?

Timelines depend heavily on scope. A single integration - syncing inventory between a warehouse system and a storefront, for example - is a smaller project than connecting freight, accounting and CRM together across multiple sales channels. Any credible provider should be able to explain, before work starts, which category a project falls into and why, rather than quoting one number that applies to every job.

Should we use a custom software development agency or build in-house?

It depends on whether the skill needed is a core, ongoing capability or a one-off build. Retailers with an internal development team often handle straightforward platform integrations themselves. A specialist custom software development company earns its place when the work spans multiple systems - payment, freight, accounting, inventory - and needs someone who has already solved that specific integration puzzle rather than learning it on the job.

Will a custom integration still work with Xero, MYOB or HubSpot?

Yes. Custom development typically extends these systems rather than replacing them. A well-built integration uses each platform's published API to keep the storefront, ledger and customer record in sync automatically, so Xero or MYOB stays the accounting system of record and HubSpot stays the CRM, without staff re-entering the same order data into each one by hand.