Why FreightLens.io About

Large ocean freight visibility platforms have been around for years, and they serve enterprise shippers well. The question was never whether they work; it was who they were built for, and who they consistently leave behind.

The mid-market visibility gap

Small-to-midsized freight forwarders and importers move meaningful cargo volumes, enough that exceptions and delays cause real operational pain, but not enough to justify six-figure platform contracts or dedicated visibility teams.

The challenges are familiar to anyone in logistics operations:

"We knew exactly where our shipments were, until they left the port. After that, we were calling carriers the same as everyone else."

How FreightLens.io was different

FreightLens.io was designed for the operational reality of growth-focused forwarders and mid-market importers: onboarding in days rather than months, pricing scaled to a growing logistics business, and direct carrier API connections so shipment data stayed current. The focus was narrow and deliberate; knowing where every container was, raising an alert when something went wrong, and feeding accurate data into systems already in use.

Carrier coverage

Carrier integrations were built systematically, starting with the lines most commonly used by mid-market forwarders in the US trade lanes:

Beyond ocean: what was planned

Ocean carrier tracking tells you where a vessel is. The critical gaps happen at the edges: the terminal gate, the rail dray, and the inland ramp. End-to-end door-to-door visibility was the intended direction. Only the first phase below was built.

Built

Ocean Carrier Tracking

Real-time container events from ocean carriers via direct API connections. Vessel location, milestones, ETAs, and exception alerts.

Never built

Terminal Visibility

Gate-in, gate-out, and availability status from major US port terminals, starting with APM Terminals covering three of the top seven US ports.

Never built

Rail & Inland Dray

Intermodal rail tracking and inland container movements, giving visibility to the final leg that most platforms ignore entirely.

Never built

TMS / ERP Push

Automated data feeds into existing systems, so the platform became invisible infrastructure rather than another tab to manage.

Never built

Ocean Bookings and Shipping Instructions

Submitting ocean booking requests and shipping instructions to carriers from a single interface, removing the documentation back-and-forth that runs over email today.

Never built

Predictive Insights

Predictive ETA modeling, carrier performance scoring, and anomaly detection, surfacing disruption before it reaches the customer.

Who FreightLens.io was built for

For those managing ocean freight visibility with carrier portals, spreadsheets, or a TMS without live carrier data, FreightLens.io was built for exactly that situation.