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
184
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
526
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
Trends·News·Alerts
hourly
🧭 Scope Scape
61
11 scopes
hourly

Frequently Asked Questions

Answers to 1205 questions about India-EU trade, FTAs, customs, CE marking, trade finance, regulatory compliance, pharma, logistics, and the AJG mandate process.

Clear

13 questions found

📋

Mandates

13 questions
How do I submit a mandate? +

Submit a mandate at mandate-submit.php. Provide: (1) your role (buyer or seller), (2) product description and HS code if known, (3) quantity and frequency, (4) target market or source country, (5) your requirements (certifications, quality standards, payment terms). AJG will review and respond within 5 working days.

What information do I need to submit a mandate? +

For a seller mandate: product name, HS code (if known), quantity available, certifications held (ISO, GMP, CE, etc.), preferred Incoterm, target markets. For a buyer mandate: product specification, quantity required, frequency, budget range, quality certifications required, preferred origin country, preferred payment terms.

How long does a typical mandate take to complete? +

Timeframe varies significantly by product and market: commodity agro-food mandates may complete in 4-8 weeks; manufactured goods mandates typically take 8-16 weeks for first shipment; pharmaceutical market entry (requiring regulatory approvals) may take 12-24 months. AJG provides a realistic timeline assessment at mandate acceptance.

Can AJG handle mandates for small quantities? +

AJG focuses on commercially viable mandates. Minimum mandate value: USD 50,000 per transaction. For SME exporters, AJG recommends consolidating with other exporters under a group mandate or participating in the AJG Academy to build export readiness first.

What markets does AJG primarily serve? +

Primary corridors: India-EU (27 member states), India-UAE, India-UK, India-USA, India-Singapore, India-Japan, India-Australia, India-South Africa, India-East Africa. AJG can facilitate trade across all 185 countries and 273 FTAs indexed on the platform, but these primary corridors are the deepest expertise.

How does AJG verify my counterparty? +

AJG conducts standard due diligence including: business registration verification, sanctions screening (OFAC, EU, UN lists), Dun & Bradstreet credit check, bank reference check, and ECGC/Coface country and buyer risk assessment. For high-value mandates, AJG requires audited financial statements from the counterparty.

Does AJG handle the entire trade transaction? +

AJG' mandate scope covers: counterparty identification, introduction, negotiation facilitation, documentation guidance, FTA route optimisation, regulatory compliance guidance, and payment structure recommendation. Physical logistics, legal contracts, and banking are handled by the principals' own service providers.

What happens if a deal does not close? +

If a mandate does not result in a completed trade transaction, AJG earns no commission. There is no cancellation fee or break-up cost. AJG reserves the right to withdraw from a mandate if it determines the mandate is not commercially viable, the principals are not acting in good faith, or regulatory barriers make completion impossible.

Can both a buyer and a seller submit mandates for the same product? +

Yes — and this is AJG' most efficient route. When a buyer mandate and a seller mandate match (same product, compatible volumes, compatible quality specs and certifications), AJG can work both simultaneously, accelerating the matching process.

What is an active mandate? +

An active mandate is a mandate currently being worked by AJG — where a principal has been accepted, counterparty search is underway, and AJG is actively facilitating the connection. Active mandates are listed (in anonymised form) on active-mandates.php.

How does AJG handle confidentiality? +

All mandate submissions are treated as confidential. AJG does not disclose principal identities to third parties without written consent. NDAs are executed with principals on request. AJG' online systems are secured and mandate data is not shared with any third party.

Can I mandate AJG to find a buyer in multiple countries simultaneously? +

Yes. A multi-country mandate is priced with a higher commission rate to reflect the additional complexity and the value of multi-market access. AJG will specify which markets are covered in the mandate agreement.

What is the difference between a mandate and a franchise? +

A mandate is a specific trade transaction AJG is facilitating. A franchise is an ongoing relationship where a franchisee uses the AJG platform and brand to originate and work mandates in their territory. Mandate commissions go to AJG; franchise arrangements share commissions between AJG and the franchisee.

Can't find your answer? Ask our principals directly.

Ask the Principals Contact Form

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

User POV — for the practitioner navigating the Faqs institutional hub

Eight dimensions

1 · Possibility

