Shipment / Bill of Lading: Data Point Intelligence Guide

A bill of lading names the shipper, the consignee and the goods on the same page. It is the closest thing international trade has to a confession.

Understanding the Shipment / Bill of Lading as an intelligence artifact

A shipment record is the documentary trace of goods moving between parties. The bill of lading is the core artifact, carrying a document number, shipper and consignee names and addresses, notify party, carrier and vessel, ports of lading and discharge, container and seal numbers, goods description, commodity code, gross weight, package count and freight terms. Manifest data filed with customs before arrival is the machine-readable equivalent, and in several countries it becomes publicly accessible after release.

Variants change what you can see. A master bill runs between carrier and forwarder while a house bill runs between forwarder and the actual shipper, so consolidated cargo hides real parties behind an intermediary. Telex release, switch bills and transshipment through a third port deliberately break the paper chain. Air waybills and rail consignment notes follow the same commercial logic with different field names and filing regimes.

Why it matters

Shipment records tie an entity to a physical movement on a specific date, which corporate records and sanctions lists cannot do. They expose supply relationships that no party discloses voluntarily: who supplies whom, in what volume, through which intermediaries. Because the same fields repeat across many shipments, they support network construction, volume estimation, route reconstruction and detection of front companies inserted between a real buyer and a controlled supplier.

What analysts actually look for

These are the concrete, observable signals that carry weight in this area of work:

Repeated shipper and consignee pairs establish a durable supply relationship and reveal its cadence over time.
Notify party details frequently name the real controlling entity standing behind a nominal consignee.
Address and telephone details in the record link trading entities to physical premises and to each other.
Route choice, especially transshipment through a known re-export hub, indicates deliberate obfuscation of origin.
Goods descriptions inconsistent with the declared code or the container type suggest deliberate misdeclaration.
Volume and frequency establish capacity, which can be tested against the consignee's premises and stated business.
Sudden insertion of a new intermediary shortly after a designation date shows adaptation to sanctions pressure.
Container and seal numbers link the document to a physical asset and to terminal movement records.

Where the data comes from

Authoritative and openly available collection points. Always confirm licensing and terms before operational or commercial use:

ImportYeti — Free search over US import bill of lading data by company, with supplier and volume history.
Panjiva — Commercial global shipment records with entity resolution across countries, aliases and spellings.
ImportGenius — Commercial bill of lading and manifest data drawn from multiple national customs sources.
UN Comtrade — Aggregate bilateral trade used to judge whether a shipment volume is normal for the corridor.
FMC licensed intermediary register — US registry of ocean transport intermediaries and NVOCCs named on bills of lading.
Equasis and IMO GISIS — Vessel identity, ownership and management detail for the carrier named on the document.
OFAC and EU consolidated lists — Screening for designated shippers, consignees, vessels and intermediaries in the record.
OpenCorporates — Registry records for the trading entities together with their officers and registered addresses.

A working method

A repeatable sequence beats ad-hoc searching. This is a practical starting workflow:

Extract and normalise parties — Parse shipper, consignee and notify party into names, addresses and contacts, standardising them before any matching.
Resolve entities — Match parties to company registry records, treating name variants, transliterations and shared addresses as candidate links.
Distinguish house from master — Establish whether the record is a forwarder-level bill concealing underlying parties, then seek the house bill.
Validate the cargo — Compare goods description, commodity code, gross weight and container type for internal consistency and plausibility.
Reconstruct the route — Map load, transshipment and discharge ports, then check the named vessel's track for the voyage dates.
Screen every party — Run all named parties, the vessel and the carrier against sanctions, denial and debarment lists.
Build the network — Aggregate shipments over time to graph supply relationships, volumes and the emergence of new intermediaries.

How this connects across the intelligence taxonomy

Intelligence work does not respect neat boundaries. The mission domain you are working, the disciplines you practise, and the data points you pivot on are one connected system. These are the direct relationships for this entry — every link is also a tag, so you can follow any thread across the whole library.

Collected by these disciplines

