Flexport as API layer for forwarding
Flexport
The real upside in Flexport is not moving boxes, it is turning a phone, email, and spreadsheet workflow into software that coordinates shippers, carriers, warehouses, and customs brokers in one system. Traditional forwarding still depends on people chasing rates, booking space, fixing document errors, and updating customers by hand. Flexport started with a shipper dashboard, but the bigger prize is becoming the operating layer that lets logistics counterparties exchange shipment data directly and with less labor.
-
Freight forwarding is a big but low margin service business. Flexport did $3.3B of revenue in 2021 with 20% gross margin and 1% net margin, versus incumbent forwarders like DSV, Expeditors, and Kuehne + Nagel that also operate at modest net margins. That is why software style coordination revenue matters so much more than pure forwarding volume.
-
What the API layer replaces is the manual glue work. Instead of a shipper emailing a forwarder for status, then the forwarder calling a carrier or warehouse, each party can push booking, tracking, and exception data into the same system. That creates faster handoffs, fewer mistakes, and a product that gets better as more counterparties connect.
-
The comparison is less with old line forwarders and more with adjacent logistics software and fulfillment players. ShipBob monetizes every step after goods hit the warehouse, receiving, storage, pick and pack, and parcel shipping. Flexport has pursued the same expansion logic from international freight into fulfillment, especially after buying Shopify's fulfillment arm.
The next phase is logistics unbundling in reverse, where the winning platforms stitch freight, warehousing, fulfillment, and merchant software back together through shared data pipes. If Flexport keeps deepening those connections, it can capture more of the transaction flow around each shipment and look less like a cyclical forwarder and more like logistics infrastructure.