PLATE P.03 — ONLINE STORE

Ecommerce website development in Adelaide

A custom online store is a shop built as one piece of software — catalogue, checkout, stock and fulfilment built for how you actually sell, not a theme with plugins bolted on. Ozwebnet builds custom ecommerce websites from scratch in Adelaide, South Australia, for businesses across Australia. You receive the source code and the IP, under one fixed quote staged against milestones.

START A BRIEF → WHAT IS INCLUDED ↓
FIG. P.03 — A SHOP COUNTER: TILL, TERMINAL, PARCEL AND STOCK BINS · HOVER TO POUR
GENERAL NOTES 02 / 08

What is a custom ecommerce website?

An online store whose catalogue, cart, checkout, stock and dispatch are one piece of software written for your business, instead of a hosted platform's theme with an app for every gap. Your products, pricing rules and fulfilment steps are built in, not bolted on, and the code is yours.

SECTION A–A 03 / 08

Who should build a custom online store rather than use a hosted platform?

BUILT FOR
Merchants whose catalogue, pricing or fulfilment no longer fits a platform's rules; stores that need to talk to a warehouse, POS or accounting.
REPLACES
Plugin towers, platform subscription and app fees, the theme everyone else runs.
NOT FOR
A small catalogue that a hosted platform serves well today — we will say so.
SCHEDULE OF WORKS 04 / 08

What is included in a custom online store build?

01

Catalogue and product data

Products, variants, prices, images and stock on hand, held as your own data rather than a platform's.

02

Cart, checkout and payment gateway connection

The cart applies your pricing rules; checkout hands the payment to the gateway and records the result against the order.

03

Stock and fulfilment flow

A paid order becomes a pick list, and the stock count moves with it as the order is picked and dispatched.

04

Customer accounts and order history

Customers see their orders and addresses in one place; your staff see the same order record.

05

Reporting on sales and stock

What sold, what is on hand and what is moving, drawn from the store's own records rather than an exported spreadsheet.

06

Connections to your warehouse, accounting or POS

Orders, stock levels and invoices move between the store and the systems you already run, so data entered once moves where it is needed.

07

Handover of the source code with the IP assigned to you

The store is yours: the code, the rights, and a working build at every milestone along the way.

TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.

STAGES 05 / 08

How is an online store built and priced?

One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.

SEE THE FIVE STAGES ANIMATED →
  1. 01 SURVEY

    Discovery

    We learn what you sell, how you price it, and how an order leaves the building.

  2. 02 BLUEPRINT

    Specification

    Catalogue, checkout, stock and fulfilment are specified in writing; the fixed quote is set here.

  3. 03 FORGE

    Build

    Built station by station — catalogue, cart, checkout, fulfilment — each a working milestone.

  4. 04 TEMPER

    Testing

    Test orders placed, paid and picked before launch.

  5. 05 DEPLOY

    Launch

    The store goes live, and you receive the source code with the IP assigned to you.

DETAIL 1 — ORDER FLOW, SECTION B–B 06 / 08

How an order moves through a custom online store

Follow one order through the store. Six stations, one record — browse, cart, pay, pick, ship and return all read and write the same order, because they are one piece of software rather than six apps passing messages.

BROWSE
The catalogue reads your own product data — variants, prices, stock on hand.
CART
The cart applies the pricing rules agreed at the specification stage, as part of the store rather than an app bolted on.
PAY
Checkout hands the payment to the gateway chosen at the specification stage and records the result against the order.
PICK
A paid order becomes a pick list against numbered bins; the stock count moves with it.
SHIP
The dispatched order is marked as sent on the same record the customer sees.
RETURN
A return, where the store handles them, is logged against the same order so the stock count and the customer's record stay in step.
B B BROWSE CART PICK SHIP RETURN PAY 01 02 03 04 05 06 CATALOGUE PRICE RULES GATEWAY PICK LIST LABEL SAME ORDER STOCK BACK TO THE BIN · REFUND AGAINST THE PAYMENT FRONT OF THE COUNTER — THE CUSTOMER'S SIDE BEHIND THE COUNTER — YOUR SIDE ONE SYSTEM — ONE RECORD OF EACH ORDER, FROM FIRST CLICK TO RETURN SECTION B–B TAKEN ALONG THE ORDER PATH · NOT TO SCALE
DETAIL 1 — ONE ORDER THROUGH SIX STATIONS, ONE RECORD THROUGHOUT
REQUESTS FOR INFORMATION 07 / 08

Questions before you brief us

RFI-01How much does a custom ecommerce website cost?

One fixed quote, set in writing before the build and staged against milestones.

RFI-02Can the store connect to our warehouse, accounting or POS?

Yes — that is systems integration, built into the same quote or scoped as its own project.

RFI-03Are we locked in?

No. You hold the source code and the IP.

RFI-04Do you work with stores outside Adelaide?

Yes. Adelaide first, Australia-wide, remote-capable.

RFI-05What if we stop partway?

Stop at any milestone and keep a working system.

ISSUE 08 / 08

Start a brief for an online store.

One email is the whole front door. Tell us what you run or sell, what breaks today, and when you need it working. By appointment only.

BUILD YOUR BRIEF → [email protected]
RELATED SHEETS Systems integration and automation for Australian businesses → Custom web application development in Adelaide →