Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency and market pricing on Shopify is native by default: keep Shopify Markets and customize with per-market price lists, and treat Managed Markets' 6.5% + 2.5% fee stack (per July 2026 research) as a margin decision, not a requirement. Markets already ships auto-converted prices, local payment methods and duties collection on every plan. Currency-switcher apps are legacy. Build the custom pricing layer only when regional pricing strategy actually drives margin.
Your profile — see how the verdict shifts
- Confidence
- High — Markets is the platform default; the open questions are fee math and pricing sophistication, not feature gaps
- Reference scenario
- $20M–$100M GMV · 10–30% international · agency dev bench
- As of
- August 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| International under 10% of revenue | WAIT | Markets defaults (auto-converted prices, local payment methods, duties at checkout) cover a testing phase. There's nothing to buy and nothing worth building yet. |
| 10–25% international, lean ops team | DEPENDS | Managed Markets buys merchant-of-record compliance in days at 6.5% + 2.5% (per July 2026 research). Run that against owning the ops — the answer flips on margin and category. |
| 25%+ international or strategic regional pricing | CUSTOMIZE | Per-market price lists earn real money here: psychological endings, premium positioning and margin floors beat blanket FX conversion, and the fee stack starts losing to owned ops. |
| $100M+ GMV or local entities abroad | CUSTOMIZE | A percentage-of-revenue fee stack at this scale is a seven-figure line item. With entities and an ops team, owned price architecture keeps the margin and the customer record. |
What Multi-currency & market pricing Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Revenue — direct | High | Local currency plus local payment methods removes the two highest-friction moments in cross-border checkout, which is where international conversion is won or lost. |
| Customer experience | High | Duties and taxes collected upfront kill the surprise courier bill at delivery — the classic cross-border trust breaker behind refusals and chargebacks. |
| Operational efficiency | Medium | Market settings and price lists replace per-country spreadsheets and manual repricing, so finance stops re-deriving international prices every FX swing. |
| Data & insight | Medium | Owning the pricing layer keeps per-market price tests and full order records in your stack; a merchant of record intermediates part of that record. |
| Retention & LTV | Low | Stable, sensible local prices help repeat purchase at the margin, but retention is mostly won elsewhere — honest scoping keeps this row modest. |
Spend ceiling: Size the spend to your international share. Under 10% of revenue, Markets defaults are the whole answer; a managed fee stack or a pricing build only earns its cost once international volume is real. The ceiling question never changes: what would 9% of international GMV buy elsewhere?
What buying enables (top apps)
- + Merchant-of-record status: duties, local taxes and compliance handled — selling into new markets in days without hiring for international ops
- + Duties and taxes guaranteed at checkout, with the provider absorbing classification and remittance work
- + Local payment methods, currencies and cross-border logistics for markets you'd never reach solo
- + One contract replacing a patchwork of tax registrations and shipping decisions
What building additionally unlocks
- + True price architecture per market: psychological endings, premium positioning, margin floors from landed cost — not blanket FX conversion
- + Price lists synced from your ERP or margin model via the Admin API, updated on your rules instead of the FX tape
- + The full international order and customer record stays first-party — no merchant-of-record intermediation of your best growth data
- + Flat-cost scaling: the pricing layer costs the same at 10x volume while a percentage stack grows with every order
Find Your Verdict in 3 Questions
Is international more than about 10% of revenue — or strategically targeted to be?
Yes: Go to question 2.
No: Your verdict: WAIT — turn on Markets defaults (auto-converted prices, local payment methods, duties at checkout) and revisit when international demand shows up in the data.
Do you need duties, local tax and compliance handled for you — no ops capacity, no local entities?
Yes: Your verdict: BUY — Managed Markets as merchant of record; accept the 6.5% + 2.5% stack (per July 2026 research) as the price of speed and re-run the margin math yearly.
No: Go to question 3.
Does regional pricing strategy matter — psychological endings, premium positioning, margin floors by market?
Yes: Your verdict: CUSTOMIZE — Markets native plus automated per-market price lists; you keep the margin and the customer data.
No: Your verdict: WAIT — native Markets with percentage adjustments covers you; diary a re-check when the next market launches.
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 | Managed Markets switches on in days with no upfront fee; the customize build is an estimated 4–8 weeks of pricing architecture and automation (Deploi estimate, illustrative). | ||
| Recurring fees | The managed stack takes 6.5% of order value plus 2.5% currency conversion on every international order, forever (per July 2026 research); the build adds no percentage line beyond native conversion fees. | ||
| Maintenance & upgrades | The merchant of record maintains tax, duties and compliance behind its fee; the price-list build needs quarterly FX-drift reviews and API version bumps (~15–20% of build cost per year, Deploi estimate). | ||
| Switching & exit | Leaving a merchant of record means standing up payments, tax registrations and duties handling you never built; catalogs and price lists are Shopify-native objects any future stack inherits. | ||
| Risk | |||
| Vendor risk | Managed Markets puts a second commercial party (Global-e) inside your checkout; the community-reported HS-code misclassification saga shows the failure mode. The build rides platform primitives only. | ||
| Security & compliance surface | Compliance is the product: the merchant of record owns duties, local tax and consumer-law exposure. Going it alone means owning registrations and classification market by market. | ||
| Platform-deprecation exposure | Markets, catalogs and price lists are first-class platform primitives on both paths; the watch item is API versions cycling roughly every six months. | ||
| Value | |||
| Fit to requirement | Blanket FX conversion can't hold psychological price points or premium positioning by market; per-market price lists set the exact number shoppers see. | ||
| Time to market | Merchant of record has you selling cross-border in days; the build takes weeks plus pricing decisions you may not have made yet. | ||
| Performance & scale | Both paths render native storefront and checkout; at scale the difference is economic — a percentage fee grows with every order while the build cost stays flat. | ||
| Data ownership & AI-readiness | As merchant of record, the provider sits between you and the international buyer record; owned price lists and direct orders keep pricing experiments and customer data fully yours. | ||
| Focus & opportunity cost | Handing duties, tax and cross-border logistics to a merchant of record frees a lean team; the build spends dev weeks on pricing infrastructure only sophisticated operators exploit. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Markets (native) | Native — Included on all plans. The platform default for international selling; currency-conversion fees apply on converted orders | Included with your plan; conversion fees on converted orders (per July 2026 research) | The baseline everyone starts from: multi-currency presentment, local payment methods, duties collection |
| 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) | Cross-border compliance — duties, local tax, HS codes — without building an international ops function |
| Global-e (direct) | Live — The enterprise merchant of record behind Managed Markets, contracted directly | Custom percentage-of-sales contract | Enterprise cross-border programs negotiating rates, markets and logistics terms directly |
| Currency-converter apps (category) | Legacy — Legacy — sunset candidates Markets made switcher and geolocation apps redundant for core conversion; many installs linger from the pre-Markets era | Monthly subscriptions, varies | Nothing on core conversion — audit installed switchers as cleanup, not as options |
The Build Path
- Markets architecture + catalogs (the core): Define markets, currencies and payment methods natively; attach per-market catalogs with price lists for fixed local prices, rounding rules and market-specific availability.
- Price-list automation via GraphQL Admin API: Sync price lists from your ERP or margin model: landed-cost floors, FX-drift bounds and psychological endings applied by rule. Batch throttle-aware — THROTTLED errors arrive inside 200 responses.
- Optional: localization glue: Translate & Adapt for language (translations stored portably in Shopify), market-aware content via metafields, and hreflang discipline so each market's pages rank at home.
- Effort band
- $15,000–$45,000 for Markets architecture plus price-list automation — Deploi estimate (illustrative); spans the $10–25K and $25–75K contact-form bands
- Typical timeline
- 4–8 weeks for pricing architecture and automation (Deploi estimate, illustrative); Markets defaults go live in an afternoon
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): quarterly per-market price reviews against FX drift, API version bumps on the roughly six-month cycle, and onboarding each new market. There is no percentage-of-sales line item.
- What you own — and what you take on
- You own: the exact price in every market, the rounding and positioning rules, the margin model, and the complete international order and customer record. You take on: FX-drift monitoring, duties-classification homework, and the upkeep above.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0 upfront — fees start with the first order | $15,000–$45,000 (architecture + automation) |
| Years 1–3 (recurring) | ≈$540,000 in fees at the 9% all-in stack on $2M/yr international GMV | ≈$7,000–$27,000 maintenance (15–20% of build per year) |
| 3-year total | ≈$540,000 — and it scales with international volume | ≈$22,000–$72,000 — flat regardless of volume |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column = Managed Markets at the 6.5% + 2.5% framing (per July 2026 research) on a sample $2M/yr international GMV; standard payment processing and native conversion fees excluded from both columns.
- † Build column = Markets-native rails plus the price-list automation build; the managed fee buys real compliance and logistics value these cost rows don't price.
What the Sticker Price Hides
On the buy path
- — The 6.5% + 2.5% stack (per July 2026 research) is a percentage of revenue — it grows with every good quarter and never amortizes
- — HS-code misclassification is the community-reported saga: wrong duties at checkout become customer-service fires and margin surprises
- — Merchant-of-record intermediation: the provider is seller of record on international orders — confirm what customer and pricing data you keep, at signup
- — Exit means standing up tax registrations, duties handling and local payments you never built
On the build path
- — Per-market price lists need a named owner — stale FX assumptions quietly erode margin until someone reviews them quarterly
- — GraphQL price-list syncs hit the cost-based leaky bucket, and THROTTLED errors arrive inside 200 responses — a documented dev trap
- — Duties collection is native but classification quality stays your homework
- — ~15–20% of build cost per year in upkeep (Deploi estimate) as markets and catalogs multiply
What Merchants Say
The HS-code misclassification saga is the recurring Managed Markets pain theme — misclassified goods, wrong duties quoted at checkout, and weeks of support back-and-forth to unwind them.
Currency-switcher apps draw the 'why am I still paying for this?' complaint shape — merchants discover Markets already converts prices and the app is a billing leftover.
If You Change Your Mind Later
If you bought and outgrow it
Leaving a merchant of record is a real project: you re-onboard international payments, tax registrations and duties handling yourself, and how much international customer history you get back depends on the contract. Negotiate data-return and exit terms at signup, and keep your price architecture documented outside the provider.
If you built and want out
Almost nothing is stranded: markets, catalogs and price lists are Shopify-native objects any future stack inherits — including a merchant of record, if you later retreat to one. Your pricing rules and per-market data stay portable; the sync automation is the only piece you'd retire.
When This Answer Changes
We're watching for:
- ▸ Managed Markets fee or market-coverage changes — the 6.5% + 2.5% framing is July 2026 research; re-verify before any margin model
- ▸ Native Markets absorbing more managed features (duties refinements, seller-of-record options) — the frontier keeps moving toward native
- ▸ Your international share crossing roughly 20–25% of revenue — the zone where a percentage fee stack usually starts losing to owned ops (Deploi estimate)
Verdict change log:
No changes since first publication (August 2026).
Common Questions
Do I need a currency-converter app on Shopify?
No — currency-switcher apps are legacy. Shopify Markets handles multi-currency presentment, local payment methods and duties collection natively on every plan, and it's the default for new stores. If a switcher app is still installed, treat it as cleanup: it duplicates native behavior, adds script weight to the storefront, and keeps billing monthly for something the platform now includes.
What does Shopify Managed Markets cost?
Managed Markets runs 6.5% of order value plus 2.5% currency conversion, per July 2026 research — re-verify before you model. In exchange it acts as merchant of record: duties, local taxes, compliance and much of the cross-border logistics decisioning are handled for you. That's why this is a margin decision — cheap insurance while international volume is small, an expensive percentage of revenue once it isn't.
Can I set different prices per country on Shopify?
Yes — per-market price lists set fixed prices by market instead of letting FX conversion pick the number: round to psychological endings, hold premium positioning where the brand is strong, protect margin where duties bite. Markets ships percentage adjustments natively; the customize step is automating true price lists from your margin model through the Admin API — an estimated 4–8 week build (Deploi estimate, illustrative).
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Map your market list: currencies, payment methods, duties exposure, and what FX conversion currently does to your price endings
- Define the price architecture per market: rounding rules, positioning tier, margin floor from landed cost
- Build price-list automation against the GraphQL Admin API with throttle-aware batching
- Assign a named owner and a quarterly FX-drift review
- Instrument per-market conversion and margin before and after — the delta is the ROI number
If you're going with BUY
- Run the margin math first: apply 6.5% + 2.5% (per July 2026 research — re-verify) to projected international GMV and compare against owning the ops
- Audit HS-code classification quality on your catalog before launch — misclassification is the community-reported saga
- Negotiate data-return and exit terms at signup, not at exit
- Diary an annual re-decision tied to international share — the fee stack loses to owned ops as you grow
Official Docs & Sources
- Multi-currency (sell and accept payments in multiple currencies with Shopify Pay — Shopify Help Center
- Markets — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
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 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 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 Geo-Redirects & Market Routing on Shopify?
Building geo-redirects wins for mid-market Shopify stores: Markets does the heavy lifting, so the routing layer is a small one-time build you own.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Ready to own your international pricing?
Markets gives every store the rails. The margin lives in the pricing layer on top — we architect per-market price lists and the automation that keeps them honest.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. 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.