What selling online actually requires

The shopping cart and checkout flow are the visible part of an online store and, for most businesses, the easiest part to get right — most platforms handle this competently out of the box. What actually determines whether an online store works is the set of things behind the checkout button: accepting payment reliably, knowing what stock you actually have, getting the right item to the right address, handling returns without losing money on them, and charging the correct tax. Each of these is a genuine operational system, not a feature toggle.

The full list of what an ecommerce store actually requires, and where each is covered in depth

Requirement	What it involves	Covered in depth
Taking payment	A payment gateway, PCI compliance, and a merchant account or equivalent	Payment gateways explained
In-person and online payment together	If you also sell in person, keeping EFTPOS and online payments reconciled	EFTPOS vs online payments
Getting the product to the customer	Carriers, rates, packaging, delivery timeframes and tracking	Shipping and delivery setup
Knowing what you actually have in stock	Inventory tracking, and what happens when a listed item is out of stock	Managing stock and inventory online
Persuading someone to buy from a page	Product photography, descriptions, pricing display and trust signals	Product pages that actually sell
Handling the purchase that goes wrong	A returns and refunds process consistent with the ACL	Returns and refunds for online stores
Charging the right tax	GST on the sale, and the correct treatment of any imported goods or services	GST and online selling

Why the build is the smallest part of this list

A competent supplier can configure a shopping cart, product catalogue and checkout flow in a matter of days on any mainstream ecommerce platform. What cannot be configured in a day is a working relationship with a payment processor, an accurate stock count that matches physical reality, a shipping process that reliably gets orders out the door, and a returns policy your business can actually absorb financially. These are operational systems that exist around the website, not features inside it, and most of the ongoing effort of running an online store sits in this operational layer rather than in the site itself.

The decision that shapes everything else

Before any of the individual pieces above, decide what you are actually building: a small catalogue of products you fulfil yourself, a larger catalogue integrated with a wholesale or dropship supplier, or a storefront on an existing online marketplace such as Amazon or Etsy rather than your own domain. Each answer changes which of the requirements above you build yourself and which you inherit from a platform or partner — covered in marketplaces vs your own store.

What existing ecommerce platforms handle well, and what they don’t

Mainstream ecommerce platforms — Shopify, WooCommerce, Squarespace Commerce and similar — handle the checkout flow, basic payment gateway integration and standard product catalogue functionality competently out of the box. What they do not handle for you is the business decisions behind each piece: which payment gateway’s fees suit your transaction volume, how you will physically pack and ship an order, what your returns policy actually costs you if a meaningful share of orders come back, and whether your GST treatment is correct for every product and, where relevant, every jurisdiction you ship to. None of that changes the basic shopping experience customers browse through at checkout — it changes what happens once they’ve clicked “buy.”

The ongoing cost that isn’t on the invoice

None of the requirements above is a one-time setup cost. Stock has to be kept accurate continuously, orders have to be packed and shipped every day the store operates, payment disputes and chargebacks have to be handled as they arise, and customer enquiries about all of the above need a response. This ongoing operational load is the part most underestimated when a business first considers selling online — the stock side of it specifically is set out on managing stock and inventory online.

Why these seven requirements interact rather than sitting in isolation

None of the seven requirements above operates entirely independently — a shipping decision affects packaging and therefore product presentation; a payment gateway choice affects checkout design; a returns policy affects how product pages should set expectations. Treating each as a separate checklist item to tick off individually misses that a genuinely coherent store is one where these decisions were made together, with each one informed by the others, rather than bolted on sequentially as afterthoughts.

Why most of the genuine cost in an online store sits in the operational layer, not the build

A common miscalculation is treating the website build itself as the main investment and the operational requirements — payments, shipping, stock, returns, tax — as smaller supporting details. In practice, for a store expected to run for years, the ongoing operational effort of running these systems correctly typically exceeds the one-time cost of building the site itself, which is precisely why this cluster exists as a separate body of content from the pure design-and-build discussion covered in the ecommerce build service.

The minimum viable version of each requirement, for a genuinely small ecommerce store

A very small store — a handful of products, low order volume — can reasonably start with the simplest workable version of each requirement: a single payment gateway rather than several, flat-rate shipping rather than calculated, manual stock checking rather than automated synchronisation, and a simple, ACL-compliant returns policy stated in plain language. None of these minimal choices is wrong for a genuinely small operation; the risk is failing to revisit them as the business grows past the point where the minimal version remains adequate.

What to do next

Before commissioning a build, map out — on paper, before any code is written — how each of the seven requirements above will actually be handled for your specific products: who packs orders, which payment gateway you’ll use, what your returns policy will be, and whether you understand your GST obligations. A supplier can build to any of these; they cannot decide them for you.

What that build actually costs as a purchase, once these requirements are mapped, is set out on ecommerce website design in Australia.