A few things you might wonder.

This is a fictional handmade maker website template. The products, maker, prices and stock are sample data. Basket, wishlist, custom requests and checkout demonstrate browser-local workflows. No real order, payment, shipment or email is created.

Every variant lists a dispatch lead time. Ready-made demo pieces show 2–3 working days; the larger Meadow weaving shows 15–20 working days before dispatch. Delivery time is additional. A mixed basket follows the longest lead time. A real shop owner must replace these examples with actual capacity.

Yes, you can build a local custom-request draft. Choose a starting piece, material, colour direction and dimensions, then review before saving. A real maker would need to agree feasibility, a quote and timing separately. Plan your custom request →

The original AI-generated photographs illustrate the fictional craft range. Handmade variation, screen colour and dimensions can affect appearance. The selected size and finish are described on the product page; images do not change into unverified variant photographs.

Use the specific care notes on each product page. A cotton cushion, linen runner, embroidered pouch and decorative wall weaving have different needs. The care guide collects those instructions in one place. Open the care guide →

Standard delivery is £5, or free when the product subtotal is £100 or more. Express delivery is £9. Standard takes an illustrative 3–5 working days after dispatch; express takes 1–2. The demo delivery area is the United Kingdom. No delivery is arranged.

The Smart Routing assistant receives your typed question and the exact four-product catalog shown on its page. It does not receive your basket, profile or saved requests. The Email Validator receives only the email you intentionally enter in its own form. Live tools require your authorized personalized download configuration.

The intended shopping, wishlist, request and account demo state is stored in this browser. Where storage is denied, the runtime uses a usable in-memory fallback and explains persistence limits. Clear site data to remove it, or use the local reset control. No backend account exists.