Who this guide is for
This is an execution guide for exporters and trading teams shipping from the UAE to Nigeria.
UAE-to-Nigeria lanes often run as:
- re-export corridors (multiple suppliers consolidated in the UAE)
- mixed-SKU containers
- repeat replenishment cycles
The win is predictable clearance and predictable receiving.
At-a-glance checklist (before you book)
| What to confirm | Why it matters | What usually breaks |
|---|---|---|
| Incoterms and named place | Defines responsibility boundary and cost ownership | Quote and invoice disagree |
| SKU master: HS + standard description | Determines duty/compliance expectations and filing quality | Generic descriptions and HS drift |
| Packing discipline (cartons/weights) | Prevents reconciliation issues and inspection delays | Totals don't reconcile |
| Nigeria broker/importer readiness | Prevents arrival-day data collection | Missing fields and missing attachments |
| Port + inland delivery plan | Nigeria costs escalate when handoffs are late | Inland delivery not booked, storage costs grow |
Decide the operating model first
Lock these before documents:
- Incoterms and named place (Incoterms 2020: https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/)
- Payment method (open account vs documentary collection vs LC)
- Importer-of-record and clearance model (who files, where the cargo is delivered)
If these change late, your document set will change late.
Documentation checklist (UAE export -> Nigeria import)
- Commercial invoice (line-level descriptions, HS, qty/unit, values, currency, Incoterms)
- Packing list (packages, net/gross weights, marks)
- Transport document: bill of lading/airway bill (Bill of Lading)
- Product-specific permits/certificates (depends on commodity)
Single source of truth rule
Treat the shipment record as the master.
If a line item changes (HS, description, qty/unit, value), regenerate documents and re-sync the broker.
Broker handoff packet (what to send every time)
If you want fewer message cycles, send one complete packet per shipment:
| Block | What to include |
|---|---|
| Parties | exporter, importer/consignee, notify party |
| Terms | Incoterms + named place, payment method |
| Line items | SKU, HS, standard description, qty/unit, unit value, currency |
| Packaging | cartons/pallets, marks, net/gross weights |
| Docs | invoice, packing list, BL/AWB, certificates (if any) |
The operator goal is simple: no rewriting by the broker.
Incoterms: pick a default pattern your team can execute
Incoterms determine who controls freight/insurance and where responsibility transfers.
Use Incoterms 2020 as the baseline reference (source: https://iccwbo.org/business-solutions/incoterms-rules/incoterms-2020/).
Operational rule: choose a default (FOB/CFR/CIF pattern) and document exceptions.
Changing Incoterms late usually means changing invoices late.
HS classification: stop drift
HS is the international product nomenclature used as the basis for customs tariffs and trade statistics (WCO overview: https://wcoomd.org/en/topics/nomenclature/overview/what-is-the-harmonized-system.aspx).
Practical controls:
- keep a SKU master mapping
- standardize description text per SKU
- require justification for HS changes and roll out consistently
Nigeria-side customs touchpoints (high level)
Nigeria Customs Service (NCS) is the official reference point for customs information and services (source: https://customs.gov.ng/).
NCS describes the dynamics of technology and the importance of information dissemination and lists e-services including the Nigeria Integrated Customs Information System (NICIS) as part of its services ecosystem (source: https://customs.gov.ng/).
Operator takeaway: you do not need to file yourself to benefit.
You need to hand your broker declaration-ready data and a complete document set.
What to do when requirements vary by commodity
For regulated goods, do not treat compliance as a last-minute broker request.
Build a lightweight internal permit map at SKU family level:
- HS and standard description
- whether the category is commonly regulated
- what documents are typically requested by the importer/broker
- who owns the requirement internally
- lead time
This prevents the arrival-day surprise: "we need one more certificate".
Port planning: treat the destination as a system
Nigerian Ports Authority (NPA) is the Federal Government agency that governs and operates ports and lists major port complexes (source: https://nigerianports.gov.ng/ and https://nigerianports.gov.ng/ports/).
Operator takeaway: plan the last mile early.
Before dispatch, confirm:
- port/terminal and consignee receiving location
- who is responsible for port charges and inland delivery
- document cut-off dates (earlier than vessel events)
Most margin damage comes from delays after discharge.
Port selection and terminal reality
NPA lists major port complexes across Lagos and other regions (source: https://nigerianports.gov.ng/ports/).
Operator rule: confirm the destination port/terminal and delivery location early, because the last-mile plan drives your true cycle time.
If you decide delivery details after arrival, you will pay with storage and rework.
Consolidation and carton mapping (re-export lanes)
If your UAE shipment consolidates multiple suppliers or POs, add two controls:
- one carton labeling standard
- one packing list format that maps cartons to invoice line items
This prevents the most common receiving dispute: "cartons do not match the invoice".
Pre-arrival controls: stop demurrage before it starts
Nigeria-side costs escalate when the destination team starts planning after the vessel arrives.
Operational controls that consistently reduce storage/demurrage risk:
- Set a hard document cut-off earlier than carrier milestones.
- Pre-assign a receiver (a named person/team) who confirms delivery location, contact details, and receiving hours.
- Pre-book inland delivery (or at least a slot) based on the expected discharge window.
- Run a reconciliation gate: invoice totals, packing list totals, and booking data match before you release the final document packet.
Treat this as a checklist gate. If you skip it, the shipment becomes a “live problem” at the port.
Demurrage/detention prevention checklist (operator view)
| Check | Owner | When | Why it matters |
|---|---|---|---|
| Final consignee and delivery address confirmed | Sales/ops | Before BL/AWB issuance | Prevents late amendment loops |
| Broker packet sent as one package | Ops | Pre-arrival | Reduces missing-field back-and-forth |
| Inland delivery plan confirmed | Importer/receiver | Pre-arrival | Avoids post-discharge waiting time |
| Receiving window booked | Receiver | Pre-arrival | Prevents “cargo ready but no one can take it” |
| Exception list checked (new SKU/HS, regulated goods, new Incoterms) | Ops | Pre-dispatch | Triggers extra validation instead of surprises |
Receiving SOP: prevent disputes and chargebacks
On mixed-SKU containers, receiving disputes are usually data problems, not “lost cargo”.
Minimal receiving SOP that prevents most disputes:
- Receive against carton marks (not only SKU names).
- Count cartons first, then reconcile to line items.
- Photograph any damaged cartons before breaking them down.
- Capture exceptions in a single log:
carton mark / issue / quantity / photo link.
If your packing list maps cartons to invoice lines, this becomes fast. If it doesn’t, receiving becomes a manual investigation.
Documentary payments: when documents become bank-controlled
If the deal uses documentary collection or a letter of credit, documents are checked strictly.
Operator controls:
- 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
Late changes are what create last-minute corrected documents.
First shipment playbook (make shipment 1 a pilot)
Before shipment 1:
- Build a SKU master for the first 20-50 SKUs.
- Standardize invoice and packing list templates.
- Confirm the destination port/terminal and inland delivery model.
During shipment 1:
- Keep one versioned shipment record.
- Reconcile invoice totals, packing list totals, and booking data.
- Capture real costs as they occur.
After shipment 1:
- Record what changed late and why.
- Update templates and SKU master.
- Define exception triggers for next time.
If you do this, shipments 2-20 become dramatically more predictable.
Cost allocation for mixed-SKU containers
If you ship mixed SKUs, pick a consistent allocation method (weight, volume, or value).
Consistency is what makes margins comparable across shipments.
Common delay patterns (and fixes)
-
Generic descriptions Fix: standard description library aligned 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/importer changes Fix: freeze parties before issuing the transport document.
-
Unplanned inland delivery Fix: book inland delivery and receiving windows before cargo arrives.
Landed cost control: treat it as a shipment ledger
Track per shipment:
- supplier cost
- freight and surcharges
- origin charges
- destination charges
- clearance fees
- duties/taxes
- inland delivery
- bank/FX charges
- storage/demurrage/detention if they occur
Close out landed cost at shipment close.
Method reference: /resources/how-to-calculate-landed-cost.
How Tijara helps
Tijara helps teams run repeat lanes:
- structured shipment records
- SKU/HS masters for consistent documents
- shipment-level landed cost tracking
If UAE-to-Nigeria is a repeat lane, consistency is the lever.