Bangladesh: Chattogram Port Strike (NCT Lease Protest) — Operational Impact & Actions
Incident type: Labour action / port service disruption
Primary location: Chattogram (Chittagong) Port, Bangladesh
1) Who is most exposed
Treat this as high severity if Bangladesh is in your lane mix—especially for time-sensitive export programs.
Most exposed
- Bangladesh exporters/importers, with the highest near-term sensitivity in ready-made garments (RMG) and textiles.
- Global brands and retailers sourcing from Bangladesh (PO date risk compounds quickly as stoppages extend).
- Forwarders/NVOCCs and carriers managing Bangladesh allocations, feeder links, and transshipment connections (higher rollover and schedule-failure probability).
- Regional hub-dependent networks (secondary exposure) if backlog-clearing causes bunching and missed connections.
2) Status (time-stamped snapshot)
What’s happening (as publicly reported)
- Labour action linked to opposition over the planned leasing of the New Mooring Container Terminal (NCT) has disrupted port operations.
- Some updates describe the action as time-bound stoppages (e.g., limited-hour abstentions), while later reporting indicates escalation toward open-ended/indefinite stoppage.
What to assume operationally until proven otherwise
- Terminal throughput is materially reduced and may be intermittently halted depending on terminal and shift.
- Gate flows and inland interface are disrupted (truck entry/exit and container movement).
- Vessel operations may be affected, including pilotage/vessel movement interruptions during escalation phases.
What must be verified shipment-by-shipment
- Whether your specific terminal/berth is fully stopped vs. partially operating.
- Whether your feeder/mainline call is omitted, delayed, or holding at anchorage.
- Whether gates are closed, limited-hour, or selectively processing.
3) Immediate operational impacts (what breaks first)
Exports (Bangladesh → global markets)
- Cut-offs missed: rising probability of rollovers, rebooking, and space compression once services resume.
- Factory-to-port bottlenecks: cargo staging at factories/ICDs increases, with limited evacuation capacity during disruption.
- Order risk: apparel programs face higher exposure to delivery penalties, discounts, and cancellation pressure as delays extend.
Imports (global → Bangladesh)
- Delivery slippage: inbound containers may face extended dwell time and appointment failures.
- Production risk: delays in raw materials/inputs can trigger a second-wave impact even after port recovery.
Feeder and transshipment
- Missed connections: feeder bunching increases the likelihood of missed transshipment windows at regional hubs.
- Schedule reliability deterioration: expect more ETD/ETA changes, short-notice plan updates, and document amendments.
Cost exposure
- Detention/demurrage (D&D): risk tends to rise when containers become immobilised and post-restart trucking capacity tightens.
- Expedite spend: mode shifts (partial air / sea-air) may increase for launch-critical orders.
4) What to do this week (5-step action playbook)
Step 1 — Map exposure (today)
Pull all open shipments, bookings, and POs with Bangladesh involvement:
- Bangladesh as origin
- Bangladesh as destination
- Bangladesh on feeder legs / transshipment chains
Include cargo not yet moved (still at factory/ICD) and already gated containers.
Step 2 — Segment by physical position
Tag each file into one bucket:
1) At port / terminal / port-adjacent
2) At ICD / factory
3) Inland en route to port
4) Not yet produced / not yet packed
Step 3 — Decide per shipment (hold vs. protect vs. expedite)
Use a simple rule set:
- Hold: non-urgent cargo not yet gated → avoid pushing containers into a jammed interface.
- Protect: time-sensitive cargo already committed → secure the earliest feasible rebooking options; keep documents and cargo readiness tight.
- Expedite (selective): launch-critical SKUs → assess partial air or sea-air only where commercially justified.
Note: Diversion to alternate Bangladesh ports can be constrained and should be treated as case-by-case, not default.
Step 4 — Lock a customer communication rhythm
Send one update daily at a fixed time (same format every day):
- What we know (confirmed impacts and affected shipments)
- What we’re doing (hold/protect/expedite actions)
- What we need from the customer (priority ranking, flexibility, approvals)
- Next update time
Step 5 — Prepare for the restart surge
Plan for a backlog-clearing phase:
- Pre-align trucking capacity for the first 72 hours after gates reopen.
- Align early on free time / D&D posture with carriers and depots.
- Ask factories to pre-sequence the most time-critical orders for first-out movement.
5) What to monitor (recovery signals)
Strong signals
- Vessel movement/pilotage reliably resumes and the queue begins to clear.
- Yard crane activity and measurable lift volumes restart.
- Gate moves reopen with visible truck in/out flow.
- Carriers publish revised proformas with credible ETDs.
Weak signals
- “Talks ongoing” statements without physical restart.
- Partial staffing without yard/gate throughput.
6) Bottom line
- If you manage Bangladesh-linked cargo, treat this as a major incident: rollover risk and schedule failures compound the longer disruption persists.
- If you do not touch Bangladesh, this remains primarily a monitoring item, but apparel/retail networks should still check for indirect exposure through shared suppliers.
Further Reading
- Kuehne+Nagel Advisory — Port operations in Chattogram disrupted due to labour action (02 Feb 2026)
- The Daily Star — Ctg port operations halted as workers begin 24-hour strike over NCT leasing plan (03 Feb 2026)
- The Daily Star — Vessel movement at Chattogram port halted as workers escalate strike (03–04 Feb 2026 update)
- Dhaka Tribune — Chittagong Port paralyzed as workers begin indefinite strike (Feb 2026)
- bdnews24 — Work stoppage continues as port operations affected over NCT handover (02 Feb 2026)
- The Daily Star — Ctg port faces congestion risk as strike continues (02 Feb 2026)
Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe) or henry.jo@tradlinx.com (EMEA/Asia)
Leave a Reply