Guides for cold-chain quality teams
Short, practical answers to the questions QA and IT ask about temperature excursions. Each one opens with the answer.
- ColdLatch for pharmacies and hospitalsThirty sites with one fridge each: what you get, what you need, and what it costs.
- ColdLatch for food distributorsChilled and frozen stores and trucks: the temperature record your HACCP plan asks for, and a block on the stock when it matters.
- What to do when a cold room has a temperature excursion: a checklistTwelve steps, from the first fifteen minutes to the closed record.
- How to block a batch in SAP S/4HANA after a temperature excursionMovement types, the three options, and how to automate it through the standard APIs.
- GDP temperature monitoring requirements for wholesalers, in plain languageMapping, sensor placement, calibration, alarms, records and transport, with the section of the EU guidelines for each.
- Mean kinetic temperature: when it helps and when it does notThe formula, worked examples for a 2 to 8 °C room, and why it cannot see freezing.
- Connect LoRaWAN temperature sensors through The Things StackFor developers: one webhook forwards every sensor reading. Setup, the message it reads, and how to try it without a sensor.
- Send temperature readings to ColdLatch over HTTPSFor developers: for loggers and gateways that cannot publish MQTT. The request, the per-logger key, batches and answers.
- Connect any ERP or warehouse system to ColdLatch: the integration APIFor developers: without SAP, your own system sends its stock, reads the blocks QA approved, and confirms each one.
- Connect your own system to ColdLatch with a webhookFor developers: the messages ColdLatch sends for an excursion and for each QA decision, how to verify them, and how retries work.