I’ve been in the supply chain industry for 30 years. For the past decade or so, as new software solutions flooded the market, anyone who knew “how things really operated,” knew it was an industry run on relationships. Technology was just a supplement to how money, data and freight got moved from A to B. Even with our current AI gold rush, there are still industry veterans who remember faxing bills of lading and are still working with those same colleagues. I’d argue the foundation of the industry, trust, mutual respect, familiarity, has eroded to a point of no return. Not because of technology, but because of prolific freight fraud that has fostered a culture of paranoia across the industry. And as a veteran of freight technology and systems, I can tell you a lot of this distrust starts at the handover. 

Walk into almost any logistics facility in the country and you'll find the same scene at the loading bay: a person with a tablet or a clipboard. They typically don’t have any information on the trucks coming in. Is this the carrier we booked? Is this driver legit? Is that the right container, sealed the way it left the last warehouse? Security and visibility solutions have helped operators answer those questions across almost every node of the supply chain, but at pickup, carrier verification and security is about as sophisticated as a self-checkout lane. 

Cargo theft across the U.S. and Canada climbed past $725 million last year, a 60% jump, and the fastest-growing vector isn't the smash-and-grab. It's fraud: fictitious pickups, stolen identities, carriers that look legitimate on a load board and vanish with a full trailer. The FBI has said plainly that impersonation is now the dominant way freight gets stolen. And people like the veteran dock supervisor who knew every regular driver by name are retiring. Warehouse turnover sits near 50%; for long-haul drivers it's above 90%. 

So we have a place where every load in the supply chain physically changes hands, where legal custody transfers, where accurate information is scarce or absent, where information asymmetry is accelerating fraud, and where the human safety net is thinning. And it remains the one part of the chain we never really invested in. Go figure. 

Cargo security is, in fact, the shipper’s problem 

When a load is stolen through fraud, the strategic theft completes at the moment the container is released. The party that released it is the one left holding the liability. The contractual and compliance obligations that increasingly govern freight (documented carrier vetting, verified driver identity, conveyance inspection, an unbroken chain-of-custody record) all point back to the handover that let the truck through.

Today, cargo insurers, customer contracts, and programs like CTPAT increasingly demand records that paper-based shipping cannot produce, and that a warehouse workforce turning over every eighteen months cannot reliably capture by hand. Cargo security is, in fact, the shipper’s problem, and it has to be solved at pickup, inside the system that runs it, because that's where custody actually changes and where the record either gets made or gets lost.

No one owns the handover (and that’s a problem)

I got my first IT job at a 3PL in the early 1990s. It's tempting to say the cargo security problem is about bad software, that the industry tried to secure freight and the tools weren't good enough. But back then the operations team was more worried about people jumping the fence, cutting the seal, and throwing product back over. Technology wasn't available, so companies threw bodies at it.

Freight software was built for operations and throughput: carrier bookings, transit time, container locations, getting cargo moved efficiently. Security, identity, and chain of custody were understood as separate concerns, owned by separate people, and addressed, when they were addressed at all, by separate means. This is why most shippers outsource security to a guard company. Some of it got handled by point solutions bolted on from the outside: carrier-vetting services, cameras, physical ID checks by a guy named Steve. A lot of it wasn't handled by software at all.

The result is a set of capabilities that have always lived in paper documentation and verbal communication over a radio, silos, disconnected from each other and from the system that actually runs the shipment. For example, the camera never knew who the driver was, the carrier check never reached pickup, and the custody record, where it existed, sat in a binder. None of these pieces were wrong on their own. They simply were never brought together, because for most of the industry's history there was no obvious reason to make changes. 

The lesser of two evils

For most of its history, buying freight technology meant choosing between two unsatisfying options, and the choice had nothing to do with security. It was just the shape of the market.

The first option was the large enterprise platform that promised end-to-end control of everything. In practice it was a clunky, glorified system of record: an expensive license, a six month deployment, zero flexibility. It promised comprehensive coverage yet could not change with the business without a massive change request and a matching invoice. You got breadth, and you paid for it in cost and rigidity.

The second was the point solution, with the opposite promise: do one thing exceptionally well. Many genuinely deliver. But when every capability comes from a different vendor, the buyer inherits subscriptions, logins, dashboards, data formats, and renewal cycles, none of which speak to one another. Someone has to integrate them, monitor them, reconcile their outputs, and re-buy them every year. You got depth, and you paid for it in fragmentation.

So that was the trade. Breadth or depth. One expensive, rigid system or ten sharp tools that don't talk. For decades there was no third answer, and no reason to expect one.

AI-native development is the third answer. Capabilities that once demanded a specialized enterprise stack and a year of integration can now be built and deployed in a fraction of the time, at a fraction of the cost. You no longer choose between breadth and depth, or between flexibility and cohesion. You can have technology that does many things at once, changes with the business, and doesn't break the bank or trigger a year of change management.

That is what makes this moment matter for freight. Once the tradeoff collapses, capabilities that used to demand entirely separate systems can finally live in one. And the two that most need to come together are freight management and cargo security, domains that were always treated as separate concerns, owned by separate people, bought from separate vendors. For the first time, there is no reason they have to be.

Security should live inside the system already running the shipment 

For the first time, the technology exists to create a modular layer inside the system that already runs your freight. The capabilities that secure cargo (knowing the carrier, verifying the driver, watching the route, documenting what actually leaves) no longer have to be a stack of disconnected point tools or a separate enterprise security program.

We’re seeing a great convergence: cargo security and freight management becoming one single entity. And AI has made it feasible to build something modular and affordable that does both at once.

Secondarily, we’re able to address both cargo security and management because the data is the same data. For example, the booking event and the security event are not two events; they are one event seen from two angles. The instant a truck arrives for pickup, the system logging it for operations already holds nearly everything security needs, such as who is driving, what they are hauling, what the tracker sees, and exactly when it happened. Recording that as an operations entry over here and a security entry over there was never a principle of good design.

Security should live inside the system already running the shipment.

Convergence

Convergence matters because disconnected tools produce alerts, and unified systems produce decisions. A carrier-risk flag in one inbox, an ID scan in another, and a tracker feed in a third are three pieces of information someone might later assemble into a conclusion, usually after the truck is already gone. That is retroactive security. It documents how the goods were lost.

A fraudulent carrier at pickup is a decision that has to be made before the container is released. It can only be made if the carrier check, the driver's identity, the booking, and the tracker feed are all the same conversation, in the same place, at the same time. That is the entire point of bringing these capabilities together. Convergence isn't about owning fewer vendors, though you will. It's about turning a pile of after-the-fact records into a decision made at the only moment a decision still matters.

Freight has always been the supply chain’s soft spot

To be clear, there’s always been freight fraud and the handover was always the soft spot. It’s because it’s where custody is most exposed. What's new is that the excuse is gone and the stakes are higher. Solutions exist that will allow, for the first time, the party that released the load to prove who took it, prove they were authorized to, and prove that what was left matched what was supposed to. 

That is what this moment in technology actually offers logistics. To give cargo the same visibility and accountability the rest of the supply chain has taken for granted for years.

Request a demo