OOCL
Tracking OOCL Cargo Into Hamad Port, Qatar
OOCL's Far East-Middle East 1 (ME1) string names a direct Hamad Port call in its own published rotation, a merged service dating to mid-2018 under the Ocean Alliance. Here is what that actually means for a Qatar-bound shipment, and what remains unconfirmed.
OOCL Into Qatar
OOCL’s Middle East coverage runs through its ME1 (Far East-Middle East 1) service, and Hamad Port is a named call on that rotation. Trade press coverage of OOCL’s Ocean Alliance network reshuffle gives the ME1 port sequence as Tianjin, Pusan, Qingdao, Shanghai, Shekou, Singapore, Sohar, Jebel Ali, Hamad, Dammam and Jubail, returning through Singapore to Tianjin. The service in its current form was created by merging two earlier products, also both labelled ME1 and ME2, effective around the end of July 2018 — a fairly typical piece of Ocean Alliance network consolidation rather than a Qatar-specific launch.
It is worth being clear about what ME1 is not: it is not the same service that reaches Pakistan. OOCL’s Pakistan connections run on dedicated China Pakistan Express (CPX) strings — documented separately on this site’s Pakistan-tier OOCL page — which call Karachi and Port Qasim on a route via Mundra rather than the Gulf ports ME1 covers. A container moving between Qatar and Pakistan on OOCL would not stay on a single vessel between the two; it would connect through a hub, most likely one of the Gulf or Southeast Asian ports both services touch.
We could not confirm which specific terminal OOCL’s ME1 calls at Hamad Port. OOCL’s own network materials list the port call without naming a terminal, and unlike Karachi, where this site has been able to confirm specific terminal assignments for OOCL’s CPX strings, Hamad Port’s terminal assignment by carrier is not documented to the same degree in any source we could verify. We also found no confirmation of a dedicated OOCL office or named local agent in Qatar; OOCL’s relationship with its majority owner COSCO Shipping and their shared Ocean Alliance membership does not, on its own, confirm anything about OOCL’s specific local presence in Qatar.
Clearing an OOCL Shipment in Qatar
An OOCL container discharging at Hamad Port clears through Al-Nadeeb, the customs single-window system operated by Qatar’s General Authority of Customs: the importer or their clearing agent files the declaration against the invoice, packing list and bill of lading, duties and taxes are assessed, and the container is released once payment and any required inspection are complete. Maalbardaar files this declaration and coordinates with the terminal directly.
Since this page could not confirm which Hamad Port terminal ME1 discharges at, and since OOCL’s Qatar and Pakistan connections run on entirely separate services rather than one through-string, confirm both the service name and the terminal on your own arrival notice before assuming continuity with a shipment you have previously tracked on a different OOCL routing.
OOCL lanes into Qatar
Clearing customs on a OOCL shipment
Customs clearance
Customs declaration filing through Al-Nadeeb, Qatar's customs single-window system run by the General Authority of Customs, plus HS code classification and duty calculation for cargo arriving on OOCL.
Freight forwarding
Booking coordination and inland delivery arrangements once OOCL cargo is discharged at a Hamad Port terminal.
OOCL tracking to Qatar — questions
Does OOCL call Hamad Port directly?
expand_more
Yes, on its ME1 (Far East-Middle East 1) service. Trade press reporting on OOCL's Ocean Alliance service reshuffle gives the ME1 rotation as Tianjin, Pusan, Qingdao, Shanghai, Shekou, Singapore, Sohar, Jebel Ali, Hamad, Dammam, Jubail, back through Singapore to Tianjin. ME1 was formed by merging two earlier products, ME1 and ME2, effective around the end of July 2018.
Which terminal does OOCL use at Hamad Port?
expand_more
We could not confirm this. OOCL's own network materials name Hamad Port as a call on the ME1 rotation but do not specify a terminal, and no independent source gave a reliable terminal assignment to cite. Confirm the discharge terminal on your own arrival notice.
Is ME1 the same service that calls Karachi and Port Qasim in Pakistan?
expand_more
No, not according to the rotation this site could confirm. ME1's published stops are Tianjin, Pusan, Qingdao, Shanghai, Shekou, Singapore, Sohar, Jebel Ali, Hamad, Dammam and Jubail — Pakistan is not on that list. OOCL's Pakistan connections run on separate, dedicated China Pakistan Express (CPX) strings, documented on this site's Pakistan-tier OOCL page, which are different services from ME1.
Does OOCL have its own office or agent in Qatar?
expand_more
We could not confirm a dedicated OOCL-branded office or a named local agent for Qatar to the sourcing bar this site requires. OOCL is majority-owned by COSCO Shipping and the two carriers sit together in the Ocean Alliance, but they keep separate brands, booking systems and (per the global OOCL page on this site) separate container prefixes; whether that separation extends to a distinct local Qatar presence for OOCL specifically could not be verified either way.
How old is the ME1 service to Hamad Port?
expand_more
The merged ME1 product (combining former ME1 and ME2 strings) dates to around the end of July 2018, per Ocean Alliance service-reshuffle coverage from that period. That is the service's formation date, not necessarily today's exact rotation — carriers commonly adjust port sequences on a standing service over time without renaming it.
Clearing a OOCL shipment into Qatar?
Track it and clear it through one licensed team.
Not shipping with OOCL?
Qatar-specific operating details for every carrier we cover, or the full Qatar hub if you want the overview.
Ocean carriers
Air cargo
Maalbardaar is an independent logistics technology platform and is not affiliated with, endorsed by, or sponsored by Orient Overseas Container Line Limited. "OOCL" and all related marks are trademarks of their respective owners and are used here for identification purposes only. For official information, visit the carrier's own website . Carrier data sources: Container prefixes confirmed individually against the BIC ISO 6346 owner-code register (bic-code.org/bic-codes/oolu, /oocu). HQ and founding year from OOCL corporate material. SCAC cross-corroborated across two published ocean-carrier SCAC lists; NMFTA's register is paywalled, so it is not source-verified. Pakistan data sources: The ME1 rotation (Tianjin-Pusan-Qingdao-Shanghai-Shekou-Singapore-Sohar- Jebel Ali-Hamad-Dammam-Jubail-Singapore-Tianjin) and its formation as a merger of former ME1/ME2 products effective around end of July 2018 are from Container News' report on OOCL's Middle East services (container-news.com/oocl-middle-east-services/). This is the same outlet and general reporting pattern used for the Pakistan-tier OOCL page's CPX3 rotation, and it was cross-checked against the fact that ME1's port list does not include Karachi or Port Qasim, confirming ME1 and the Pakistan CPX strings are distinct services. Could NOT verify: any terminal assignment for OOCL's Hamad Port call; a current (post-2018) re-confirmation that ME1's rotation is unchanged, since carriers routinely adjust standing service rotations without a fresh press announcement; a dedicated OOCL office or named local agent in Qatar, separate from COSCO's presence or any shared Ocean Alliance arrangement; any Qatar-specific transit time.