Geospatial Intelligence — Intelligence Derived from Place
Logistics Intelligence — Cargo, Freight, and Physical Movement
Criminal Intelligence — Intelligence Supporting Criminal Investigation
Legal Intelligence — Law, Litigation, and Regulatory Intelligence
Corporate Intelligence — Understanding Companies, Structure, and Control
Maritime Intelligence — Vessels, Shipping, and the Maritime Domain
Sanctions Intelligence — Screening, Designations, and Evasion Detection
Environmental Intelligence — Environmental Conditions, Damage, and Crime
Economic Intelligence — Economic Conditions, Trade, and Market Signals
Imagery Intelligence — Interpretation of Visual Imagery

Investigated in these domains

Pivots to these data points

HS Commodity Code — The Harmonized System code classifying a traded good — the key to trade-flow analysis.
Shipping Container — An ISO container identifier — trackable across ports, vessels, and customs events.

Inside the platform: where Shipment / Bill of Lading lives

The Quantus platform is 204 pages behind a 147-item sidebar organised into six working groups: Command (24 items), Dashboards (15), Threat Theaters (14), Intelligence Domains (15), Investigate (34), and Administration (45). This entry is not a page in isolation — it is a thread running through several of them.

The modules that matter most here:

datapoint.php?dp=dp_shipment — Data point hub
domain.php?d=drugs — Drug Trafficking dashboard
domain.php?d=weapons — Weapons Trafficking dashboard
domain.php?d=wildlife — Wildlife Trafficking dashboard
domain.php?d=counterfeit — Counterfeiting & IP Crime dashboard
search.php — Advanced search, filter and pivot
correlate.php — Correlation graph
cases.php — Case management

Each dashboard is local-first: it renders from the platform’s own database rather than depending on a live third-party call, so it still works when an upstream API is unreachable or rate-limited. Heavy aggregates are cached with a hard query time cap and degrade to the last good value instead of hanging the page.

Automation, playbooks and AI skills

Analysis that only happens when someone remembers to run it is not a capability. The platform ships a 30-step automation pipeline (cron.php) that collects, ingests, resolves, enriches, correlates and scores on a schedule — 25 seeders, 11 resolvers and 7 enrichment runners, all idempotent and cursor-based so a run can be interrupted and resumed without duplicating or losing work.

AI skills that apply

The 16 one-click operations in ai-skills.php are deterministic jobs, not free-text generation. The ones that matter here:

Enrichment Runner
Enrichment → Local
Correlate Infrastructure
Summarise (Copilot)
Generate Report

Alerting closes the loop: rules in alerts.php fire on new indicators matching a saved query, so a first sighting in this area raises a notification rather than waiting to be noticed at the next review.

Feeds, data sources and the API

The collection layer runs a feed registry of free, machine-readable sources — bulk blocklists and trackers (Maltrail, IPsum, FireHOL, the full abuse.ch corpora, phishing databases, Emerging Threats, Spamhaus, DigitalSide, ThreatView), authoritative government feeds (CISA KEV, OFAC, UN and EU sanctions lists), and reference datasets (RIR allocations, ip-to-ASN and geolocation tables, MITRE ATT&CK, EPSS). collect.php pulls them server-side on a schedule; feeds.php and source-catalog.php show what is registered, what it covers and when it last ran.

Anything the platform holds is reachable programmatically. The REST API in api.php exposes 11 endpoints — status, stats, search, lookup, recent, export, bulk_check, top_threats, by_category, categories, check — and export.php streams 18 formats in bounded chunks, so a million-row export neither exhausts memory nor times out:

STIX 2.1, MISP, OpenIOC 1.1, CEF (ArcSight), LEEF 2.0 (QRadar), Zeek/Bro intel, Snort/Suricata rules, Palo Alto EDL, BIND RPZ, hosts blackhole, iptables, CSV, JSON, NDJSON/JSONL, XML.

That covers the CTI standards (STIX 2.1, MISP, OpenIOC), SIEM ingestion (CEF, LEEF, Zeek), detection engines (Snort/Suricata), and direct enforcement (Palo Alto EDL, BIND RPZ, hosts, iptables) — so intelligence developed here can be actioned in the tools you already run, without a manual reformatting step. A TAXII 2.1 server and a MISP/RSS feed are also served for pull-based sharing.

Use cases

Three ways this entry earns its keep in day-to-day work:

