Most buyers choose a freeze dryer on capacity and refrigeration. The control system gets a paragraph in the quotation and no attention until the first problem, when it becomes the most important component on the machine.
Recipes
A stored recipe holds the setpoints and the timing for each stage: freezing ramp and hold, primary drying shelf temperature and pressure, the transition criterion, and the secondary drying profile.
On a single-product machine, one recipe is enough. On a plant running four products, recipes need to be named by product and cut size, locked against accidental editing, and exportable for backup.
An exported recipe is also a record. When a batch behaves differently from the last one, comparing the two recipes takes a minute and rules out a whole category of causes.
Trend data
The controller logs shelf temperature, product temperature from each thermocouple, condenser temperature and chamber pressure, typically at one-minute intervals.
That log is what makes diagnosis possible. A vacuum leak shows as a pressure rise with a stable shelf temperature. A saturated condenser shows as rising pressure with a drifting coil temperature. A collapse shows as product temperature crossing a limit that the shelf never exceeded.
Without the log, all three look like "the batch came out wrong".
Alarms
Useful alarms are specific and actionable: over-temperature, vacuum loss, refrigeration fault, power interruption, door not sealed.
An alarm that fires for everything is ignored within a month. An alarm with no logged context cannot be investigated afterwards. Both are common.
Access levels
At minimum, three: operator, who can run and stop recipes; supervisor, who can create and edit them; administrator, who manages users and configuration.
The point is not security theatre. It is that a recipe changed by accident at 6 a.m. is a batch lost, and an edit trail tells you it happened.
Export and retention
Data export should be a readable format, not a proprietary file only the supplier can open. CSV is unglamorous and works with everything.
Retention should match the customer's own record-keeping obligations. Food businesses often keep batch records for one to three years; the controller should hold at least that, or export to a system that does.
What to ask at purchase
Can recipes be exported and reloaded? What is the logging interval and how long is data retained? Can the exported file be opened without your software? Is there an edit trail for setpoint changes? How does the system behave on power loss?
Five questions, and the answers separate a controller from a screen.
