Full stack · E-commerce · 2025
Bellas Boutique
Online store with catalog, cart, duplicate-safe checkout, PDF and XML invoices, roles and account-abuse protection, backed by 149 automated tests.
The problem
A boutique wants to sell online without depending on someone else's platform: show its catalog, take payment, issue the invoice and answer questions. In a store, bugs cost money: a double click can't charge twice, the price can't come from the browser, and two simultaneous purchases can't sell the same last item.
My role
Lead developer: database, back end and front end. Team academic project for the course Diseño Humano-Computadora (human–computer design; UIA, 2025); teammates contributed specific bug fixes.
The solution
A React front end built with Vite talks to an Express API with JWT authentication and admin, sales and customer roles. SQLite stores the catalog, inventory, orders and invoices; the server produces PDF and XML invoices and sends email notifications. It also includes support chat and password recovery.
- React UI
- Express API + JWT
- Purchase and stock rules
- SQLite
- PDF / XML invoices
Technical decisions
The server computes the price
The cart only sends products and quantities. Totals, taxes and the invoice are calculated from database prices, so tampering with the request in the browser doesn't change what is charged.
A checkout that tolerates retries
Each purchase carries an idempotency key: on a double click or a network retry, the same order is returned instead of creating and charging a new one.
Stock is never sold twice
Stock is validated and decremented on the server when the purchase is confirmed, and concurrency tests check that two simultaneous purchases can't take the same last unit.
Accounts protected against abuse
Sign-in and password recovery respond the same whether or not the account exists, are rate-limited and use single-use recovery tokens stored as hashes.
Every resource has an owner
Orders, invoices and support conversations are read after checking who they belong to, not just that a session exists.
What I verified
- 149 automated server tests passing: resource ownership, checkout idempotency, stock concurrency, account enumeration, rate limits and CORS.
- Client production build succeeds, with 0 known vulnerabilities in npm audit for both server and client.
- CORS restricted to the front-end origin, and the support email sender read from configuration with no addresses hard-coded.
- Reproducible demo environment with fictitious data: products, accounts and purchases generated from scratch, with no real data.
Scope and limitations
- Payment is simulated: there's no integration with a real payment gateway.
- The demo runs locally; there's no public live store.
- The code is in a new public repository, without the history that contained earlier test data.
Need something similar?
Tell me what you need and I'll prepare a no-obligation quote.