Triage under time pressure. An artifact or report lands and you need a defensible read in minutes, not days. Extract and normalise parties is the first move; the platform pre-computes the enrichment so the analyst spends the time on judgement rather than lookups.
Building the picture. A single indicator is rarely the story. Distinguish house from master turns one artifact into a network — shared infrastructure, repeated selectors, the same operator behind different names — via the correlation graph and the cross-entity link engine.
Producing something actionable. Analysis that ends in a document nobody can use is wasted. Build the network feeds the case file, the detection rule, the block list or the referral — with sourcing attached so the recipient can verify it.

Case management (cases.php), watchlists, saved searches and scheduled reports mean the work persists between sessions and survives an analyst leaving the team.

How each sector uses Shipment / Bill of Lading

The same entry is worked very differently depending on who you are, what authority you hold, and what you are ultimately producing. A military analyst is supporting a commander’s decision; a journalist is meeting a publication standard; an NGO caseworker is protecting a person. The underlying artifacts are shared — the constraints, outputs and thresholds are not.

🎖 Military and defence

Shipment records support logistics intelligence and counter-proliferation: who is supplying an adversary's defence industry, through which ports and intermediaries, and at what tempo. A defence analyst uses them to assess sustainment capacity, identify chokepoints and vulnerabilities in an adversary supply chain, and vet contractors in a joint operations area before contracting with them. They also support maritime interdiction planning by tying a vessel to a declared cargo and a consignee. The constraints are evidential and legal: a bill of lading is a declaration, boarding requires a legal basis under national or coalition authority, and commercial data licences apply to defence users as much as to anyone else.

🕵 National intelligence

Manifest and bill of lading data is among the highest-yield open sources for network analysis, because it names parties and dates that no entity discloses voluntarily. It answers standing requirements on procurement networks, sanctions evasion and dual-use diversion, and it fuses naturally with corporate registries, sanctions data and vessel tracking. The analytic product is usually a supply network with volumes and a timeline rather than a single transaction. Handling depends on the source: public manifest data is unclassified and shareable with industry and partners, which is often the intent, while vendor-licensed data carries redistribution limits that must be respected in dissemination.

👮 Law enforcement

Shipment records support charging decisions in smuggling, sanctions, customs fraud, counterfeiting and trafficking cases by placing named parties on a specific movement of specific goods on a specific date. Public manifest extracts are useful for leads, but evidence normally requires the filed declaration obtained from the customs authority, along with the carrier's records, which come by production order or summons and arrive with a custodian attestation. Cross-border records require mutual legal assistance or a customs mutual assistance agreement. The declaration proves what was declared, not what was in the container, so the physical inspection or controlled delivery remains the evidential core.

🔍 Private investigation and corporate security

Corporate investigators use shipment data for supplier verification, counterfeit source tracing, competitive intelligence within lawful limits, forced-labour and sanctions exposure in the supply chain, and litigation support. It is one of the few sources that reveals a competitor's or counterparty's actual trading relationships. The constraints are contractual and legal: vendor terms restrict redistribution, some jurisdictions restrict use of customs data, and a private actor may not obtain declarations from a customs authority or induce a broker or forwarder to disclose client records. Name resolution errors are common, so verify before a report asserts a supply relationship.

📰 Journalism and OSINT media

Trade record journalism has exposed sanctions circumvention, arms transfers and illicit timber and seafood chains. The verification standard is to obtain the record itself rather than a vendor summary, resolve the named parties to registry entities, check the vessel and voyage against tracking data, and corroborate with a second document or source before asserting a supply relationship. Vendor entity resolution merges similarly named companies, and reporting a supply relationship that does not exist is both a correction and a legal exposure. Give the named companies specifics and a genuine right of reply, and protect sources who supply non-public records.

🌍 NGO, humanitarian and human rights

Shipment data lets human-rights and environmental organisations connect a factory or plantation to the brands importing from it, which is the evidential core of most supply chain accountability work. It supports customs petitions on forced labour, due diligence complaints and campaign reporting. Practice should be careful with attribution: a consolidated bill names a forwarder rather than the buyer, and misnaming a company damages both the target and your credibility. Where evidence includes worker testimony, protect the workers, since identifying a specific shipment can identify who spoke. Preserve records to accountability standards because these findings often become submissions.

🎓 University and research

