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.
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.
Commercial carriers (FedEx, UPS, DHL)
Commercial carriers plug directly into the marketplace's parent org. No separate Verified Account is required.
The marketplace's parent Zonos org uses account-level third-party billing with each carrier. The carrier's account number on the label belongs to Zonos; the carrier invoices Zonos directly; Zonos invoices the marketplace through LCG at quote time.
No per-seller carrier account is needed. The marketplace is the sole account holder.
Shipments valued at $2,500 USD or more require formal entry with CBP and must use a commercial carrier. Postal operators cannot process high-value shipments that exceed the formal entry threshold.
Commercial carrier returns do not use the cross-org tracking-match mechanism. Marketplaces typically handle commercial returns either as separate shipments billed to the destination-country account or by issuing prepaid return labels through the carrier.
Postal operators
Each postal operator requires a separate Verified Account org per marketplace. The Verified Account connects to the marketplace's parent org via tracking-number cross-org match: when the postal operator transmits manifest data, Zonos matches the tracking number to an orderCreate on the parent org and billing flows through LCG.
The Verified Account itself does not need a billing method for forward shipments in the marketplace-managed model. Billing is handled at the parent org level.
Use a dedicated postal shipper number exclusively for Zonos-fulfilled forward shipments. The cross-org tracking match works by looking up the tracking number from an incoming manifest against an orderCreate on the parent org—if the same shipper number is also used for returns, non-Zonos shipments, or other fulfillment flows, those manifests will match against LCG orders they don't belong to and billing will be incorrect.
If returns need to run through the same postal operator, use a separate shipper number for the return flow and keep it off the Verified Account used for forward shipments.
For postal shipments to the EU valued at €150 or less, VAT is collected at checkout
under the Import One-Stop Shop (IOSS) scheme. By default, Zonos's own IOSS
registration is used—the marketplace doesn't need to register separately, and VAT
remittance is handled through Zonos.
If your platform has its own IOSS registration and needs to use it instead, reach out
to your Zonos contact to discuss the setup. Using your own IOSS is possible in certain
configurations, but the default path is Zonos's registration.
Create one Verified Account org for Australia Post, linked to the marketplace's parent org. Each seller's Australia Post shipper identifier (MLID / APCN / APBCN) maps through the marketplace's single parent org via the Verified Account.
Set dutyTaxPayor to SENDER_PAYS_ZONOS. The Verified Account does not need a billing method for forward shipments — billing flows through the parent org via LCG.
Pass ECOMMERCE_GOODS on itemCreateWorkflow for all marketplace goods, including promotional items. Australia Post rejects GIFT + SENDER_PAYS_ZONOS for U.S. destinations.
Create one Verified Account org for Canada Post, linked to the marketplace's parent org. For CA → US, the marketplace passes a Zonos Account Key through Shippo's Canada Post integration. For CA → EU, the same Verified Account + cross-org mechanism applies; EU-bound shipments under €150 are covered by Zonos's IOSS by default.
For supported EU destinations, per-country value limits, and full setup details, see
Postal DDP.
Japan Post can be used for DDP shipments in the marketplace-managed model, but most marketplace platforms use a commercial carrier for Japan-origin flows instead. If Japan Post support is needed for your platform, reach out to your Zonos contact to discuss setup.
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
Ship&Co
Ship&Co is the recommended platform for Japan-origin commercial shipments. It generates FedEx labels and passes Zonos's FedEx third-party billing account number on the carrier call, so FedEx bills Zonos directly and Zonos invoices the marketplace through LCG.
Key fields:
customs.ioss_number — for EU destinations, holds the IOSS number (Zonos's or the marketplace's own)
consignee_tax_id — the buyer's tax ID for the destination country; this is not where Zonos's tax ID goes
Zonos's tax IDs for non-EU remittance destinations (UK VAT, NO VOEC, AU GST, NZ IRD, SG GST) go in the shipper/sender section of the commercial invoice
Certification: Each new destination lane requires a test label review before go-live. Ship&Co generates a test label, Zonos reviews the API call output and commercial invoice, and confirms the lane. See Labels outside Dashboard.
Shippo
Shippo supports Canada Post, Australia Post, UPS, FedEx, and others. The billing mechanism varies by carrier.
Canada Post: Shippo passes a Zonos Account Key as a header on Canada Post API calls. Canada Post recognizes the key and routes duties and taxes to Zonos. The same mechanism covers CA → EU DDP (available November 4, 2026). The marketplace loads a single Account Key into Shippo per Canada Post account.
Australia Post: Shippo passes the Verified Account identifier (APBCN/MLID) to Australia Post. Billing flows via cross-org tracking match to the parent org.
UPS — Unlock: For high-value or commercial lanes, Zonos enables UPS Unlock on the marketplace's master UPS account. Shippo includes a zx-<order> reference on UPS labels; UPS calls Zonos to validate the shipment and pulls customs data; UPS bills Zonos for duties and taxes.
Unlock fires based on the shipper number on the label, not the master account. Purchase all labels on the master UPS account via Shippo rather than seller sub-accounts — if sellers each use their own shipper numbers, each would need Unlock enabled separately.
FedEx: Shippo's duties_payor field supports FedEx third-party billing. UPS does not honor this field at clearance despite accepting it at the API level.
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.
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.
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.
Clear text that matches the HS classification; CBP Error Code 336 fires on missing or vague descriptions
Required per shipment
Field↕
Notes↕
Filer code
Supplied by Zonos for entries Zonos files
IOR number
Supplied by Zonos; identifies Zonos as the importer of record for marketplace postal shipments
Shipper name and address
Complete origin party
Consignee name and address
Complete destination party
Postal tracking number
Used 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.
Shipping lanes
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
orderCreateon 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.
Commercial carriers (FedEx, UPS, DHL)
Commercial carriers plug directly into the marketplace's parent org. No separate Verified Account is required.
Account structure
The marketplace's parent Zonos org uses account-level third-party billing with each carrier. The carrier's account number on the label belongs to Zonos; the carrier invoices Zonos directly; Zonos invoices the marketplace through LCG at quote time.
No per-seller carrier account is needed. The marketplace is the sole account holder.
Billing
Third-party billing must be set up with each carrier separately:
The marketplace sees one consolidated LCG invoice from Zonos rather than separate carrier invoices.
DDP coverage
DDP is available for most country pairs via each carrier's native DDP program. Country-pair availability varies by carrier:
Formal entry threshold
Shipments valued at $2,500 USD or more require formal entry with CBP and must use a commercial carrier. Postal operators cannot process high-value shipments that exceed the formal entry threshold.
Returns
Commercial carrier returns do not use the cross-org tracking-match mechanism. Marketplaces typically handle commercial returns either as separate shipments billed to the destination-country account or by issuing prepaid return labels through the carrier.
Postal operators
Each postal operator requires a separate Verified Account org per marketplace. The Verified Account connects to the marketplace's parent org via tracking-number cross-org match: when the postal operator transmits manifest data, Zonos matches the tracking number to an
orderCreateon the parent org and billing flows through LCG.The Verified Account itself does not need a billing method for forward shipments in the marketplace-managed model. Billing is handled at the parent org level.
Shipper identifier scoping
Use a dedicated postal shipper number exclusively for Zonos-fulfilled forward shipments. The cross-org tracking match works by looking up the tracking number from an incoming manifest against an
orderCreateon the parent org—if the same shipper number is also used for returns, non-Zonos shipments, or other fulfillment flows, those manifests will match against LCG orders they don't belong to and billing will be incorrect.If returns need to run through the same postal operator, use a separate shipper number for the return flow and keep it off the Verified Account used for forward shipments.
IOSS for EU-bound shipments
For postal shipments to the EU valued at €150 or less, VAT is collected at checkout under the Import One-Stop Shop (IOSS) scheme. By default, Zonos's own IOSS registration is used—the marketplace doesn't need to register separately, and VAT remittance is handled through Zonos.
If your platform has its own IOSS registration and needs to use it instead, reach out to your Zonos contact to discuss the setup. Using your own IOSS is possible in certain configurations, but the default path is Zonos's registration.
Australia Post (AU → US)
Create one Verified Account org for Australia Post, linked to the marketplace's parent org. Each seller's Australia Post shipper identifier (MLID / APCN / APBCN) maps through the marketplace's single parent org via the Verified Account.
Set
dutyTaxPayortoSENDER_PAYS_ZONOS. The Verified Account does not need a billing method for forward shipments — billing flows through the parent org via LCG.Pass
ECOMMERCE_GOODSonitemCreateWorkflowfor all marketplace goods, including promotional items. Australia Post rejectsGIFT+SENDER_PAYS_ZONOSfor U.S. destinations.For supported destinations, content type mappings, and full setup details, see Zonos and Australia Post — Verified Accounts.
Canada Post (CA → US, CA → EU)
Create one Verified Account org for Canada Post, linked to the marketplace's parent org. For CA → US, the marketplace passes a Zonos Account Key through Shippo's Canada Post integration. For CA → EU, the same Verified Account + cross-org mechanism applies; EU-bound shipments under €150 are covered by Zonos's IOSS by default.
For supported EU destinations, per-country value limits, and full setup details, see Postal DDP.
Japan Post
Japan Post can be used for DDP shipments in the marketplace-managed model, but most marketplace platforms use a commercial carrier for Japan-origin flows instead. If Japan Post support is needed for your platform, reach out to your Zonos contact to discuss setup.
For destination and service level details, see Zonos and Japan Post — Verified Accounts.
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.
duties_payorShip&Co
Ship&Co is the recommended platform for Japan-origin commercial shipments. It generates FedEx labels and passes Zonos's FedEx third-party billing account number on the carrier call, so FedEx bills Zonos directly and Zonos invoices the marketplace through LCG.
Key fields:
customs.ioss_number— for EU destinations, holds the IOSS number (Zonos's or the marketplace's own)consignee_tax_id— the buyer's tax ID for the destination country; this is not where Zonos's tax ID goesCertification: Each new destination lane requires a test label review before go-live. Ship&Co generates a test label, Zonos reviews the API call output and commercial invoice, and confirms the lane. See Labels outside Dashboard.
Shippo
Shippo supports Canada Post, Australia Post, UPS, FedEx, and others. The billing mechanism varies by carrier.
Canada Post: Shippo passes a Zonos Account Key as a header on Canada Post API calls. Canada Post recognizes the key and routes duties and taxes to Zonos. The same mechanism covers CA → EU DDP (available November 4, 2026). The marketplace loads a single Account Key into Shippo per Canada Post account.
Australia Post: Shippo passes the Verified Account identifier (APBCN/MLID) to Australia Post. Billing flows via cross-org tracking match to the parent org.
UPS — Unlock: For high-value or commercial lanes, Zonos enables UPS Unlock on the marketplace's master UPS account. Shippo includes a
zx-<order>reference on UPS labels; UPS calls Zonos to validate the shipment and pulls customs data; UPS bills Zonos for duties and taxes.Unlock fires based on the shipper number on the label, not the master account. Purchase all labels on the master UPS account via Shippo rather than seller sub-accounts — if sellers each use their own shipper numbers, each would need Unlock enabled separately.
FedEx: Shippo's
duties_payorfield supports FedEx third-party billing. UPS does not honor this field at clearance despite accepting it at the API level.Key field mappings:
reference_1/reference_2ReferenceNumberzx-<order>prefix required by UPS Unlocksku_codeProductIDduties_payorEU 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
itemCreateWorkflowand 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.skumanufacturerProductIdgtinIf 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 includessku,manufacturerProductId, andgtinat 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
Required per shipment
orderCreatePGA 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:
Timing TBD:
Was this page helpful?