1.Goals
This article is intended for customers using end-to-end (E2E) services. It provides comprehensive integration guidance—from creating bookings and generating labels to ensuring label print quality and retrieving tracking event details.
2.Obtaining Shipping Labels
Customers can create bookings and generate shipping labels using either of the following methods:
1) Log in to the FCM Portal.
2) Integrate with the genericDataAndLabel API.
Once system checks (field validation and denied-party screening) are completed, the label will be generated. Duplicate shipment IDs are not allowed. Below is an overview of both methods:
2.1FCM Portal
Log in to the FCM Portal to create a booking. Your FCM Portal login credentials and CW1 account details will be sent via email.
Access FCM Portal: https://myfcm.dhl.com/
For detailed instructions, refer to the FCM Portal page.
2.2 genericDataAndLabel API
Integrate with the genericDataAndLabel API to create bookings and generate labels.
For more information, see the E2E API Integration page.
3.Labeling Requirements
Example of a white label:
3.1Basic Printing Configuration
- Printer Model: ZEBRA GX420D
- Label Size: 100*150mm
- Label type: Thermal
4.CN Mainland Customer Pick-up Request
Customers must submit pickup requests via the FCM Portal. Refer to Section 3.3 of the DHL FCM Portal User Guide for details.
Notes:
For CN mainland customers: Requests before 16:00 → earliest pickup same day; after 16:00 → next day.
5.HK Customer Self‑Delivery Process
After customers in the Hong Kong region complete order placement, attach the small‑parcel last‑mile labels, and update the small‑parcel to big‑parcel mapping data, they must deliver the cartons—packed according to DHL requirements—to the designated HKG warehouse.
Both the email pre-alert and the physical goods must arrive at the warehouse no later than 15:00 on the same day. If either one is missing, shipment cannot be arranged.
Pre‑alert Email Subject: Customer Name + Delivery Date + Number of Cartons/Bags + Total Pieces
Please send the pre-alert email to all of the following email addresses, and cc your sales representative:
hkg.ops@dhl.com & ka_ching.lam@dhl.com & zhuo_quan.li@dhl.com
6.Shipment Tracking
6.1 Track via DHL Official Website
Once the order is placed, customers can visit the official DHL website to check subsequent tracking status updates. If CN customers have any questions regarding the existing tracking events, please contact the DGF eCommerce C/S team <cs-ecomteam.sz@dhl.com>.
DHL Official Website: https://www.dhl.com/
6.2 Track via Integration with Tracking APIs
- Tracking Pull API
Allows customers to actively send requests to query tracking details.
Tracking Pull API documentation: https://dhl1.portal.swaggerhub.com/dconnectordhlcom/docs/tracking-pull-api
- Tracking Push API
Allows customers to subscribe to tracking status updates, and the system will automatically push tracking updates.
Tracking Push API documentation: https://dhl1.portal.swaggerhub.com/dconnectordhlcom/docs/tracking-push-api
7.Notes for official launch
1) After completing E2E onboarding, customers must continuously monitor and address label printing quality issues during operations. Ensure the following:
- All fields meet the required specifications.
- Labels are printed clearly and completely, with no barcode interruptions.
- Labels are affixed flat, free of scratches, water stains, wrinkles, tape coverage, or other defects.
Example of proper label placement:
2) Fields requirements:
| Scope | Applies to | Product code | FCM fields | API fields | Requirement |
|---|---|---|---|---|---|
| Global | All | All | Shipper reference | shipmentId | Must be 5–30 characters, no spaces (max 15 for IN customers) |
| Global | All | All | All fields | All fields | Use ASCII characters only to avoid recognition errors |
| Global | All | All | - | label.format | Shipping labels must be in PDF format; ZPL and PNG are not supported |
| Global | All | All | All fields | All fields | Do not include special characters such as “|” in transmitted data |
| Global | All | All | Fiscal Id | fiscalId | Enter the IOSS number only in the “fiscalId” field |
| Global | All | All | shipperAddress | shipperAddress | “shipperAddress” must not contain Chinese characters |
| Origin | CN / HK | - | - | - | Please refer to origin - CN/HK page |
| Origin | IN | - | - | - | Please refer to origin - IN page |
| Destination | US | PLG, PLT | description | description | Product descriptions must comply with ACAS requirements |
| Destination | US | PLG, PLT, PDC, PLD, PPM | HS Code | shipmentContents.hsCode | Use the correct HS code from the DHL-provided US HS Code Whitelist |
| Destination | US | All (CDZ Clearance) | Item weight | shipmentContents.grossWeight | Item weight must be included in shipment data |
| Destination | US | PLG, PLT (T11 Entry) | - | - | Please refer to destination - US page |
| Destination | GCC countries | PLG, PLT | - | - | Please refer to destination - GCC countries page |
| Destination | CA | PLG, PLT | name | consigneeAddress.name | Consignee names must be in English or French only |
| Destination | EU | PKW, PLG, PLT, PPW, PPD, PED, PPM, PKM, PDC, PLD | HS Code | shipmentContents.hsCode | Use the correct HS code from the DHL-provided EU HS Code Whitelist |
8. AI Automated Support
For common errors or inquiries during the integration process, please visit our AI Automated Support via the link below.
AI Chatbot URL:https://cnk2zb8zv2.coze.site/
Please Note:
- AI-Generated Responses: Answers are generated automatically by AI and cannot be guaranteed 100% accurate. Please use them as a reference.
- Continuous Updates: As this is a newly launched tool, the current knowledge base is limited and might not cover every niche scenario yet. We are constantly expanding and optimizing the content.
- Human Support is Always Available: If the AI cannot fully resolve your query or if you require deeper technical assistance, please feel free to contact your account manager or support team (ecs.pi_support@dhl.com) directly.
9. FQA
1) Does the system allow duplicate shipment IDs? What happens if I send the same shipmentId again?
No, duplicate shipment IDs are not allowed. If you send a repeated shipmentId, the system will return the following error:
"[Generate Label] Generating label batch fail: PackageId have successfully called external
parcel API before. Same packageId cannot repeatedly call".
2)What should I do if I receive an error indicating the shipper or consignee information is suspected to be on the deny party list?
Error message: [NECST Group:220785572907008] Shipper/consignee information is suspected to be deny party.
Solutions:
- Retry the request with the same shipmentId and order details after 1–2 hours.
- Wait for DHL to email you the verification result.
a. If verification passes, re-submit the request with the same shipmentId and order details.
b. If verification fails, update the shipmentId and consignee/shipper information before resending.
If you wish to receive email notifications for deny party verification results, provide your email address to ecs.pi_support@dhl.com for configuration.
3) For PLT/PLG services to GB, what address format should I use? What happens if it’s incorrect?
Ensure the house number appears before the street name, e.g.: Flat 7, Arkwright Mansions Finchley Road. If the format is incorrect, the delivery note may display an incomplete address, which can affect successful delivery.
4) Can I use Packstation as the delivery address for shipments to Germany? How should it be formatted?
Yes, Packstation can be used as the consignee address for shipments to Germany. If you wish to use this type of address, please contact your sales manager for assistance with configuration.
Packstation address format:
| Field | Rule |
| Consignee Address 1 | For standard addresses: Enter street name + house number (e.g., Fürstenbergstr. 15). For Packstation addresses: Enter Packstation + keywordId (e.g., Packstation 255). |
| Consignee Address 2 | For Packstation addresses: Enter the Postnumber. For standard addresses: Leave blank. |