Zonos vs. Global-e: Landed-Cost Software or Merchant of Record?
Zonos wins for mid-market Shopify stores selling past roughly 10% international share: you stay seller of record and pay software pricing instead of a percentage of every order. Global-e wins at enterprise cross-border scale, where a negotiated merchant-of-record contract spans channels one Shopify storefront never sees. Native Markets duties collection plus owned HS codes covers supported lanes without either vendor, and head-to-head comparisons hide that lane.
Your profile — see how the verdict shifts
- Confidence
- Medium — The seller-of-record versus merchant-of-record split is structural and well documented; the crossover moves with international share, margin, and ops capacity, and both vendors' pricing is unverified
- Reference scenario
- $20M–$100M GMV · 10–25% international · DTC parcels · Shopify storefront
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| International under 5% of sales (testing) | WAIT | Neither vendor pays for itself on marginal volume. Run native Markets duties collection on supported lanes, or the parent page's Managed Markets call, and learn where demand lives first. |
| 5–25% international, DTC parcels | BUY | Zonos is the reference-scenario winner: guaranteed landed cost at checkout, your entity on every invoice, and software pricing that grows slower than a revenue-share line ever would. |
| B2B or wholesale cross-border | BUY | Business buyers need your company on invoices and their tax IDs handled directly; a reseller structure gets in the way of wholesale terms. Zonos keeps the paperwork in your name. |
| 25%+ international or multi-channel enterprise | DEPENDS | Global-e direct earns its contract weight here: negotiated economics, multi-region logistics, and coverage for marketplaces and retail. Model it against owning the flow before signing either. |
What Zonos vs. Global-e Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | A guaranteed duties-inclusive total at checkout converts shoppers who abandon at vague duties-may-apply warnings; all three lanes deliver the mechanism on their supported markets. |
| Operational efficiency | High | Global-e deletes registrations, remittance, and duty disputes from your ops entirely; Zonos automates the math but leaves the function yours, and the native lane leaves both. |
| Retention & LTV | Medium | A first parcel that arrives without a courier ransom note qualifies the customer for a second order; misquoted landed costs are how international cohorts quietly die. |
| Data & insight | Medium | Staying seller of record keeps duty, carrier, and margin data per market in your own stack; a merchant of record holds much of that math behind its fee. |
Spend ceiling: Cap total cross-border cost, whether fees or software plus labor, at the margin your international orders actually carry; a lane that costs more than the margin is the wrong lane at any feature depth (Deploi estimate, illustrative).
What buying enables (top apps)
- + Guaranteed landed cost and prepaid-duty options at checkout while you stay seller of record
- + Your invoices, your customer relationship, and your wholesale terms intact, which the reseller model can't offer
- + Per-market duty and margin visibility feeding pricing and assortment decisions
- + On the Global-e side: a whole compliance function carried by the provider at enterprise scale
What building additionally unlocks
- + A flat cost base on supported lanes: no software subscription and no percentage stack as volume grows
- + Owned, auditable HS-code governance in your catalog via the Admin API, the community-proven fix for the misclassification saga
- + A per-market DDP/DDU policy under your rules rather than a provider's defaults
- + An exit that rounds to zero: everything built here carries into either vendor later
Find Your Verdict in 3 Questions
Is international under roughly 5% of sales and mostly a test?
Yes: Your verdict: WAIT — run native Markets duties collection on supported lanes (or the parent page's Managed Markets call) and revisit when share grows.
No: Go to question 2.
Do you sell cross-border at enterprise scale: 25%+ share, multiple channels, or negotiated logistics needs?
Yes: Your verdict: BUY — Global-e direct; a negotiated merchant-of-record contract covers channels and volume the packaged lanes never see.
No: Go to question 3.
Do B2B invoices, wholesale terms, or first-party buyer data require your entity to stay seller of record?
Yes: Your verdict: BUY — Zonos; landed-cost software keeps your name on every invoice and the fee line growing slower than revenue.
No: Your verdict: BUY — Zonos still wins the reference scenario on economics; re-run the native-lane coverage math yearly before each renewal.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | Zonos runs 2–6 weeks of integration, HS-code readiness, and carrier wiring (Deploi estimate, illustrative); the native lane starts by classifying the whole catalog, an estimated 4–8 weeks (Deploi estimate, illustrative). A Global-e contract takes months of enterprise onboarding. | ||
| Recurring fees | Zonos prices as software plus per-order landed-cost fees; native collection is included with Markets on supported lanes, leaving carrier DDP fees and upkeep as the recurring lines. Global-e's revenue share scales with every order. | ||
| Maintenance & upgrades | Zonos absorbs duty-rate and threshold churn behind its data product; the native lane re-checks classifications every time the catalog or a tariff schedule moves, and that review never ends. | ||
| Switching & exit | Leaving Zonos is an integration swap because registrations, carrier accounts, and HS codes already sit in your name; the native lane strands nothing at all. A Global-e exit is a merchant-of-record unwind of 4–8 weeks (Deploi estimate, illustrative). | ||
| Risk | |||
| Vendor risk | Zonos is one independent vendor inside your duty-quoting path; Global-e concentrates the entire cross-border operation in a single contract. The native lane has no vendor to lose. | ||
| Security & compliance surface | Zonos handles the landed-cost math while customs liability stays with you; the native lane leaves both the math inputs and the liability on your desk. Only a merchant of record moves compliance off your entity, and that is Global-e's actual product. | ||
| Platform-deprecation exposure | Native duties collection is first-party checkout surface; Zonos tracks checkout and API changes like any integration, upkeep the vendor absorbs on the roughly six-month version cycle. | ||
| Value | |||
| Fit to requirement | Zonos fits DTC and B2B sellers who want guaranteed totals with their own name on the invoice; native collection covers supported lanes and stops where lane coverage does. | ||
| Time to market | Zonos quotes duties within weeks of kickoff; the native lane waits on catalog classification before checkout can quote a duty honestly. Global-e's enterprise cycle is the slowest path and the most complete one. | ||
| Performance & scale | All three lanes quote landed cost inside native checkout at full speed; what separates them at volume is economics and control, not throughput. | ||
| Data ownership & AI-readiness | Zonos processes order data while customers, pricing, and HS codes stay first-party; the native lane keeps everything inside Shopify. A merchant of record intermediates parts of the buyer record behind the fee. | ||
| Focus & opportunity cost | Both seller-of-record lanes keep duty ops in-house as a standing claim on finance and support attention; Global-e is the only lane that deletes the function, and its fee prices exactly that. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Zonos | Live — Landed-cost specialist: duty and tax quoting with checkout tools while you stay merchant of record | Tiered subscription plus per-order fees (illustrative) | Cross-border sellers keeping their own name on the invoice and the buyer record |
| Global-e | Live — Enterprise cross-border merchant-of-record platform; its infrastructure also underpins Shopify's Managed Markets program | Revenue-share, contract-negotiated | Enterprise cross-border programs spanning channels beyond one Shopify storefront |
| Shopify Markets + duties at checkout | Native — The lighter lane: duties collected at checkout while you stay merchant of record and handle remittance | Included with Markets; carrier DDP fees separate | Owning the flow without either vendor where lane coverage suffices |
| Shopify Managed Markets | Live — Shopify's managed cross-border product, powered by Global-e as merchant of record | 6.5% of order value + 2.5% currency conversion (per July 2026 research — re-verify) | Global-e-grade merchant of record without enterprise contracting |
The Build Path
- Native duties collection on supported lanes: Markets estimates and collects duties in native checkout where supported; you stay merchant of record and keep every fee line flat.
- HS-code governance via the Admin API: Assign, store, and bulk-correct HS codes on your own products through the Admin API and metafields. Classification quality drives quote quality on every path, both vendors included.
- Per-market DDP/DDU policy layer: Encode a written policy in market settings and checkout copy: prepaid duties where guaranteed totals convert, DDU with plain messaging where de minimis thresholds carry most orders.
- The escalation path, named honestly: When unsupported lanes or missing guaranteed totals start costing orders, add a swappable landed-cost vendor. That upgrade is the Zonos path, which is why this lane never strands work.
- Effort band
- $15,000–$40,000 for catalog classification, checkout wiring, and the policy layer (Deploi estimate, illustrative); spans the $10–25K and $25–75K contact-form bands
- Typical timeline
- 4–8 weeks for the native lane (Deploi estimate, illustrative); Zonos integration runs 2–6 weeks once chosen; a Global-e contract takes months
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): classification reviews when the catalog or a tariff schedule moves, API version bumps, and carrier fee spot-checks. There is no percentage-of-sales line and no software subscription.
- What you own — and what you take on
- You own: the buyer relationship, the classification record, the per-market DDP/DDU policy, and a cost base that stays flat as volume grows. You take on: customs exceptions, refused parcels, and lane-coverage limits, which is exactly what both vendors charge to absorb.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $8,000–$20,000 (integration + catalog readiness) | $15,000–$40,000 (classification + wiring) |
| Years 1–3 (recurring) | $36,000–$90,000 (software + per-order fees) | $9,000–$24,000 (maintenance + reviews) |
| 3-year total | ≈$44,000–$110,000 | ≈$24,000–$64,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column = the Zonos path: software subscription plus per-order landed-cost fees and in-house compliance ops on an illustrative $3M/yr international slice.
- † Build column = the native lane: classification build, native duties collection on supported lanes, and upkeep. A direct Global-e contract prices as negotiated revenue share and is discussed in the caption, not charted.
What the Sticker Price Hides
On the buy path
- — Per-order fees plus subscription still compound; model the Zonos line on your real mix before assuming software always wins (Deploi estimate, illustrative)
- — Compliance ops stay home on the Zonos path: registrations, remittance, and carrier DDP wiring are your job, and finance hours are the hidden line
- — Global-e minimum-volume commitments and notice periods can outlast the growth plan that justified them
- — HS-code quality drives every quote; bad classifications produce bad landed costs on your letterhead, whichever vendor calculates them
On the build path
- — Classification is never done: new SKUs ship unclassified unless the product workflow enforces HS codes, and as seller of record the margin surprises are yours
- — Lane coverage is the ceiling: unsupported destinations and missing guaranteed totals quietly cost orders until someone measures the loss
- — DDU lanes push duties to the doorstep, and parcel refusals plus return shipping can eat the margin the avoided fees saved (community-reported pattern)
- — ~15–20% of build cost per year in upkeep (Deploi estimate) as tariffs, thresholds, and the catalog move
What Merchants Say
The HS-code misclassification saga is the category's defining thread: goods misclassified at onboarding, wrong duties charged for months, and a community thread running two years on getting classifications corrected.
The seller-of-record complaint shape: landed cost quoted correctly, then registrations, remittance, and carrier disputes consuming finance hours nobody budgeted when the software was signed.
If You Change Your Mind Later
If you bought and outgrow it
Leaving Zonos is an integration swap: registrations, carrier accounts, and customer records already sit in your name, so a replacement vendor or a merchant-of-record program slots in within weeks (Deploi estimate, illustrative on timing). Leaving Global-e is heavier: a negotiated exit through notice periods, then invoices, registrations, and remittance re-homing to your entity over 4–8 weeks (Deploi estimate, illustrative). Negotiate data-return terms at signing, not at departure.
If you built and want out
Little is stranded on the native lane: HS codes on your own products are the portable asset and move to Zonos, to Global-e, or to any future stack without rework. The realistic exit is an upgrade, not a rescue; you add a vendor on top of classification work that keeps paying either way.
When This Answer Changes
We're watching for:
- ▸ International share crossing roughly 10–15% of sales: re-run the crossover math each quarter, because percentage economics move faster than feature lists
- ▸ Managed Markets fee framing moving off the 6.5% + 2.5% structure (per July 2026 research; re-verify): it reprices the mid-market on-ramp to Global-e's infrastructure
- ▸ Native Markets absorbing more duties capability or classification tooling; each release shrinks what both vendors add
Verdict change log:
No changes since first publication (August 2026).
Common Questions
What is the difference between Zonos and Global-e?
Seller of record is the difference. Zonos sells landed-cost software: duty and tax quoting, prepaid-duty options, and compliance data while your company keeps selling the order. Global-e becomes merchant of record: its entity sells the order, carries duties and compliance, and prices as a negotiated share of revenue. Mid-market stores meet the same Global-e infrastructure as Shopify Managed Markets, framed at 6.5% payments plus 2.5% currency (per July 2026 research).
When does Zonos beat a Global-e style contract?
Zonos wins once international passes roughly 10% of sales and you want your own entity selling: software plus per-order pricing grows slowly while a revenue-share contract grows with every order. Zonos also wins wholesale: B2B buyers need your name on invoices and their tax IDs handled directly. Global-e takes the matchup back at enterprise scale, roughly 25%+ international or multi-channel programs, where negotiated terms and logistics services earn the contract weight.
Can native Shopify duties collection replace both vendors?
Yes, on supported lanes. Shopify Markets estimates and collects duties in native checkout while you stay merchant of record, included with your plan where supported. The homework is classification: HS codes governed on your own products via the Admin API. Coverage is the ceiling; when guaranteed totals or unsupported lanes start costing orders, the Zonos path is the upgrade, and the parent duties page prices the full decision.
Your Next Steps
If you're going with BUY
- Audit HS codes and product data before any integration; classification quality drives quote quality on both vendors
- Model all three lanes on 12 months of real international volume: Zonos software, revenue-share terms, and the native lane
- Scope registrations and remittance obligations per target market before committing to stay seller of record
- Negotiate data-return and exit terms at signing, especially on a merchant-of-record contract
- Set a quarterly fee-versus-ops review so the lane choice stays evidence-based
If you're going with CUSTOMIZE
- Classify the catalog first: HS codes assigned at the product level via the Admin API and metafields, auditable and yours
- Turn on native duties collection for supported markets and confirm plan fees and lane coverage
- Write the per-market DDP/DDU policy with refusal math attached, and say it plainly at checkout
- Baseline orders lost to unsupported lanes monthly; that number is your future Zonos business case
- Assign a named owner for classification reviews whenever the catalog or a tariff schedule moves
Official Docs & Sources
- Duties and import taxes — Shopify Help Center
- Managed Markets — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Duties & Import Taxes on Shopify?
Duties and import taxes are a true DEPENDS: pay the merchant-of-record fee while lean, own the flow as international scales, never build the landed-cost engine.
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Should You Build or Buy Translation on Shopify?
Translation on Shopify is a CUSTOMIZE call: free native Translate & Adapt as the floor, an owned AI pipeline on the translation APIs past three locales.
Should You Build or Buy Cross-Border Compliance for Shopify?
Cross-border compliance is bought expertise: GPSR-class rules need specialist review per market, while your store publishes the documentation it produces.
Should You Build or Buy Product Reviews on Shopify?
Buying a reviews app beats building one for most Shopify merchants under roughly $15M in revenue.
Ready to pick your cross-border lane?
We'll model Zonos-style software, a merchant-of-record contract, and the native lane on your real international mix, then wire HS-code governance whichever way you go. The percentage math decides; we just do the arithmetic honestly.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing is pending verification and gets re-verified before publish. The parent duties-and-import-taxes page settles buy-vs-build for the capability; this page decides the named head-to-head plus the native lane it hides. This page is general information, not customs, tax, or legal advice. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.