Researchers use shipment microdata for supply chain network analysis, trade fragmentation studies and illicit flow estimation. Key methodological issues are coverage bias, since public manifest data is dominated by a handful of countries and absence of records rarely means absence of trade, confidentiality requests that remove significant traders, and entity resolution error that fabricates or destroys network edges. Report the resolution method and an estimated error rate. Vendor licences frequently prohibit redistribution of the underlying records, so plan replication around derived statistics and share code. Named contacts in records are personal data and should be excluded from any published dataset.

Playbook: working Shipment / Bill of Lading end to end

A repeatable sequence, from the moment the requirement lands to the moment a product is delivered and the case is closed out. Each phase states what you are trying to establish, not merely what to click — the point is a defensible chain of reasoning, not a checklist.

Phase 1 — Establish the record type

Determine whether you are holding a master bill between carrier and forwarder, a house bill between forwarder and the actual shipper, an air waybill, a rail consignment note or a customs manifest extract. Each conceals and reveals different parties. A good output states the document type and what it can and cannot show. Stop when you know whether the consignee named is the buyer or an intermediary.

Phase 2 — Preserve and normalise

Store the record as retrieved with source, date and any document reference, then parse shipper, consignee, notify party, carrier, vessel, ports, container numbers, goods description, weight and codes into structured fields. Keep the raw text alongside the parsed version. A good output is a structured record with a pointer to its unaltered source. Stop when every field is captured, including the ones you do not currently need.

Phase 3 — Resolve the parties

Match shipper, consignee and notify party to company registry records, treating transliteration, name variants and shared addresses as candidate links rather than confirmed identity. Record the evidence for each match. Vendor entity resolution should be treated as a suggestion. A good output is an entity table with match confidence and supporting registry references. Stop when each party is either resolved with evidence or explicitly marked unresolved.

Phase 4 — Chase the underlying bill

Where the record is a master bill or names a forwarder as consignee, the real parties sit on the house bill. Seek it through the data source, the customs authority via lawful process, or by inference from consistent volume, route and timing patterns. A good output either identifies the underlying parties or documents that the record is forwarder-level. Stop when the limitation is resolved or clearly stated in the product.

Phase 5 — Validate the cargo internally

Compare goods description, commodity code, gross weight, package count, container type and declared value for consistency. A tank container against dry goods, a weight impossible for the described cargo, or a code inconsistent with the description are the classic misdeclaration signatures. A good output is a consistency check with each discrepancy named. Stop when the document has been read against itself completely.

Phase 6 — Reconstruct the voyage

Map load port, transshipment points and discharge port, then check the named vessel's position history for the voyage dates. A route inconsistent with the vessel's actual track is a strong indicator that the document is wrong or the cargo moved differently. A good output is a route with dates checked against tracking. Stop when the physical movement either corroborates or contradicts the paperwork.

Phase 7 — Screen everyone named

Run shipper, consignee, notify party, forwarder, carrier and vessel against sanctions, export-control denial, debarment and enforcement lists with dated versions. Apply ownership rules to capture unlisted subsidiaries of designated parents. A good output is a dated screening log covering every named party. Stop when nothing named in the record remains unscreened. Repeat the screen against the designation dates relevant to the shipment, not only against today's list. Historic movements must be judged against the measures in force at the time.

Phase 8 — Aggregate into a network

Combine records over time to build shipper and consignee pairs, volumes, cadence and route patterns. A single shipment is an anecdote; the network is the finding. Watch for the emergence of new intermediaries and changes in route or corridor. A good output is a graph with edge weights reflecting volume and time. Stop when adding records no longer changes the structure you are describing.

Phase 9 — Test against designation dates

Overlay sanctions designation dates, control list additions and enforcement actions on the shipment timeline. Insertion of a new intermediary or a change of transshipment hub within weeks of a designation is a recognised adaptation signature. A good output is a before and after comparison anchored to the designation date. Stop when the response, or its absence, is documented. Note that absence of any change is also a finding, since it suggests the network was unaffected or unaware.

Phase 10 — Check capacity plausibility

Test declared volumes against the consignee's premises, stated business, storage and processing capacity using facility and registry evidence. A trading company at a residential address importing industrial volumes is a front, and this check identifies it without any non-public data. A good output pairs volume with an assessment of physical capability. Stop when the volume is either plausible or demonstrably not.

Phase 11 — Separate declaration from cargo

