GPS Smart Locks for Fleets, and the Device Estate Behind Them
Locks and sensors are the only part of a fleet platform someone can cut, unplug or forget to charge. KO Fleetz runs them as one estate: authority issued from a desk instead of a keyring, events written onto the trip that was running, and every unit answerable for still doing its job.
Where the software stops and the ironmongery starts
Access control in most fleets is a brass padlock, a numbered bolt seal, and a board of keys behind the transport office door. It works in the sense that things are mostly locked. It fails in the sense that the board cannot tell you who took the key for the curtain-sider on the fourteenth, and the seal cannot tell you anything until somebody reads the number off it at the far end.
Underneath that sits a second, quieter mess. A modern tractor unit carries a tracker, two fuel probes, a reefer controller and a lock on the trailer behind it, and there is a fair chance those came from four suppliers with four portals, four support numbers and four SIM contracts. Nobody in the business owns the sum of them. Procurement bought them, an installer fitted them, and operations assume they work because the map has dots on it.
Those two problems are actually one problem, and they surface together. A load goes short and the lock has no memory of the journey. The fuel figures look strange and nobody can say whether the probe is wrong or the driver is. In both cases the fleet is holding hardware it paid for, mounted on vehicles it owns, producing evidence it cannot use.
Treat the hardware as an estate, not a shopping list
The organising idea in this module is that anything bolted to a vehicle is an enrolled, addressable asset with a job description. A lock, a tracker, a fuel probe, a temperature sensor and a door camera are all things that must be commissioned, powered, connected, credentialed, watched and eventually retired. Handling them one product at a time is how estates rot. Handling them as a register is how they stay worth something in year three.
Once they are enrolled in KO Fleetz, their output stops being four separate feeds. A door state change carries the coordinate the vehicle was at, the trip it belonged to, the consignment on board and the credential that authorised it, because all of those already exist on the same timeline. That is the practical difference between owning smart locks and owning cargo security: one is a device that reports, the other is a chain of events that holds together when a customer disputes something six weeks later.
Authority moves too. Instead of a physical key that works everywhere forever for whoever is holding it, a person gets rights to a door, at a site, inside a window, and KO Fleetz records the grant and the use. What this module will not tell you is that a padlock is armour. Determined attack defeats hardware; the module's contribution is that the attack is timed, located and known about while the vehicle is still on the road rather than discovered at the dock.
Capabilities
What KO Fleetz Smart Locks & Cargo Security Software does
Authority instead of keys
Opening rights are granted to a person for a door, a site and a window, then expire. The grant and the use are both recorded. A key on a hook records neither.
Every device on one timeline
Door state, position, temperature and tank level share a clock, so KO Fleetz reads them together rather than asking a supervisor to align four portals by eye.
Vendor-neutral enrolment
Units from different manufacturers join one register where their protocols allow it, so new hardware next year does not mean abandoning this year's history.
Power and connectivity budgeting
Battery draw, charge cycles and data use are tracked per unit. A lock that flattens on a Friday is an operational problem long before it is a security one.
Escalation weighted by what is on board
A pharmaceutical consignment and a load of aggregate do not deserve the same alert policy, and KO Fleetz lets the value of the freight decide who gets woken up.
Buffered behaviour off-network
Devices work through coverage gaps and upload on reconnection, so a tunnel, a container yard or a rural lane produces a late record rather than none.
Commissioning as a real job
Fitting is captured as work with an installer, a date, a serial and a vehicle binding, which is what makes a failing batch findable rather than discoverable.
Retirement tied to the vehicle register
Disposing of an asset releases its hardware. Units are recovered or retired and SIMs cancelled, so the data bill stops covering somebody else's trucks.
How it works
How KO Fleetz does it
Step 1: Name the risk you are actually buying for
Pilferage on a night trunk, customs-supervised movements, cold chain integrity and yard key control lead to different hardware. Decide this before buying any of it.
Step 2: Fit and commission against the register
Devices are enrolled with serial, model, firmware and SIM, bound to a vehicle, and signed off by the fitter. Their output then inherits trip and driver context.
Step 3: Write the access policy
Who may open what, where, and inside which window. Depot staff, drivers, customer sites and subcontractors each get a scope instead of one shared credential.
Step 4: Run the work and read the exceptions
Routine openings inside a rostered window are logged and left alone. The rest collect in a worklist with position, trip and credential already attached.
Step 5: Keep the estate honest
Silence, flat readings, fading batteries and lapsed calibrations open tasks. Every swap updates the register, so coverage stays a fact rather than an aspiration.
Outcomes
What changes
- Authority granted from a desk, scoped and dated
- Keys retired
- Door, position and sensor events read together
- One clock
- Hardware decisions stay yours to change
- Vendor-neutral
- A device that goes quiet becomes a job
- No dead spots
Explore in detail
Every smart locks & cargo security software capability
Each of these is a capability page in its own right, with the workflow, the limits and the awkward questions answered.
What this module connects to
Four categories carry most of the weight. Telematics hardware is the first: trackers and gateways that forward device traffic and give the lock its position context. Electronic lock and seal manufacturers are the second, connected through their published protocols and APIs where those exist, and evaluated honestly where they do not — a closed device that emits only a pre-cooked status is a real limitation and we will say so during selection. The third is consignment data from ERP and WMS platforms, which is what lets an access rule know that this trailer is carrying that customer's order to those three drops. The fourth is connectivity: mobile network providers and IoT SIM management platforms, so data plans and suspended lines are visible next to the devices they belong to rather than on a separate invoice nobody reads.
Explore integrationsFrequently asked questions
Tracking answers where the vehicle is. This module answers what is happening to it and to the things bolted onto it. Doors, seals, temperature probes, cameras and the credentials that operate them all live in KO Fleetz, along with the unglamorous lifecycle around them: commissioning, firmware, SIMs, batteries, calibration and disposal. Most fleets buy tracking first and reach this module when a load goes missing, a customs regime demands electronic sealing, or somebody finally counts how many devices are billing data on vehicles that left the fleet.
No, and it is worth being specific about where that breaks down. If your existing locks or sensors speak a documented protocol or expose an API, they can usually be enrolled and managed alongside anything else. The genuine blocker is a sealed device whose manufacturer publishes only a finished status and no raw value, because then we can display what it says without ever verifying whether it is true. We would rather identify which of your models fall in that category during evaluation than after the invoice.
That is the normal starting point and usually the sensible one. Fleets begin where losses actually happen: a particular lane, a night trunk, one customer's high-value contract, or the movements a customs authority requires to be sealed electronically. Unequipped vehicles still produce position, stop and delivery records in KO Fleetz, so they keep a partial trail. The difference is that the gap is visible in the record rather than papered over, and you can extend coverage once the first tranche has proved what it is worth.
Installation is done by qualified fitters, either ours, a partner's, or your own workshop once trained, and the choice usually comes down to how your vehicles cycle through the yard. A tracker and a lock on a trailer is a short job. A full sensor set with fuel probes and a calibration fill takes longer, because a probe fitted without a proper multi-point calibration produces confident readings that are quietly wrong. Most fleets stage it against planned service visits rather than pulling vehicles out of work.
It is a lock. Given time, tools and privacy, it comes off, and so does every other padlock ever fitted to a trailer. It also secures one locking point and has no opinion about a curtain being slashed or a roof being opened. What it changes is latency and evidence. A defeated mechanical seal is a discovery at the destination; a defeated smart lock is an alert with a coordinate and a timestamp while the vehicle is still moving. That is a real trade, not an absolute guarantee.
Liability follows your insurance and your contracts, not our software, and any vendor implying otherwise is selling comfort. What KO Fleetz changes is the quality of the file you bring to the conversation. Instead of two conflicting accounts and a seal number, you have the openings, their positions, the credentials behind them and the device's own health record for that day, including whether it was reporting at all. Insurers and consignees respond differently to a timeline than they do to a recollection.
Bring one route you cannot explain
Pick a lane where loads go short or keys go missing. We will map the hardware it would take, the events KO Fleetz would have logged, and the gaps that would still remain.