FLSIGForeign Logistics & Strategy Insights Group

The economics of bill-of-lading data: who buys it, who uses it, what for

Published March 25, 2026

This brief examines the commercial structure of the bill-of-lading data market: who generates the records, who aggregates them, who buys the resulting products, and what use cases sustain the pricing. Researchers at FLSIG observe that the bill-of-lading data category is widely consumed but poorly understood, and that the user who does not grasp the upstream economics tends to over-pay for breadth they do not need or under-pay for granularity they do.

Where the records come from

A bill of lading is, in its primary function, a transport document: a receipt issued by the carrier acknowledging that goods have been received for shipment, identifying shipper, consignee, vessel, port pair, cargo description, and quantity. Its commercial role as a document of title is older than its role as a data source. The data role exists, in the form most familiar to researchers, because of a specific regulatory regime.

The dominant source of structured, queryable bill-of-lading records in the open ecosystem is the United States Automated Manifest System (AMS), administered by US Customs and Border Protection. Under the regime described in CBP's Automated Manifest System documentation, ocean carriers are required to file manifests for cargo destined to or transhipping through the US, in advance of arrival. Significant portions of these filings are released into the public record. The records identify shipper and consignee at company-name granularity, list cargo by description (often with HS codes), state weights and container counts, and identify the vessel, voyage, and port pair.

FLSIG analysis indicates that the AMS regime is the structural backbone of the commercial bill-of-lading data market globally, in the sense that the US import side is the largest single data stream and most accessible. Other jurisdictions, notably Brazil, India, certain Mercosur economies, and a number of Latin American countries, release analogous records under their own regimes. Most of the rest of the world does not.

The aggregator layer

The records, as released by customs authorities, are voluminous, dirty, and require cleaning, deduplication, entity resolution (multiple variants of the same company name), and indexing before they become commercially useful. The aggregator layer exists to perform this work. A handful of commercial aggregators dominate the segment, with a long tail of regional and niche providers behind them.

The aggregator's product, abstracted, is a queryable database in which the customer can interrogate flows by HS code, by named shipper, by named consignee, by country pair, by port pair, by date range, or by combinations of these. Pricing tiers reflect the granularity, the recency, the geographic coverage, and the volume of queries permitted.

Who actually pays

FLSIG analysis suggests the buyer base for bill-of-lading data sorts into five archetypes, each with distinct economics.

Trade-finance and credit-insurance underwriters use the data to verify counterparty trade history, validate working-capital advances against shipping records, and detect anomalies that may indicate fraud or distress. The use case is high-value, the per-query cost tolerance is high, and the data must be reliable. This segment effectively underwrites the upper-tier subscription pricing of the major aggregators.

Competitive-intelligence and corporate-strategy functions at larger industrial firms use the data to track competitor sourcing, identify upstream supplier relationships, and detect shifts in geographic supply patterns. The use case is high-value but lumpy; firms typically buy access in bursts tied to specific projects rather than as a continuous subscription.

Supply-chain risk and ESG due-diligence teams use the data to trace supplier relationships, identify exposure to specific jurisdictions or named entities, and support compliance with emerging supply-chain due-diligence regimes. This segment has grown materially in recent years as regulatory regimes, including the EU Corporate Sustainability Due Diligence Directive and analogous national rules, have expanded the documentation burden on importers.

Sales and business-development teams at industrial exporters use the data to identify import volumes by potential customers, prioritise prospect lists, and detect when an existing customer's purchasing pattern shifts. This is the use case most relevant to the mid-market exporter audience, and the one with the most variable willingness to pay.

Researchers, journalists, and policy analysts use the data, often at lower granularity, to study trade flows. This segment buys at the bottom of the pricing schedule and underwrites little of the aggregator margin.

How the buyer mix shapes the data product

The product architecture of the aggregator market is shaped by the upper tiers of the buyer base, not by the bottom. Researchers at FLSIG note three consequences for the mid-market exporter.

First, the entity-resolution work that reconciles name variants to a stable corporate identity is done to a level that satisfies trade-finance underwriters. The mid-market exporter benefits from this without paying for it directly.

Second, the user-interface conventions are inherited from the credit and corporate-strategy buyers, which means the dashboards favour individual-counterparty deep-dives over aggregate market views. The exporter looking for an aggregate market view will sometimes find the interface frustrating, even when the underlying data supports the query.

Third, the recency premium is steep. The most recent two to four weeks of data carries a meaningful price premium over data older than a quarter, because the high-paying use cases of credit underwriting and risk monitoring depend on timeliness. The mid-market exporter whose use case is structural market sizing does not need this premium and should not pay for it.

What the data does not show

FLSIG analysis indicates that several common misreadings of bill-of-lading records stem from inattention to what the records do not contain.

They do not contain price. The cargo value declared to customs is filed in a separate stream (the formal entry, not the manifest), and is not part of standard bill-of-lading releases. Practitioners who quote "unit prices" from bill-of-lading-derived datasets are typically importing the price from the matched customs entry data, and the matching is imperfect.

They do not reliably identify the ultimate buyer. The consignee on the bill of lading may be a forwarder, a customs broker, or a holding entity. Identifying the operating buyer requires a layer of corporate-relationships data that aggregators bolt on at the higher tiers.

They cover ocean cargo. Air freight, road, and rail flows are not captured by the AMS regime and are surfaced only by separate, generally less comprehensive, data streams.

Where the data sits in a research stack

The practical place for bill-of-lading data in a mid-market exporter's research stack is as a complement to aggregated trade statistics and, where available, transactional customs records. The aggregated statistics tell the exporter what is being imported into a market. The transactional customs records, where accessible, tell the exporter at what value and under what HS classification. The bill-of-lading data identifies the named counterparties, the vessel cadence, and the supplier-relationship structure. FLSIG treats the broader customs-data side of this stack in its customs data primer, and the HS coordinate that joins these layers in HS-code intelligence: from classification to strategic insight.

The exporter who understands which buyer archetype's economics subsidise the data product being evaluated can negotiate and use that product with better leverage than a buyer treating all aggregator pricing as one category. The economics are not opaque; they are not advertised.