Panjiva: what it returns, and whether it works in Clay

Panjiva is not available in Clay. It is best for Diligence, Content demo. Pricing: Sales call. Access: UI and enterprise data feeds through S&P Global Market Intelligence. Pricing unknown (enterprise, sales-led)..

Trade dataEvidence: External observationLast checked

Data domains: Trade, Company, Corporate hierarchy, Signals, Competition.

What does Panjiva return?

Official fields: (from Panjiva shipment record and company pages, not an API schema) bill of lading number; departure date; arrival date; consignee; shipper (with original-format names); notify party; carrier; port of lading; port of unlading; shipment origin; weight (gross and net); quantity; container count; CIF value and declaration number (some customs sources); HS code categories on company profiles. TEU and full feed schema not confirmed.

What can you derive from it?

1. Nearshoring move: an importer's share of shipments from China falling while Mexico or Vietnam rises. 2. Supplier concentration: share of volume from the top shipper shows supply risk. 3. Volume momentum: quarter-on-quarter shipment growth by consignee proxies demand. 4. Customer list inference: consignees of a competitor's factories reveal its accounts. 5. Corporate linkage: shipments rolled up to S&P entity IDs show group-level activity across subsidiaries.

How would a GTM team use it?

1. PE screen: use Panjiva inside Capital IQ to score targets on import growth and supplier diversity during sourcing. 2. Revenue trigger: alert supply chain, customs or 3PL portcos when an importer starts shipping from a new country. 3. Competitive watch: monitor competitor factory shipments and flag new consignees each month. 4. Market map: size an HS-code category across 20+ customs sources by importer. 5. Buyer map: importers with rising concentration risk are prospects for sourcing and supplier-diversity offers.

What are the caveats?

Not a native Clay integration as of 2026-10-17 (checked against Clay's integrations catalog). No public API confirmed, so it cannot be called directly through Clay's HTTP API column; use exports or a contracted feed. Causality: same forwarder and NVOCC caveat as ImportGenius; a shipment shows goods moving, not who ultimately buys or why. Coverage: varies by customs source; US data is bill-of-lading based, other countries vary in detail. Official field schema for the feed was not found publicly; fields listed are those shown on Panjiva record pages.

Sources

  1. Panjiva documentation