Did the sanction cut the molecule or just the route? Belarusian potash after Klaipėda
Trade-flow companion to the price wedge (R72), producer-side variant. Most cases in this corpus track a consumer-side control (China restricts a buyer); this is the fourth-generation producer-side variant — a Western sanction on a foreign producer — but with a signature none of the earlier producer cases (Russian aluminium / diamonds / gold / uranium) carry: the sanctioned producer is landlocked, so the control could attack a single physical transit chokepoint (one railway to one port) instead of the molecule. This is a DUAL-SCORE / alternative-track signal — never folded into any Tier-1 exposure score. Research, not investment advice; nothing here asserts a laundered origin on any single shipment — the finding is that the detector itself goes blind when the trans-shipment partner is a co-dominant producer of the same material.
Verdict
Belarus (Belaruskali, one state producer at Soligorsk) held ~20% of the world potash market before 2022 — a top-3 supplier alongside Canada and Russia. The EU (4th package, June 2021), the US (OFAC designation of Belaruskali Dec-2021, of the Belarusian Potash Company Aug-2022) and above all Lithuania's termination of Klaipėda rail transit on 1 February 2022 were built to sever the single artery that had carried Belarusian potash to seawater since 2009. For one year it worked: 2022 production fell ~60% to ~3 Mt, and Belarus's world share collapsed from ~20% to ~9% (OSW; REFORM.news/Kommersant). Then it leaked — not by re-labelling a molecule, but by re-routing the chokepoint. Russia opened its ports; the volume came back.
| Belarusian potash | 2018–19 peak | 2022 (sanction bites) | 2023–2025 (recovery) |
|---|---|---|---|
| World market share | ~20% | ~9% | recovering toward pre-2022 |
| Production / output | rev. $2.7–2.8 bn (2018–19) | −60%, ~3 Mt (2022) | ~7 Mt (2024, reported) |
| Export volume | ~11–12 Mt product/yr via Klaipėda | slumped | ~12 Mt (2025 est., Argus) — exceeding pre-sanction |
| Sea route | Klaipėda (Lithuania), since 2009 | Klaipėda closed 1 Feb 2022 | 11.6 Mt via Russian ports (2025, Kommersant) |
| China share of Belarus sales | 17% (2021) | — | >70% (2023), ~$1.5 bn |
Sources: OSW Centre for Eastern Studies commentary (2024-11-20); REFORM.news reporting Kommersant (2025 Russian-port total + split); RFE/RL; Carnegie (Jan 2026); Argus potash pricing (via press). Tonnages mix K₂O-nutrient and KCl-product bases across sources — treat the direction (collapse → recovery) as firm and the absolute levels as basis-ambiguous; see caveats.
The 2025 Russian-port throughput, per Kommersant (via REFORM.news), splits:
| Russian export gateway for Belarusian potash (2025) | share |
|---|---|
| Bronka (St Petersburg) | 50% |
| Ust-Luga | 25% |
| Rail to China + CIS (land border, no port) | 9% |
| JSC PKS (St Petersburg) | 8% |
| BazisPort (St Petersburg) | 7% |
Belarus now uses terminals at ~20 Russian ports from St Petersburg to the Caspian (Murmansk, Novorossiysk, Astrakhan, Vladivostok also cited). The locked-out Western tonnage was redirected to Brazil, China and India; Belaruskali reportedly discounted up to 50% below market (>60% to Brazil) to clear it. By Argus's read Belarus was on track to ship over 12 Mt in 2025 — above pre-sanction levels.
Why this case breaks the detector (the co-producer blind spot)
Every earlier case leans on volume-implausibility: a country with ≈0% of world capacity for the material posts a surge, and that is arithmetically impossible without laundered origin (Thailand antimony, phosphate's phantom flags). That test is structurally defeated here. The trans-shipment partner is Russia — the world's #2 potash producer (~19% of ~39 Mt K₂O world output in 2023, Uralkali + EuroChem; USGS MCS 2024). A surge in potash leaving Russian ports trips no implausibility alarm, because Russia can legitimately produce almost any volume you observe. The molecules can pass through a genuine top-3 producer's export infrastructure and emerge indistinguishable, by volume alone, from that producer's own output.
So the two fingerprints this desk usually reads are both muted:
- Volume-implausibility → blind. Russia is a legitimate mega-producer; you
cannot separate re-flagged Belarusian MOP from genuine Russian MOP in destination customs on tonnage grounds. This is the potash analogue of the Myanmar-KIO intra-origin blind spot and the cobalt reporter-wall — a structural limit, not a data lag.
- Common-ownership tell → not established (N). The sanctioned monopoly trader
(Belarusian Potash Company) still markets the tonnage; the new hop is a logistics relationship with Russian port operators (Bronka, Ust-Luga, PKS, BazisPort), not a namesake shell of the antimony (Youngsun → Thai Unipet) pattern. We did not trace a Belarusian→Russian ownership pipe to a named registry filing, and do not assert one.
What is cleanly public, and what makes the leak visible without either fingerprint, is the route + volume-recovery data itself: port-by-port throughput (Kommersant), the producer's own recovered export total (Argus), and the collapse-then-recovery share series (OSW). When the molecule can't be caught, the logistics chokepoint and the producer's revenue recovery are the signal.
The transmission chain
`` Belaruskali (Soligorsk) ──[Klaipėda rail/port, until 1 Feb 2022]──> world market │ sanction severs the single Western artery ▼ Belaruskali ──[rail east into Russia]──> ~20 Russian ports (Bronka 50%, Ust-Luga 25%, St Petersburg terminals) ──> Brazil / China / India (non-sanctioning buyers), at 50–60% discounts │ └─(open question)─> any leg re-flagged Russian-origin into a *sanctioning* market would be invisible to the volume test — co-producer blind spot ``
The control targeted a route and a set of buyers, not the commodity. A landlocked producer with a co-sanctioned neighbour that (a) owns seawater and (b) is itself a top-3 producer of the identical molecule has a ready-made bypass — and the bypass restores volume without ever needing a phantom flag, because the non-Western buyers don't require one.
What it implies for the Tier-1 blind spot
A Tier-1 exposure score that reads "Belarusian potash −60%, sanctions effective" off 2022 data would be two years stale and directionally wrong: 2025 volume is at or above pre-sanction levels. More importantly, the score cannot use its standard laundering detector here at all — so for any material whose only viable trans-shipment partner is a co-dominant producer of the same material, the alternative track must fall back to route/throughput and producer-revenue evidence rather than implausible-origin customs tables. Potash is the template for that fallback.
Caveats (why this is GATE 0)
- No post-relabel customs table. We have not traced Belarusian potash entering
a sanctioning market under a false Russian/third-country flag to a named customs dataset — because, per the co-producer blind spot, such a table would be indistinguishable from genuine Russian trade. The relabel-into-EU/US leg is an open question, not a finding.
- No ownership pipe. Common-ownership tell = N (logistics, not a shell);
no registry filing traced.
- Basis ambiguity. Sources mix K₂O-nutrient and KCl-product tonnage and
"production" vs "export"; the ~3 Mt (2022) / ~7 Mt (2024) / ~12 Mt (2025) figures are not a single consistent series. Direction is firm; levels are approximate.
- The port split is one newspaper report (Kommersant via REFORM.news), not a
customs release; treat the percentages as indicative.
- Inference framing throughout: this documents a **route-circumvention and
market-redirection that neutralised the sanction's volume effect, evidenced by public logistics and pricing data — it does not** assert smuggling or origin fraud on any shipment.
The EU carve-out footnote (a second, legal leak)
Distinct from the physical re-routing, the EU's 2021 potash measures were widely reported to contain an HS-code carve-out (bands of potassium-chloride K₂O content left outside the restriction), which let a slice of Belarusian potash keep entering the EU legally — the transformation-washing family's cousin: not a false origin, but a legal gap in the instrument. That leg is noted here as a known reported loophole, not quantified in this pass — flagged for a GATE-1 follow-up against the consolidated EU regulation text.