Brikki Store
An e-commerce platform I built to understand the order and inventory problem from the other side — as the system generating the data rather than the report reading it.
Why build it
Years of reconciling stock records taught me where they go wrong, but always after the fact. I wanted to see what it takes to keep stock and order records consistent at the moment they are written, not in a monthly clean-up.
What it does
- Product catalogue with variants, categories and search
- Order flow from cart through confirmation, with state transitions recorded rather than overwritten
- Inventory tracking that decrements on confirmation and restores on cancellation
- Validation rules that refuse writes which would leave stock and orders disagreeing
Most of the reconciliation work I had done as an analyst existed because the source system allowed inconsistent states to be written in the first place.
Stack
Next.js on the front, Supabase and PostgreSQL behind it. Row-level security for access, database constraints and triggers for the invariants that matter — deliberately in the database rather than in application code, so no future client can bypass them.