A FAQ atlas that consolidates the recurring questions from across all entity types — country, vertical, FTA, corridor, tool — into searchable answers replaces the per-page micro-FAQ scatter with a single navigable surface. The possibility is to make the platform answerable to questions even when the user does not know which page would have hosted the answer. The atlas is also the highest-density SEO surface because each Q+A is naturally a target keyword.

2 · Plausibility

Plausibility tracks question-currency. FAQs go stale when underlying answers change; a FAQ that says "the FTA covers up to 90 percent of HS lines" is wrong if the coverage changed. We attach last-verified per FAQ + cron-driven detection of question-answer drift. The plausibility floor is the verification cadence.

3 · Probability

On a six-month horizon, FAQ-led search is dominated by long-tail question queries that aggregator sites do not answer well. The probability that the atlas wins these queries is high because it is structured + sourced + searchable. Aggregate FAQ traffic typically grows compounding with the atlas size; doubling the atlas roughly doubles the inbound.

4 · What works

What works is one-question-one-answer-one-screen format. The reader arrived for an answer; they get it in two paragraphs and a sourced reference. Cross-references to deeper content live below the fold for readers who want depth. What works less well is questions answered with another question; we reject those at intake.

5 · What doesn't work

What does not work is over-stuffing answers. A two-paragraph answer with a sourced reference outperforms an eight-paragraph essay every time on FAQ pages because the user came for an answer not an article. Editorial discipline keeps answers tight.

6 · Common pitfall

A common pitfall is duplicating per-page FAQs into the atlas without context. A FAQ that is meaningful on a city page may be context-dependent in a way the atlas page cannot replicate. We tag context-dependent FAQs and surface their context-anchor explicitly in the atlas-version answer.

7 · Counter-intuitive insight

Counter-intuitively, the FAQs that drive the most cross-page traffic are not the most-searched questions but the questions that most often have follow-up questions. A user asking "what is rules of origin?" is at the start of a multi-question journey; a user asking "what is the Singapore postal code?" is at the end of a one-question journey. We weight follow-up-likelihood when prioritising FAQ deepening.

8 · Highest-leverage move

The highest-leverage move is the question-cluster surface: groups of related questions arranged in a rough learning order. A user reading "what is rules of origin?" sees a cluster including "how do I prove rules of origin compliance?", "what documents are needed?", "who issues the certificate?" — moving them from one question to a procedural understanding in five clicks. The cluster compute is graph-walk over the question-relation taxonomy.

Eight user intents

9 · Who gains most

For curious readers without deep platform-knowledge — first-time visitors arriving via long-tail search, students researching trade-related topics for coursework, professionals fact-checking specific points mid-work, and the question-driven sub-group of any of the above who reach for FAQ pages by reflex. The schema serves all four because a good FAQ answer is universally useful regardless of audience.

10 · Irreducible essence

They want a direct answer in two paragraphs, with a sourced reference, and a path-forward to deeper content if they want to keep going. The schema delivers all three: the answer is the headline, the reference is in-line, the deeper-content link is below.

11 · Optimal timing

When they have a specific question. FAQ traffic peaks during workdays + weekday evenings (curious learners). Editorial freshness matters because question-answer drift is most-likely to surface on FAQs that read confidently — a confident wrong answer is worse than no answer.

12 · Where (sub-areas)

Where they read it: 60 percent mobile because question-search is opportunistic. The mobile design surfaces the answer above the fold with the source-reference inline. Desktop readers consume the question-cluster surface more.

13 · Why misunderstood

Because FAQ content is the cheapest SEO win in trade-content publishing — every Q+A is a natural keyword target, and aggregator sites do not answer well. The why for the atlas is fundamentally about claiming the long-tail SERP for trade questions before competitors do.

14 · Highest-leverage sub-paths

Which FAQ-cluster dominates per audience: terminology FAQs ("what is X?") for new visitors, procedural FAQs ("how do I do X?") for execution-mode visitors, comparison FAQs ("X vs Y?") for diligence-mode visitors, edge-case FAQs ("what if X happens?") for problem-solving-mode visitors.

15 · Whose advice to trust

Whose perspective answers the question: the schema labels each answer with the actor-perspective (principal, broker, banker, regulator, lawyer) where it matters. A "what documents are needed for an LC?" answer differs depending on whether the asker is the importer, exporter, or bank.

16 · How to proceed differently

How they engage: arrive via search, read the answer, click through to deeper content if interested, exit the platform satisfied. Conversion to deeper engagement is moderate; conversion to repeat visit is high because FAQs build name-recognition. The atlas is a top-of-funnel surface that pays off in long-term recurrence.

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