Write the product so that what was declared, what the physical record shows and what you infer are visibly distinct. A bill of lading evidences a declaration about cargo, not verified contents, and any assertion about what actually shipped needs inspection or a separate source. A good output survives the objection that the document only proves what someone wrote. Stop when the language matches the evidential weight.

Phase 12 — Manage licence and disclosure

Record the source and its redistribution terms for every record, mask personal contact details, and decide what can be published or shared with partners. Where the finding names companies, prepare specifics for a right of reply. A good output is a product whose sourcing can be disclosed without breaching a licence or exposing an individual. Stop when the licence position and the personal data position are both documented.

The platform ships this as a step-checked workflow in playbooks.php, so progress is recorded against a case rather than held in someone’s head.

Source register: what to collect from, and how

Sources are listed with their access model so you can plan around cost and licensing before you build a dependency on them. Open means no account required; registration means a free account or API key; licensed means paid or institutional access. Always confirm current terms — licensing changes, and a source that was free for research may not be free for commercial or evidential use.

Source	Access	What it gives you	How it is used here
ImportYeti	Open	Free search over United States import bill of lading records by company, with supplier relationships, volumes and shipment history.	Fast free first pass to establish whether a United States importer has a documented relationship with a foreign supplier.
Panjiva	Licensed	Commercial global shipment records across many countries with entity resolution, alias handling and company profiles.	Broadest multi-country coverage for network construction, though entity resolution must be verified before relationships are asserted.
ImportGenius	Licensed	Commercial bill of lading and manifest data drawn from United States and several other national customs sources with search and alerting.	Alternative coverage and alerting on named parties, useful for monitoring a network for new counterparties over time.
UN Comtrade	Registration	Aggregate bilateral trade statistics by commodity code, partner and period, published from national customs returns.	Establishes whether an observed shipment volume is normal or exceptional for that corridor and commodity.
FMC licensed ocean transportation intermediaries	Open	United States register of licensed freight forwarders and non-vessel-operating common carriers with addresses and qualifying individuals.	Identifies and verifies the intermediaries named on bills of lading and links them to responsible individuals.
Equasis	Registration	Free consolidated vessel data including identity, ownership, management history, classification and port state control inspections.	Verifies the carrier vessel named on the document and exposes its ownership and management structure.
IMO GISIS	Registration	Official International Maritime Organization ship particulars, company identification numbers, casualty and port reception records.	Authoritative confirmation of vessel identity and registered company numbers where commercial sources disagree.
OFAC and EU consolidated sanctions lists	Open	Designations covering companies, individuals, vessels and aircraft, with identifiers and programme codes.	Screens every named party, the vessel and the carrier against binding restrictions before a relationship is asserted.
OpenCorporates	Registration	Company records aggregated from official registers across jurisdictions with officers, addresses, status and filings.	Resolves shipper and consignee names to legal entities and exposes shared addresses and officers linking parties.
MarineTraffic and VesselFinder	Registration	Terrestrial and satellite position data, port call histories and vessel particulars derived from automatic identification system broadcasts.	Tests whether the vessel named on the document actually made the voyage the paperwork describes, and when.
National customs authorities	Licensed	The filed declarations themselves, with complete party details, valuation and classification, held by the importing or exporting state.	The evidential source obtained by lawful process, as distinct from the derived commercial extracts used for leads.
Global Fishing Watch	Open	Open vessel behaviour analytics derived from position data, including transhipment encounters, loitering and transmission gaps.	Corroborates or challenges a declared voyage where transhipment at sea would break the documentary chain.

Prefer sources that publish a methodology and a revision history. A dataset that changes silently is a liability in any product that has to survive challenge.

Tooling

Tools commonly used against Shipment / Bill of Lading. None of these replace judgement, and each carries its own failure modes — know what a tool infers versus what it observes.

OpenRefine — Clusters and normalises shipper and consignee name variants before entity resolution; clustering is heuristic and merging distinct companies is a common failure.
Neo4j or Linkurious — Builds and queries supply networks from resolved parties and shipments; visual density suggests importance that shipment counts alone do not establish.
pandas — Aggregates shipment records into volumes, cadence and route statistics; requires careful deduplication because the same movement often appears in several records.
Vessel tracking platforms — Verify the named vessel's actual voyage against the declared route; coverage gaps at sea are normal and must not be read as concealment.
yente or sanctions screening services — Screens large party lists against consolidated designations; thresholds must be tuned for transliterated trading names or the queue becomes unusable.
Aleph — Cross-references shipment parties against registries, leaks and court records in one index; coverage is uneven and absence of a match proves nothing.
Document capture with hashing — Preserves retrieved records with retrieval timestamps for evidential integrity; commercial platforms often prohibit bulk capture, so terms must be checked.

