The Hive · IoT · Shipment Tracking
The map showed you the problem.This fixed it.
You paid for visibility. You got a dot on a map and a person paid to stare at it. Shipment Tracking is the discipline that reads every sensor on every load and acts on what it reads — reroutes, rebooks, notifies, holds — before the customer calls, before the claim opens, before anyone at your company is awake.
0 sensor reads per load, per day. 0 of them need you.
Last night · replayed
One line left the field.
Here is what it did.
Visibility platforms vs. Shipment Tracking
Same sensor. Same alert.
Different company at 2 AM.
One of these is a subscription. The other is a colleague.
Last night · autonomous
- 01:47Reefer on load 3318 drifted 4°F past spec. 90 minutes to integrity loss. Alerted driver and dispatch, rerouted to the nearest cold-storage transfer.load saved
- 02:31Tracker silent 40 minutes outside Joliet. Cross-checked carrier’s last ping and driver’s HOS clock: planned rest stop. Sent the shipper the real status before their morning check-in.call never made
- 04:12ETA slipped past the dock window. Rebooked the appointment, notified the receiver, updated the customer link. One pass.dock held
- 05:58Shock event on a pharma pallet at a cross-dock. Flagged the pallet, opened the exception, requested photos at delivery, notified the account before the receiver signed.claim killed
- 06:40Light exposure on a sealed container between two scheduled stops. Flagged a possible tamper, held the delivery for inspection, notified security and the account.theft flagged
The mandate
We don’t list features.
We publish the job.
Decides on its own
- Reads position, temperature, humidity, shock, light, and door state on every assigned device, continuously
- Resolves every position to a place — a yard, a crossing, a rest stop. Never a coordinate.
- Computes ETA against the appointment, not the map
- Sends the customer the status the moment the operation knows it
- Reroutes cold chain to the nearest compliant transfer when integrity is at risk
- Rebooks dock appointments the ETA has already broken
- Opens exceptions with evidence attached: sensor trace, timestamp, location, photos requested
Escalates to you
- Any reroute that changes the delivery date
- Any exception above a claim threshold you set
- Any device silent past your limit with no corroborating signal
Never touches
- Rate, margin, carrier selection — that’s TMS
- The customer relationship — that’s CX and CRM
- Anything outside the limits you set on day one
Act 3 · borders & cash
One reading. Four teams move.
Nobody scheduled a meeting.
- IoTreroutes to cold storage
- TMSrebooks the receiver’s dock
- CXtells the account before they ask
- FINholds the carrier invoice pending excursion review
Governed
Bold is easy.
Bold you can audit is rare.
- Reroute reefer to transfer facility, 90 miles off route. Temperature 3°F over spec.
- Spike coincides with a scheduled stop. Door sensor opened at 03:19. This is a door event, not a drift. Recommend hold.
- Temperature recovering. Door closed 03:24.
- Reroute rejected. Load delivered on time.
Both sides of that argument are in your log. Forever.
Your turn
Go ahead.
Break one.
Pick one. Nothing here reaches a person.
Running today.
At a company whose freight is real.
Shipment Tracking reads sensors in production at Watchmen Logistics, Elyon SCI’s Customer Zero. Every decision on this page is the kind Watchmen’s freight gets, every night. Not demonstrated on a slide. Not pending a pilot. Running.
Read the Customer Zero story →
What it reads
- BLE tags for pallet and case
- cellular cold-chain trackers for reefers
- GPS units for trailers and assets
Your hardware or ours.
Your tracking platform can tell you where the load is.
Ask it what it did about it.