Factsheets: 📈 Markets 🎯 Mandates 📋 Case Studies 📘 SOPs 🏛 Trade Bodies 🏙 Cities 🌍 Countries 🇮🇳 Indian States ⚓ Ports 🏛️ SEZs 🤝 Blocs 📜 FTAs 🛤 Corridors ⚙ Verticals 📦 Commodities 🧮 Tools ⚖️ Compare 🌐 Bilateral Hubs 📚 Library 🎓 Academy ✍️ Essays 📰 Blog 🔤 Lexicon ❓ FAQ 📡 Authority Sources ⚡ Daily Pulse 📰 Topic Briefs 📡 Google Signals 🧭 Scope Scape cron-refreshed
Live factsheets · cron-refreshed

All factsheets at a glance

Command center →
📈 Markets
554
global + India · commodities + indices + shares + crypto + FX
minute
🎯 Mandates
69
sell + buy · live
daily
📋 Case Studies
37
closed · anonymised
weekly
📘 SOPs
42
step-by-step playbooks
weekly
🏛 Trade Bodies
1,350
291 baseline + 1059 hand-curated
monthly
🏙 Cities
1,584
global atlas
daily
🌍 Countries
197
multilateral
weekly
🇮🇳 Indian States
37
state trade profiles
monthly
⚓ Ports
52
global maritime gateways
monthly
🏛️ SEZs
31
global SEZ profiles
monthly
🤝 Blocs
28
tracked
monthly
📜 FTAs
273
active or signed
monthly
🛤 Corridors
37
tracked
monthly
⚙ Verticals
50
sectoral
weekly
📦 Commodities
51
HS-coded intelligence
monthly
🧮 Tools
105
free utilities
monthly
⚖️ Compare
pairwise combinations
monthly
🌐 Bilateral Hubs
184
India × every country
weekly
📚 Library
140
interconnected
monthly
🎓 Academy
25
trade education
monthly
✍️ Essays
30
long-form analysis
monthly
📰 Blog
34
editorial
weekly
🔤 Lexicon
312
glossary terms
monthly
❓ FAQ
155
curated Q&A
monthly
📡 Authority Sources
140
curated · vetted
hourly
⚡ Daily Pulse
145
rolling 5,000 cap
hourly
📰 Topic Briefs
29
permanent archive
hourly
📡 Google Signals
123
hourly
🧭 Scope Scape
61
11 scopes
hourly
Daily factsheet · mandates
Last refresh: 15 days ago
Next:
Mandates
69
sell + buy · live
Live now
69
currently active
Verticals
20
covered

Home → Active Mandates

Active Trade Mandates

Live buy requirements, sell offers, JV positions, and investment mandates. All commission-only. All NCNDA-protected. Parties introduced only after Three P qualification. 24-month commission tail on all transactions.

Data last updated: 1 April 2026  ·  Next: 1 May 2026
BUY
Germany
EU Auto Components

German Tier 1 automotive buyer seeking IATF 16949 certified Indian precision component suppliers. Volumes: 500K–2M units/yr. HS 8708/7318. Multiple SKUs.

Engineering Value: EUR 2M/yr
High priority Enquire →
SELL
Telangana
Indian Pharma APIs

WHO-GMP API manufacturer seeking EU CMO/distributor relationships. 12 molecules. 6 generics competitive vs Chinese source. EU GMP audit ready.

Pharma Value: USD 8M/yr
High priority Enquire →
BUY
Scandinavia
Organic Textiles

Nordic retailer seeking GOTS-certified organic cotton garment manufacturers. EUR 800K/season. 4 garment categories. Post-FTA opportunity.

Textiles Value: EUR 800K/season
Medium priority Enquire →
JV
Portugal
Portugal Fulfilment

Indian D2C brand seeking EU fulfilment partner. Portugal preferred — both AJG principals on-ground. Revenue share or equity. EU-India corridor.

D2C Value: TBD
High priority Enquire →
SELL
Kerala
Kerala Spice Processor

FSSAI + AGMARK certified processor seeking European retail buyers. GI-eligible. Organic lines available. APEDA registered.

Agro Value: EUR 1.2M/yr
Medium priority Enquire →
INVEST
NCR Delhi
NCR Engineering MSME

EU investor seeking minority stake in precision engineering MSME. Revenue ₹8 Cr. IATF track record. Acquisition or PE round open.

Investment Value: INR 8 Cr revenue
Medium priority Enquire →
BUY
EU
Solar Component Supply

EU solar developer seeking Indian ALMM-listed solar module supplier for utility-scale project. Post-CBAM planning needed.

Green Energy Value: EUR 15M project
High priority Enquire →
SELL
Bengaluru
Indian SaaS to EU

B2B SaaS platform (logistics tech) seeking EU distribution partner. GDPR compliant. SOC2 audited. ARR USD 2M growing.

Technology Value: USD 2M ARR
High priority Enquire →
BUY
Netherlands
Ayurvedic Product Range

Dutch wellness importer seeking Indian Ayurvedic product manufacturer. EU Novel Food/EFSA compliance required. 15 SKUs.

