DOCS

DDP shipping for marketplaces

Landed Cost Guarantee, DDP fulfillment across commercial and postal lanes, and flexible configurations for marketplace platforms at scale.

Zonos's Landed Cost Guarantee (LCG) is the billing and accuracy foundation for marketplace DDP. At quote time, Zonos calculates the full landed cost—duties, taxes, and fees—and guarantees that amount. The marketplace collects it from the buyer at checkout; if the actual duty at customs differs, Zonos covers the shortfall. There are no surprise charges for buyers and no reconciliation work for the marketplace.

In the marketplace-managed model, the marketplace holds one parent Zonos org configured for LCG and is the sole API caller. Every shipment—regardless of which seller fulfilled it—flows through this single org. Postal lanes (Australia Post, Canada Post, and similar operators) each require a Verified Account—a separate Zonos org created for that operator. When the postal operator electronically transmits manifest data, Zonos matches the tracking number to the original orderCreate on the parent org, so duties and taxes bill through LCG rather than being assessed at delivery. Commercial lanes use account-level third-party carrier billing.

This is the standard approach for large platforms that want to centralize billing and abstract customs compliance from their seller base.

How it works 

  1. Parent org holds LCG certification, billing, and API credentials. The marketplace calls orderCreate on every shipment, passing a tracking number, item data, and party data.

  2. Postal lanes each require a separate Verified Account org per postal operator (Australia Post, Canada Post, etc.). The Verified Account connects to the 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 never bills for forward shipments.

  3. Commercial lanes (FedEx, UPS, DHL) plug directly into the parent org via account-level third-party billing. The carrier bills Zonos's account number; Zonos invoices the marketplace through LCG.

  4. Returns are not covered by the forward-shipment flow above. See Shipping lanes for per-carrier return handling.

Item and party data requirements 

The marketplace is responsible for providing complete item and party data on every API call.

Item fields

Field↕Notes↕
nameClear merchandise description
descriptionDistinct from name; used for HS classification
hsTariffCode6–10 digit HS code, or omit to let Classify handle it
countryOfOriginISO 3166-1 alpha-2 (e.g., AU, CA)
amountDeclared value—no $0 (see Valuation below)
currencyCodeISO 4217 currency code
skuRequired for EU-bound shipments (M-PID)
manufacturerProductIdRequired for EU-bound shipments (NS-PID); must differ from SKU
gtinRequired for EU-bound shipments when the product has one (S-PID); UPC, EAN, or GTIN-14

Party fields

Party↕Required fields↕
Origin (seller)Full name, address, phone, email—required for FTA eligibility
Destination (buyer)Full name, address, phone, email
PayorTypically THIRD_PARTY with the marketplace as payor

Valuation 

$0 declared value is not accepted on commercial goods shipped across borders.

  • Giveaways and promotional shipments must still carry a value—the price the seller would normally sell at, or the fair market value.
  • Effective January 20, 2027 (U.S. Entry Type 13): $0 declarations are outright rejected by CBP. Submitting $0 before that date may also be treated as a responsible-supervision failure under CBP review.
  • Legal basis: 19 CFR Part 152 (customs valuation hierarchy). Value must be declared in accordance with the transaction value standard.

Content type 

Marketplace-distributed items—including free or promotional items—must use ECOMMERCE_GOODS or COMMERCIAL_GOODS, not GIFT.

Per CBP's interpretation of 19 CFR 10.153, bona fide gifts are personal transfers between individuals motivated by generosity, not commercial distributions by a marketplace. Marketplace items don't qualify—even when the recipient paid nothing.

Practical consequences:

  • Australia Post will reject GIFT + SENDER_PAYS_ZONOS combinations for U.S.-bound shipments.
  • Incorrect content type can delay clearance or trigger reclassification at CBP.

Pass ECOMMERCE_GOODS on itemCreateWorkflow for all marketplace-distributed goods.

FTA configuration 

Marketplaces with sellers from FTA partner countries (AU, CA, MX, KR, and others) can claim preferential duty rates. Use ALLOWED mode (not ENABLED) so an FTA rate is only applied when the marketplace explicitly sets the free_trade_agreements attribute on the item. This gives per-seller, per-product control rather than applying FTA claims across all eligible items automatically.

Collect per-product attestation at the point sellers enter country of origin. Keep attestation records in case CBP requests documentation.

For supported agreements, claim fields, and certificate-of-origin requirements, see Free trade agreements.

Lane support 

For lane-specific requirements—commercial carrier billing, per-operator Verified Account setup, EU inbound PID requirements, and U.S. Entry Type 13—see Shipping lanes.

Was this page helpful?


Get support·Legal docs·© 2026 Zonos