Guides
Customs
Specific, accurate item data prevents avoidable booking failures.
These are fixture contract requirements. They do not establish live provider acceptance; current V1 production creation rejects customs requests.
Required item fields
| Field | Meaning |
|---|---|
| description | Specific goods, 3–200 characters |
| quantity | Positive whole number |
| value | Positive unit value in customs currency |
| weight | Positive unit weight in kg |
| hs_code | 6–10 tariff digits |
| country_of_origin | Manufacturing origin, uppercase country code |
Tax identifiers
eori is the sender identifier; recipient_eori is the receiver identifier. vat_id and ioss_id are optional structurally and may become required or invalid for a live route. PX must validate service and legal eligibility before a live booking. The sandbox checks syntax and supported terms, not customs compliance.
Existing PX requirements
Current provider adapters validate item descriptions, tariff codes and origins, map EORI/IOSS fields and choose DAP/DDP differently. Public V1 must centralize the capability requirements before live availability. Do not invent an HS code or origin when a merchant omits it.