Wellness & Yoga Value: EUR 500K/yr
Medium priority Enquire →

All mandates anonymised. Parties introduced under NCNDA only. Commission on completion. 24-month tail.

Submit Your Mandate →

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this institutional hub

User POV — for the practitioner navigating the Mandates institutional hub

Eight dimensions

1 · Possibility

A mandates hub that publishes live trade-mandate listings as structured records (origin + destination + commodity + volume + payment-terms + counterparty-fit + timeline) replaces the broker-WhatsApp ecosystem with a transparent surface. The possibility is to make the trade-mandate market searchable rather than rumour-driven, which is what the existing channels overwhelmingly are. Sellers find the right buyer faster, buyers find the right supplier with less spam.

2 · Plausibility

Plausibility tracks counterparty-quality control. The hub is only useful if mandates are real and properly characterised. Spam-mandate flooding would destroy the surface within a month. We control by requiring a human-in-the-loop review on every mandate before publishing, a counterparty-attestation field, and a rejection-rate metric we publish to keep ourselves honest about throughput.

3 · Probability

On a six-month horizon, mandate-led search is concentrated among professional traders and import-export firms, not retail browsers. The volume is moderate but the conversion-to-deal rate is high when matches occur. The probability that the hub becomes a deal-flow surface depends more on counterparty-quality than on visit-count, which is why the editorial review gate is the main lever.

4 · What works

What works is the structured-mandate format: every mandate has the same eight headline fields (origin, destination, commodity, volume, payment-terms, counterparty-fit, timeline, principal-contact). Visitors scan a list of mandates as quickly as scanning a stock-ticker. What works less well is unstructured "I am looking for X" prose; we reject those at intake and ask for the structured form.

5 · What doesn't work

What does not work is leaving mandates open indefinitely. A mandate that is two months old with no movement is dead but stays in the listings, polluting the surface. We auto-archive at 60 days unless the principal extends, and we flag close-to-expiring mandates so principals know to close them out cleanly.

6 · Common pitfall

A common pitfall is over-publishing buyer details. The hub publishes the mandate but not the buyer identity at the listing level — interested counterparties contact us, we vet, then we make the introduction. This is a deliberate friction trade: less throughput, less spam, higher signal. The friction is the value.

7 · Counter-intuitive insight

Counter-intuitively, smaller mandates outperform larger ones on conversion. A $500K mandate with three interested counterparties closes more often than a $50M mandate with twelve, because larger mandates have more decision-makers and more stages of due diligence. We surface "deal-stage probability" alongside the headline volume to set expectations honestly.

8 · Highest-leverage move

The highest-leverage move is the mandate-fit alerter: counterparties subscribe to a structured pattern (e.g. "pharma APIs from India to Africa, $1-5M lots, LC payment") and the hub emails them when a matching mandate publishes. The compute is trivial; the user value is high because the alternative is checking the hub daily, which most professionals will not do.

Eight user intents

9 · Who gains most

For active trading firms running deal-pipelines, brokerage operations seeking principal-aligned counterparties, mid-market exporters and importers expanding their counterparty base, treasury professionals deploying trade-finance capital, and the principal sub-group who specifically use the platform because it is principal-only (no brokerage skim). The schema rewards principal-only behaviour by highlighting principal-attestation in every mandate listing.

10 · Irreducible essence

They want a structured deal-flow surface they can scan in minutes per visit and trust to be real. The eight-field format delivers that. They also want to be findable — when their counterparty-fit matches a buyer, the alerter notifies them without their having to monitor the hub continuously.

11 · Optimal timing

When they are building or replenishing deal pipeline. Most professionals visit weekly rather than daily; the alerter handles the days-in-between. Editorial review cadence (intake → publish) is target 24 hours so mandates do not go stale during the review gate.

12 · Where (sub-areas)

Where they read it: 80 percent desktop because mandate research is a workflow task that benefits from multi-tab + keyboard. The mobile design is functional but secondary; we do not optimise for thumb-zone composition because the audience is overwhelmingly at-desk.

13 · Why misunderstood

Because the existing trade-mandate market is opaque, broker-mediated, and rumour-driven. A structured, principal-only, vetted surface is the antithesis of those characteristics. The why is fundamentally about returning trust + speed to a market that has lost both to broker-fragmentation.

14 · Highest-leverage sub-paths

Which mandate-pattern dominates per audience: long-form contract mandates for the trader-firm, short-form spot mandates for the broker-replacement use-case, structured-finance mandates for the treasury professional, sourcing-led mandates (buyer LFL + RFP) for the importer, supply-led mandates (seller-LFB) for the exporter.

15 · Whose advice to trust

Whose deal-flow shape drives the schema: professional traders structure differently than corporate procurement, which structures differently than commodity brokers. The eight-field format is intentionally sparse so each audience uses it differently — traders fill in counterparty-fit precisely, procurement fills in payment-terms precisely, brokers fill in timeline precisely.

16 · How to proceed differently

