What this guide covers
This is an operations-first guide for exports from India to Nigeria.
On this corridor, reliability comes from boring discipline:
- stable line-item data
- clean packing totals
- a broker packet that is complete
- destination planning before arrival
At-a-glance checklist
| What to confirm | Why it matters | What usually breaks |
|---|---|---|
| Incoterms and named place | Defines who owns freight/insurance/clearance and cost boundaries | Quote vs invoice mismatch |
| IEC readiness | Export setup dependency | Late onboarding |
| SKU master: HS + standard description | Duty/compliance expectations and filing quality | Generic descriptions and HS drift |
| Packaging/weights totals | Prevents reconciliation issues | Totals don't reconcile |
| Destination plan (port + inland) | Delays after discharge create cost | Inland delivery not planned |
Decide the operating model first
Before you generate any PDFs, 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 -> Nigeria 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 and re-sync.
Broker handoff packet (what to send every time)
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 | becomes declaration data |
| Packaging | cartons/pallets, marks, net/gross weights | supports reconciliation and inspection |
| 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 exports/imports from India (source: https://www.dgft.gov.in/CP/).
Controls:
- version your invoice and packing list
- freeze consignee/importer details before BL is issued
HS classification: keep it stable
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.
Nigeria-side customs and ports (high level)
Nigeria Customs Service is the official reference point for customs services and information (source: https://customs.gov.ng/).
Nigerian Ports Authority is the Federal Government agency that governs and operates ports and lists major port complexes (sources: https://nigerianports.gov.ng/ and https://nigerianports.gov.ng/ports/).
Operator takeaway: plan last-mile delivery and document cut-offs before dispatch.
Port planning: treat the destination as a system
Nigeria cost blowouts are usually planning failures, not “bad freight”.
Before dispatch, confirm:
- Destination port/terminal and final delivery location.
- Who owns port charges, clearance fees, and inland delivery.
- A document cut-off earlier than carrier milestones.
- Receiving hours and a named receiver.
If you wait until cargo arrives to decide receiving, you pay with storage and rework.
Consolidation and carton mapping (mixed-SKU containers)
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 line items.
This reduces disputes and makes inspections/receiving faster.
Pre-arrival controls: stop demurrage before it starts
Most port-related margin damage comes from starting the destination plan too late.
Before cargo arrives, confirm:
- a hard document cut-off (earlier than carrier milestones)
- delivery address and a named receiver (with receiving hours)
- inland delivery plan (booking owner + internal cut-off)
- a reconciliation gate: invoice totals, packing list totals, and booking data match
If you do this consistently, “port delays” turn into a short exception list you can manage.
Receiving SOP (prevent disputes)
Minimal receiving SOP that prevents most disputes on mixed-SKU shipments:
- receive against carton marks first
- count cartons, then reconcile to line items
- photograph damage before breakdown
- log exceptions as:
carton mark / issue / quantity / photo link
Documentary payments (LC / documentary collection)
If your deal uses documentary collection or a letter of credit, 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).
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.
-
Missing broker packet Fix: one structured handoff packet with line items, packaging, and attachments.
-
Late consignee changes Fix: freeze parties before BL/AWB.
-
Unplanned inland delivery Fix: book inland delivery and receiving windows before arrival.
Cost allocation for mixed-SKU containers
If you ship multiple SKUs in one container, pick a consistent allocation method for shared costs (freight, origin/destination charges):
- by weight
- by volume
- by invoice value
Consistency matters more than the perfect method. It is what lets you compare margins shipment-to-shipment.
Exception triggers (when to slow down)
Treat these as triggers to run extra checks before dispatch:
- new SKU or HS change
- new consignee/importer-of-record
- change in Incoterms or payment method
- new discharge port/terminal or new inland delivery pattern
Landed cost control
Track per shipment:
- supplier cost
- freight/surcharges
- origin/destination charges
- duties/taxes
- inland delivery
- bank/FX
- storage if it occurs
Close the ledger at shipment closeout so margins stay real.
Landed cost as a milestone ledger
For repeat Nigeria shipments, track 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)
This is the simplest way to see which part of the system is moving your margin.
If costs are rising, the ledger also shows whether the fix is an upstream document control change or a downstream port/receiving planning change.
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