Who this guide is for
This is an execution guide for teams shipping from the UAE to Tanzania.
If you run East Africa supply lanes, your biggest leverage is repeatability: stable master data, clean documents, and early destination planning.
At-a-glance checklist (before you book)
| What to confirm | Why it matters | What usually breaks |
|---|---|---|
| Incoterms and named place | Defines who owns freight/insurance/clearance and which costs belong in landed cost | Quote and invoice disagree |
| SKU master: HS + standard description | Duty/compliance expectations and filing quality depend on it | Generic descriptions, HS drift |
| Packaging/weights discipline | Prevents reconciliation and inspection delays | Totals don't reconcile |
| Tanzania broker/importer readiness | Avoids arrival-day data collection | Missing fields, missing attachments |
| Inland delivery and receiving plan | Delays after discharge destroy cycle time | Delivery booked late, storage costs grow |
Decide the operating model first
Before you generate any PDFs, lock these three decisions:
- Incoterms and the 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 (UAE export -> Tanzania import)
- Commercial invoice
- Packing list
- Transport document (BL/AWB) (Bill of Lading)
- Product-specific permits/certificates when required
Single source of truth rule
Treat the shipment record as the master.
If line items change, regenerate documents and re-sync the broker.
Broker handoff packet (reduce back-and-forth)
Treat the broker handoff as a single deliverable. 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.
HS classification: control 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).
For repeat SKUs:
- build a SKU master
- standardize description text
- keep an owner + change log
Tanzania-side touchpoints: TRA and TANESW
TRA is the official reference point and provides customs and excise information including import procedures (source: https://www.tra.go.tz/ and https://www.tra.go.tz/page/import-procedures).
TRA lists TANESW (Tanzania Electronic Single Window) as an e-service (source: https://tanesw.tra.go.tz/ptle/).
Operator takeaway: make your broker handoff a single packet.
- parties and terms
- line items (HS, standard descriptions, qty/unit, values)
- packaging (cartons/weights)
- attachments (invoice, packing list, BL/AWB, certificates)
TANESW readiness checklist (operator view)
Even if your broker/importer is driving TANESW steps, operators should validate readiness before dispatch:
| Check | Why it matters |
|---|---|
| Importer-of-record is final | avoids consignee changes late |
| HS + standard descriptions are declaration-ready | reduces classification and rewrite loops |
| Invoice/packing totals reconcile | prevents “fix the documents” cycles |
| Certificates (if any) are identified early | avoids arrival-day surprises |
| Document cut-off is set | keeps bank/LC and broker timelines realistic |
Port planning: Tanzania Ports Authority
Tanzania Ports Authority (TPA) publishes official information about ports and port processes (source: https://www.ports.go.tz/index.php/en/).
Operator takeaway: plan beyond arrival.
Before dispatch, confirm:
- discharge port and consignee receiving location
- who pays which charges
- inland delivery booking and receiving windows
Inland delivery: plan beyond the port
Treat the destination as a system: discharge, clearance, and final delivery.
Operator controls that keep the lane predictable:
- Confirm the final delivery point (warehouse/site) and any appointment rules.
- Decide who owns last-mile booking and when it must be locked.
- Put receiving constraints into the broker packet (hours, contacts, delivery instructions).
If you wait until discharge to decide receiving, storage costs and idle time grow quickly.
Consolidation and carton mapping (re-export lanes)
If you consolidate multiple suppliers/POs in the UAE, add two controls:
- One carton labeling standard (marks are your receiving language).
- One packing list format that maps cartons to invoice lines.
This reduces disputes and makes inspections and receiving much faster.
Documentary payments (LC / documentary collection)
When documents are bank-controlled, “small” wording changes become expensive.
Controls that prevent the most common failure mode (corrected documents after dispatch):
- 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
Pre-arrival controls (reduce storage risk)
The easiest cost to avoid is the cost of waiting.
Before the vessel/flight arrives, confirm:
- delivery address and a named receiver
- inland delivery booking plan (and internal cut-off)
- a reconciliation gate: invoice totals, packing list totals, and booking data match
If you do this consistently, delays become exceptions instead of the default.
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 the SKU master.
- Define exception triggers (new SKU/HS, new route, new Incoterms).
Exception triggers (when to slow down)
Slow the lane down on purpose when any of these happen:
- new SKU or HS change
- new consignee/importer-of-record
- new route (new discharge port or new inland delivery pattern)
- switch to LC/documentary collection
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.
-
Consolidation chaos Fix: carton-level mapping and consistent marks.
-
Late consignee changes Fix: freeze parties before issuing BL/AWB.
-
Unplanned inland delivery Fix: book inland delivery and receiving windows before arrival.
Landed cost control
Track per shipment:
- supplier cost
- freight and surcharges
- origin charges
- destination charges
- clearance fees
- duties/taxes
- inland delivery
- bank/FX
- storage if it occurs
Close the ledger at shipment closeout so margins stay real.
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
If UAE-to-Tanzania is a repeat lane, repeatability is the lever.