Cold chain logistics software holds the condition of a temperature-sensitive consignment as a record: readings from origin to handover, gaps where readings are missing, departures from the limits set for that product, what was done when something went wrong, the decision taken on the consignment, and the evidence produced for the customer. With Pentoggle, an operator can describe how condition is actually monitored and generate the starting application around it.
What this page does not do. It states no condition requirement. It contains no temperature range, no permitted excursion, no storage condition, no standard and no certification requirement. What conditions apply to a given product, what tolerance is acceptable, what records must be kept and for how long depend on the product, the customer's requirements and the applicable rules, and they are matters for your own adviser and your customer contracts. Nothing here should be read as guidance on any of them, and the position you take remains your business's own responsibility.
What this page is about is the operational problem once those limits are known: capturing the record, noticing when it breaks, and being able to produce it.
Many operators already run Tally for accounting and may have monitoring devices from a provider. Those stay where they are. What is often still managed outside them is the consignment-level condition record: what it shows, where it is incomplete, and who decided what on the strength of it.
Key takeaways
- In cold chain, the condition record can be as commercially important as the movement itself. A consignment delivered without a defensible condition record is difficult to bill and difficult to defend.
- Gaps in a record are as significant as readings outside limits, and they are easier to miss because nothing alerts on an absence.
- Handovers are where records break, because monitoring frequently belongs to whoever holds the goods and does not travel with them.
- A departure from limits requires a decision by someone qualified to make it, and the decision is worth recording alongside the reading that prompted it.
- A useful number is the share of consignments delivered with a complete condition record from origin to handover.
The device is often not the problem
Monitoring devices work. Data loggers, sensors and telematics-linked probes record readings, and providers supply them with their own portals.
The trouble starts at identifiable points, and all of them are about what happens around the device.
When the record lives with the device, not the consignment
The provider's portal knows what a device recorded. It does not know which consignment that device was travelling with, or which customer is waiting for the evidence.
When nobody notices a gap
A device stopped recording for several hours. Nothing alerts on silence, so the gap is discovered when somebody assembles the record for a customer weeks later.
When the record does not survive a handover
Goods move from a vehicle to a cold store to another vehicle. Each leg may be monitored by a different party with a different system, and the consignment-level record has to be stitched together afterwards, if it can be.
When an excursion is handled and not recorded
Something went outside limits, somebody made a call, the consignment moved on. The call may have been correct and there is no record of who made it or on what basis.
What cold chain software holds
The consignment and its requirements
What is being moved, for whom, and the condition limits set for that product by your customer or your own procedures.
Condition readings
Readings over time from devices or manual checks, held against the consignment rather than against the device.
Coverage
Which parts of the journey are covered by readings and which are not, so gaps are visible as gaps.
Exceptions
Readings outside the limits set for the consignment, and periods where readings are missing.
Response
What was done when an exception arose, by whom, and when.
Decision and release
Whether the consignment was released, held, returned or rejected, who decided, and on what basis.
Handover points
Condition recorded at each change of custody, with the party receiving and the party releasing.
Evidence
The condition record for a consignment, produced in the form your customer requires.
The record can be part of what you are selling
In general freight the deliverable is the goods arriving. In cold chain the customer may be buying two things: the goods arriving, and a demonstration that they arrived in the condition required. Which of those your customer expects, and in what form, depends on the product and the contract.
That has a practical consequence that is easy to underestimate. A consignment that was in fact kept within its required conditions but cannot be evidenced may create a similar commercial difficulty to one where a condition departure is established. The customer's own obligations may depend on being able to show the condition of what they received, and where you cannot supply that, the difficulty tends to come back to you regardless of what actually happened in the vehicle. Where responsibility actually sits is a matter for the contract.
This is why the completeness of the record matters as much as the readings in it, and why gaps deserve as much attention as excursions.
Three things follow for how the record should be built.
Hold readings against the consignment, not the device. A device is a piece of equipment that moves between jobs. The consignment is what the customer asks about. Where the record is organised by device, producing consignment evidence is a reconstruction, and reconstructions are contestable.
Treat absence as an event. A period with no readings should appear in the record as a gap with a duration, not as empty space. Nothing alerts on silence unless you build something that does.
Retain it for as long as your customers and your obligations require. How long that is depends on the product and the arrangement, and it is a question for your adviser. What the application should do is keep the record retrievable by consignment rather than by date or by device, because that is how a query will arrive.
Handovers are where records break
Many cold chain journeys involve more than one custodian. Origin premises, a vehicle, a cold store, another vehicle, a delivery point. Each may be monitored separately, and monitoring rarely travels with the goods across a change of custody.
The result is a record with structural gaps at exactly the points where risk is highest, because loading and unloading are when goods are most exposed and when custody is ambiguous.
Two practices address this and neither requires new equipment.
Record condition at the handover itself. A reading taken and logged at the moment of transfer, by the party releasing and ideally acknowledged by the party receiving, closes the boundary. It also provides evidence of the condition at that point, which can help establish where a later problem may have arisen. Where a problem is found later, the question is which leg it happened on, and a handover reading is what informs that.
Make the coverage map visible. For a given consignment, which legs have readings and which do not. Where a leg is not monitored, that should be a known and accepted position rather than a discovery. Some legs may genuinely not be monitored, and knowing that in advance is different from finding it out during a claim.
Where a third party holds the goods, what they monitor and what they will provide is a contractual matter worth settling before the first consignment rather than during the first dispute.
An excursion needs a decision, and the decision needs a record
When readings fall outside the limits set for a consignment, something has to happen. The operational question is who decides what, and the answer should be settled before it occurs rather than at two in the morning.
The application's role here is narrow and worth stating precisely. It can hold the limits you have been given, flag readings outside them, notify whoever you have designated, hold what was decided and by whom, and keep that alongside the readings. It cannot determine whether a product remains fit, and it should not be built as though it can.
That determination depends on the product, the extent and duration of the departure, the customer's requirements and the applicable rules, and it belongs with whoever is qualified and authorised in your arrangement to make it. For some products and some customers, that person is not in your organisation at all.
What the record should capture is straightforward: what the readings showed, when the exception was raised, who was notified, who decided, what they decided, and what was done with the consignment. That sequence is what makes a decision defensible later, and its absence is what makes a correct decision look like an unexamined one.
Recording exceptions consistently also produces the pattern. Exceptions concentrated on one route, one vehicle, one cold store or one handover point indicate a specific operational cause, and that is a fixable finding rather than a series of individual incidents.
Where cold chain looks different by business type
- Pharmaceutical Logistics Software, where condition is one requirement among several and documentation dominates.
- City Distribution Software, where dairy and frozen goods move on repeating routes with many short handovers.
- Warehouse Management Software, where storage condition becomes part of the stock record.
- Bulk and Tanker Transport Software, where temperature-controlled bulk products carry condition and quantity questions together.
- Last-Mile Delivery Software, where the final handover is to a consumer and the record ends at the door.
- 3PL Software, where the condition record is a contractual deliverable to a client.
Why operators choose Pentoggle for cold chain
Readings held against the consignment
Not against the device, so producing evidence for a customer is a lookup rather than a reconstruction.
Gaps treated as events
Missing periods shown with a duration, because nothing alerts on silence unless it is built to.
Handover readings at each change of custody
Condition recorded and acknowledged at transfer, which is what makes it possible to establish where a problem arose.
The decision recorded with the reading
Who was notified, who decided, what they decided and when, held alongside what prompted it.
Sits around your monitoring provider and your accounting
Your provider continues supplying devices and readings. Tally and comparable systems continue handling accounting and GST. Pentoggle assembles the consignment-level record and the workflow around it.
A useful number for cold chain
The share of consignments delivered with a complete condition record from origin to handover.
Complete means covered end to end by readings or by an accepted position that a particular leg is not monitored. It is a measure of whether you can evidence what you did, which is a different question from whether you did it well.
Read it before the exception rate, not after. An operation with few exceptions and an incomplete record may simply not be looking during the periods when exceptions occur.
Break incompleteness down by cause. Device failure, device not fitted, a leg with a third-party custodian who does not provide data, and readings lost at a handover are four different problems with four different remedies, and only the breakdown distinguishes them.
Track exceptions and their resolution separately. What matters there is not only how many arose but how many were decided and recorded by someone authorised to decide them, since an exception resolved without a recorded decision is the one that becomes difficult later.
Ready to build cold chain software?
Your consignments are monitored.
Producing the record for one of them, six weeks later, when a customer asks, is the part that decides whether the monitoring was worth anything.
Describe how your consignments are monitored and where custody changes to Pentoggle in plain English and generate a working first version in hours, then refine it around your process.