DOCS

Shipping lanes and carrier requirements

Lane-specific integration requirements for marketplace platforms using the Zonos marketplace-managed model.

This doc covers what each shipping lane requires when a marketplace operates as the single Zonos account holder—using a parent Zonos org configured for LCG billing and Verified Accounts for postal lanes.

For an explanation of the two integration models and which one fits your platform, see the marketplace overview.

All sections below assume the marketplace-managed pattern: the marketplace holds one Zonos parent org, calls orderCreate on every shipment, and routes postal lanes through per-operator Verified Accounts connected to the parent via tracking-number cross-org match.

Carriers 

Marketplace shipments move through two types of carriers: commercial carriers (FedEx, UPS, DHL) and postal operators (Australia Post, Canada Post, Japan Post). The billing setup and integration requirements differ between the two.

Shipping platforms 

Marketplaces typically purchase labels through a shipping platform rather than integrating carrier APIs directly. The platform determines which carriers are available, how Zonos billing is wired in, and what field mapping is needed.

Carrier↕Ship&Co↕Shippo↕
FedEx✅ Third-party billing (certified)✅ Third-party billing via duties_payor
UPS—✅ Unlock on master account only
DHL—✅
Canada Post—✅ Zonos Account Key header
Australia Post—✅ Verified Account identifier

EU inbound product identifiers 

Required from November 1, 2026 for all EU-bound B2C postal shipments valued at €150 or less, per EU customs regulation.

Zonos accepts these identifiers at the item level on itemCreateWorkflow and transmits them to the postal operator's manifest, which flows to IPC and EU customs. No separate submission to EU customs is required from the marketplace.

Zonos field↕PID type↕Required?↕Notes↕
skuM-PID (Merchant Product Identifier)Always requiredCan be the marketplace's internal product ID
manufacturerProductIdNS-PID (Non-Standardised Manufacturer Product Identifier)Always requiredMust be distinct from the SKU—a common integration mistake
gtinS-PID (Standardised Manufacturer Product Identifier)Required when the product has oneUPC, EAN, or GTIN-14

If a product has no GTIN (no barcode), Zonos uses the Y081 placeholder. Do not invent or fabricate a GTIN—transmitting a false identifier is a customs violation.

Marketplace integration note: These fields come in via itemCreateWorkflow. Ensure the seller data model includes sku, manufacturerProductId, and gtin at the product level before the November 1, 2026 deadline.

For more on EU PIDs in the catalog context, see EU product identifiers.

U.S. inbound — Entry Type 13 

Effective January 20, 2027, CBP's Entry Type 13 (ET13) replaces the informal entry process for all postal shipments into the United States. The item and shipment fields below are required from that date.

Required per item

Field↕Notes↕
HS code10-digit HTS code for U.S. entry
Country of originISO 3166-1 alpha-2
Declared valueNo $0 declarations (see marketplace overview)
Merchandise descriptionClear text that matches the HS classification; CBP Error Code 336 fires on missing or vague descriptions

Required per shipment

Field↕Notes↕
Filer codeSupplied by Zonos for entries Zonos files
IOR numberSupplied by Zonos; identifies Zonos as the importer of record for marketplace postal shipments
Shipper name and addressComplete origin party
Consignee name and addressComplete destination party
Postal tracking numberUsed for cross-org match to orderCreate

PGA data

Partner Government Agency (PGA) data requirements apply to U.S. inbound shipments containing regulated goods—food, cosmetics, electronics with FCC requirements, and similar categories. CBP currently waives PGA data for postal entries (FR 2026-21570, effective October 22, 2026), but this waiver has no announced end date and enforcement is expected to begin in early 2027. Marketplaces with regulated product categories should treat PGA data collection as a near-term requirement, not a future one.

Zonos supports PGA data collection for Verified Account marketplaces. See PGA checks for supported agencies and how to pass PGA data.

Enforcement notes

In effect now:

  • CBP Error Code 336 ("INVOICE/MERCH DESC REQUIRED FOR ET13") deployed October 15, 2026. Missing or inadequate merchandise descriptions now trigger rejection at CBP.
  • $0 declared values will be rejected outright from January 20, 2027. Submitting $0 before that date may still be treated as a responsible-supervision failure.

Timing TBD:

  • PGA data enforcement is expected in early 2027 but CBP has not announced an exact date.
  • FTA verification on postal entries is new—CBP's document-request frequency for postal FTA claims will not be clear until post-January 20 enforcement patterns emerge.

Was this page helpful?


Get support·Legal docs·© 2026 Zonos