Versions in file names
The valid recipe is called “final_v3_new.xlsx”. Which version applied to Tuesday's batch is guesswork.
Industries Batch and formulation
Wherever material is mixed to a recipe, the same questions come up: which version applied to this batch, what was actually weighed in, and what is the stock afterwards? I built a system for this in the glass industry. Its building blocks carry over to your formulations.
Typical situations
The valid recipe is called “final_v3_new.xlsx”. Which version applied to Tuesday's batch is guesswork.
The mixing order goes to the scale on paper. What was actually weighed in comes back late or not at all.
Stock levels are updated by hand. At month end the inventory count does not match calculated consumption.
What a batch cost is worked out later in a separate sheet, with whatever prices were at hand.
Building blocks
Every change creates a new version with date and reason. Posted batches keep the version they were made with.
The order to the scale is generated from the valid version. Posting it deducts consumption from stock straight away.
Key figures, batch size and cost are calculated from the recipe version and stay tied to it.
Wrong postings are cancelled or reversed. The original transaction stays visible.
What already runs
Features from W-Make Batch. Demo access is available on request.
See details →State of references
I have no public references outside the glass industry in this area yet. In the first call we check how far the existing domain core carries over to your formulations.
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