| | | | |
| | | | Different shipments cannot include same package number |
| | Client’s parcel number (client-side identifier) | | Unique Client reference ID |
| | Service that is selected for parcel delivery | | Allowed values: REGISTERED, NOT_REGISTERED, EMS, PRIME, PARCEL_EPG, PARCEL_UPU, TRACKABLE, NONPOSTAL, Use NONPOSTAL for Customs Clearance shipments. |
| | | | Channel code with “|OPS-CC” suffix for customs clearance flows. 1. SameDay-> “SD RO|OPS-CC”/“UNIS LV|OPS-CC” 2. DPD-> “DPD RO|OPS-CC” etc. Ask for more codes that should be used if needed. |
| | | | Allowed values: DDP, DDU, CLEARED
Use DDP for IOSS customs clearance EU flows. |
| | | Yes, when parcel ID is generated by client | |
| | Parcel total weight in kilograms | | Must be a positive number |
| | Total Price of the parcel, currently expected in USD | | 1. TotalPrice > 0 2. Max 2 decimals 3. If not filled, the system will calculate based on quantity & item price |
| | | | |
| | Consignor VAT representative. In EU IOSS Broker is expected | | Field is mandatory when non-EU sender sends DDP EU non-cleared goods |
| | Information about the originator | | Must include “address” object with country code to indicate origin of goods “CN” |
| | Information about the consignor | | Must include “name”, “address” and represents sender. |
| | Information about the recipient | | Must include “name”, “phoneNumber”, “address” object for importer |
| | List of items in the parcel | | Each item must include “commodity”, “hsCode”, “quantity”, “weight”, “price” |