Inspection & In-Date Control
Where an item must be in date, the store simply will not release it.
Calibration, test and tag, gas detector bump, lifting and rigging, or any periodic check you already run. Due dates are held against the serialised item, not the SKU, and issue is blocked when the item falls outside its window — at the point of issue, not in a report somebody reads on Monday.
A control with an unlogged override is not a control.
Somebody must always be able to release an item — a job cannot stop because a calibration lapsed overnight. So the block has a named human override, and the override is itself logged, against a name and a time, and appears on the same report as the block. The exception becomes visible rather than invisible.
The monitor he always uses is three days out of bump test. The store holds it. He takes the next one, which is in date, and is gone in ninety seconds. Nobody had to notice. That is the entire point.
Gating at the point of issue is the only place the control is reliable, because it is the only place the decision is actually being made. Registers, spreadsheets and weekly exports catch it afterwards, which is after it mattered.
It gates on the data you give it. If your calibration due dates are wrong, it will gate confidently and wrongly — so the first job is the register, not the hardware. We do that work with you and we do not pretend it is trivial.
Holding an item because a calibration lapsed is an automated decision affecting a person at the point of work. We disclose it, make it visible in the record, and keep the override path a named human. How we handle that →
Tell us which of your items carry a regime.
Calibration, inspection, bump test, hydro, hold time — if that list currently lives in more than one place, we can bring it into one register and gate issue on it.