Eight dev dimensions

17 · Data architecture

Data architecture: per-FAQ record with question + answer + actor-perspective + source-reference + last-verified-date + question-cluster-tags + cross-references. The cluster-graph is hand-curated; the per-FAQ data is editorial. Search index is text-indexed across question + answer + cluster-tags.

18 · Schema markup

Schema markup: each FAQ page emits as FAQPage with mainEntity Question children. Each Question has acceptedAnswer + dateModified + sameAs (the source-reference). The hub itself emits a parent FAQPage aggregating high-priority Q+A. JSON-LD identifier "ajg:faq::{slug}".

19 · Internal linking

Internal linking: FAQs hub → individual FAQ URLs (one per question) + cluster-pages (groups of related FAQs). Each individual FAQ links to relevant deep-content (entity hubs, methodology essays, SOPs). Cross-content injector surfaces relevant FAQs throughout the platform — a city page mentions "rules of origin" and gets a FAQ link for that term.

20 · Page-speed posture

Page-speed posture: FAQ pages are tiny (under 25 KB compressed). The hub is the heavier surface because it surfaces the question-cluster index (typically 200+ questions across clusters); we virtualise rendering with intersection-observer.

21 · Mobile UX

Mobile UX: FAQ page is question-as-headline + answer-as-body + source-reference-as-footer. Cluster pages are vertical-scroll lists of question-headers (tap-to-expand). Search input is sticky-top. All tap targets 48 px.

22 · Accessibility

Accessibility: FAQ pages use proper heading + section semantics. Cluster pages have role=region per cluster with aria-labelledby. Tap-to-expand questions are role=button with aria-expanded. Screen readers traverse cluster pages cluster-by-cluster.

23 · SEO saturation

SEO saturation: each FAQ page has unique H1 (the question), meta-description (the answer summary), FAQPage schema for the single Q+A, BreadcrumbList. Cluster pages emit FAQPage with the full cluster set. Speakable on the answer text. The hub gets ItemList plus the high-priority FAQPage extract.

24 · Extensibility

Extensibility: question-cluster taxonomy grows organically as the atlas widens. Adding new actor-perspectives requires schema-bump but is rare. New cross-references between FAQs are continuously curated; the cluster-graph densifies as the atlas grows.

Eight dev intents

25 · Maintainer audience

For the developer maintaining this atlas, the question-cluster graph is the most editorially-influenced data structure. Algorithmic clustering misses the pedagogical sequencing that makes clusters useful. We maintain the graph by hand at data/faq-clusters.php with cluster-master + question-to-cluster mappings.

26 · Architectural commitment

What changes when FAQs update: data/faqs-data.php gains records or updates existing ones with verification-bumps. The cluster-graph picks up new questions on next-cron rebuild. The text-search index reindexes nightly to pick up new questions.

27 · Refresh cadence

When the cron runs: nightly at 06:00 UTC for the search-index rebuild + cluster-graph cache refresh + verification-cadence sweep. Stagger from other crons.

28 · File map

Where files live: data/faqs-data.php (the registry), data/faq-clusters.php (the cluster graph), includes/faq-template.php (renderer). Hub at /faqs.php; individual FAQs at /faqs/{slug}/; cluster pages at /faqs/cluster/{slug}/.

29 · Existence rationale

Why hand-curated cluster graph: because pedagogical sequencing requires editorial judgement. "What is X?" sequences differently into deeper questions depending on the reader's expected next step, and that depends on context that algorithmic clustering does not capture.

30 · Highest-leverage extension

Which renderer: includes/faq-template.php emits the question + answer + actor-perspective badge + source-reference + cluster-rail + cross-references rail. Accepts $faq_slug. Echoes directly. Idempotent.

31 · Authoritative sources

Whose responsibility: FAQ authoring is editorial. Question-cluster curation is editorial-with-data-assist (we surface candidate cluster memberships from search-co-occurrence, editorial decides). Schema validity enforced by pre-flight.

32 · Maintenance procedure

How to add a new FAQ: (1) author question + answer + actor-perspective + source-reference; (2) submit through admin/faq-intake.php; (3) editorial review checks for over-stuffing + actor-perspective accuracy; (4) on approval, faq-publish.php writes to data/faqs-data.php; (5) editorial assigns to clusters. Total: about 30-60 minutes per FAQ.

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 ↓