Ecommerce website packages and what a store really costs

An online store costs more than a brochure site, and the reason is not that the pages are prettier. It is that a store is a piece of operational software that happens to have a website attached. It takes money, calculates tax, quotes freight, manages stock, and produces records that eventually have to reconcile with your accounting. Every one of those is a system with its own rules, its own failure modes and its own ongoing cost — the same systems a physical retail shop already runs, just rebuilt for a shopper who never walks through a door.

Search demand for the packaged version is small but real: “ecommerce website design packages” was measured at 70 searches a month at a keyword difficulty of 0 on 31 July 2026, recorded in research/national-volume-au.json. Low volume, and the people asking are usually about to spend a meaningful amount of money.

This page covers what actually makes a store cost more, and which of those costs never stop.

Product data is the largest hidden cost

The most underestimated line in any ecommerce project is getting the products into the store.

Every product needs a name, a description, a price, a stock keeping unit, an image or several, dimensions and weight for freight calculation, tax treatment, stock levels, and its place in a category structure. Variants multiply this. A shirt in five sizes and four colours is twenty sellable items, each with its own code, its own stock count and potentially its own image.

Nobody enjoys this work and almost nobody budgets for it properly. It can be done three ways, and the choice materially changes the figure: you supply a clean spreadsheet in the format the platform imports, in which case it is quick; the supplier builds that spreadsheet from whatever you have, which is slow and billed; or products are entered by hand, which is the slowest option of all and is what happens by default when nobody planned.

Ask directly how product loading is handled, how many products are included, and what the cost is per product beyond that. A quote that says “products loaded” without a number attached is not a quote.

The related question is where the data lives. If you already run point-of-sale or inventory software, ask whether the store will sync with it or whether you will be maintaining stock levels in two places forever. Maintaining two is a daily operational cost that never appears in any build quote.

The payment gateway

Taking money online means a payment provider, and payment providers charge on every transaction for as long as you trade. That fee is entirely separate from what you pay to have the store built, and over a few years of trading it will typically exceed the build.

What to establish before you choose:

• The per-transaction cost, including any fixed component, and whether it differs for international cards or for payment methods like buy-now-pay-later.
• Whether there is a monthly account fee on top of transaction fees.
• Settlement timing. How many days between a customer paying and the money reaching your account, because this is your working capital.
• Chargeback handling and what a disputed transaction costs you.
• Whether the checkout keeps the customer on your site or sends them elsewhere, since that affects both the build and your completion rate.
• What onboarding requires. Providers verify businesses, and that process can take longer than the remaining build.

The build cost of connecting a mainstream gateway to a mainstream platform is usually modest, because it is a well-trodden path. The build cost of an unusual gateway, or a gateway your bank has recommended that nobody has integrated before, is not modest at all.

Shipping rules are where stores get complicated

Freight is the part clients think will be simple and suppliers know will not.

Flat-rate shipping is straightforward. Everything beyond it is logic that has to be built and tested: rates by weight, rates by cart value, rates by destination, free shipping over a threshold, separate handling for bulky or dangerous goods, click and collect, local delivery zones, and live rate lookups against a carrier’s system.

Australia adds its own difficulties. Distances are long, regional and remote surcharges are real, and the difference between metropolitan and regional freight on a heavy item can exceed the margin on the product. If your catalogue mixes small light items with large heavy ones, your shipping and delivery logic is a genuine piece of work, and it needs testing against real addresses in real regions before launch, not after. Packaging is a related, separate cost most quotes leave out entirely: a box, void fill and a satchel or parcel large enough for the actual product add up per order and belong in your margin calculation, not just your shipping calculation.

Ask what shipping and delivery scenarios are included, how many carrier integrations, whether fulfilment (picking, packing and dispatch) is something your business handles in-house or through a third party, and what testing is done against actual postcodes.

GST on what you sell

This is separate from the GST on your build quote, and both matter.

Your store has to charge GST correctly on the products you sell, display prices in a way that meets Australian requirements for showing a total price to consumers, and produce tax invoices that your accountant can work with. Most platforms handle standard cases well once configured. The configuration still has to be done deliberately, by someone who knows which way your business works.

Where it needs care:

• Whether displayed prices include GST. For consumer sales in Australia the expectation is that a customer sees the total they will pay.
• GST-free items. Certain foods, some medical items and others are treated differently. If your catalogue includes any, the treatment has to be set product by product, and getting it wrong is a compliance problem rather than a cosmetic one.
• Whether GST applies to shipping in your circumstances.
• Overseas customers, if you sell internationally, where different rules apply.
• Whether your business is registered for GST at all, which changes what the store should be doing.

Two points worth stating plainly. First, GST configuration is your responsibility as the trader, not your web supplier’s, whatever they set up on your behalf. Second, this is a question for your accountant, not for a web page, and the half hour it costs to ask is cheap compared with reconciling a year of incorrectly taxed orders.

