CargoGate assessed: a 92 percent pilot is the strongest number, and the only one

SAL Logistics Services launched CargoGate with Elm at LEAP 2026, a digital service covering shipment pickup and delivery at its air-cargo stations. TechScoop has not used the system, has not observed it at a terminal and has not spoken to a user. This is an assessment of the published information and of the workflow it describes. The workflow being targeted is worth setting out, because it is invisible unless you have waited in it. A shipment that has cleared customs still has to be physically released to a haulier. The driver arrives at the cargo terminal, queues, presents documentation, waits while the consignment is located and released, then loads. Every one of those steps involves a person checking a document against a record held somewhere else. At the volume a national ground handler processes, the queue is itself a significant operating cost, in terminal dwell time for the handler and in truck and driver utilisation for the freight forwarder on the other side of the gate. Digitising that is not conceptually difficult and is operationally brutal. Terminal software fails on the ground rather than in the architecture: a driver without the app, a shipment that will not scan, a document in the wrong format, an exception the workflow does not cover. Any of those sends the participants back to the counter, and once people learn that the counter still works, the system is dead. Which is why the single number SAL published is the right one. The company says the pilot recorded 92 percent operational adoption across its main stations in Riyadh, Jeddah, Dammam and Madinah. Adoption at that level across four stations means the system was not merely tested but taken up by most of the people who would have to use it, which implies the exception paths were good enough to keep users inside it. That is the hardest thing to achieve in this category and the most meaningful evidence available. It is also the only number, and it measures the wrong thing for a buyer. Adoption tells you people used the system. It does not tell you the terminal ran faster. The figures that would establish that are gate dwell time before and after, truck turnaround time, shipments released per hour per station, and the proportion of releases completed without human intervention. None has been published. It is entirely possible for a system to reach high adoption and deliver modest throughput improvement, if the digitised step was not the bottleneck. The architecture choice is sound and worth crediting. SAL describes CargoGate as built on secure, government-grade digital architecture using Elm's capabilities. Elm builds and operates digital platforms used across Saudi government services, and the identity and integration layer is precisely what a gate process needs when the shipment record, the carrier, the driver's identity and the customs status all live in different systems. Building that in-house is not something most ground handlers can justify. Borrowing it is faster and ties the roadmap to another company, which is a trade rather than a flaw. The rollout position is unclear from published material. The pilot covered four main stations. The launch is described as covering SAL's stations, but no station-by-station schedule has been published and there is no statement of whether every station is live from launch or whether this is a phased extension. A freight forwarder planning operations needs that answer and cannot currently get it. Commercial terms are equally unpublished. Whether CargoGate is included for existing customers or billed separately, whether there are transaction fees, and what integration a forwarder's own systems require have not been described. SAL has said the platform creates long-term monetisation potential through value-added digital services and ecosystem integration, which is a statement of intent about future products rather than a description of current pricing. The exception question is the one an operations manager would ask first and it is unaddressed. What happens when a shipment does not scan, when documentation is disputed, when a driver arrives without the application, or when the system is unavailable. A gate process needs a defined degraded mode, and how good that mode is determines whether the 92 percent holds under stress. Who this is likely to work well for: forwarders and hauliers operating regularly through the four pilot stations, where adoption is established and the workflow is proven at some scale. Who should wait: operators at stations outside the pilot, until the rollout schedule is published, and anyone who needs to plan around guaranteed availability without a stated service commitment. The questions to ask SAL. What were gate dwell time and truck turnaround before and after at the pilot stations. Which stations are live now and what is the schedule for the rest. What does it cost and what integration does it require. And what is the defined process when the system is unavailable. On publi