Supply chain database: types, examples and finding shippers
A supply chain database is an organised record of the companies, products, shipments and relationships in a supply chain, built so people can search and filter it. The term covers very different things: company directories, research databases, public trade statistics, shipment-level records of who imports what, and a company’s own ERP or TMS data. For a freight forwarder looking for shippers, the useful kind is shipment-level data, because it shows which companies actually move freight on your lanes.
What is a supply chain database?
It is the memory of a supply chain: who supplies whom, what moves, on which route, how often, and who to talk to. A good one is a working system, not a folder of exports. Records are matched, kept current and searchable by the questions people ask, such as “which importers bring furniture from Vietnam into Los Angeles?”
Most supply chain databases hold some mix of four layers:
- Movement data. Customs declarations, bills of lading, shipment references, ports, modes and dates.
- Entity data. Shippers, consignees, suppliers, carriers, ports and terminals, with names and addresses.
- Commercial data. Account owner, status, quotes, notes and contacts from your CRM.
- Context. Rates, disruptions, product classifications such as HTS codes.
Which layers matter depends on who is asking. A buyer wants supplier capabilities. A researcher wants industry reports. A forwarder’s sales team wants movement data tied to named companies.
Types of supply chain databases
Search for “supply chain database” and you get a state directory, a university library guide and a SQL schema on the same page. They are all supply chain databases, built for different jobs:
| Type | What it holds | Examples | Who uses it |
|---|---|---|---|
| Industry supplier directories | Companies that can serve one industry, filterable by location and type | NYSERDA Offshore Wind Supply Chain Database (companies list themselves, updated monthly), NY-BEST battery and energy storage database | Developers and buyers looking for local suppliers |
| Research and market databases | Industry reports, company financials, journal articles | IBISWorld, ABI/INFORM, Business Source (often through a university library) | Students, analysts, strategy teams |
| Public trade statistics | Monthly or annual trade totals by country and product code, no company names | UN Comtrade, USA Trade Online (US Census Bureau), Eurostat Comext, BTS freight indicators | Market sizing, lane trends |
| Shipment-level trade data | Who imported or exported what, from where, how often | Commercial platforms built on customs declarations and bills of lading | Forwarders, carriers and suppliers finding customers |
| Supplier master data | Your own suppliers: legal names, certifications, performance, payment terms | Procurement and SRM systems | Procurement teams |
| Operational databases | Orders, bookings, shipments, inventory and milestones | ERP, TMS, WMS | Operations and finance |
The aggregate sources are free and official, and they are good for sizing a lane. They don’t tell a sales rep who to call. Only shipment-level data names the importer or exporter.
Logistics databases: the sources that matter to a forwarder
Not all logistics data deserves equal attention. Some sources help operations track freight. Others help sales find revenue. Each answers a different question:
| Source | What it tells you | Sales use |
|---|---|---|
| Customs declarations | Importer or exporter, goods, origin, destination, how often | Finding active shippers on a lane |
| Bills of lading | Shipment-level parties, ports, containers, dates | Qualifying an account by volume and pattern |
| Your CRM | Owner, stage, past quotes, lost reasons | Not prospecting into accounts you already work |
| Carrier schedules | Services, transit times, cutoffs | Giving a proposal a concrete angle |
| Port and terminal data | Which gateways matter for a region | Territory planning by port |
| Your own TMS and customer portals | Booking rhythm, exceptions, growth at existing customers | Growing accounts you already have |
The common mistake is treating all of these as one feed. The value comes when the answers connect at account level: this company, on this lane, owned by this rep, last quoted in March.
How forwarders use a shipment database to find shippers
Most freight sales teams don’t have a prospecting problem. They have a data problem. A rep is told to “target consumer goods importers in the Midwest”, pulls names from memory and directories, and sends outreach that has nothing to do with how that company ships. A shipment database replaces that guesswork in four ways.
Start with movement, not logos
Industry, size and region are easy filters and weak ones. They don’t say whether a company is moving freight on lanes where you can compete. Start from trade activity instead: importers with recurring shipments on your corridor, through your gateways, in goods you handle well. Reps don’t need more names. They need fewer, better ones. A rule that works: if a rep can’t explain from movement data why an account is on the call list, the list is guesswork.
Put sales time where your lanes are strong
If your network is strongest on a few origin and destination pairs, the database should show where shipper activity overlaps with them. Filtering by product classification narrows it further. A sales director can then assign territories by lane density and account fit instead of broad geography, so one rep doesn’t inherit a dense cluster of active importers while another gets a huge region of poor fits.
Watch for changes
A static list goes stale. The accounts worth a call this week are the ones where something changed: a new importer on the lane, a jump in volume, a new supplier country, a switch of forwarder. Those are reasons to reach out that a shipper recognises. The same data works at port level (see port import and export reports) and for one company at a time (see company import and export data).
Give the first message a reason to exist
“We’d love to support your logistics needs” says nothing. Compare two openers:
Weak: “Hi [Name], we’re a forwarder with great rates from Europe. Can we quote your next shipment?”
Better: “Hi [Name], [Company] started buying from a new supplier in Ningbo this spring, alongside your usual Shanghai flows into Buenaventura. If that lane is still settling in, we run weekly Ningbo sailings to Buenaventura and clear customs in Colombia. Worth a short call?”
The second only works if the database ties the company to a lane and a change. That is the whole point of using one for sales.
Example: what Colombian import data shows
US bills of lading name the importer, so US imports are where most people start. Colombian import records name both sides of the trade. Here are imports into Colombia, from the Coreties Colombia import data as of 24 October 2026:
- 19,000+ Colombian companies imported by ocean or air between August 2025 and July 2026.
- 10,600+ of them bought from China by sea, 2,800+ from the United States and 1,400+ from Brazil.
- Almost every ocean import record names the Colombian importer and the supplier abroad, along with the HS code and the carrier.
Colombian companies importing each cargo group by sea, August 2025 to July 2026. Source: Coreties Colombia import data, figures as of 24 October 2026, rounded down.
Plastics and polymers (3,900+ importers) and machinery (3,600+) are the biggest cargo groups, so a forwarder strong in machinery can start with those 3,600+ companies.
The third bullet is what makes this a supply chain database and not a customer list. A forwarder with a China desk can see which Colombian importers buy machinery from which Chinese suppliers, and which carrier moves it today. Public trade statistics give you one number for the value of Chinese exports to Colombia. They don’t give you a single company to call. Other countries are on the Coreties data pages.
Keep the data clean
Most supply chain database projects fail long before anyone sees a dashboard. Teams assume more data will make up for poor data discipline. It won’t.
Deduplicate entities. One importer shows up under its legal name, a trading name, a branch and a typo. Left alone, two reps prospect the same company, managers overestimate coverage, and shipment history splits across near-identical records.
Keep one golden record per account. The version your business agrees is current: legal and trading names, branch relationships, owner, status, lanes, shipment pattern, and contacts with verified emails.
Ingest carefully. Standardise company names, addresses, units and dates before matching. Decide which source wins when fields conflict. Track how often each source refreshes, and show unresolved conflicts to users instead of hiding them. A smaller dataset people trust beats a bigger one they argue about.
Govern contact data. Decide who can edit records, who owns quality, and how opt-outs work. If outreach uses personal data, build the privacy rules of each market into the process from the start.
How to choose a prospect database for logistics
If the goal is finding shippers, ask any vendor these questions on one of your own lanes, not a demo lane:
- Does it name the importer or exporter, or only show aggregate trade?
- Can I filter by origin, destination, port, product and volume at the same time?
- How fresh is it, and does it show what changed (new on lane, growth, new suppliers)?
- Does it merge one company’s name variants into one account?
- Does it find a named decision-maker with a deliverable email, or only a generic company inbox?
- Can it check against my CRM so reps don’t contact existing customers?
- How does outreach leave the system: from my reps’ own mailboxes, with someone approving each message?
For a side-by-side view of tools, see the lead generation software guide for freight forwarders and the Coreties comparisons.
Where Coreties fits
Coreties is a shipment database built for this one job. It finds the importers and exporters on a lane from customs declarations and bills of lading, and shows what changed: companies new on the lane, growing volumes, new buyers. Supply Chain Analysis gives a rep sourced reasons to reach out to a specific company. Contact discovery finds a named person with a deliverable email, never a guessed one. Drafted messages wait for the rep’s approval and send from their own mailbox. The full flow is on how it works, and the guide to finding shippers covers the method without any tool.
Supply chain database FAQ
What is a supply chain database?
An organised, searchable record of the companies, products, shipments and relationships in a supply chain. Depending on the type, it holds supplier directories, research reports, trade statistics, shipment-level records or a company’s own operational data.
Are public trade statistics enough to find shippers?
No. Sources like UN Comtrade and USA Trade Online report totals by country and product. They are good for sizing a lane, but they don’t name importers or exporters. For that you need shipment-level data, plus your CRM so you don’t contact existing customers.
What’s the difference between a supplier database and a shipment database?
A supplier database is a buyer’s record of its own suppliers: certifications, performance, payment terms. A shipment database records trade between companies you don’t yet work with, which is what a forwarder needs for prospecting.
What database technology do supply chain systems use?
Transaction systems such as ERP and TMS usually run on relational SQL databases. Analytics on large shipment histories runs in data warehouses or columnar databases. Graph databases suit questions about multi-tier relationships, such as which suppliers sit behind your supplier’s supplier.
What is a supply chain management database?
Usually the operational data behind supply chain management software: orders, suppliers, inventory, shipments and milestones in an ERP, TMS or WMS. It records your own supply chain. It doesn’t show other companies’ trade, so it won’t help you find new customers.
Is there a database of logistics or freight forwarder companies?
Yes, but most are directories: names, addresses and services that companies list themselves, like the industry directories in the table above. They tell you who exists, not who moves freight. To find shippers that need a forwarder, use shipment-level data on the lanes you sell.
Do small forwarders need an enterprise data stack?
No. Start with one lane, one branch or one segment. Build a trusted list of active importers, match it against your CRM, remove duplicates, find the right contacts, and reach out with a message tied to what each company ships.
Want to see your own lane in the data? Get a free market study for one of your lanes, or book a demo.
