Spreadsheets between shifts
Batch sheet, stock and log sit in separate files. Values get retyped, and in the end every list has its own version of events.
Industry · Glass
I build software for plants where spreadsheets, paper slips and verbal handovers have reached their limit. Recipe, batch sheet, silo stock and shift log come together in one system, and every correction stays traceable.
Typical situations
Batch sheet, stock and log sit in separate files. Values get retyped, and in the end every list has its own version of events.
In the morning the silo level does not match consumption. Nobody can say when the difference appeared.
A recipe version was changed. Which version applied to which batch, and why it changed, is not written down anywhere.
Your business application has run for years, but hardly anyone dares touch the code. Every change takes a long time.
Batch log software
Post batches, deduct silo stock and keep corrections traceable.
Batch sheet software
Create batches from the recipe, then check, print and post them.
Glass batch calculation
From oxide composition to batch weights, with a worked example.
Products
For daily operations: batch sheet, batch log with silo deduction, shift book, daily log and day close.
For recipe work at the desk: versions, oxide and redox calculation, checks and a print-ready batch sheet.
CSV export for SAP, REST API for machine data, several sites and user roles.
Day to day
Production software is often opened only because it has to be. I build it to take work off the people running the plant. Then data gets entered in full, and the reports are right.
A posting shows straight away what it does: new stock, redox position, cost. Deviations show up while the shift is still running.
Key figures and open tasks show where the shift stands and what is still missing before handover.
Recipe version, consumption and cost sit together. There is no need to gather them from several lists.
The proof

For running production · reference version
01The complete version. Postings, stock and shift handover share one data model.
Batch management for container-glass production, designed for furnaces pulling 150 to 600 t/d: from batch sheet through silo and batch log to the daily log, with the shift book as the everyday workplace.
Recipe
Composition, version, temperature and cost stay linked to later consumption.
Batch sheet
The order to the scale, generated directly from the valid recipe version.
Silo
Consumption is deducted from stock automatically.
Batch log
What was weighed stays assigned to batch and recipe version.
Log
The day close records what the next shift will find.
Demo access on request.
Updates
Recent changes to the application, straight from the update feed. Entries appear in the language they were written in.
Umfangreiches Audit der Buchungslogik über LKW-Wareneingang, Stück- und Scherbenlager, Siloabzug, Stornos und Tagesabschluss. Was früher beim Abgleich still verworfen wurde, wird jetzt als offener Posten im Bestand ausgewiesen. Stornos erzeugen echte Gegenbuchungen.
View →Die Schichtbuch-Seite von W-Make Batch ist auf eine Orientierungszeile, vier Kennzahlen und Filter mit Zählern umgebaut. Der fachliche Inhalt bleibt: Erfassen, Störungen, Wartung, Meldungen, Aufgaben, Fotos und Schichtübergabe sind unverändert erreichbar.
View →Other industries
First call · 30 minutes · free
Describe in a few sentences where things get stuck today. You get a reply and an honest assessment within two working days.
Discuss a process in this industry