How they engage: enter via the mandate-list (filtered or unfiltered), drill into specific mandates of interest, request introduction via the principal-contact path. Time to decision: under three minutes per mandate scan; under a week from request-introduction to first-call. The surface compresses the deal-cycle without removing necessary diligence.

Developer POV — for the architect, maintainer, future contributor to this hub

Eight dev dimensions

17 · Data architecture

Data architecture: per-mandate record with the eight headline fields + intake-timestamp + review-status + expiry-timestamp + match-history. Counterparty-fit is a structured field with sub-attributes (sector, geography, deal-size-range, payment-tolerance). The matcher operates on the counterparty-fit pattern; the listing renders the headline view.

18 · Schema markup

Schema markup: each mandate emits as Demand or Offer (depending on direction) with itemOffered + areaServed + acceptedPaymentMethod + validThrough. Principal-contact emits as ContactPoint behind a contact-form gate, not as visible JSON-LD. Spam-prevention is the rationale for the gate.

19 · Internal linking

Internal linking: mandates hub → individual mandate pages → vertical hub (the relevant sector) → corridor hub (the relevant origin-destination pathway). Each individual mandate page carries a "similar mandates" rail computed from counterparty-fit similarity. Cross-content injector surfaces relevant trade-bodies + library nodes.

20 · Page-speed posture

Page-speed posture: mandate list is server-paginated (50 per page) for fast initial paint. Filter chips are server-side via URL parameters. Individual mandate pages are lightweight (under 30 KB compressed). PageSpeed-100-v7 layer applies; the alerter subscription is a tiny form with no client-side dependencies.

21 · Mobile UX

Mobile UX: mandate cards stack vertically with the eight headline fields visible in a compact summary. Tap-expand reveals full mandate detail. The alerter subscription is a sticky CTA at the bottom of the hub. Filter chips are horizontal-scroll above the list.

22 · Accessibility

Accessibility: each mandate card has aria-label combining direction (offer/demand) + commodity + headline volume. Filter chips are role=button with aria-pressed reflecting active state. Screen readers traverse mandates in date-published order.

23 · SEO saturation

SEO saturation: each individual mandate page has unique H1 + meta-description. The hub itself emits ItemList of currently-active mandates. Filtered hub views (e.g. /mandates/?vertical=pharma) get canonical-different URLs with their own ItemList. Speakable on the mandate summary line.

24 · Extensibility

Extensibility: the eight-field format is fixed for now to maintain comparability across mandates. Adding a ninth field would require schema migration which we delay until a clear new field is needed. Sub-attributes within counterparty-fit are extensible without schema changes — we add new sub-attribute keys as the matcher evolves.

Eight dev intents

25 · Maintainer audience

For the developer maintaining this hub, the most operationally-sensitive part is the review queue. Mandates that are stuck in review become a deliverable backlog; mandates that pass review without proper scrutiny become a quality problem. The review-queue dashboard at admin/mandate-review.php is the operations-control surface, and its SLA is the 24-hour intake-to-publish target.

26 · Architectural commitment

What changes when mandates flow through: data/mandates-data.php gets new records on review-pass; existing records expire on the auto-archive cron; the alerter fires email/digest events on every publish. The matcher index rebuilds nightly so newly-published mandates start matching subscriptions on next-day cadence.

27 · Refresh cadence

When the cron runs: nightly at 02:00 UTC for the auto-archive sweep + matcher index rebuild + alerter digest dispatch. Stagger from other crons. Real-time notification path (webhook to subscriber inbox) for high-priority match patterns; the rest go through the daily digest.

28 · File map

Where files live: data/mandates-data.php (the registry), data/mandate-archive.php (expired mandates kept for analytics), includes/mandate-matcher.php (the counterparty-fit matcher). Hub at /mandates/index.php (passthrough to /active-mandates.php per v140.1 fix); review tools under admin/.

29 · Existence rationale

Why human-in-the-loop review: because algorithmic spam-detection in this domain is unreliable. Trade mandates have legitimate jargon that flags spam-classifiers; spam mandates use legitimate-looking templates. The cost-of-error is asymmetric — a spam mandate published damages trust more than a real mandate held for review for an extra day. We bear the human cost.

30 · Highest-leverage extension

Which renderer: includes/mandate-template.php emits the headline summary + full detail panel + similar-mandates rail + introduction-request form. Accepts $mandate_id. Echoes directly. Idempotent.

31 · Authoritative sources

Whose responsibility: intake review is on the editorial / operations team (currently Amit + Vinod). Counterparty-fit schema curation is shared editorial + dev. Schema validity enforced by pre-flight. The principal-attestation flag is operationally enforced via the contact-form gate, not via code.

32 · Maintenance procedure

How to extend the matcher: (1) define new counterparty-fit sub-attribute (e.g. ESG-compliance, cold-chain-capability); (2) extend mandate intake form to capture; (3) extend matcher to score on new sub-attribute; (4) re-run nightly matcher index rebuild. Total: about half a day per new sub-attribute including form changes.

PhiloJain Music
Loading…

Explore

Explore the AJG knowledge graph

Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.

All hubs · 80 surfaces · click to expand ↓