Also confirm, separately, whether the build quote itself is inclusive or exclusive of GST. Across the nine Australian cost pages checked on 31 July 2026 and recorded in research/pricing-bands.json, none stated it.

Ongoing platform costs, which are not part of the build

This is the section most likely to change your decision, and the one most often absent from a quote.

An online store carries recurring costs regardless of who built it:

• Platform subscription, if you are on a hosted platform, charged monthly or annually and typically stepped by feature tier or sales volume.
• Transaction fees to the payment provider, on every order, forever.
• Additional platform fees charged by some hosted platforms when you use an external payment provider rather than theirs.
• Applications and extensions. Stores accumulate these. Subscriptions, reviews, loyalty, advanced shipping, accounting sync, marketing tools. Each carries a monthly fee, and it is common for the combined total of small monthly applications to exceed the platform subscription itself.
• Hosting and licences, if you are on a self-hosted platform, where you pay less in subscription and more in maintenance responsibility.
• Email and notification services for order confirmations and shipping updates.
• Security and compliance obligations attached to handling payments, which are lighter if the payment provider handles card data and heavier if anything touches your systems.
• Maintenance, which for a store is not optional in the way it can be argued for a brochure site. A broken contact form costs you an enquiry. A broken checkout costs you every order until someone notices. This is covered on website maintenance cost.

Ongoing maintenance, per month Figures withheld. Each band must be drawn from at least 10 delivered projects and the dataset must be reviewed and released before any number is shown.

What it is	Typical	Range	Projects
Ongoing maintenance (per month)	Withheld — not yet reviewed

Figures not published. The pricing dataset has not been reviewed and released, so no figure is shown here. The site is built to refuse to render prices in this state rather than show a provisional number. What is published and what is not.

Why every figure on this page is withheld (6 reasons)

• dataset status is "PLACEHOLDER_UNREVIEWED", not "VERIFIED"
• dataset publishable is false, not true
• GST treatment has not been stated — ACL s48 requires it explicitly, at equal prominence
• the dataset has not been dated — undated figures are not citable
• the collection method has not been written down — an unsourced figure is an assertion
• no band passes the band-level audit

The useful exercise is to build a twelve-month total: the build, plus every recurring item above, plus an allowance for transaction fees at your expected turnover. Do it before you choose a platform, because platform choice drives most of the recurring side and it is expensive to reverse.

Common questions about ecommerce packages

Why does an online store cost more than a brochure site? Because a store is operational software with a website attached. It takes money, calculates tax, quotes freight, manages stock and produces records that have to reconcile with your accounting. Each of those is a system with its own rules, its own failure modes and its own ongoing cost.

What ongoing costs does a store carry after the build? Platform subscription, payment transaction fees on every order, additional platform fees on some hosted platforms when you use an external payment provider, application and extension subscriptions, hosting and licences if self-hosted, email and notification services, and maintenance. Build a twelve-month total before choosing a platform.

What a store build should include

When comparing ecommerce quotes, check each of these is addressed explicitly rather than assumed:

• Number of products and variants included, and the rate beyond it.
• Category structure and how customers filter and search the catalogue.
• The checkout flow, including guest checkout and whether accounts are required.
• Which payment methods are configured.
• Shipping rules and how many scenarios are covered.
• Tax configuration and who is responsible for confirming it.
• Order notification emails, and whether they are branded or platform defaults.
• Inventory sync with any existing system.
• Testing, including real test transactions through the live gateway before launch.
• Handover and training. Someone in your business has to be able to add a product, refund an order and adjust stock, and being taught that is part of the job.
• Who owns the store and the data, and how you would export both if you left.

Ecommerce and online store builds Figures withheld. Each band must be drawn from at least 10 delivered projects and the dataset must be reviewed and released before any number is shown.

What it is	Typical	Range	Projects
Ecommerce / online store	Withheld — not yet reviewed

Figures not published. The pricing dataset has not been reviewed and released, so no figure is shown here. The site is built to refuse to render prices in this state rather than show a provisional number. What is published and what is not.

Why every figure on this page is withheld (6 reasons)

• dataset status is "PLACEHOLDER_UNREVIEWED", not "VERIFIED"
• dataset publishable is false, not true
• GST treatment has not been stated — ACL s48 requires it explicitly, at equal prominence
• the dataset has not been dated — undated figures are not citable
• the collection method has not been written down — an unsourced figure is an assertion
• no band passes the band-level audit

The band figures are withheld while the underlying dataset is marked as unreviewed, and the reasons are itemised in the pricing dataset. When they appear they will carry the number of projects behind them, the period they cover, and the scope each band assumes, since a store band without a product count attached is close to meaningless.

The general version of these questions is on how a website quote is built up, and the fixed-bundle version is on website design packages.