Series
8,000 km in 45 Days: BESS Logistics from China to CEE
- Ep. 1 · Origins - Where the journey begins
- Current episode: Ep. 2 · At Sea - The maritime leg
- Ep. 3 · On Borders - Customs clearance at CEE ports
- Ep. 4 · Oversized - 43 tons meets CEE roads
- Ep. 5 · After Delivery - From quay to commissioning
- Ep. 6 · Insured? Marine cargo insurance
Series A, "8,000 km in 45 Days" | Episode 2
The containers have cleared the factory gate. The Shipper's Declaration is signed. Now begins the longest and least controllable segment of the journey: 28–65 days at sea, depending on routing. This episode covers what happens between the Chinese port of loading and the CEE gateway port – and what procurement managers must get right before the vessel sails.
The Situation
The BESS containers – 20-foot High Cube units weighing approximately 43 tons each – have completed Factory Acceptance Testing (FAT), been loaded at the manufacturer's facility, and trucked to the Chinese port of origin. The Bill of Lading has been issued. The cargo is now in the hands of the maritime carrier.
This is the point where the EPC project manager's direct control ends and the carrier's responsibility begins. The containers will transit either via the Suez Canal (30–35 days to Black Sea ports, available but less frequent) or via the Cape of Good Hope with transshipment at Piraeus or Istanbul (55–70 days total). The routing decision was made at booking – now the shipment executes against that plan.
What You're Actually Dealing With
Classification and Stowage: UN3536 Under IMDG Code Amendment 42-24
BESS containers with lithium-ion batteries installed are classified as UN3536: Lithium Batteries Installed in Cargo Transport Unit under the IMDG Code Amendment 42-24, which became mandatory on 1 January 2026. This classification applies when the batteries are permanently secured within the container structure and designed to provide external power – the defining characteristic of utility-scale BESS.
The critical regulatory change in Amendment 42-24: Stowage Category D now applies to UN3536 cargo. This means:
- On-deck stowage only – BESS containers cannot be stowed below deck
- SW1 applies: Protected from sources of heat
- SW2 applies: Clear of living quarters
- Prohibited on passenger vessels carrying more than 25 passengers (or more than 1 passenger per 3m of overall length)
This is a change from the previous Stowage Category A, which permitted either on-deck or under-deck stowage. The shift reflects lessons learned from thermal runaway incidents and the difficulty of managing lithium battery fires in enclosed hold spaces.
State of Charge: The 30% Rule
Under IMDG Code provisions, BESS units must be shipped at a State of Charge (SoC) not exceeding 30% of rated capacity. This requirement exists because lower SoC reduces the potential energy available for thermal runaway and limits the severity of any fire event.
The OEM is responsible for ensuring SoC compliance before the container leaves the factory. The SoC declaration appears in the Shipper's Declaration for Dangerous Goods. If SoC exceeds 30%, the shipment requires special approval from the State of Origin and the State of the Operator – a process that adds weeks and is rarely granted for commercial BESS shipments.
Carrier Acceptance: Utilization-Based, Not Equipment-Limited
A common misconception: that only certain vessels can carry heavy BESS containers. In reality, container ships are fully capable of handling 45–50 ton containers. The constraint is utilization balancing, not equipment capability.
Carriers restrict the volume of BESS cargo accepted per vessel based on:
- Total weight distribution across the ship
- Ratio of heavy containers to standard containers
- DG cargo limits per voyage (often expressed as a percentage of total TEU capacity)
- On-deck stowage availability (now mandatory for UN3536)
This means booking windows for BESS cargo are tighter than for standard freight. During peak shipping seasons – particularly Q3–Q4 when RESTORE-funded projects were racing to meet deadlines – booking windows of 3–4 weeks were common. In 2026, with RESTORE 2 projects in execution, similar constraints apply.
Routing Realities: Suez vs. Cape of Good Hope
As of April 2026, the routing picture for Asia–Europe BESS shipments is as follows:
Direct services via Suez Canal:
- Transit time: ~30–35 days to Constanța or Burgas
- Frequency: 1–2 sailings per month (not weekly)
- Carriers: Niche operators still transit Suez, offering faster solutions
- Trade-off: Less frequent, less predictable scheduling
COGH routing via transshipment:
- Transit time: ~55–70 days to Constanța or Burgas
- Frequency: Weekly mainline services with feeder connections
- Transshipment hubs: Piraeus (Greece) and Istanbul (Turkey) are dominant; Tekirdag (Turkey) is an alternative used by MSC
- Trade-off: Longer transit, but more regular sailings and security-driven routing
The choice between these options is made at booking based on the carrier's declared route. Planning should be based on the carrier's announced service, not on assumptions about which route will be used.
Transshipment at Piraeus or Turkish Hubs
For COGH-routed shipments, transshipment is the norm. The mainline vessel discharges at Piraeus, Istanbul, or Tekirdag, and containers transfer to feeder vessels serving Black Sea ports.
Key operational realities:
- Feeder frequency: Weekly departures to Constanța, Burgas, and Varna
- Missed connection impact: A missed feeder adds 3–7 days to the timeline
- Peak season delays: During Q3–Q4, Piraeus can hold containers for up to 2–3 weeks before feeder transfer
- Carrier responsibility: The through carrier manages all transshipment logistics, including DG compliance – the freight forwarder does not book feeder connections separately
Storage fees at transshipment ports are not charged to the client if the delay is not the client's fault. However, if documentation issues prevent onward movement, the clock starts.
The Timeline
The sea leg timeline depends entirely on routing:
Critical clarification: These are port-to-port transit times. They do not include customs clearance (1–5 working days) or inland delivery to the construction site. A "65-day transit" means 65 days to the quay in Burgas – not to the BESS park.
Where procurement managers consistently underestimate:
- Feeder connection variability: The mainline vessel may arrive on schedule, but the feeder departs once per week. A 2-day delay at the hub can become a 9-day delay at the destination.
- Peak season congestion: Q3–Q4 transshipment delays at Piraeus are structural, not exceptional. Build them into the baseline plan.
- Documentation-driven holds: If the Bill of Lading shows a weight discrepancy with the Packing List, customs may hold processing after discharge. The terminal always unloads – but the container sits until documentation is reconciled.
The Documents
The following documents govern the sea leg. All are transmitted electronically or via courier to the consignee and customs broker – documents do not physically travel with the cargo.
Prepared by the OEM/Shipper:
Shipper's Declaration for Dangerous Goods: Certifies DG classification, UN number, SoC. Common error: Wrong UN number (UN3480 instead of UN3536).
UN38.3 Test Summary: Proves battery passed transport safety tests. Common error: Test summary for different battery model than shipped.
Material Safety Data Sheet (MSDS): Chemical composition and hazard information. Common error: Outdated version (must reference current IMDG edition).
Packing List: Itemizes contents and weights. Common error: Weight based on design specs, not actual VGM.
Commercial Invoice: Value declaration for customs. Common error: Does not necessarily include cargo weight.
Certificate of Origin: Proves country of manufacture. Common error: Missing or incorrect for preferential duty treatment.
Prepared by the Carrier (or Forwarder as Contractual Carrier):
Bill of Lading (B/L): Contract of carriage, proof of shipment. Common error: Weight discrepancy with Packing List.
Verified Gross Mass (VGM) Declaration: Actual weighed container mass. Common error: Packing List not updated to match VGM.
The Weight Documentation Problem
Weight discrepancies between the Packing List and Bill of Lading are the single most common documentation failure in BESS shipping. The root cause:
- The manufacturer provides Packing List weight based on standard/design specifications
- The VGM declaration – based on actual weighing of the finished product after final securing – reflects the true weight
- The carrier uses VGM data for the B/L
- If the Packing List is not updated after production changes (e.g., additional securing material), a discrepancy exists
The fix: Ensure the Packing List reflects actual weighed cargo aligned with VGM data before B/L issuance. This requires coordination between the manufacturer, the freight forwarder, and the carrier during the pre-shipment window.
Placarding Requirements
UN3536 containers require Class 9 placards and UN number markings on four sides of the container (left, right, front, and back). This is a SOLAS/IMDG requirement that terminals and carriers verify before loading.
What Goes Wrong
The following failure modes are drawn from Unimasters' operational experience across 40+ BESS deployments. All are caused by client-side errors – operational processes (terminal handling, vessel acceptance, feeder connections, DG handling at transshipment ports) work as designed.
Failure Mode 1: State of Charge Above 30%
What happened: A BESS shipment arrived at the Chinese port with SoC at 45%. The carrier rejected the booking at the documentation review stage.
Why: The OEM had not discharged the batteries to transport-compliant levels after FAT. The Shipper's Declaration correctly stated the SoC – which triggered the rejection.
Consequence: The containers returned to the factory for discharge. The project lost 12 days and incurred additional trucking and handling costs.
Prevention: Confirm SoC compliance in writing from the OEM before containers leave the factory. Include SoC verification as a FAT checklist item.
Failure Mode 2: Weight Discrepancy Between Packing List and B/L
What happened: The Packing List stated 42,800 kg per container. The VGM declaration showed 43,450 kg. The B/L reflected the VGM figure. At the destination port, customs flagged the discrepancy and held processing.
Why: The manufacturer had added additional securing material after the Packing List was issued but did not update the document. The VGM – based on actual weighing – captured the true weight.
Consequence: Customs held processing for 4 working days while documentation was reconciled. Storage fees accumulated daily.
Prevention: Require the manufacturer to update the Packing List to match VGM data before B/L issuance. The draft B/L is for data verification – use it.
Failure Mode 3: Incorrect UN Classification
What happened: A shipment was declared as UN3481 (Lithium-ion batteries contained in equipment) instead of UN3536 (Lithium batteries installed in cargo transport unit).
Why: The shipper used a classification template from a previous project involving smaller battery systems. BESS containers designed to provide external power require UN3536.
Consequence: The carrier rejected the booking. Re-documentation and re-booking added 8 days to the timeline.
Prevention: Verify UN classification with the DGSA (Dangerous Goods Safety Adviser) before booking. UN3536 applies when batteries are permanently secured within the container and designed to provide external power.
Failure Mode 4: CE Marking Non-Compliance Discovered Post-Shipment
What happened: BESS containers arrived at Burgas. During customs processing, the CE Declaration of Conformity referenced a different battery model than the units shipped.
Why: The OEM had updated the battery cells between the time the CE documentation was prepared and the time of production. The Declaration of Conformity was not updated.
Consequence: Customs held the shipment pending resolution. The project team arranged for a third-party conformity assessment in Bulgaria – a process that took 3 weeks.
Prevention: Verify CE documentation matches the exact product configuration being shipped. This is a FAT checklist item, not a post-shipment discovery.
Failure Mode 5: Missed Feeder Connection at Piraeus
What happened: The mainline vessel arrived at Piraeus on schedule. The weekly feeder to Burgas had departed 2 days earlier. The next feeder was 5 days away.
Why: The mainline vessel had experienced a 3-day delay at an intermediate port. The feeder schedule is fixed – it does not wait for delayed mainline arrivals.
Consequence: The shipment arrived 5 days later than planned. This was within the project buffer, but it consumed contingency that was needed later.
Prevention: Build feeder connection variability into the baseline plan. Assume a missed connection is possible and plan for the next available sailing.
What This Means for Your Project
- Confirm SoC compliance before containers leave the factory. Include SoC verification as a FAT checklist item. If SoC exceeds 30%, the shipment cannot proceed without special approval.
- Reconcile Packing List weight with VGM data before B/L issuance. The draft B/L is the verification checkpoint. Use it.
- Verify UN classification with the DGSA. UN3536 applies to BESS containers designed to provide external power. Incorrect classification triggers booking rejection.
- Build transshipment variability into the baseline plan. For COGH-routed shipments via Piraeus, assume 2–3 weeks of potential delay during Q3–Q4. For other periods, assume 1 week.
- Clarify transit time definitions with all stakeholders. "65 days" means port-to-port. Add 1–5 working days for customs clearance and additional time for inland delivery.
Key Takeaways
- UN3536 BESS containers are now Stowage Category D (on-deck only) under IMDG Code Amendment 42-24, effective 1 January 2026. This is a change from the previous Category A.
- State of Charge must not exceed 30% for sea transport. Verify compliance before containers leave the factory.
- Transit times range from 28–65 days depending on routing. Direct Suez services offer 30–35 days but are less frequent (1–2/month). COGH routing via Piraeus/Istanbul takes 55–70 days with weekly sailings.
- Weight discrepancies between Packing List and B/L are the most common documentation failure. The root cause is Packing List data based on design specs rather than actual VGM. Fix this before B/L issuance.
- Transshipment delays at Piraeus can reach 2–3 weeks during peak season. Build this into the baseline plan, not the contingency buffer.
Frequently Asked Questions
Q: What UN number applies to utility-scale BESS containers?
A: UN3536 (Lithium Batteries Installed in Cargo Transport Unit) applies when batteries are permanently secured within the container and designed to provide external power. This is distinct from UN3480 (standalone batteries) or UN3481 (batteries contained in equipment).
Q: What is the maximum State of Charge for BESS sea transport?
A: The State of Charge must not exceed 30% of rated capacity under IMDG Code provisions. Shipments exceeding 30% SoC require special approval from the State of Origin and the State of the Operator – a process that adds weeks and is rarely granted for commercial BESS.
Q: How long does sea transit from China to CEE ports take in 2026?
A: Transit times range from 28–65 days depending on routing. Direct services via Suez take approximately 30–35 days to Constanța or Burgas but are available only 1–2 times per month. COGH routing via Piraeus or Istanbul takes 55–70 days with weekly mainline services and weekly feeder connections.
Q: What stowage category applies to UN3536 BESS containers?
A: Stowage Category D applies under IMDG Code Amendment 42-24, effective 1 January 2026. This means on-deck stowage only, protected from sources of heat (SW1), and clear of living quarters (SW2). BESS containers are prohibited on passenger vessels carrying more than 25 passengers.
Q: What causes weight discrepancies between the Packing List and Bill of Lading?
A: The manufacturer typically provides Packing List weight based on standard/design specifications. The VGM (Verified Gross Mass) declaration – based on actual weighing after final securing – reflects the true weight and is used by the carrier for the B/L. Discrepancies arise when the Packing List is not updated after production changes. The fix: align Packing List with VGM data before B/L issuance.
Q: What happens if a BESS container misses its feeder connection at Piraeus?
A: Feeder connections to Black Sea ports (Constanța, Burgas, Varna) typically depart once per week. A missed feeder connection adds 3–7 days to the timeline. During peak season (Q3–Q4), Piraeus can hold containers for up to 2–3 weeks before feeder transfer due to congestion.
Q: Who is responsible for booking feeder connections from transshipment hubs?
A: The through carrier manages all transshipment logistics, including feeder connections. The freight forwarder does not book feeder connections separately from mainline carriage. Feeder arrangements are part of the overall booking with the carrier.