Build a complete e-commerce website (store, cart, payments, admin)

You are a senior full-stack developer who has shipped many online stores. Build a complete, production-ready e-commerce website with me, phase by phase, so I can deploy it and take real orders.

## The store
- Store name: [STORE NAME]
- What we sell: [PRODUCTS, e.g. clothing, electronics, handmade jewellery]
- Number of products at launch: [NUMBER]
- Country and currency: [COUNTRY], [CURRENCY]
- Payment gateway: [e.g. Razorpay, Stripe, PayPal] plus cash on delivery: [YES/NO]
- Tech stack I prefer: [e.g. Laravel + MySQL, Next.js + PostgreSQL, or "you choose"]
- Hosting: [e.g. shared hosting, VPS, Vercel]
- Brand colours and style: [COLOURS, e.g. "minimal, white with black accents"]

## Features the customer sees
1. Home page: hero banner (managed from admin), featured categories, best sellers, new arrivals, offers strip, trust badges (secure payment, easy returns, delivery time), newsletter signup.
2. Category and search pages: filters (price range, size, colour, brand, rating, in stock), sorting (popular, newest, price low-high and high-low), pagination, search with suggestions as you type and typo tolerance.
3. Product page: image gallery with zoom, variants (size, colour) with their own price, stock and SKU, price with MRP and discount percentage, stock status, delivery date estimate by pincode/ZIP, description tabs, size chart, reviews with photos and star breakdown, related and "frequently bought together" products.
4. Cart: add, remove, change quantity, save for later, coupon codes, shipping estimate, stock checked again before checkout.
5. Checkout: guest checkout and sign-in, saved addresses, shipping method choice, order summary, tax calculation ([TAX RULES, e.g. GST 18%]), payment through the gateway with webhook confirmation (never trust the browser redirect alone), order confirmation page and email.
6. Customer account: sign up, sign in, forgot password, email verification, order history, order tracking, invoice PDF download, cancel or return request, wishlist, saved addresses, profile.
7. Pages: about, contact form, FAQ, shipping policy, returns and refunds, privacy policy, terms.

## Admin panel
1. Dashboard: today's and this month's sales, orders, average order value, top products, low-stock alerts, sales chart.
2. Products: create, edit, duplicate, bulk import and export by CSV, variants, multiple images with drag-to-sort, SEO fields (slug, title, description), draft or published.
3. Categories and brands with nesting, images and SEO fields.
4. Orders: list with filters by status and date, order detail, change status (pending, paid, packed, shipped, delivered, cancelled, returned, refunded) with an email to the customer at each step, add tracking number, print invoice and packing slip, refunds through the gateway.
5. Inventory: stock per variant, stock history, low-stock threshold.
6. Customers: list, detail, order history, block.
7. Coupons: percentage or fixed, minimum order value, expiry date, usage limit per coupon and per customer, specific products or categories.
8. Reviews: approve, reject, reply.
9. Content: home page banners, menus, policy pages.
10. Settings: store details, tax, shipping zones and rates, payment keys, email templates.
11. Staff accounts with roles (owner, manager, order staff) and an activity log.

## Store-specific rules
- Prices, stock and coupon validity are always recalculated on the server at checkout. Stock is reserved inside a database transaction so two people cannot buy the last item.
- Payment status is updated only from the verified gateway webhook. Handle duplicate webhooks safely.
- Product schema (Product, Offer, AggregateRating), BreadcrumbList and Organization JSON-LD on the right pages.
- Transactional emails: order placed, payment received, shipped (with tracking), delivered, cancelled, refund issued, password reset.

## Quality rules (apply to every phase)
- Security: prepared statements or an ORM for every query, output escaping, CSRF tokens on every form, passwords hashed with bcrypt or Argon2, rate-limited login, role checks on the server for every admin route, file uploads checked by type and size and stored outside the web root or with random names, secrets only in an .env file.
- Validation: validate every input on the server (and also in the browser for speed). Show clear error messages next to the field that is wrong, and keep what the user already typed.
- Performance: pagination on every list, database indexes on every column used for search, filter or join, lazy-loaded and resized images (WebP), caching for pages that rarely change, no N+1 queries.
- Responsive and accessible: mobile first, works from 360px to wide desktop, proper labels on every form field, keyboard navigation, visible focus, colour contrast of at least 4.5:1, alt text on images.
- SEO: clean URLs, a unique title and meta description per page, canonical tags, Open Graph tags, schema.org JSON-LD where it applies, an XML sitemap and robots.txt.
- Code: small functions with clear names, one responsibility per file, comments only where the reason is not obvious, consistent formatting, no dead code.
- Errors: friendly error pages (404, 500), server errors written to a log, never shown to visitors.
- Deliver with: a README (install steps, .env example, how to create the first admin), database migrations and seed data with realistic sample content, and a deployment checklist.

## How to work with me
Do not write code yet. First reply with:
1. A short summary of what you understood, and anything in the brief that is unclear or contradictory (ask me, do not guess).
2. The final tech stack, with a one-line reason for each choice.
3. The folder and file structure.
4. The full database schema: every table, column, type, index and relation.
5. Every page or screen, and every API endpoint (method, path, who can call it, what it returns).
6. The build plan as numbered phases, each one small enough to finish and test on its own.

Wait for me to reply "go". Then build one phase at a time:
- For every file, give the full path and the complete code. Never write "...", "rest of the code stays the same" or TODO.
- After each phase, tell me how to run it, what to click to test it, and what is still missing. Then wait for me to reply "next".
- If you change a file you already gave me, give the whole updated file again.