An ecommerce website brief needs to describe how an order will work, from choosing a product to receiving it. Page designs matter, but they cannot settle an unclear stock process, missing product information or a delivery rule nobody has agreed on.
For a Melbourne retailer selling locally or across Australia, a useful starting point is a small set of real products and order scenarios. You can use them to define the work, compare proposals and check the finished store. You do not need a polished specification before the first conversation.
Write down who is buying, what they need to choose and what could stop them. A customer ordering a single item for delivery has different needs from a trade customer requesting bulk pricing or someone booking local collection.
Choose a primary launch goal and the evidence you will use to assess it. That might be completed orders with correct payment and fulfilment records. If your store is primarily a catalogue that generates quotes, define a received, usable quote request instead. Keep those journeys separate when describing the scope.
Record the practical constraints too: a fixed trading date, who can prepare content, existing contracts and the person who will approve decisions. These determine what can reasonably be included in the first release.
Select examples that expose the differences in your catalogue: a straightforward item, one with size or colour options, and an item with an unusual delivery or ordering requirement. If you sell bundles, subscriptions, made-to-order goods or restricted combinations, include a relevant example rather than assuming the standard product setup covers it.
For each example, gather its identifier or SKU, name, description, price, images, options, stock behaviour and any dimensions or weight needed for delivery. Identify who owns each field and where its approved value comes from. Keep the master copy in an agreed place so that corrections do not spread across conflicting spreadsheets and email attachments.
Agree on a small test import before moving the full catalogue. WooCommerce’s product import guidance recommends testing a sample on staging and checking the resulting products. Shopify’s CSV guidance explains that included blank fields can overwrite existing values when matching products are overwritten. A supplier export needs checking against the selected platform’s format.
Give the developer order examples, not just the instruction “set up shipping”. Include a normal delivery, a regional or otherwise excluded destination where relevant, a large or heavy item, and local collection if you offer it. State what should happen when an order contains products with different delivery rules.
For each scenario, decide what the customer should see, how the charge is calculated and how staff will handle the order. Add delivery estimates, collection instructions, stock shortages and cancellation or return workflows to the brief. Identify who supplies and approves your customer policies and tax settings.
The point is to turn an exception into an explicit decision before someone encounters it at checkout. Any rule you have not settled should remain an open question in the proposal, with an owner and a decision date.
List the systems that must exchange information: stock, accounting, point of sale, fulfilment, customer records or email marketing. For each connection, describe what moves, in which direction, how often and which system is authoritative.
For example, if stock is managed elsewhere, what happens when a store order arrives before the next stock update? If an accounting connection fails, who notices and how is the order reconciled? Ask the implementer to explain the supported workflow, recurring charges, access requirements and failure handling before treating an integration as included.
Give a named person responsibility for each external account. Account ownership, setup work and ongoing support belong in the scope alongside the connection itself.
Keep a record of the current store’s important product, category and information URLs, together with useful search and sales baselines. Ask which addresses can stay the same. Where a necessary change moves a page, map its old address to the relevant replacement and include redirect checking in the work.
Google’s site-move guidance covers URL mapping, redirects, internal links, canonicals and monitoring. That planning reduces avoidable mistakes; it does not guarantee unchanged rankings through a migration.
Also decide what happens to products, customer accounts, order history, discounts, subscriptions and gift balances where applicable. Confirm which data can move through the agreed method, what needs a separate process and what customers or staff must do. Assign responsibility for the final stock and order reconciliation around the changeover.
Use your representative products and order scenarios as the acceptance checklist. Ask the proposal to identify who runs each check and what evidence will be retained:
Payment testing should use the provider’s supported test method where available. Any real transaction or refund needs the account owner’s approval and a reconciliation plan. Your live store’s acceptance checks should be specific enough that both parties can recognise when the agreed work is complete.
Sort the brief into what is necessary to trade, what is useful for the next release and what still needs investigation. A feature that depends on an unresolved supplier or integration should not quietly become a promise with a fixed launch date.
Before accepting a quote, identify the catalogue and content allowance, design and review rounds, integration responsibilities, migration work, testing, training and post-launch support. Ask for platform, hosting, licence and maintenance charges separately from the build fee, and clarify who owns the accounts and working assets.
A larger feature list does not automatically make a stronger first release. A clearly scoped store that staff can operate gives you a firmer basis for deciding what to improve next.
Start with your current website, representative products, intended delivery area and the most difficult order you need to handle. Add the people responsible for content, stock and approvals, plus the timing or budget constraints that matter. Unresolved decisions are useful inputs to discovery.
If you are still comparing providers, read our guide to choosing an ecommerce website developer in Melbourne. For the work G29 can discuss and scope, see ecommerce website services or start a project enquiry.