29 Oct
Downstream mappings deployed today
For orders that include PID values, iShipper sends the available data to the downstream systems included in this release.
At a glance
EU Customs requires M-PID and NS-PID for EU-bound shipments from 1 November 2026. iShipper will enforce these fields from 2 November.
2 Nov
iShipper validation starts
M-PID and NS-PID become mandatory in iShipper for EU-bound orders. S-PID remains optional.
After 2 Nov
IT provides the transition report
The report covers EU-bound orders created from 26 October up to the mandatory-validation cutover, so teams can follow up on missing PID data.
2026 RELEASE CALENDAR
All dates · 2026PID rollout by date
Select a date to see the requirement or deployment scheduled for that day.
REPORT ORDER RANGE
Orders created from 26 October enter the report population
The transition report covers EU-bound orders created from this date up to the iShipper mandatory-validation cutover. IT will provide the report after 2 November.
MAPPING DEPLOYMENT
Remaining downstream PID mappings
YCC, ACL, A1, London Hub, and Sengi are scheduled for deployment. DHL and SingPost are already live and pass available PID data when an order is created.
EU CUSTOMS REQUIREMENT
M-PID and NS-PID required for EU-bound shipments
The EU Customs requirement takes effect on 1 November. It is a Sunday, so iShipper validation is scheduled for the next day to ensure customer support is available if validation prevents an order from being created.
ISHIPPER VALIDATION + INDIA POST MAPPING
Mandatory checks and India Post PID mapping
iShipper starts requiring M-PID and NS-PID on EU-bound orders. The PID mapping for the existing India Post PDDP EU channel is also scheduled for deployment. IT will provide the transition report after the validation deployment.
iShipper PID fields
This table describes iShipper field-level validation and limits. Each PID is captured at the order customs-item level.
| UI Field Name | API Parameter Name | API Parameter Layer | Description | Mandatory / Optional | Data Type | Max Length | Remark |
|---|---|---|---|---|---|---|---|
| Merchant PID | MerchantPid | OrderList[].OrderCustoms | Merchant Product Identifier (M-PID), such as SKU, Product Code, or Listing ID. | Mandatory for EU from 2 Nov | String | 255 | EU Customs requires M-PID from 1 November 2026. iShipper validation starts on 2 November. |
| Manufacturer PID | ManufacturerPid | OrderList[].OrderCustoms | Non-Standard Manufacturer Product Identifier (NS-PID), such as Model Number, MPN, or Style Number. | Mandatory for EU from 2 Nov | String | 255 | EU Customs requires NS-PID from 1 November 2026. iShipper validation starts on 2 November. |
| Standardised PID | StandardisedPid | OrderList[].OrderCustoms | Standardised Product Identifier (S-PID), such as GTIN, EAN, UPC, or ISBN. | Optional | String | 255 | Optional under the current iShipper validation requirement. |
Current scope of the Data Requirement ExcelThe Excel currently lists iShipper’s general PID requirements. Special data requirements and limitations for individual downstream systems are not yet included in the version available today, 29 October 2026. These downstream-specific details will be compiled and updated in the relevant announcement emails on 2 November 2026.
Downstream PID mapping deployments
When a customer supplies PID data on an order, iShipper passes the available values to the relevant downstream system.
DHL and SingPost
For orders created now that include PID data, iShipper already sends the available PID values to these downstream systems.
- DHL
- SingPost
Other downstream mappings
These mappings are scheduled for deployment today.
- YCC
- ACL
- A1
- London HubLDN Hub channel
- Sengi
India Post
PID mapping will be added to the existing India Post PDDP EU channel. This supports DTDC shipments to the EU using India Post. For orders with PID values, iShipper will pass the available data to the downstream flow after deployment.
Transition-period EU order report
IT will provide this report after the 2 November iShipper validation deployment.
Orders created from 26 Oct until the validation cutover
The report will help the relevant teams identify EU-bound orders created before mandatory validation and follow up with customers or arrange to complete the PID data in the system.
- Report delivery: after 2 November deployment
- Order population: EU-bound orders created from 26 October until mandatory validation is deployed
- Purpose: customer follow-up or completion of missing PID data
Need another PID report or information?
Submit a request through the Asendia Service Desk.
Open Asendia Service Desk ↗Customer action
Please prepare the required product identifiers for EU-bound shipments.
- Provide an M-PID and NS-PID for each product in EU-bound orders from 1 November 2026.
- Enter PID values in the relevant product / customs item fields in iShipper.
- S-PID remains optional in iShipper under the current requirement.
Data Requirement Excel: current scope
The Excel currently contains iShipper’s general PID requirements. Downstream system-specific data requirements and limitations are not included in the version available today, 29 October 2026; they will be compiled and updated in the relevant announcement emails on 2 November 2026.
Open Data Requirement Excel ↗