Loop Launches Logistics Data Platform After $95M Series C

What does Loop's new platform do for fleet software?

Loop's Logistics Data Platform extracts and standardizes data trapped in emails, PDFs, and disconnected systems — the fragmented invoice, BOL, and shipment records that cause TMS integrations to fail and force manual reconciliation in small-fleet back offices. The platform launched Monday after a $95 million Series C round led by Valor Equity Partners, with backing from 8VC, Founders Fund, Index Ventures, J.P. Morgan Growth Equity Partners, and Tao Capital Partners.

"Automation and AI are only as powerful as the data foundation they operate on," said Matt McKinney, CEO and co-founder of Loop. "With this launch, Loop fundamentally shifts from a platform that helps humans work faster to an autonomous system that executes complex logistics strategies on their behalf."

Why bad data kills fleet software projects

For decades, logistics teams have worked with unstructured data — rate confirmations in email threads, detention charges on paper receipts, accessorial fees buried in carrier invoices. Transportation can't optimize costs when fuel surcharges and detention are manually keyed from PDFs. Finance lacks visibility into true landed costs when accessorials arrive weeks after the primary invoice. Customer-care teams operate reactively because shipment exceptions live in a different system than the TMS.

McKinney traced the problem to his time at Uber Freight. "When we were on the freight product at Uber Freight, we found an industry-wide problem: invoice reconciliation," McKinney said. "As we got into that and realized what was causing all the issues and exceptions, we discovered it was bad data."

The breakthrough came when large language models that McKinney expected to mature in 2030 delivered in 2025, making Loop's data-extraction mission viable at scale.

What the platform does that TMS integrations don't

Loop's platform ingests documents and communications from any source — email, EDI, API, scanned paper — and outputs structured records that feed TMS, WMS, and financial systems without manual data entry. The system identifies invoice line items, matches them to shipments, flags exceptions, and surfaces cost variances that would otherwise require a clerk to reconcile spreadsheets against carrier statements.

For small fleets running legacy TMS software, the platform acts as a translation layer. A carrier sends a detention invoice as a PDF attachment. Loop extracts the stop time, calculates the billable hours, matches the shipment ID, and writes the charge into the TMS as a structured record — no manual keying, no missed accessorials, no month-end surprise when the carrier statement doesn't reconcile.

The platform also surfaces cost patterns that fragmented data hides. If a shipper consistently generates detention at the same facility, Loop flags the pattern and quantifies the cost. If a lane's fuel surcharges diverge from the contracted formula, the system surfaces the variance before the invoice is paid.

Where this fits in the fleet-software stack

Loop does not replace TMS, load boards, or fleet-management platforms — it sits upstream, cleaning the data those systems consume. Fleets moving AI driver coaching into the cab rely on clean telematics and video metadata; Loop addresses the parallel problem on the transactional side, where invoice and shipment data determine whether the TMS can automate billing, whether finance can close the books without manual reconciliation, and whether AI tools have the foundation to optimize routing or carrier selection.

The platform's value proposition is highest for fleets and 3PLs that handle high document volume — brokerage operations reconciling hundreds of carrier invoices per week, dedicated fleets managing accessorials across dozens of shippers, intermodal operators tracking container fees and chassis charges across multiple terminals. Small fleets with simpler operations may not justify the integration cost unless manual reconciliation is already consuming multiple hours per week.

What changes for fleets using this

Fleets that adopt the platform eliminate the manual step between receiving a carrier invoice and posting the charge in the TMS. Detention, lumper fees, and fuel surcharges flow into the system as structured data the moment the document arrives. Finance teams close books faster because accessorials are captured in real time rather than surfacing weeks later. Transportation teams see true lane costs — including every accessorial and surcharge — without waiting for month-end reconciliation.

The platform also enables AI tools that require clean historical data. Predictive routing models need accurate detention and dwell-time records. Carrier-selection algorithms need complete cost data, including every accessorial. Load-tendering automation needs real-time rate and capacity data that matches the contracted terms. Loop's platform provides the foundation those tools require — the difference between an AI pilot that fails because the training data is incomplete and one that delivers measurable cost reduction.

For fleets evaluating the platform, the decision hinges on whether manual data entry and invoice reconciliation currently consume enough labor hours to justify the integration cost and whether the TMS and financial systems can ingest the structured data Loop outputs. The platform does not fix poor carrier communication or eliminate accessorials — it surfaces them faster and ensures they are captured in the systems that drive operational and financial decisions.