Start with the catalogue, not the homepage
How the range really differs, who buys which part of it, and what your enquiries and returns say buyers keep asking. This is the briefing, and it decides everything after.
Websites and landing pages · Ecommerce website design · Sydney
Most online stores are not losing sales because they look wrong. They are losing them at one specific moment, when a buyer cannot find the single fact they came for, or discovers a cost they were not shown.
Grab the snowball. Give it a spin, and watch it grow as you scroll. Just like a store that answers first.
The short answer
Ecommerce website design is the work of building an online store around a particular catalogue and a particular set of buyers, rather than fitting the catalogue into a layout that was drawn before anybody saw it. It covers how products are grouped, what a product page has to prove, how search and filtering behave, and how much of the final cost a buyer can see before they commit to anything.
It is a different job from designing a site that explains a business. A brochure site succeeds if a reader understands you and gets in touch. A store succeeds only if a stranger can find one item among hundreds, satisfy themselves about a detail nobody thought to write down, and pay without meeting a number they were not expecting. Every one of those is a structural decision, and none of them is a matter of taste.
Which is why the build starts with the catalogue rather than the homepage. How many products, how they genuinely differ, what buyers ask before they order, what your delivery actually costs to each part of the country, and whether you sell to trade and retail at once. Get those right and the design work becomes straightforward. Get them wrong and no amount of polish recovers it. Because our Snowball SEO platform automates the auditing, the tracking and the reporting other agencies bill by the hour, more of the budget goes into that structural work.
The difference
Five places, in a fixed order, and each one narrows what is left for the next. Knowing which of them is costing you most is the whole of the briefing, because fixing them out of order wastes the budget.
On the ranking side of the same store, which is a separate discipline with separate decisions, our guide to ecommerce SEO in Australia covers what a category and product structure has to do to be found in the first place.
The cost
How many products you have and how genuinely they differ, how much of your operation the store has to talk to, and whether you are starting again or rebuilding around a catalogue that already works. Two stores with the same number of items can be very different jobs.
One catalogue, one buyer type
A clean structure, product pages that answer properly, and a checkout with no surprises in it. The shortest build, and the one most small ranges should start with.
Variants, trade pricing, integrations
Where the catalogue has real complexity in it, or the store has to agree with an inventory system, an accounts package or a warehouse. Most of the effort is here.
Keeping what already earns
Replacing the structure without losing the rankings, the URLs or the customer history the current store has accumulated. Slower, and the sequencing matters more than the design.
We quote after looking at your actual catalogue and your actual enquiries, so the scope follows the range rather than a rate card. On budget ranges more broadly, our guide to what a website costs in Australia sets out the shape of it.
How complicated the catalogue really is matters more than how large it is, which is why a hundred simple products can cost less to build for than twenty configurable ones.
Two things get sold hard into Australian ecommerce budgets and return very little. Both are worth recognising before you read a proposal.
The first is a homepage nobody sees. A great deal of design attention goes to the front of a store, when most buyers arrive from a search directly onto a product or a category and never see it at all. The money belongs where they land.
The second is a plugin for every problem. A store assembled from twenty third-party add-ons works on the day it launches and becomes progressively harder to change, because each one has its own update cycle and its own opinion about your checkout. Fewer moving parts is worth paying for, and it is rarely quoted as a feature because it does not look like one.
The scope
Six things, and the first two decide how much value the other four can add. The last is what stops the store quietly decaying after launch.
Categories and filters that match how people describe your range rather than how it is stocked, so a buyer who knows roughly what they want can reach it in two moves.
The size, the fit, the stock position, the compatibility, the delivery date. One unanswered question is worth more lost orders than any amount of layout.
The full delivered cost visible before the checkout rather than inside it, and every step that exists earning its place.
On the platform that suits the catalogue, talking to the inventory, accounts or fulfilment systems the business already runs on.
Category and product structure that search engines and AI answers can read, decided during the build rather than retrofitted after launch.
Set up so the five drop-off points can be told apart, because a single conversion figure cannot tell you which one to fix.
The return
A theme is the right answer more often than agencies admit, and the wrong answer in a way that is expensive to discover late. The honest test is what your catalogue asks for, not what your competitors have.
A small range of simple products, one type of buyer, delivery that costs roughly the same everywhere, and no other system to talk to. In that case the defaults a theme ships with are close to the decisions you would have made anyway, and paying to remake them is waste.
Configurable products, trade and retail buyers at once, delivery that varies sharply by weight or destination, or stock that lives in another system. Each of those is a place where the theme has already decided something, and working against a default is consistently more expensive than building past it.
The failure we are called in to repair is nearly always the same one: a store that fitted the range when it launched, then grew two product lines and a trade account, and is now held together by add-ons that each solve one problem and argue with each other. On when a rebuild is worth it rather than another patch, our guide to website redesign sets out the test we use.
The process
The structural decisions land early and cheaply. The build is the predictable part. What genuinely takes time is product content, and it is the part most quotes are quietly optimistic about.
How the range really differs, who buys which part of it, and what your enquiries and returns say buyers keep asking. This is the briefing, and it decides everything after.
Where your current store loses people, or where a new one is most likely to. Ranked, so the budget goes to the expensive leak rather than the visible one.
Categories, filters, the product template and the checkout flow agreed before anything is designed, because these are the decisions that are expensive to reverse later.
Chosen for your range and your integrations. We will say plainly when the honest answer is a theme with a light touch rather than a build.
Product copy, imagery and specifications, with the real time it takes stated up front rather than discovered in week six.
Measurement that separates the five drop-off points, so the first quarter after launch improves the store instead of guessing at it.
The brief
Four questions. Each one separates an agency that has run a store through a second Christmas from one that has only ever launched them.
A useful answer names one and shows what it was read from. An agency that cannot tell arrival from discovery from checkout is going to rebuild whatever is easiest to rebuild, and that is almost never the expensive leak.
Ask for the redirect plan before the design. A store that launches beautifully and loses its category rankings has cost you more than it earned, and the sequencing that prevents it has to be decided at the start, not at the end.
Every one is a future update that can break your checkout. The answer should be a number, with a reason for each, and an agency that has maintained stores will give you a smaller number than one that has only built them.
This is where ecommerce projects actually slip. If the quote assumes you will supply four hundred product descriptions and nobody has said so out loud, the launch date is not real.
We are happy to answer all four before you commit, and to say when a theme and a tidy-up would serve you better than a build. If the store is sound and the problem is that nobody finds it, that is a different job and our search engine optimisation service is where it belongs.
Start here
Send us the store, or the catalogue if there is not one yet. The check is a working session rather than a sales call, and you leave with three things whether or not you appoint us.
Good questions
Building an online store around a particular catalogue and a particular set of buyers: how products are grouped and filtered, what each product page has to prove, how much of the delivered cost is visible before the checkout, and which other systems the store has to agree with. The visual design follows those decisions rather than leading them.
Not from 1 October 2026. The Reserve Bank removed its prohibition on no-surcharge rules, and eftpos, Mastercard and Visa each then decided to impose one from that date; American Express, which the Bank does not regulate, decided the same separately. It covers card surcharges only, so weekend, public holiday, booking and service fees are untouched, and so are the fees your payment provider charges you. If your checkout adds a card fee today, it has to come out, and the cost belongs in your prices instead.
Yes. The Reserve Bank states that discounts for particular payment methods remain allowed, and that removing the prohibition on no-surcharge rules is not intended to prevent them. So steering buyers towards a cheaper method is still possible; it just has to be done as a discount rather than as a penalty.
A theme is genuinely enough for a small range of simple products, one type of buyer, delivery that costs much the same everywhere and no other system to talk to. It starts to cost you once you have configurable products, trade and retail buyers at once, delivery that varies sharply, or stock held somewhere else.
The structure and the build are the predictable parts. Product content is not: copy, imagery and specifications for a real catalogue routinely take longer than everything else combined, and a timeline that does not say who is writing it and by when is not a timeline.
It can, and that is decided by the redirect and structure plan rather than by the design. The plan has to exist before anything is built, which is the single question worth asking an agency first if you already have a store that earns.
For the build itself, location matters less than whether the agency has maintained stores rather than only launched them. It matters more where the work touches photography, product content or stock you physically have, which is easier when somebody can stand in the warehouse.