Cross-reference high-volume suppliers against compliance events, active sanctions, and serious litigation. Spot the supply-risk gaps before they hit your lanes.
Three suppliers above the $50M trade threshold carry meaningful compliance overlay in 2024. Cipla shipped $439M with 71 active litigations and 1 recent serious compliance event. Granules shipped $158M with 20 active litigations and no compliance events. Hikal shipped $94M with one serious compliance event. None are blockers; all warrant procurement-side monitoring and a dual-source readiness check on the dependent lanes.
| # | Supplier | 2024 trade | Litigation | Compliance events | Posture |
|---|---|---|---|---|---|
| 1 | Cipla | IN · multi-plant | 71 active litigations | $439M · 1 event | VAI |
| 2 | Sun Pharmaceutical Industries | IN · multi-plant | 65 active litigations | $687M · sanction | OAI |
| 3 | Lupin | IN · multi-plant | 68 active litigations | $582M | VAI |
| 4 | Granules | IN · Vizag | 20 active litigations | $158M | VAI |
| 5 | Hikal Limited | IN · multi-plant | 1 compliance events | $94M | VAI |
All suppliers above a trade-volume threshold, or your active sourcing book. The overlay applies to every supplier in scope.
Compliance events, active sanctions, litigation counts, and recent serious-event indicators from v_risk_flags. Each flag is joined to the supplier entity at the warehouse layer.
Citation-anchored brief with the flagged suppliers ranked by volume × severity, and a recommended monitoring posture per supplier.
A $500M supplier with one minor flag matters more than a $5M supplier with five major flags. The ranking carries both dimensions.
Active sanction (highest), serious compliance event (high), litigation cluster (medium). Each surface as a distinct chip on the supplier row.
Suppliers above the flag threshold and within your sourcing book trigger an immediate dual-source readiness check. The brief surfaces the dependent lanes.
Trade volumes are aggregated and anonymised. Compliance events are public-record overlays from regulatory and legal filings. The composite respects the trade-data disclaimer.
A real chat thread in PharmaDB. Type a question, the AI agent runs the tools, the answer lands as a saveable note.
pharmagraph_query Twelve suppliers tracked at over $50M of 2024 trade · count is active litigations · the compliance overlay against trade volume.
The supplier-reliability overlay is the risk-adjusted view of the supplier book. PharmaDB joins trade volume to active sanctions, litigation, and serious compliance events, ranks by volume × severity, and surfaces the dependent lanes for monitoring. The view is company_trade_exports; the join is to v_risk_flags and the underlying compliance and legal feeds.
An FDA warning letter, an active import alert, or a comparable EMA/MHRA/EDQM enforcement event. The page surfaces only events in the past 24 months; older events sit in the supplier history but don't trigger the active flag.
Open commercial and patent litigation where the supplier is a named party. Active is computed against a court-status feed and refreshed weekly. Pure patent challenges in the buyer's favour don't surface; only material commercial or regulatory disputes do.
Yes. Either the supplier is on an active sanctions list or not. The flag carries a 'has_active_sanction' indicator that escalates the supplier severity to the top of the brief regardless of other signals.
Multinational generic firms typically carry several dozen active patent-and-commercial disputes at any time. The flag count is not a verdict on the supplier; it is a signal that the supplier operates in litigation-heavy markets and that supply continuity could be affected by a court outcome.
The warning-letter monitor is a feed of FDA enforcement events at the plant level. The supplier-reliability overlay is a supplier-level join against the full risk-flag catalog: sanctions, litigation, compliance events. The two run as a paired view.
Trade aggregates and risk flags refresh weekly. The overlay recomputes on every refresh. The catalog row carries the last-computed timestamp surfaced on every result page.
Bring the molecule, the lane, or the supplier you're sourcing this week. The AI agent runs it on PharmaDB in 30 minutes. You keep the brief.