AI skills and automation in detail

These are deterministic jobs with defined inputs and outputs, not open-ended prompting. Each is idempotent and cursor-based: interrupt one and it resumes where it stopped rather than duplicating work or losing progress.

Enrichment Runner — Walks the indicator set through a chosen provider in time-boxed, cursor-based batches that resume rather than restart.
Enrichment → Local — Materialises enrichment into the local store so dashboards render from your own database instead of a live third-party call.
Correlate Infrastructure — Builds the cross-entity link graph: shared hosting, reused certificates, overlapping registrants, repeated selectors.
Summarise (Copilot) — Produces a narrative summary beside the underlying records. It explains; it never creates indicators or assigns attribution.
Generate Report — Assembles a sourced product from the current case or query, with provenance attached to each element.

A note on the boundary: the only skill that involves a language model is Summarise (Copilot), and it writes prose about records that already exist. Nothing else on this list involves generation of any kind. No indicator, relationship or attribution in the platform originates from a model. See the full skill list.

Tradecraft notes

The distinctions that separate a competent analyst from a fast one:

Know which bill you are reading. A master bill names the forwarder as shipper or consignee and hides the real parties by design, so a network built entirely from master bills maps logistics providers rather than trade relationships.
The notify party is the most underused field on the document. It frequently names the entity that actually cares about the arrival, which is often the real buyer or its agent rather than the nominal consignee.
Absence of records is not absence of trade. Public manifest data is dominated by the United States and a handful of other countries, and confidentiality requests remove significant traders entirely, so a clean search across a European corridor means almost nothing.
Verify vendor entity resolution before you rely on it. Aggregators merge similarly named unrelated companies routinely, and a fabricated supply relationship in a published report is both a correction and a legal problem.
Compare the declared route against the vessel's actual track as a matter of routine. Paperwork is adjusted more easily than a hull moves, and a voyage the ship did not make is among the strongest indicators available.
Watch the timing around designation dates. New intermediaries, changed transshipment hubs and fresh incorporations appearing within weeks of a listing form a recognisable adaptation pattern that a static network view will miss entirely.
Test volume against physical capacity. A consignee whose registered premises could not hold or process the declared volumes is a front company, and this can be established from imagery and registry data alone.

Measuring whether it is working

Capability claims should be falsifiable. These are the measures that show whether work on Shipment / Bill of Lading is producing anything, and they are worth baselining before you change process or tooling.

Proportion of named parties resolved to registry entities with recorded evidence rather than accepted from vendor entity resolution.
Rate at which asserted supply relationships survive verification against a second independent source before the finding is published.
Number of front companies identified through capacity and premises checks rather than through screening hits.
Median time from a designation being published to the affected shipment network being reassessed for adaptation.
Share of findings in which the declared route was checked against the named vessel's actual tracked movement for the voyage dates.
Proportion of products where source licence terms and personal data handling are documented before dissemination.

Beware of measuring volume alone. Indicator counts and report counts rise easily and say little; time-to-attribution, proportion of findings that survive review, and how often a product changed a decision say a great deal.

Common pitfalls

Public manifest data is largely US-centric plus a handful of other countries, so absence of records rarely means absence of trade.
Shippers can request confidentiality, which removes significant traders from otherwise complete datasets.
Freight forwarder names dominate consignee fields, masking the beneficial buyer behind consolidated cargo.
Goods descriptions are written for customs rather than analysts and are frequently generic or deliberately vague.
Vendor entity resolution merges similarly named unrelated companies, creating supply relationships that do not exist.
A bill of lading evidences a declaration about cargo, not verified contents; only inspection establishes what shipped.

Legal and ethical considerations

