From one readingto a signed release.

01 · Hardware

Probes that travel with the product

A probe taped to the outside of a pallet wrap measures the warehouse. Ours sit in the payload cavity, paired to the shipment at pack out, with the placement photographed into the record. Bring your own loggers if you prefer; the ingest API accepts any device that can post JSON.

02 · Ingest

Gaps are recorded, not hidden

Shipments lose signal in holds, in bonded areas and over water. The probe keeps logging to on-board memory and uploads the buffer on reconnect. The record shows the reading time and the upload time side by side, so a gap in coverage never looks like a gap in the data.

{
  "shipment": "SHP-4471",
  "probe": "MK4-00918",
  "readings": [
    { "at": "2026-01-14T06:32:00Z", "temp_c": 4.8, "ambient_c": 19.2 },
    { "at": "2026-01-14T06:33:00Z", "temp_c": 4.9, "ambient_c": 19.6 }
  ],
  "buffered": true
}

03 · Alerting

A rota, not a mailbox

Escalation runs to a named reviewer with a backup. Every raise and every acknowledgement lands in the shipment record with a timestamp, which is the number an inspector writes down.

1. Minute 0

   Reading crosses the profile limit. The record opens an event.

2. Minute 0 to 1

   On-call reviewer raised by push and SMS with lane, probe, value and slope.

3. Minute 5

   No acknowledgement. The backup reviewer is raised by voice call.

4. Minute 15

   Still open. The depot contact and the programme lead join the thread.

5. Close

   Reviewer records the response and the outcome against the shipment.

Silence rules exist for lanes where a known ambient spike is not a payload risk. QA approves each rule, and the record shows which rule suppressed which alert.

04 · Evidence

The pack closes with the shipment

Nothing is assembled after the fact. Each element attaches while the shipment moves, so release is a review rather than a reconstruction.

1. 01

   Raw readings

   Every logged value with probe ID, in CSV and JSON, unedited

2. 02

   Probe calibration

   Certificate, date and tolerance attached to the shipment

3. 03

   Placement record

   Pack-out photographs and the probe position in the load

4. 04

   Alert trail

   Who was raised, when, and when they acknowledged

5. 05

   Excursion analysis

   Window, peak, duration and mean kinetic temperature

6. 06

   Release decision

   Reviewer, role, stability reference and signature time

Coldharbour supplies documentation and evidence. Validating the system inside your quality framework stays with your organisation.

05 · Integrations

Send it where the work happens

Webhooks

Signed with HMAC SHA-256, retried with backoff for 24 hours, replayable from the console.

REST API

Cursor paginated reads for lanes, shipments, readings and events. Write access for shipment metadata.

Warehouse

Scheduled CSV or Parquet to SFTP or S3, partitioned by shipment.

Systems

SAP EWM, Veeva Vault, ServiceNow and Slack, each with a documented field mapping.

06 · Security and data

Boring on purpose

Data residency

EU or US region, chosen per tenant at onboarding.

Access

SSO through SAML or OIDC, role based, with per-programme scoping.

Audit trail

Append only. Readings cannot be edited or deleted, and every export is logged.

Retention

3 to 12 years by plan, with legal hold on any shipment under review.

Backups

Point in time recovery to 35 days, restore tested quarterly.

Certification

Not claimed on this demonstration build. Ask for the current status.

Reading the data first? Open the lane explorer