China to India Import Export Guide 2026

Who this guide is for

This is an operations-first guide for import teams buying from China into India.

The China-to-India lane becomes "system work" quickly because you usually have:

• Repeat SKUs across many shipments
• Multiple suppliers and purchase orders
• Consolidations (LCL or multi-vendor containers)
• Tight timelines that make rework painful

The goal is simple: make each shipment a structured record, not a pile of PDFs.

At-a-glance checklist (before you book)

Decide the operating model first

Before generating documents, lock these:

1. Incoterms and the named place (Incoterms 2020: https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/)
2. Payment method (open account vs documentary collection vs letter of credit)
3. Clearance model in India (broker-managed, in-house, hybrid)

Late changes here create late document changes. Late document changes create customs delays.

Documentation checklist (China export -> India import)

Baseline document set for most commercial imports:

• Commercial invoice (line-level descriptions, HS, quantity/unit, unit price, currency, Incoterms)
• Packing list (packages, net/gross weights, carton marks)
• Transport document: bill of lading (sea) or airway bill (air). See: /glossary/bill-of-lading
• Any commodity-specific certificates/permits (depends on product category)

The single source of truth rule

Treat the shipment record as the master. Documents are outputs.

If any of these change, regenerate everything:

• HS code
• Description
• Quantity/unit
• Value/currency
• Packages/weights
• Party names and addresses

Do not accept "small edits" to one PDF without updating the shipment record.

Incoterms: pick a default pattern your team can execute

Incoterms define the responsibility boundary for freight, insurance, and who controls which step.

Use Incoterms 2020 as the baseline reference (source: https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/).

Practical guidance for China-to-India operators:

• FOB (common when you want control of freight): you typically manage the main carriage and can standardize forwarder handoffs.
• CIF (common when suppliers quote "all-in" freight): you must still insist on clean documents and a clear breakdown of costs.
• DDP-like promises (delivered duty paid): only use if you have a proven destination execution model. Otherwise, disputes happen at the exact moment cargo is stuck.

Pick a default and document exceptions. Changing Incoterms late usually means changing invoices late.

HS classification: control it like pricing

HS is not a clerical detail. It is a classification system used as a basis for customs tariffs and trade statistics.

WCO overview: https://wcoomd.org/en/topics/nomenclature/overview/what-is-the-harmonized-system.aspx

Practical controls:

• Build a SKU master mapping: SKU -> HS -> standard description -> typical packaging
• Assign an owner and a review cadence
• When your broker suggests a different HS, treat it like a pricing change: review impact, approve, record, and roll out consistently

This prevents the most common failure mode: the same SKU imported under different HS codes across shipments.

India-side baseline readiness (IEC and importer profile)

