Source collection
Customs declarations, bill-of-lading or shipment sources, and bilateral or mirror trade sources are handled as distinct source categories.
Source transparency
Trade Data Methodology
BillOfLadingData.com organizes customs declarations, bill-of-lading records and mirror trade data into searchable trade intelligence. Sources are standardized and connected to companies without implying that every country has identical granularity, fields or freshness.
Processing model
From source record to usable intelligence.
The processing sequence preserves the distinction between source trade activity and later company, contact or KYB enrichment.
Coverage snapshot: Methodology
Schema standardization
Country names, ports, dates, units, product descriptions and HS codes are mapped into consistent fields while source-native detail is retained where required.
Company normalization
Company names and identifiers are normalized to reduce spelling, suffix and formatting differences across source records.
Entity and relationship matching
Shipment parties are connected to normalized businesses and trade relationships using available identifiers and contextual fields.
Update processing
New source deliveries are validated, transformed and added on the cadence shown in the country catalog. Frequency differs by source.
Enrichment and governance
Available contacts and KYB information can be matched after company identification. Enrichment remains separate from the underlying trade record.
Source categories
Direct and mirror data are not the same.
Customs declaration data
Government or official reporting sources may include importer, exporter, product, HS code, value, quantity, origin, destination and transaction dates. Available fields differ by country and period.
Bill-of-lading and shipment data
Manifest and bill-of-lading sources may include shipper, consignee, notify party, ports, carrier, vessel, container, product description, dates and transport details. Master and house bill handling differs by source.
Mirror or bilateral data
Mirror data describes trade between reporting partners and is useful for market analysis. It should not be interpreted as the same company-level or shipment-level detail as a direct transaction source.
Normalization and matching
What happens to the data.
Country, port and location values are mapped to consistent reference formats.
Product descriptions and HS codes are retained and normalized where a source supports them.
Duplicate handling considers source identifiers and available record attributes.
Company matching uses available names, identifiers, domains, addresses and contextual trade information.
Contact and KYB records are attached only after a company match can be made.
Source-native fields remain available for country-specific API or bulk requirements where agreed.
Limitations
What buyers should confirm.
Source availability can change. Confidential, suppressed or incomplete records may omit parties, values or quantities. Product language, HS-code depth, transport modes, history and update timing differ by market.
A relevant sample and field specification should be reviewed before integration or bulk purchase. Country pages show centrally published information, while the commercial specification confirms the exact delivery.
Read complete data-quality notesA clear next step
Validate the methodology for your requirement.
Share the countries, fields, time period and intended use. We’ll confirm the applicable source type, limitations and delivery structure.