Lycon Stitches\x20\xf0\x9f\xaa\xa1 is a premium Nigerian men's fashion and tailoring house specializing in Jalabiyah, traditional wear, ready-to-wear, and custom tailoring. This System Requirements Document defines a world-class, fully responsive, production-ready fashion e-commerce application for that house, built so that it reads as a genuine luxury brand rather than a generic storefront template.
The product intent, drawn directly from the authoritative requirement thread, is a sophisticated fashion experience in which customers can discover collections, view products, choose sizes and colours, order online or through WhatsApp, track orders, manage accounts, and request custom tailoring, while the house manages products, orders, inventory, promotions, content, and customers through a complete admin dashboard.
The audience is twofold:
The application must communicate Craftsmanship. Confidence. Quality. Elegance. It is mobile-first, accessible, secure, fast, search-optimised, and deliberately restrained rather than decorative.
Lycon Stitches is delivered as a single production web application with two clearly bounded experiences on one shared catalog, order, and customer backbone:
Order life follows Pending â Confirmed â Processing â Ready â Shipped â Delivered across both experiences. Payments are handled by a secure external payment provider; the application never stores payment card details. WhatsApp is an accepted, first-class ordering channel, with the destination number configured by the house in Settings.
The current delivery is a live, first-party web application with application-owned customer identity, provider-owned payment, and Cloudinary-hosted media on Vercel infrastructure.
Delivery ownership. Everything the customer sees and does inside the storefront is first-party custom interface: browsing, filtering, product evaluation, tailoring requests, cart, checkout data entry, order tracking, and account management are all built and owned by Lycon Stitches. Two parts of the journey deliberately leave the first-party surface: payment, which is completed on a secure external payment provider's surface and never touches application storage for card data, and WhatsApp ordering, which opens the shopper's WhatsApp client with a pre-composed, professional order message addressed to the house's configured number. Both are accepted, intentional boundaries, not gaps.
Identity and access. Customers establish their own access from the public storefront â first-use enrolment and returning verification are the same surface â and that identity carries their wishlist, cart continuity, checkout details, orders, saved addresses, notifications, and account settings. Browsing, discovery, search, size guidance, support, product evaluation, the tailoring request, and ordering by WhatsApp require no identity at all; they are open to anyone. The admin experience is addressed by provisioning: store managers sign in with credentials issued by the house, and privileged store state is never reachable by public registration. Administrative routes are protected and authorised on the server, and the store's WhatsApp number, media, prices, stock, promotions, and homepage content are all controlled by the house rather than hard-coded.
Current versus future. Everything specified here is in current scope. The document deliberately contains no placeholder sections, no Lorem ipsum, no unfinished "coming soon" modules, and no adjacent commerce capabilities that the brand did not ask for. Where a realistic implementation exists, it is specified rather than stubbed.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No completed page designs yet.
Completed design pages will appear here when they are ready to preview.
No comments yet. Be the first!