Spreadsheets between shifts and teams
Order, stock and log sit in separate files. Values get retyped, and in the end every list has its own version of events.
Jan Wagner · software for real-world operations
I build software for businesses where spreadsheets, paper and verbal handovers have reached their limit. In production, the warehouse, the lab and the office. Every posting, every correction and every handover stays traceable.
14 years in industry · own products · Germany
The same processes exist in
Industries
I come from the glass industry, where I have my own products. The building blocks behind them carry over wherever material, shifts and approvals meet.
Recipe, batch sheet, silo, shift book and day close for container-glass production. This is where my own products and a running demo are.
Own productsView industry 02For plants that mix, weigh and dose to a recipe. Versions, weighings and consumption stay connected.
Transferable building blocksView industry 03Shift book, faults, maintenance and handover in one place. Whoever takes over sees at once what is still open.
Transferable building blocksView industry 04Goods receipt, storage locations, inventory count and stock reconciliation. Every movement has a record, every difference a cause.
Transferable building blocksView industry 05Test values, limits and releases right on the transaction. A deviation shows while there is still time to act.
Transferable building blocksView industry 06Forms, mail attachments and spreadsheets become one application in which a case can be followed from start to finish.
Transferable building blocksView industryTypical situations
Order, 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 stock does not match consumption. Nobody can say when the difference appeared.
A recipe, a price or a specification was changed. Which version applied when, and why, 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.
Building blocks
Industries differ in vocabulary. Underneath are the same basic questions. These building blocks already run in W-Make Batch and are adapted to your process.
Corrections are cancellations, reversals or reconciliations. The original transaction stays visible.
Runs in W-Make BatchRecipes and master data have versions. Whatever is posted keeps the version that applied at the time.
Runs in W-Make BatchReceipt, withdrawal, inventory count and open items. Every figure leads to its transaction.
Runs in W-Make BatchFaults, maintenance, tasks and photos in one timeline. Open items go explicitly to the next shift.
Runs in W-Make BatchWho may see, change and approve what is checked on the server.
Runs in W-Make BatchPrint and PDF, CSV export for SAP, REST API for machine data, German and English.
Runs in W-Make BatchServices
We walk through a process that is causing you problems, ideally on site in production. You come away with an overview of where data gets lost or maintained twice, and a recommendation on what to tackle first.
Arrange a callI build new business applications or bring existing ones back to a maintainable state. Typical topics are postings with cancellation and reversal, versioned master data, calculations tied to a recipe version, and repeatable day closes.
Arrange a callForms, mail attachments and a spreadsheet become one application in which a case can be followed from start to finish. That can be a web app or an application for Android, Windows or Linux, depending on where the work happens. Examples include document filing, administration and approvals.
Arrange a callI join your development team where business and engineering struggle to meet: integrations, grown code, and architecture decisions that become expensive to change after go-live. I work within the architecture you already have.
Arrange a callThe 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.
Day to day
Business software is often opened only because it has to be. I build it to take work off the people at the workplace. Then data gets entered in full, and the reports are right.
A posting shows straight away what it does: new stock, key figures, cost. Deviations show up while there is still time to act.
Key figures and open tasks show where the day stands and what is still missing before handover.
Version, consumption and cost sit together. There is no need to gather them from several lists.
How it works
30 minutes, free of charge. You describe the process, and I tell you plainly whether and how I can help.
I look at the process, on site where possible. Your existing lists and forms are the most important source.
You get in writing what will be built, in what order, and what it costs.
The application is built in verifiable steps. After that I run it for you, or your IT takes over.
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 →Development log
The latest commits from the product repositories — public, straight from Gitea. Activity without claims.
175 commits in the last 30 days
First call · 30 minutes · free
A few sentences about the process are enough: what runs in lists or side calculations today, and who works with it. Within two working days you get a reply and a clear view of whether I am the right person for it.
Arrange a call