{"id":89,"date":"2026-06-23T02:49:47","date_gmt":"2026-06-23T02:49:47","guid":{"rendered":"https:\/\/huajiayilogistics.com\/china-un-locode-directory-transport-hubs\/"},"modified":"2026-06-23T03:02:50","modified_gmt":"2026-06-23T03:02:50","slug":"china-un-locode-directory-transport-hubs","status":"publish","type":"post","link":"https:\/\/huajiayilogistics.com\/da\/china-un-locode-directory-transport-hubs\/","title":{"rendered":"China UN\/LOCODE Directory: Full List of Transport Hubs"},"content":{"rendered":"<p>For international shipping, a small location code can determine whether a container booking, bill of lading, customs declaration, or inland delivery instruction is interpreted correctly. UN\/LOCODE, formally the United Nations Code for Trade and Transport Locations, is the global location coding system used to identify ports, airports, rail terminals, inland cities, and other transport points. In China, where cargo may move through coastal ports, bonded zones, airports, rail hubs, and inland distribution centers, using the correct code helps avoid confusion between similar city names and different transport terminals.<\/p>\n<p>This guide provides a practical overview of the <strong>UN\/LOCODE China list<\/strong> for importers, Amazon sellers, freight forwarders, customs teams, and logistics managers. It explains how China UN\/LOCODE entries are structured, how to read the codes, where the major hubs are located, and how these codes are used in freight quotes, container bookings, port of loading and port of discharge fields, customs documents, incoterms planning, and warehouse delivery instructions.<\/p>\n<p>Please note that the table below is a practical reference sample, not the complete official database. UN\/LOCODE entries can be updated, added, or modified, so shippers should always verify critical codes against the latest official UNECE directory or with their freight forwarder before issuing final shipping documents.<\/p>\n<h2>What is UN\/LOCODE and how China entries are structured<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"What is UN\/LOCODE and how China entries are structured for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-1-what-is-un-locode-and-how-china-entries-are-structured.png\"\/><\/figure>\n<p>UN\/LOCODE is maintained by the United Nations Economic Commission for Europe (UNECE) and is widely used across global trade and transport systems. It provides a standardized five-character code for locations involved in international commerce. These locations may include seaports, airports, inland container depots, rail terminals, border crossings, postal exchange offices, and major logistics cities.<\/p>\n<p>For China, the code format generally begins with the two-letter ISO country code <strong>CN<\/strong>, followed by a three-character location identifier. For example, <strong>CNSHA<\/strong> is commonly used for Shanghai, <strong>CNSZX<\/strong> for Shenzhen, and <strong>CNNGB<\/strong> for Ningbo. These codes are often displayed in shipping platforms, carrier schedules, customs systems, freight forwarding software, and transport documents.<\/p>\n<p>The <strong>UN\/LOCODE China list<\/strong> is important because many Chinese logistics locations have overlapping names, multiple terminals, or different English spellings. For example, a shipment described only as \u201cShanghai\u201d may refer to a seaport, airport gateway, bonded warehouse area, factory pickup city, or inland trucking destination. A recognized location code makes the transport instruction clearer and easier to process across carriers, customs brokers, overseas agents, and warehouse teams.<\/p>\n<p>In practice, UN\/LOCODE helps answer questions such as:<\/p>\n<ul>\n<li>Which city or port is the port of loading?<\/li>\n<li>Which location should appear on the bill of lading?<\/li>\n<li>Is the destination a seaport, inland city, airport, or rail hub?<\/li>\n<li>Does the freight quote include inland pickup or only port-to-port service?<\/li>\n<li>Which customs declaration location should be used for export or import clearance?<\/li>\n<\/ul>\n<p>For authoritative information, users can consult the <a href=\"https:\/\/unece.org\/trade\/cefact\/unlocode-code-list-country-and-territory\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">UNECE UN\/LOCODE country and territory code list<\/a>, the <a href=\"https:\/\/unece.org\/trade\/uncefact\/unlocode\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">UNECE UN\/LOCODE overview<\/a>, and related trade facilitation resources from <a href=\"https:\/\/www.wcoomd.org\/\" rel=\"nofollow noopener noreferrer\" target=\"_blank\">the World Customs Organization<\/a>.<\/p>\n<h2>How to read a China UN\/LOCODE code<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"How to read a China UN\/LOCODE code for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-2-how-to-read-a-china-un-locode-code.png\"\/><\/figure>\n<p>A China UN\/LOCODE normally contains five characters. The first two characters identify the country, and the last three identify the specific location. For example:<\/p>\n<ul>\n<li><strong>CN<\/strong> = China<\/li>\n<li><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/li>\n<li><strong>CNSHA<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/li>\n<\/ul>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits <strong>CNNGB<\/strong>. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits, <strong>CN<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits <strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits, <strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits, <strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits <strong>UN\/LOCODE China list<\/strong>, cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<h2>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"Major China transport hubs by region for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-3-major-china-transport-hubs-by-region.png\"\/><\/figure>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<p><strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong> cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<h2>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"Sample China UN\/LOCODE directory table for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-4-sample-china-un-locode-directory-table.png\"\/><\/figure>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<table>\n<thead>\n<tr>\n<th>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/th>\n<th>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/th>\n<th>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/th>\n<th>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Shanghai<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>CNSHA<\/td>\n<\/tr>\n<tr>\n<td>Shenzhen<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>CNSZX<\/td>\n<\/tr>\n<tr>\n<td>Ningbo<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>CNNGB<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>Guangzhou<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>CNGGZ<\/td>\n<\/tr>\n<tr>\n<td>Xiamen<\/td>\n<td>Fujian<\/td>\n<td>Seaport and regional export gateway<\/td>\n<td>CNXMN<\/td>\n<\/tr>\n<tr>\n<td>Tianjin Xingang<\/td>\n<td>Tianjin Municipality<\/td>\n<td>Major North China seaport for Beijing and Hebei cargo<\/td>\n<td>CNTXG<\/td>\n<\/tr>\n<tr>\n<td>Dalian<\/td>\n<td>Liaoning<\/td>\n<td>Northeast China seaport and logistics hub<\/td>\n<td>CNDLC<\/td>\n<\/tr>\n<tr>\n<td>Fuzhou<\/td>\n<td>Fujian<\/td>\n<td>Regional port and manufacturing export city<\/td>\n<td>CNFOC<\/td>\n<\/tr>\n<tr>\n<td>Hangzhou<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>Inland city, e-commerce and air cargo support hub<\/td>\n<td>CNHGH<\/td>\n<\/tr>\n<tr>\n<td>Beijing<\/td>\n<td>Beijing Municipality<\/td>\n<td>Capital city, air cargo and administrative logistics hub<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>Chengdu<\/td>\n<td>Sichuan<\/td>\n<td>West China inland, air, rail, and distribution hub<\/td>\n<td>CNCTU<\/td>\n<\/tr>\n<tr>\n<td>Chongqing<\/td>\n<td>Chongqing Municipality<\/td>\n<td>Yangtze River, rail, inland logistics, manufacturing hub<\/td>\n<td>CNCKG<\/td>\n<\/tr>\n<tr>\n<td>Wuhan<\/td>\n<td>Hubei<\/td>\n<td>Central China rail, river, road, and distribution hub<\/td>\n<td>CNWUH<\/td>\n<\/tr>\n<tr>\n<td>Nanjing<\/td>\n<td>Jiangsu<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>Jiangsu<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<tr>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<td>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits.<\/p>\n<h2>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"How shippers use UN\/LOCODE in booking, customs, and delivery planning for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-5-how-shippers-use-un-locode-in-booking-customs-and-deliv.png\"\/><\/figure>\n<p>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits <strong>cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https:\/\/developers.cloudflare.com\/workers\/wrangler\/configuration\/#limits<\/strong>, <strong>port of discharge<\/strong>, place of receipt, and place of delivery. For example, an exporter in Suzhou may truck goods to Shanghai, where the ocean shipment departs under the port of loading code CNSHA. If the final destination is Los Angeles, Hamburg, Felixstowe, Jebel Ali, or Sydney, the corresponding destination code may appear alongside the China origin code in the carrier booking.<\/p>\n<p>For Amazon sellers, the correct origin code helps freight forwarders prepare accurate routing and cost estimates. A freight quote from Shenzhen may differ significantly from a quote from Ningbo, Qingdao, or Tianjin Xingang because trucking distance, port charges, carrier options, sailing frequency, and customs arrangements vary by region. If a supplier says the goods are \u201cnear Shanghai,\u201d the forwarder may still need to confirm whether the cargo is in Shanghai, Suzhou, Hangzhou, Ningbo, or another nearby city.<\/p>\n<p>For customs teams, UN\/LOCODE supports consistent location identification in export documentation, import entries, and logistics records. Although customs systems may also require local customs district codes or port codes, UN\/LOCODE remains useful in commercial invoices, packing lists, bills of lading, sea waybills, arrival notices, and internal shipment records.<\/p>\n<p>For freight forwarders, a reliable <strong>UN\/LOCODE China list<\/strong> helps standardize communication between sales, operations, overseas agents, carriers, customs brokers, and trucking vendors. Instead of relying only on free-text city names, teams can align route planning around recognized location codes. This reduces the risk of booking cargo under the wrong origin, quoting the wrong inland haulage, or issuing shipping instructions with inconsistent locations.<\/p>\n<p>For logistics managers, UN\/LOCODE also supports network analysis. If a company imports from multiple Chinese factories, mapping origin locations by code can show which suppliers ship through Shanghai, Ningbo, Shenzhen, Qingdao, or Tianjin. This helps compare freight rates, transit times, consolidation options, incoterms responsibilities, and warehouse delivery patterns.<\/p>\n<h2>Common mistakes when using China location codes<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"Common mistakes when using China location codes for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-6-common-mistakes-when-using-china-location-codes.png\"\/><\/figure>\n<p><strong>1. Confusing city codes with terminal codes.<\/strong> A UN\/LOCODE identifies a transport location, but it may not identify a specific container terminal. A carrier may still require terminal details, vessel cutoff time, empty container pickup depot, and gate-in location.<\/p>\n<p><strong>2. Using airport codes as if they are always UN\/LOCODEs.<\/strong> Some UN\/LOCODE identifiers resemble IATA airport codes, such as CNPEK for Beijing or CNHGH for Hangzhou. However, air cargo codes, airport codes, and UN\/LOCODE entries are not always interchangeable. Always check the document field requirement.<\/p>\n<p><strong>3. Selecting a coastal port when the cargo is actually inland.<\/strong> A factory may be located in Chengdu, Chongqing, Wuhan, Zhengzhou, or Xi\u2019an, while the export container is routed through Shanghai, Ningbo, Shenzhen, or Qingdao. The place of receipt and port of loading may need different codes or descriptions.<\/p>\n<p><strong>4. Mixing up Qingdao codes.<\/strong> Qingdao is widely associated with CNTAO in transport usage. Users should be careful not to enter an incorrect or outdated code when preparing a bill of lading or carrier booking.<\/p>\n<p><strong>5. Assuming the supplier\u2019s nearest city is the correct shipping origin.<\/strong> The commercial supplier address, factory address, export customs location, container pickup location, and port of loading can all be different. This is common under EXW, FCA, FOB, and DDP shipping arrangements.<\/p>\n<p><strong>6. Not updating internal templates.<\/strong> Many companies reuse booking forms, purchase order templates, and logistics spreadsheets. If an old code or wrong origin remains in the template, the error can flow into freight quotes, shipping instructions, customs declarations, and warehouse delivery notices.<\/p>\n<p><strong>7. Treating sample lists as official databases.<\/strong> A blog post, carrier table, or forwarder spreadsheet can be helpful, but the official UNECE directory should be used for verification. The <strong>UN\/LOCODE China list<\/strong> is maintained and updated periodically, so final document checks are important.<\/p>\n<h2>How Huajiayi Logistics can help<\/h2>\n<figure class=\"wp-block-image size-full\"><img decoding=\"async\" alt=\"How Huajiayi Logistics can help for China UN\/LOCODE transport hub logistics planning\" src=\"https:\/\/huajiayilogistics.com\/wp-content\/uploads\/2026\/06\/huajiayi-unlocode-section-7-how-huajiayi-logistics-can-help.png\"\/><\/figure>\n<p>Huajiayi Logistics supports importers, Amazon sellers, freight forwarders, customs teams, and logistics managers with practical China shipping solutions. Our team helps confirm the correct origin, port of loading, destination routing, incoterms responsibility, export documentation requirements, and delivery plan before cargo moves.<\/p>\n<p>For ocean freight, we can assist with FCL and LCL bookings from major China ports such as Shanghai, Ningbo, Shenzhen, Guangzhou, Xiamen, Qingdao, Tianjin Xingang, and Dalian. For air freight, we support major gateways including Shanghai, Shenzhen, Guangzhou, Beijing, Hangzhou, Chengdu, Zhengzhou, and other key airports. For inland cargo, we help coordinate factory pickup, warehouse consolidation, export customs declaration, trucking, rail options, and final handover to the selected carrier.<\/p>\n<p>We also help customers review shipping documents for consistency. This includes checking whether the city name, UN\/LOCODE, port of loading, port of discharge, place of receipt, delivery address, incoterms, consignee details, and cargo description align across the commercial invoice, packing list, bill of lading, booking confirmation, and customs documents.<\/p>\n<p>If your team needs to build an internal <strong>UN\/LOCODE China list<\/strong>, compare port options, or confirm the right China origin for a freight quote, Huajiayi Logistics can provide route guidance and operational support based on your supplier location, cargo type, delivery deadline, and destination market.<\/p>\n<p><strong>Need help with China shipping routes or document details?<\/strong> Contact Huajiayi Logistics for support with UN\/LOCODE checks, freight booking, customs documentation, and end-to-end China logistics planning.<\/p>","protected":false},"excerpt":{"rendered":"<p>For international shipping, a small location code can determine whether a container booking, bill of lading, customs declaration, or inland delivery instruction is interpreted correctly. UN\/LOCODE, formally the United Nations Code for Trade and Transport Locations, is the global location coding system used to identify ports, airports, rail terminals, inland cities, and other transport points. [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-89","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/posts\/89","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/comments?post=89"}],"version-history":[{"count":2,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/posts\/89\/revisions"}],"predecessor-version":[{"id":102,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/posts\/89\/revisions\/102"}],"wp:attachment":[{"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/media?parent=89"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/categories?post=89"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/huajiayilogistics.com\/da\/wp-json\/wp\/v2\/tags?post=89"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}