Batchmaker family · Next.js recipe studio
Recipe-Studio · Next
The focused basic version for recipes, raw materials, glass chemistry and export – without hardware tracking or production bookings.
- Responsibility
- Product architecture, full-stack development, and calculation engine.
- Technology
- Next.js 16 · React · TypeScript · Drizzle ORM · SQLite · Vitest · Playwright
- Status
- Live · current basic variant
- Positioning
- The current workbench: smaller scope, typed architecture and a clear hand-off into operations.
Situation
Situation
Recipe work needs the same domain core as production: raw materials, oxide calculation, redox, batch size, cost, versions. It does not need silos, shifts and live bookings. A full operations system is too heavy for desk-side development. You want to change a recipe version, check the chemistry and print a ticket without opening a shift.
Force both into one product and the workbench inherits hall rules while the hall inherits draft states. Drafts leak into stock, or stock is rebuilt at the desk. Both are expensive.
Decisions
Decisions
- 01
The same domain core for recipe, raw material and glass chemistry, smaller scope: no silos, no shifts, no live bookings.
- 02
Its own server, SQLite file and lean browser interface. Studio does not hang off the operations product.
- 03
Validation is a visible step. A calculation that runs quietly on save will not be found later.
- 04
Batch tickets originate here as draft and print-ready output. Booking happens in W-Make Batch.
- 05
No unverifiable efficiency claims. The product is the workbench, not a substitute for operations.
What you can inspect
A look at the application.
What you can inspect
The flow as a model.
01
Recipes
Version, compare, import and export, bound to raw materials and cost.
02
Materials
Master data from which oxide and batch size are later calculated.
03
Chemistry
Oxides, redox, physics, and calculations you can inspect.
04
Tickets
Draft, scale, preview, print-ready output.
05
Validation
A dedicated step before a version counts as usable.
What remains
What remains
Product boundaries are architecture. A good tool does not have to model the neighbouring process in full. Mix studio and operations and you carry drafts into stock, or stock onto the desk.
batchmaker-standalone.w-make.com →30-min analysis · free