Ask three Melbourne agencies to quote an online store and you can get three numbers that are not close to each other. Same conversation, same products, wildly different totals.
That is not usually one of them being greedy. It is that an ecommerce quote is mostly made of things that are not the website, and each agency has made different assumptions about who is doing them.
Once you know what those things are, the quotes stop being mysterious and start being comparable.
This page is about the build. If you are still deciding whether you need a store at all, when to build an eCommerce store instead of a brochure website is the earlier question, and if you are weighing up platforms, WordPress, Shopify or WooCommerce covers that one.
Most of the cost is not the website
Design and development is often the smaller half of an ecommerce invoice. The rest is:
Product data. Payment, shipping and tax setup. Integrations with whatever you already run. Migration, if a store already exists. Testing the whole thing actually takes money correctly.
A brochure site is largely a design and content job. A store is an operations project with a website attached, which is why quoting one from a page count produces a number that means nothing.
Product data is the variable that decides the number
This is the big one and almost nobody expects it.
Forty products is a small job. Four hundred is a different project. And the real multiplier is variants: a shirt in five sizes and four colours is twenty combinations, each needing its own stock number, and possibly its own image.
Then every product needs images that are consistent with each other, and a description with sizes, materials, care instructions and shipping dimensions. Written once, properly, per product.
So the question that moves an ecommerce quote more than any design decision is: who is producing that, you or the agency?
If you supply it, the build is cheaper and faster, and you keep control of how your products are described. If the agency produces it, you are buying a photography and copywriting project that happens to be inside a website quote. Neither is wrong. But a quote that includes it and a quote that assumes you will do it are not comparable, and they rarely say which they are.
The practical advice: ask every quote to separate design and development from product data. Most of the gap between three quotes lives in that line.
Theme or custom, and why the honest answer is usually theme
Agencies make more money on custom builds. We will still tell you that most Melbourne small businesses should use a well chosen theme, configured properly.
A good theme is maintained by somebody else, tested across devices and browsers you will never see, updated when the platform changes, and costs a fraction. The gap between a theme configured carefully by someone who knows what they are doing and a custom build is much smaller than the price difference suggests, and most of what makes a store feel good is photography, product organisation and checkout flow rather than bespoke layout.
Custom genuinely earns its place in three cases. When the way you sell does not fit a product and variant model, which is common for made-to-order and configurable goods. When you need a buying flow no theme supports. And when an integration has to behave in a way off-the-shelf tools will not. We build custom in exactly those cases, as part of our custom software and integration work.
Custom because you want to look different from other stores is the most expensive way to buy a small visual difference.
Every integration is its own small project
“It needs to talk to our accounting system” is one sentence and anywhere from an afternoon to a fortnight.
The common ones for a Melbourne retailer are accounting, inventory, a point of sale if you also sell in a shop, shipping and label printing, and email marketing. Some have mature, well supported connections and are genuinely quick. Others need middleware or custom work, especially where the two systems disagree about what a product is.
The one that catches people is point of sale. If you sell in person and online, you need one source of truth for stock, and getting that right is its own piece of work rather than a checkbox. Shopify or WooCommerce for Australian retailers goes into which platform suits that situation.
Worth doing before you ask for quotes: list every system the store has to speak to, by name. That list changes the price more than the design brief does.

