The original description
« I run a repair shop for garden machinery. I manage a stock of spare parts: each item has a reference, a purchase price and an alert threshold, and belongs to a supplier. Stock moves in when a supplier order arrives, and out when a part goes onto a repair. I want to see the total stock value, items below their alert threshold and this month's movements. »
The plan validated before generation
Before writing a single line, Blueprint Maker turns this description into a plan you validate. For StockAtelier, the proposed plan fits on one screen: four entities — Item, Supplier, Stock movement, Purchase order — and their links: an item belongs to a supplier, a movement concerns an item, an order groups item lines.
The statuses inferred from the text also appear in the plan: a movement is either stock-in or stock-out; a purchase order goes through draft, sent, received. The three requested indicators (stock value, items below threshold, this month's movements) are spelled out. If something is missing or superfluous, you fix it here — what gets built is what was announced.
- Entities: Item, Supplier, Stock movement, Purchase order
- Relations: item → supplier; movement → item; order line → item
- Statuses: in / out; draft / sent / received
- Indicators: stock value, items below threshold, movements over 30 days
Navigation: one section per entity
The generated application opens on a clean sidebar: Dashboard, Items, Suppliers, Movements, Orders. Each section leads to a list — not a spreadsheet, a real application list: a search field at the top, columns sortable in one click, pagination.
The item list shows the reference, name, supplier, quantity in stock, purchase price right-aligned in currency format, and the alert threshold. An item that has dropped below its threshold stands out immediately. On the movements side, a type filter (in / out) and date sorting put the history back in your hands in two clicks.
The item record, with its history
Clicking “GX-390 belt” opens its record: reference, supplier (clickable — it leads to the supplier record), purchase price, quantity in stock, alert threshold. Below comes the part that changes everything compared to a spreadsheet: the movement history of THIS item, as a dated table — March 12, 20 units in when order PO-2024-018 arrived; March 27, 2 units out.
That linkage is not cosmetic: it comes from the generated relational database. Renaming the item renames it everywhere, and the displayed quantity follows from the movements — nothing is hand-copied.
Entering a stock movement
The “New movement” form is short because the structure does the work: the item is picked from a dropdown (no reference retyped by hand, so no typo), the type is an in / out choice, the quantity is a numeric field, the date is pre-filled with today, and a comment field holds the context (“Mr Bernard's mower repair”).
On save, the movement list, the item record and the dashboard all reflect the entry — every screen reads the same database.
The dashboard: the pitch's numbers, computed on the database
The dashboard carries exactly the indicators requested in the description: total stock value in euros (sum of quantities × purchase prices), the number of items below their alert threshold, movement volume over 30 days, and a stock breakdown by supplier.
These numbers are queries on the database, not manual entries: every recorded movement updates them. A simple chart sits alongside the tiles — movement trend over the past weeks — with no theatrics: the goal is to answer the pitch's questions every morning.
Demo data: judging on full screens
StockAtelier arrives filled: several months of simulated activity, some thirty plausibly named items (belts, spark plugs, blades, air filters), four suppliers, orders at every stage and movements spread over time — including, deliberately, a few items below their threshold so you can see the alert at work.
That's a deliberate choice: you don't judge a management tool on empty tables. The demo data is then cleared to make room for the real thing. The application lives at its dedicated URL, and its complete source code exports (ZIP or GitHub push) — standard Next.js + Prisma.