Aggregate trade flows by destination currency. Where is your USD-equivalent exposure to ZAR, NGN, BRL, or TRY? Hedge the material currencies.
Of $14.2B in 2024 declared export value across 174 destination countries, $4.13B (29.2%) flows to USD-settled destinations. EUR-zone is the next concentration at 13.9% ($1.96B). The remaining 57% sits across 99 distinct currency zones, the long tail where hedging cost compounds fastest.
All trade or a portfolio. Default returns the destination currency exposure for the full trade book; a portfolio scope returns just the molecules you ship.
Destination country resolved to currency code. USD-equivalent trade value summed per currency. Share, growth, and ranking computed at the warehouse layer.
Citation-anchored brief with the top currencies, the hedging priorities, and the historical volatility band per currency.
Every destination currency normalised to USD-equivalent value. The output is comparable across the trade book regardless of headline FX rates.
Currencies above 1% of trade are flagged as material. Currencies above 5% trigger the hedging-priority workflow with an estimated notional.
Each currency's historical USD volatility folds in. A 10% ZAR exposure with 20% historical volatility is a different hedge than 10% GBP exposure with 8% volatility.
If non-USD exposure is concentrated in a small set of currencies, the hedging book is straightforward. If it is spread across 20+ currencies, the cost of hedging exceeds the saving on most positions.
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 destination currencies tracked in 2024 · share is USD-equivalent value as fraction of total trade book · 0 to 1 scale.
The currency exposure view is the treasury-facing FX map. PharmaDB aggregates destination-country trade by currency code, surfaces the material exposures, and overlays historical volatility for the hedging priority decision. The view is molecule_country_flow joined to countries for currency resolution.
Trade declarations are denominated in USD by convention, but the cash flow on the destination side is in local currency. The page maps the USD-equivalent exposure so a treasury team can quantify how much of the book is exposed to non-USD FX risk.
PharmaDB's default is a currency that accounts for 5%+ of the trade book and has at least 10% annualised USD volatility. Currencies below the size threshold rarely pay back the hedging cost; currencies below the volatility threshold rarely need it.
Several Eurozone destinations (France, Germany, Italy, Spain) share the same currency. The page aggregates them into one EUR bucket so the hedging book reads correctly. The country-level detail is preserved in the underlying view.
An FX move that's not passed through to local prices erodes margin on the destination side. The currency-exposure view sits next to the API price benchmark distribution so the pricing team can model both signals together.
Yes. The currency aggregation is destination-driven; both API and FDF trade roll up to the same currency buckets. FDF often pays back hedging better because the price stickiness on the destination side is higher.
Trade aggregates refresh monthly. Currency aggregation 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.