countries · sectors · sub-national hubs · trade bodies · FTAs · tools · academy · essays
11 questions found
Sea freight transit times from Indian ports to EU ports: JNPT/Mundra to Rotterdam (Netherlands): 22-28 days. JNPT to Hamburg (Germany): 24-30 days. JNPT to Antwerp (Belgium): 22-27 days. Chennai to Felixstowe (UK): 22-26 days. Times vary by shipping line, routing (via Suez Canal or Cape of Good Hope in Red Sea disruption), and transshipment at Colombo, Jebel Ali, or Port Klang.
Primary EU ports receiving Indian sea freight: (1) Rotterdam (Netherlands) — Europe' largest port, 40%+ of EU container imports, ideal for Netherlands, Belgium, Germany, (2) Hamburg (Germany) — Germany' primary port, good for Northern Europe, (3) Antwerp (Belgium) — diamond, chemical, and general cargo hub, (4) Felixstowe (UK) — primary UK port for Indian goods, (5) Piraeus (Greece) — growing Mediterranean hub, good for Eastern/Southern EU, (6) Barcelona (Spain) — good for Spain, Portugal, and Southern France.
FCL (Full Container Load): you book an entire container for your cargo — 20ft (maximum ~28 CBM) or 40ft (maximum ~67 CBM). FCL is cost-effective when your cargo fills at least 70% of the container. LCL (Less than Container Load): your cargo shares a container with other shippers' cargo. LCL has a higher per-CBM rate but no minimum volume. Rule of thumb: if your cargo exceeds 15 CBM, FCL is usually cheaper than LCL.
ISPM 15 (International Standards for Phytosanitary Measures No. 15) requires all wood packaging material (pallets, crates, dunnage) used in international shipments to be heat-treated at 56°C for 30 minutes or fumigated with methyl bromide, and marked with the ISPM 15 stamp showing treatment method and country code. All wood pallets and crates in India-EU shipments must be ISPM 15 treated. Non-ISPM 15 compliant wood packaging causes consignment rejection and quarantine at EU entry.
ATA Carnet is an international customs document allowing temporary importation of goods (samples, exhibition goods, professional equipment) into multiple countries without payment of import duties. Valid for 1 year. Issued by chambers of commerce in India (FICCI, CII, ASSOCHAM). Use ATA Carnet for: goods displayed at EU trade fairs (Hannover Messe, Ambiente, Interpack), samples for potential EU buyers, professional equipment for site visits.
Bill of Lading (B/L): a negotiable document of title — whoever holds the original B/L controls the goods. Required for LC transactions where the bank needs document control as security. Original B/L must be surrendered at destination to release goods. Sea Waybill: a non-negotiable document — goods are released to the named consignee without presenting the original document. Used for open account trade between trusted parties. Sea Waybills process faster at destination but cannot be used for LC transactions.
Recommended: Institute Cargo Clauses A (ICC-A) — the broadest all-risks marine cargo cover. ICC-A covers all risks of loss or damage except war, strikes, inherent vice, and deliberate damage. For high-value cargo (pharma, gems, electronics): ICC-A plus War Risk cover (separate endorsement) plus Strike, Riots and Civil Commotions (SRCC). Insure for CIF value + 10% (standard practice). Note: CIP Incoterm requires ICC-A minimum; CIF Incoterm only requires ICC-C minimum — always upgrade to ICC-A.
Red Sea disruptions (from late 2023) caused by Houthi attacks on commercial vessels in the Red Sea caused most shipping lines to reroute via the Cape of Good Hope (around Africa), adding 10-14 days to India-EU transit times and significantly increasing freight rates. As of 2026, many shipments still use the Cape route. Check current routing with your freight forwarder and budget for extended transit times and higher rates.
(1) Approach 2-3 FIATA-registered freight forwarders in India for quotes (FCL or LCL), (2) Compare rates, transit times, routing (direct or transshipment), and cut-off dates, (3) Book via forwarder — they handle booking with shipping line (Maersk, MSC, CMA CGM, Hapag-Lloyd), (4) Deliver cargo to the CFS (for LCL) or ICD/port (for FCL) before the container cut-off, (5) Forwarder handles shipping bill filing through their CHA, (6) Receive B/L from shipping line (typically 5-10 days after sailing).
A Multimodal (or Combined Transport) Bill of Lading is issued when goods travel under a single contract covering more than one mode of transport — e.g., road from factory to Indian port, then sea to Rotterdam, then road to German buyer. The multimodal transport operator (MTO) issues a FIATA Multimodal Transport B/L (FBL) covering the entire journey under a single document. Useful for door-to-door India-EU shipments.
Cold chain logistics maintains products at controlled temperatures throughout the supply chain. Required for: pharma bioproducts (2-8°C), vaccines (-70°C for some), fresh fruit and vegetables (2-8°C), dairy (-18°C for frozen), seafood (0-4°C or frozen). Cold chain India-EU: refrigerated containers (reefers) from Indian port via sea to EU port. MCOLD and CIAL (Cochin) are key Indian cold chain export hubs. EU importers of Indian cold chain products must also have compliant GDP (Good Distribution Practice) cold storage.
Can't find your answer? Ask our principals directly.
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
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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
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.
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}".
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.
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.
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.
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.
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.
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
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.
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.
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.
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}/.
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.
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.
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.
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.
Explore
Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.