Worked example: Ecommerce / DTC
An illustrative DTC buying journey
Try Aurora's illustrative product, basket and order-review journey. Inspect migration checks, compare DTC website costs and scope your own store.
A demonstration build on one of our own live demos, not a client project. It shows exactly how we’d approach yours.
Aurora is our own fictional direct-to-consumer store. Choose a product and colour, edit the basket and review an example order in the browser. The demonstration ends with an illustrative order preview; payment, customer-data capture and fulfilment remain separate production work. Try the Aurora buying journey.
Follow the product-to-checkout journey
A product page has to answer a short sequence of buying questions: what is this, what does it cost, what have I selected and what happens next? Aurora makes those choices inspectable:
- Choose a product and colour. The sample catalogue offers an Original Tote, Classic Crossbody and Travel Pouch, each with Natural and Ink variants.
- Add the selected variant to the basket. Edit its quantity or remove a line. The basket keeps the product and colour together.
- Check delivery and the total. The sample rule adds £4.95 below a £100 item subtotal, with free delivery from £100. These are fictional demonstration terms.
- Review the example order. Inspect the lines and amount, return to the basket to edit, then complete the illustrative preview.
For a small check, one Original Tote is £49. With the sample £4.95 delivery charge, the order preview totals £53.95. Every product, price, delivery rule and order reference is illustrative. Tax treatment and live payment behaviour are outside this demonstration.
The browser holds the sample selections only for this visit. The preview asks for neither payment details nor customer contact information. Its completion state demonstrates the interface, rather than an accepted order or a recorded payment.
The work between a demo and your live store
A live build starts with your catalogue, selling regions and approved delivery and returns terms. We agree the required product fields, stock behaviour, customer tasks and payment-provider handoff before implementation.
The release checklist records what happens when payment succeeds, is cancelled or fails; when a payment notification repeats; and when an item becomes unavailable. Order creation, confirmation and fulfilment each have an agreed source and owner. A successful browser preview alone does not verify those connections.
We also agree representative mobile and desktop checks, performance measurements and consent-aware analytics events. Recorded purchase actions must use the agreed order and payment basis. The code, store, payment account and customer list stay under your control.
Post-purchase workflows, such as returns administration or approved customer updates across systems, can be scoped with Turing Automate. Website and checkout delivery stays with Turing Websites.
Inspect a small migration and acceptance pack
The migration and checkout acceptance ZIP is a separate synthetic teaching example. Its products are unrelated to Aurora's demo catalogue.
Three source variants become two records ready for staging and one held for review because its SKU is missing. One ready record has stock 0: a checked stock value is different from a missing identifier. The held row is kept out of the staging products and redirect candidates.
The pack includes the source records, field map, staging output, draft redirect plan, expected controls and a checkout acceptance sheet. Products remain unpublished and redirects disabled. Actual test results and evidence fields stay pending until someone performs the agreed checks in the selected environment. An inspected plan is distinct from an executed migration.
Inspect the source CSV, checkout acceptance sheet and field and checking notes alongside the ecommerce build scope.
Compare costs on the same scope
Online selling sits in our Growth tier, from £5,000 for UK projects, with the agreed scope fixed and itemised. Use the published web design pricing and US delivery page for market-specific starting prices.
The DTC cost guide includes the existing three-year cost worksheet. Compare build, migration, platform, hosting, apps and payment assumptions for the same catalogue and currency. Keep unresolved costs blank until a supplier confirms them. The Shopify or custom ecommerce comparison helps decide which route belongs in that brief.
Bring your store to scope
Start with your current website and platform, catalogue size, selling countries and the change you want. Add the connections and migration requirements you already know. Discuss your ecommerce website to open an editable project enquiry.