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.
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.
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.
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.
Returns are not covered by the forward-shipment flow above. See
Shipping lanes for per-carrier
return handling.
$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.
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.
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.
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.
DDP shipping
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
orderCreateon 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
Parent org holds LCG certification, billing, and API credentials. The marketplace calls
orderCreateon every shipment, passing a tracking number, item data, and party data.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
orderCreateon the parent org and billing flows through LCG. The Verified Account itself never bills for forward shipments.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.
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
namedescriptionhsTariffCodecountryOfOriginAU,CA)amountcurrencyCodeskumanufacturerProductIdgtinParty fields
THIRD_PARTYwith the marketplace as payorValuation
$0 declared value is not accepted on commercial goods shipped across borders.
Content type
Marketplace-distributed items—including free or promotional items—must use
ECOMMERCE_GOODSorCOMMERCIAL_GOODS, notGIFT.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:
GIFT+SENDER_PAYS_ZONOScombinations for U.S.-bound shipments.Pass
ECOMMERCE_GOODSonitemCreateWorkflowfor 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
ALLOWEDmode (notENABLED) so an FTA rate is only applied when the marketplace explicitly sets thefree_trade_agreementsattribute 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?