E-Commerce Website Build

Description

The store first: catalog, cart, checkout, and an admin page you can run yourself without calling me. I build it with Next.js and render it on the server, so each product gets its own URL that Google can read. At handover the repository and every account become yours. Payments are not part of this one. If you want the store taking money from day one, take the bundle.

Details

This one is for a store that does not exist yet, and one whose look has to be your own. If your site is already running and only needs to start taking money, the gateway integration is a far smaller job.

### What only this package gives you

• A design built for your shop, not an existing look reused.
• Any feature your workflow needs, as long as we agree it up front.
• The repository becomes yours. You can carry on with anyone afterwards, including without me.
• Two rounds of revisions, and no cap on how many products the catalog holds.

### Included

• Next.js App Router, rendered on the server, so each product sits on its own URL that Google can read.
• Catalog with categories, search, and stock tracking.
• Cart and checkout.
• An admin page you can run yourself: products, categories, stock, orders.
• Layout adapts to the screen, with light and dark modes.
• SEO groundwork: sitemap, structured data, and Open Graph images.
• Core Web Vitals in the green on the launch build.
• Deployed to Vercel on your own domain, with SSL.
• Repository and every account handed over to you at the end.
• Two rounds of revisions, as long as they stay inside the scope we agreed.
• Thirty days of bug fixes after handover.

### Not included

• Payment gateway integration. Take the bundle, or add it later as its own job.
• Shipping and courier integration.
• Product photos, copywriting, and typing your catalog in.
• Hosting, domain, and third-party fees. All of it stays in your name.
• Anything we did not agree on at the start. If you ask for more mid-project, I price it before I build it.

### Stack

The auth and database rows are not locked in here. We decide them together at the first call, weighing what your team already runs against what the catalog actually needs.