Shipment datasets contain commercially sensitive information and personal data such as named contacts, and most vendor feeds impose contractual limits on redistribution. Confirm that your source and its intended use are lawful in your jurisdiction. Naming a company as a sanctions evader carries defamation and commercial-damage risk, so separate the documented record from inference and state confidence explicitly. Retain the original record with retrieval date and source reference to preserve its evidential value.

Data integrity: no fabrication, no drift, no hallucination

Intelligence that cannot be traced back to a source is not intelligence, it is assertion. Everything in this entry — and everything in the platform behind it — is built on a small number of non-negotiable rules.

Provenance on every record

Every indicator carries the source that supplied it, a first-seen and last-seen timestamp, and a sighting count. Where several feeds report the same artifact, each contribution is recorded separately rather than collapsed, so you can see whether a finding rests on one source or twelve. Source attribution travels with the data into every export, so a recipient can audit a claim without asking you for the working.

Nothing is invented to fill a gap

If the platform has no data for Shipment / Bill of Lading, it says so. Empty is displayed as empty — never padded with plausible-looking placeholder values, sample records or illustrative examples that a reader might mistake for observations. A dashboard with no rows is a true statement about collection coverage, and it is treated as a gap to close, not a blemish to hide.

Scoring is deterministic and reproducible

Threat scores, reputation grades and risk tiers are computed from stated inputs with fixed weights, not estimated. The same inputs always produce the same output, and the formula is visible rather than a black box. Aggregates are cached with an explicit time-to-live so a figure on screen is never silently stale — and when a heavy query exceeds its time budget the platform serves the last known-good value and labels it, rather than inventing a fresh number or hanging.

Where AI is used, and where it is not

Language models summarise and explain. They do not create indicators, assign attribution or manufacture relationships. No IP address, wallet, hash or identity in the platform originates from a model — every one is ingested from a named feed, resolved from a reference dataset, or entered by an analyst with a source recorded. Copilot output is presented as narrative alongside the underlying records, never in place of them, so a reader can always check the summary against the evidence.

Guarding against drift

Enrichment is additive and timestamped rather than overwriting. Reference data — sanctions lists, allocations, taxonomies — is re-synchronised from the authority on a schedule instead of being edited in place, so local copies cannot quietly diverge from the source of truth. Attribution is recorded with a confidence level and the reporting it rests on, and inferred relationships are labelled as inferred. When a source retracts or corrects, the correction propagates rather than leaving a stale assertion behind.

What this means for you

You can put a finding from this platform in front of a regulator, a court, a board or a partner agency and show where each element came from. That is the standard the tooling is built to — because in this work, being confidently wrong is more damaging than being usefully uncertain.

By the numbers

The taxonomy this entry belongs to is not a marketing list — it is the actual structure of the platform: 52 mission domains, 52 intelligence disciplines and 65 data points, each with a live dashboard behind it. Supporting that: 18 indicator types, 14 playbooks, 16 AI skills, 18 export formats and a 30-step automated pipeline.

This particular entry connects directly to 10 intelligence disciplines, 10 mission domains, 2 closely related entries — every one of them a tag you can follow, and a dashboard you can open.

Questions analysts actually ask

The consignee is a freight forwarder. How do I find the real buyer?

Look at the notify party first, since it frequently names the entity that actually needs to know the cargo has arrived. Then seek the house bill, which sits under the master bill and names the underlying shipper and consignee; some data sources carry both, and a customs authority holds them. Failing that, work by pattern: consistent volumes, commodity, route and timing across many shipments through the same forwarder often identify a single underlying buyer, and delivery records, warehouse locations or subsequent domestic movements can confirm it. Until you have that, say the record is forwarder-level rather than naming a buyer you have inferred.

How reliable are goods descriptions on bills of lading?

They are written for customs and commercial purposes, not for analysts, and they range from precise to deliberately meaningless. Generic descriptions such as machinery parts or general merchandise are extremely common and are not by themselves suspicious. What is analytically useful is internal inconsistency: a description that does not match the commodity code, a weight impossible for the described goods, a container type unsuited to the cargo, or a description that changed between the master and house bill. Treat the description as one field to be cross-checked rather than as a statement of contents.

Can I use shipment data to prove a company breached sanctions?

