Who this guide is for
This is an operations guide for exporters shipping from India to Kenya.
If you ship repeat SKUs, treat the corridor like a lane: master data, templates, and closeout discipline.
At-a-glance checklist
| What to confirm | Why it matters | What usually breaks |
|---|---|---|
| Incoterms and named place | Defines responsibilities and cost boundaries | Incoterms mismatch across quote vs invoice |
| IEC readiness (India) | Export setup dependency | Late onboarding or missing details |
| SKU master: HS + standard description | Drives duty/compliance expectations | Generic descriptions and HS drift |
| Broker handoff packet (Kenya) | Filing speed depends on it | Missing fields and missing attachments |
| Inland delivery plan | Mombasa is not the final destination | Delivery booked late, storage costs grow |
Decide the operating model first
Before you generate any documents, lock:
- Incoterms and named place (reference: https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/)
- Payment method (open account vs documentary collection vs LC)
- Destination setup (who is importer-of-record, who clears, who arranges inland delivery)
Late changes here create late document edits. Late document edits create delays.
Documentation checklist (India export -> Kenya import)
- Commercial invoice
- Packing list
- Transport document (BL/AWB) (Bill of Lading)
- Commodity-specific certificates/permits when required
Single source of truth rule
Treat documents as outputs of one shipment record.
If HS/description/qty/weights change, regenerate documents and re-sync your forwarder/broker.
Broker handoff packet (Kenya)
Make the clearance handoff a single packet. One packet per shipment:
| Block | What to include | Why it matters |
|---|---|---|
| Parties | exporter, importer/consignee, notify party | prevents party-name rework |
| Terms | Incoterms + named place, payment method | keeps responsibility boundary stable |
| Line items | SKU, HS, standard description, qty/unit, unit value, currency | declaration-ready data |
| Packaging | cartons/pallets, marks, net/gross weights | supports reconciliation and inspections |
| Attachments | invoice, packing list, BL/AWB, certificates | reduces missing-attachment loops |
Operator goal: no rewriting by the broker.
India-side baseline: IEC
DGFT describes IEC as a mandatory business identification number for imports/exports from India (source: https://www.dgft.gov.in/CP/).
Operator controls:
- do not ship on draft invoices
- version invoice and packing list
- freeze consignee details before BL/AWB
HS classification: stabilize it
HS is the international product nomenclature used for tariffs and trade statistics (WCO: https://wcoomd.org/en/topics/nomenclature/overview/what-is-the-harmonized-system.aspx).
Build a SKU master with ownership and change logs.
Kenya-side touchpoints: single window + customs context
KenTrade states it is mandated to establish and manage Kenya's National Electronic Single Window System (NESWS) and provides TradeNet portal access points (source: https://kentrade.go.ke/about-kentrade and https://kenyatradenet.go.ke/kesws/jsf/login/KESWSLoginPage.jsf).
KenTrade also publishes practical guidance documents for imports and exports that help teams understand the single window ecosystem at a high level (sources: https://www.kentrade.go.ke/wp-content/uploads/2022/11/220927_WEB-Imports.pdf and https://www.kentrade.go.ke/wp-content/uploads/2022/11/220927_WEB-Exports.pdf).
KRA is the official authority reference point for Kenya tax/customs services (source: https://www.kra.go.ke/en/).
KRA lists iCMS as an online service on its official website (source: https://www.kra.go.ke/en/).
Operator takeaway: send one broker packet per shipment (parties, terms, line items, packaging, attachments).
Port of Mombasa planning (KPA)
KPA describes itself as the heart of trade and commerce for Kenya and the region and operates port services (source: https://www.kpa.co.ke/).
Plan last-mile delivery before dispatch.
Mombasa is a milestone, not the finish line
If your consignee is up-country (or you have multi-drop delivery), plan the inland leg before the vessel arrives.
Operator controls:
- Confirm delivery location and receiving hours before BL issuance.
- Decide who owns inland booking and the internal cut-off.
- Put receiving constraints into the broker packet (contacts, appointment rules).
This is how you avoid the most common cost spike: cargo is available, but delivery is not ready.
Consolidation and carton mapping (mixed-SKU shipments)
If you ship mixed SKUs or consolidate multiple POs, add two controls:
- One carton labeling standard (marks).
- One packing list format that maps cartons to invoice lines.
This makes receiving fast and reduces disputes.
Documentary payments (LC / documentary collection)
If the deal uses a letter of credit or documentary collection, documents are checked strictly.
Controls that prevent rework:
- freeze templates early
- avoid late edits to consignee name, description text, Incoterms, quantities, and amounts
- set a document cut-off earlier than vessel/flight events
First shipment playbook (make shipment 1 a pilot)
Before shipment 1:
- Build a SKU master for the first 20–50 SKUs (HS + standard description + unit + packaging).
- Standardize invoice and packing list templates.
- Confirm destination model (who clears, who delivers, who receives).
During shipment 1:
- Keep one versioned shipment record.
- Reconcile invoice totals, packing list totals, and booking data.
- Capture costs as they occur.
After shipment 1:
- Record what changed late and why.
- Update templates and SKU master.
- Define exception triggers (new SKU/HS, new route, new Incoterms).
Exception triggers (when to run extra checks)
Add a lightweight exception checklist that triggers extra validation whenever you introduce a new SKU/HS, change consignee/importer-of-record, switch Incoterms, or change the delivery pattern inland.
If you run this lane weekly, make exceptions explicit. A corridor becomes reliable when “special cases” are identified before booking, not discovered during clearance.
Common delay patterns (and fixes)
-
Generic descriptions Fix: standard description library tied to HS.
-
Weights and package counts don't reconcile Fix: pack-out template and totals check.
-
Late consignee changes Fix: freeze parties before BL/AWB.
-
Unplanned inland delivery Fix: book delivery and receiving windows before arrival.
Landed cost control
Track per shipment:
- supplier cost
- freight and surcharges
- origin/destination charges
- duties/taxes
- inland delivery
- bank/FX
Close the ledger at shipment closeout so margins stay real.
Landed cost as a milestone ledger
For repeat lanes, treat landed cost as a shipment ledger that accrues charges at milestones:
- booking (freight/surcharges)
- export release (origin charges)
- arrival/discharge (destination charges)
- clearance (fees, duties/taxes)
- delivery (inland transport)
Closing this ledger per shipment is what makes margins comparable across weeks and routes.
Method reference: /resources/how-to-calculate-landed-cost.
How Tijara helps
Tijara helps repeat lanes run clean:
- structured shipment records
- reusable SKU/HS masters
- shipment-level landed cost tracking