Asian Elegance By Z sells South Asian women’s clothing to UK shoppers who already knew the brand on Instagram. The business problem was not “need a pretty website.” It was that orders lived in DMs, sizes were explained in chat, and there was no cart the owner could hand to a customer at 11pm. We built asianelegancebyz.co.uk as a WooCommerce store that matches how this audience actually buys: by collection (Ready to Wear vs wedding), then by look, then by a question on WhatsApp if the size chart is not enough.
The brief we actually received
Wedding and Ready to Wear pieces are not the same product psychologically. One is researched, often with family input. The other is closer to a weekly browse. A single “Shop” dump of SKUs would bury both. The owner also needed to add products herself after launch — a store that only a developer can update is a store that goes stale in two weeks.
What we refused to do
- Drop a multi-purpose theme and swap the logo. Those themes fight fashion photography and slow the first screen.
- Hide WhatsApp because “real stores only use checkout.” This audience already trusted chat. Removing it would have cut conversions.
- Force every shopper through a long account-creation wall before they could buy a dress they already wanted.
Information architecture
Navigation follows the way customers talk: collections first, not a 40-item mega menu. Product pages keep fabric, occasion, and size information above the fold on a phone. Related products stay inside the same collection so a wedding shopper is not dumped into casual separates.
Mobile checkout and media
Most sessions are phones. We treated checkout fields, button size, and image weight as one problem. Fashion photos are large; we compressed them so the gallery still looks sharp without blocking add-to-cart. WhatsApp sits as a real path for size questions, not a floating badge that covers the Buy button.
What the owner can do without us
WordPress admin for products, prices, and collection assignment. We trained against the actual catalogue — not a dummy “product 1.” If a new wedding set goes live on a Thursday, it should be on the site Thursday, not after a ticket queue.
Stack and ownership details
WordPress + WooCommerce on hosting the client controls. Payments and shipping rules were configured for UK fulfilment realities, not a generic “worldwide” plugin default. Domain and admin credentials sit with the business. We documented how to add a product, assign a collection, and publish — then walked through it on a screen-share with their catalogue open.
What we measured after launch
We watched whether shoppers could reach a product from the homepage in two taps on a phone, whether WhatsApp still captured size questions without covering checkout, and whether the owner could publish a new SKU without calling us. Those are operational metrics. Vanity homepage animations were not success criteria.
Lessons we reuse on other fashion stores
- Split wedding vs everyday shopping paths early — one grid for both audiences loses both.
- Keep chat when the brand grew on chat; do not force a pure cart identity overnight.
- Train on the real catalogue. Dummy “Product 1” training does not stick.
Outcome
The live site is a self-serve store with categories, cart, and payment — plus chat for the questions a size chart cannot answer. The owner’s time moved from typing order details in Instagram to fulfilment and design. That is the only outcome that mattered for this brief.
If you are briefing a similar store
Send us your collections (not a dump of every SKU), whether WhatsApp is a sales channel, and who will upload products. Read e-commerce essentials if you are still deciding features, then request a quote with the live Instagram or current site.
QA checklist we used before go-live
- Product page: size chart visible without opening a PDF on mobile.
- Cart: guest checkout path works; WhatsApp does not cover the Buy button.
- Admin: owner can create a product, assign Ready to Wear vs Wedding, publish in under 10 minutes.
- Images: gallery loads without blocking first paint on a mid-range Android phone.
- Payments: test order completes; confirmation email arrives to the shop owner.
Why this write-up is specific (not portfolio filler)
We publish project notes so business owners can see real decisions — not generic "beautiful websites" claims. Every section maps to something we refused, shipped, or trained on for this UK fashion brand.