It can be the backbone but rarely the whole case. The record can establish that a movement was declared between named parties on a date, which combined with a designation date and the ownership position is powerful. What it does not establish is what was actually in the container, whether the parties knew of the designation, or whether a licence or exemption applied. Prosecutions normally combine the declaration obtained from the customs authority with carrier records, financial records and communications, all obtained by legal process. As an analyst, present the documented movement and the timing, and mark the intent element as assessment.

Why does the same shipment appear three times in my dataset?

Because the same physical movement generates multiple records: a master bill and one or more house bills, separate filings by carrier and forwarder, amendments and corrections, and in some datasets one record per container. Deduplicating naively on container number or bill number will either merge distinct consignments or leave duplicates that inflate your volume figures dramatically. Build a deduplication rule using bill number, container, date and party combination, test it against a sample you have checked by hand, and report volumes with a note on the method. Inflated volume claims from undeduplicated data are a common published error.

A company requested confidentiality and disappeared from the data. What now?

Work the counterparties. Confidentiality requests suppress the requesting party's name from public manifest extracts but do not suppress the other side of the transaction, so the foreign supplier's records may still show shipments to a suppressed or partially masked consignee, with volume, port and commodity intact. Aggregate statistics for the corridor and commodity code still include the flow. Vessel and container records may still be visible. Also note the request itself as a finding: it has a date, and a company that sought confidentiality shortly after adverse attention is telling you something.

Is it lawful to use commercial shipment databases in every jurisdiction?

Not uniformly. The underlying data originates from national customs filings, and countries differ on whether manifest information is public, whether it may be resold, and whether use for particular purposes is permitted. Vendor contracts add further restrictions, typically prohibiting redistribution, bulk export and use in products sold onward. Records also contain personal data such as named contacts and telephone numbers, which engages data protection law in Europe and elsewhere. Confirm the lawful basis for your use, respect the licence, minimise personal data, and be prepared to explain your sourcing if the finding is challenged.

Standards, frameworks and further reading

Work that references a recognised framework is easier to defend, easier to hand over, and easier for a partner to consume:

The WCO SAFE Framework of Standards defines advance cargo information requirements and risk assessment against manifest data.
The WCO Data Model standardises the data elements exchanged between traders and customs administrations.
The Revised Kyoto Convention sets the international baseline for customs procedures including declaration and release.
The UN Layout Key and UN/EDIFACT messages define the structure of commercial trade documents exchanged internationally.
The Hague-Visby and Rotterdam Rules govern the legal effect of the bill of lading as a contract and document of title.
The International Ship and Port Facility Security Code frames security requirements for ships and terminals handling the cargo.
The US Trade Act advance manifest rules are what generate the publicly accessible United States import manifest data most analysts rely on.
UN/LOCODE standardises the port and inland location codes appearing throughout shipment records.

References

Primary sources and authoritative references for this entry. Publishers revise and retire material, so treat the retrieval date as part of the citation and re-check before relying on any of it in a formal product.

SAFE Framework of Standards and the WCO Data Model — World Customs Organization. International standards for cargo declaration content and risk assessment.
Licensed ocean transportation intermediaries register — United States Federal Maritime Commission. Register of forwarders and non-vessel-operating carriers named on bills of lading.
Equasis vessel information system — Equasis, hosted by the European Maritime Safety Agency. Consolidated ship identity, ownership and inspection data for named carriers.
Global Integrated Shipping Information System — International Maritime Organization. Official ship particulars and company identification numbers.
UN Comtrade database — United Nations Statistics Division. Aggregate bilateral trade used to benchmark observed shipment volumes.
Sanctions programmes and designation lists — Office of Foreign Assets Control, US Department of the Treasury. Designations covering trading parties, vessels and carriers.
OpenCorporates company register aggregation — OpenCorporates. Registry records used to resolve shipper and consignee identities.
Global Fishing Watch vessel behaviour data — Global Fishing Watch. Open analytics on encounters, loitering and transmission gaps relevant to transhipment.

Link integrity: every reference above was verified with a live request when this page was generated. Where a publisher had moved or withdrawn a document, the link was repointed at a preserved copy in the Internet Archive and marked as archived. Anything with no reachable copy anywhere had its link removed rather than left to rot — the source is still credited, it simply cannot be linked.

Put it into practice

The Quantus Intel threat intelligence platform operationalises this entry: resolves shipment parties into supply networks and screens every counterparty and carrier. Explore the platform, or browse the rest of the library by following any tag above.