The Australian setup that rarely appears as a line item
A few things are specific to selling here and quietly consume build time.
GST handling and whether prices display inclusive, which is what Australian shoppers expect and what the law requires for consumer pricing. Shipping zones and rates that reflect what it actually costs to send to Perth rather than a flat number chosen optimistically. Click and collect if you have a shop. Payment methods beyond card, because buy now pay later is close to expected in some categories here. And a returns process that satisfies consumer guarantees rather than a policy page copied from an American store.
None of it is difficult. All of it takes time, and it tends to be absorbed into a quote rather than stated, which is part of why two quotes differ.
Migrating an existing store costs more than starting clean
If you already sell online, replacing the store is harder than building the first one, and quotes often underestimate it.
Products, variants, customers and order history all have to move. URLs have to be redirected or you lose the search rankings the old store earned, which is the single most common way a replatform goes badly. And the messier the existing data, the longer all of it takes.
Good reasons to migrate: you have outgrown the platform, the costs climb with turnover in a way that no longer works, or you need something the current system genuinely cannot do. Disliking the admin screen is not a good reason. When to rebuild instead of tweaking applies here as much as it does to a brochure site.
What you are actually choosing between
Every ecommerce quote is a position on three trade-offs, and it is worth knowing which one you are being sold.
Cheaper build against your own time later. The lower the quote, the more of the product data, setup and fiddling lands on you. That can be the right trade if you have the time and you would rather keep the cash. It is a bad trade if you are already the person doing everything.
Capability against maintenance. More custom functionality means more that can break, more that needs updating, and more that depends on knowing how it was built. Ask who maintains it and what that costs before you buy it.
Convenience against ownership. Hosted platforms are easier and you rent them. Self-hosted is more work and you own it. Both are legitimate and the two platform posts above argue the detail.
On comparing the quotes themselves, the arithmetic from what an agency should cost applies: convert the number into hours and ask whether the scope fits inside them.
Start smaller than feels right
The stores that stall are almost never the ones that launched too simple. They are the ones that tried to load four hundred products before going live and ran out of momentum at ninety.
Launch with your best sellers, one payment method and shipping that is simple enough to be right. Find out what people actually buy and what it really costs you to pack and post it. Then expand with real information instead of assumptions.
It also gets the store earning sooner, which is the only thing that makes the rest of the budget easier.
Frequently Asked Questions
Why do eCommerce quotes vary so much for the same brief?
Because the brief is rarely the same once you look underneath it. The two questions that move the number most are how many products there are and who is preparing the product data. Forty products with photos and descriptions already written is a very different job from four hundred with none, even though both get described as an online store. Ask any quote you receive to separate design and development from product data and integrations, and the differences between quotes usually explain themselves.
Is a custom eCommerce site worth it over a theme?
For most Melbourne small businesses, no, and we will say so before quoting the custom option. A well chosen theme configured properly covers what the overwhelming majority of stores need, it is maintained by somebody else, and it costs a fraction. Custom earns its place when the way you sell genuinely does not fit a product and variant model, when you need a buying flow no theme supports, or when an integration has to behave in a way off-the-shelf tools will not. Custom for the sake of looking different is the most expensive way to buy a small visual difference.
How much of an eCommerce build is product photography and copy?
On a catalogue of any size it is routinely the largest single line, and it is the one owners do not expect. Every product needs consistent images and real descriptions with sizes, materials and shipping dimensions. If you supply all of it, the build is cheaper and faster. If the agency produces it, you are paying for a photography and copywriting project that happens to sit inside a website quote. Neither is wrong, but you should know which one you are buying.
Should I move my existing store to a new platform?
Only with a clear reason, because migration usually costs more than building fresh. Products, variants, customers, order history, URLs and redirects all have to move without breaking search rankings or losing data, and the messier the existing store the longer that takes. Outgrowing the platform, costs that climb with turnover, or an integration the current system genuinely cannot support are good reasons. Disliking the admin screen is not.
Can I start smaller and expand later?
Yes, and for most businesses that is the right call. Launch with your best selling products rather than the whole catalogue, one payment method and simple shipping, and add from there once you know what people actually buy and what it costs you to fulfil. Stores that stall usually stall because the owner committed to loading four hundred products before launch and ran out of momentum at ninety.
The bottom line
An ecommerce quote is not really a quote for a website. It is a quote for product data, integrations, Australian setup and a website, in roughly that order of impact on the number.
So when the three quotes come back at different numbers, do not start by comparing totals. Ask each one to split design and development from product data and integrations, and tell them who is supplying the photography and descriptions. The spread usually collapses once everyone is quoting the same job.
And be sceptical of custom unless one of the three real reasons applies. A theme configured well by someone who knows the platform will serve most Melbourne retailers better than a bespoke build they cannot afford to maintain.
If you want somebody to read the quotes you already have and tell you where they differ, have a chat with us, or see how we approach eCommerce builds. We will tell you when a store is the wrong thing to build.