A shop is not ready just because its product grid looks finished. It is ready when a customer can understand the product, pay successfully and receive the right information, and your team can fulfil the order. Use this checklist to prepare the operational details before design work starts.
Organise the first product catalogue
Start with the products you are actually ready to sell. For each one, prepare a clear name, description, price, stock position and original images. Include the details a customer cannot check in person: dimensions, materials, compatibility, care instructions or what is in the box, as applicable.
Products with colours, sizes or other variants need a consistent structure. Record which combinations exist and whether they have different stock or prices. A developer cannot reliably infer those rules from a folder of photographs.
- Use consistent product names and category labels.
- Supply images you own or are licensed to use.
- Confirm whether stock is tracked online, in a physical shop, or both.
- Identify any products that need special delivery arrangements.
Define delivery before designing checkout
Write down the destinations you serve, delivery prices, dispatch times and any order thresholds. Check whether remote areas, heavy items or mixed baskets need different treatment. A simple flat-rate rule is easier to launch than a complex carrier integration, but it must reflect the service you can deliver.
Distinguish dispatch time from the carrier's delivery estimate. Make collection options clear if you offer them. Decide what happens when an item is unavailable after an order is placed and who handles the customer communication.
Choose and test the payment flow
The payment provider account should belong to the business. Account verification, supported payment methods and settlement arrangements need to be checked with that provider. Payment processing fees are separate from website development unless your proposal explicitly says otherwise.
Test a successful payment, a declined payment and a cancelled checkout. The store should not mark an order paid simply because a visitor opens a success page. Payment confirmation needs to come from a verified provider response. Stripe explains this distinction in its Checkout fulfilment guidance.
Follow an order all the way through
Place a test order and act as both the customer and the shop owner. Check the order total, delivery selection, confirmation screen, email, order record and fulfilment steps. Test a refund using the provider's test environment where supported.
Check the destination of the shop notification emails. A beautifully formatted message is not enough if it goes to an inbox nobody monitors. Give staff only the access they need and document the everyday order process before handover.
Review the small-screen experience
On a phone, a customer should be able to inspect images, select a variant and reach the basket without accidental taps or overlapping controls. Check error messages with the on-screen keyboard open. Try a long delivery address and a basket containing more than one item.
Keep important information close to the decision: product price, delivery context, stock status and the next step. Do not hide essential conditions behind a promotional banner or rely on hover interactions.
Prepare policies and customer support
Agree who supplies your delivery, returns, privacy and sales information. These should reflect your actual business and products, rather than being copied from another shop. Get appropriate professional advice for your obligations; a website build is not legal advice.
Finally, decide how customers can ask about an order and how you will identify it. The goal is a manageable store, not just a launched store.
Our starter ecommerce scope is designed for a focused catalogue with standard requirements. Send us your product count, delivery rules and any existing systems through the shop enquiry form so we can confirm the right scope before quoting.