DGFT describes the Importer-Exporter Code (IEC) as a mandatory business identification number for exports/imports from India (source: https://www.dgft.gov.in/CP/).

If you are a trading company importing repeatedly, treat importer readiness as a pre-flight check:

• Importer details frozen (legal name/address)
• Internal policy for who can approve consignee changes
• Your broker has the right identifiers and can reuse them

If you change importer details late (or per shipment), you increase the chance of declaration rework.

India customs touchpoints: ICEGATE (high level)

ICEGATE is the Indian Customs EDI gateway portal used for online customs-related services (source: https://www.icegate.gov.in/).

Even if your broker uses ICEGATE for filing, the operator goal is the same: produce declaration-ready data.

The broker handoff: what to send as a single packet

If you want fewer back-and-forth cycles, send your broker one structured packet per shipment:

If you can generate this packet from one shipment record, you stop most rework before it starts.

What "declaration-ready" means in practice

It means your shipment record contains a clean, reusable representation of what will be declared:

• Line items: HS, standard description, quantity, unit, unit value, currency
• Packaging: package counts, package type, net/gross weights
• Parties: importer, exporter, consignee, notify party
• Incoterms and named place
• Supporting documents list

If you can hand this to the broker without a back-and-forth, you will reduce cycle time.

Supplier controls that matter on China-to-India

Most rework originates upstream. Two supplier controls remove most of it:

1. Use your invoice and packing list templates.
2. Force standard descriptions per SKU (not free text).

If you consolidate shipments:

• Require carton-level mapping (carton -> SKU lines)
• Require consistent carton marks

This makes receiving and inspection faster, and it reduces the "we can’t reconcile cartons" loop.

First shipment playbook (do this once, then reuse)

The fastest way to stabilize this corridor is to make the first shipment intentionally "slow and perfect".

Before shipment 1:

1. Build a SKU master for the first 20-50 SKUs (HS + standard description + unit + packaging).
2. Create invoice and packing list templates and make suppliers use them.
3. Decide your default Incoterms pattern.
4. Define who can approve changes (price/quantity/HS/consignee).

During shipment 1:

1. Keep one versioned shipment record.
2. Run a reconciliation check: invoice totals = packing list totals = PO totals.
3. Build an inspection packet (photos/specs) for any ambiguous goods.

After shipment 1:

1. Do a post-mortem: what changed, where rework happened, and what to standardize.
2. Update the SKU master and templates.

If you do this, shipments 2-20 become predictable.

Inspection readiness: build a small packet per shipment

Even when everything is correct, shipments can be selected for inspection based on risk criteria.

Build an inspection packet in your shipment record:

• High-resolution product photos (for ambiguous goods)
• Datasheets/spec sheets for technical items
• Country-of-origin evidence from suppliers (as needed)
• A clear mapping from packing list packages to invoice line items

The goal is answering questions quickly while the cargo is still at the port.

Common delay patterns (and fixes)

1. HS drift Fix: SKU master with an owner; require broker justification for changes.

2. Generic descriptions Fix: standard description library per SKU (aligned to HS mapping).

3. Unit mismatches (PCS vs sets vs cartons) Fix: primary unit per SKU; show conversions explicitly.

4. Weights don’t reconcile Fix: pack-out template that ties packages to weights and totals.

5. Consolidation chaos Fix: carton-level mapping and consistent marks.

6. Late consignee changes Fix: freeze importer/consignee details before BL/AWB is issued.

Landed cost control on China-to-India imports

If you want accurate unit economics, you must track landed cost per shipment.

Treat it as a ledger that accrues charges at milestones:

• Supplier cost (invoice)
• Freight and surcharges
• Insurance (if applicable)
• Origin charges and documentation fees
• Destination charges
• Clearance fees
• Duties and taxes (HS-driven)
• Inland delivery
• Bank and FX charges linked to the deal
• Demurrage/detention (if they occur)

Close the shipment ledger when the shipment closes, not at month-end.

Cost allocation (simple rules that avoid margin lies)

If you import multiple SKUs in one container, your landed cost accuracy depends on allocation.

Pick an allocation method and keep it consistent:

• Allocate freight by weight for dense goods.
• Allocate by volume for bulky/light goods.
• Allocate by value when risk/insurance/finance costs track value.

The method matters less than consistency. Consistency allows you to compare margins across shipments.

Method reference: /resources/how-to-calculate-landed-cost.

A repeatable workflow (simple but effective)

To make this corridor predictable, implement a small operating system:

1. SKU master: HS + standard description + packaging
2. Shipment record: structured line items + parties + terms
3. Document generation: invoice/packing list generated and versioned
4. Exception triggers: new SKU, new supplier, new Incoterms, new route
5. Closeout: reconcile landed cost per shipment

What "good" looks like on this corridor

If you are running China-to-India as a lane, "good" looks like:

• A shipment record that produces documents and filings data without retyping
• A stable HS and description mapping for repeat SKUs
• A documented exception process (new SKU, new Incoterms, new supplier)
• A shipment closeout that produces an accurate landed cost and margin view

A note on duty and tax changes

On any import lane, duty rates and compliance requirements can change, and some product categories can attract additional measures.

Treat your internal SKU master as a living asset:

• Review HS mapping periodically.
• Confirm duty treatment with current official references and your broker.
• When something changes, record the effective date and roll it out consistently.

For official starting points, CBIC and ICEGATE are the primary public portals for Indian Customs information and services (sources: https://www.cbic.gov.in/ and https://www.icegate.gov.in/).

How Tijara helps

Tijara is designed for repeat imports:

• Structured shipment records (so filings and documents stay consistent)
• Reusable SKU/HS masters that prevent drift
• Shipment-level landed cost tracking for true margins

If you run China-to-India as a sourcing lane, the leverage is in repeatability.