Industrial software · product development
W-Make Batch
Batch management for container-glass production — from the batch ticket to the daily log.
- Responsibility
- Domain model, full-stack development, and technical quality.
- Stack
- Node.js · Express · SQLite · Web Components · native tests · Playwright
- Evidence
- Public product demo
Situation
A production process lives on recipes, material use, silos, shifts, and calculations. Built as a loose set of screens, the domain relationships disappear — and bookings become editable table rows.
Decisions
- 01
Domain bookings are states, not CRUD records that can be deleted at will.
- 02
The batch ticket and the daily log belong in one model, not in separate tools.
- 03
Calculations and material flows stay traceable even when the interface stays lean.
Evidence
Not features. Systems.
Decisions
The domain core as a model.
01
Recipe
Composition and version stay tied to later consumption.
02
Batch
The ticket is a domain order, not a printout of a table.
03
Log
The day closes as a traceable state, not an exported list.
Outcome
An operable system with a public demo. Confidential client data, volumes, and internal metrics stay unpublished.
Takeaway
A production system improves when domain irreversibility is part of the architecture — not a form validation.
batch.w-make.com →