Skip to content
Engineering deep-divesAll articles

Medusa vs Shopify Plus vs Vendure in 2026: Commerce & TCO

Engineering and 36-month TCO teardown of Medusa vs Shopify Plus vs Vendure in 2026: Medusa v2 Workflows SDK vs NestJS GraphQL vs Shopify Plus variable GMV and third-party gateway fees, B2B pricing, and owned commerce math.

Oleksandr Saiko
Oleksandr SaikoCEO · Idealogic
Author: Oleksandr SaikoPublished: Updated: Reading time: 20 minHow we write →
On this page
Medusa vs Shopify Plus vs Vendure: Idealogic 2026 engineering comparison covering workflows saga rollback, GraphQL vs REST APIs, B2B pricing, gateway fees, and 36-month commerce TCO

If you've outgrown retail templates, the Medusa vs Shopify question usually arrives together with wholesale pricing. Once turnover crosses eight figures, finance wants the Medusa vs Shopify Plus fee math, backend leads compare Medusa vs Vendure on TypeScript ergonomics, and NestJS teams look at Vendure vs Medusa on APIs and licensing.

Our guides on ecommerce app development cost, order management systems, and inventory management software cost size end-to-end builds. This one compares the commerce engine itself, one headless commerce platform against another. Take $25,000,000 in annual GMV ($15M multi-currency D2C plus $10M wholesale B2B across four regions) on Shopify Plus with external Adyen routing. In our model that costs about $10,500 a month in variable platform fees, gateway fees, and apps before any storefront work starts. Some of the fee rates behind that number are assumptions, and we mark them where they appear.

At Idealogic, our custom software development, JavaScript development, SaaS development, and progressive web app development teams build Shopify Plus headless storefronts, Medusa v2 stacks, and Vendure marketplaces across logistics and supply chain and manufacturing. You get three things here: how the engines differ, how an owned PostgreSQL 17 stack isolates B2B prices and holds inventory with Saga compensation, and a 36-month TCO model at $25M annual GMV.

The short version

Pick Shopify Plus for standard D2C under about $5M a year on Shopify Payments. Pick Medusa v2 when B2B price lists, external payment processors, and ERP sagas matter more than launch speed.

  • Shopify Plus is the fastest to launch and has Shop Pay. Shopify Plus pricing starts at $2,300/mo on a 3-year term or $2,500/mo on a 1-year term. Higher-volume merchants move to a variable platform fee (we model 0.40% of D2C and 0.18% of B2B GMV), and card volume outside Shopify Payments carries a 0.20% third-party gateway fee. Checkout logic runs inside Wasm Shopify Functions.
  • Medusa v2 gives you MIT code and no GMV fee. Medusa v2 keeps its modules isolated, joins them through declarative Module Links, and rolls back ERP, WMS, and PSP steps with the Medusa Workflows SDK.
  • Vendure v3 suits NestJS teams, with a licensing catch. Vendure v3 brings NestJS decorators, Channels, and GraphQL APIs. Its core has been GPLv3 since v3.0, and the Vendure Commercial License comes bundled with the paid plans.
  • At $25M/yr GMV ($15M D2C + $10M B2B), owned Medusa v2 on PG17 comes to $154,800 over 36 months in our model, against $214,200 for Medusa Cloud Enterprise and $448,200 for Shopify Plus with apps. That's 65.5% ($293,400) less than Shopify Plus, with payback in 3.93 months. The Vendure Enterprise figure ($213,900) rests on a license assumption below Vendure's list price, which the TCO section explains.

Medusa vs Shopify Plus vs Vendure v3 (plus Saleor): 2026 commerce internals

Medusa is an MIT-licensed Node.js and TypeScript commerce framework built from isolated modules. Shopify Plus is Shopify's hosted enterprise plan, priced with a base fee that becomes a variable platform fee at higher volume. Comparing medusa vs shopify plus or medusa vs vendure comes down to four things: platform fee math, checkout sandboxes, cross-module database coupling, and open-source licensing.

The four differences between Shopify Plus, Medusa v2, Vendure v3, and owned PostgreSQL 17 commerce stacks in 2026

Shopify Plus pricing in 2026: base fee, variable fee, 0.20% gateway fee

Start with what Shopify publishes. Plus costs $2,300/mo on a 3-year term or $2,500/mo on a 1-year term, and merchants who route cards through Adyen, Stripe direct, or Braintree instead of Shopify Payments pay a 0.20% third-party transaction fee (Shopify Plus pricing). Shopify also says higher-volume merchants move to a variable platform fee based on revenue and business model, with D2C and B2B treated separately (Shopify Help Center).

What Shopify doesn't publish is the rate. Our model assumes 0.40% of D2C GMV and 0.18% of B2B GMV, billed as max(base_fee, variable_fee), which on the 1-year price puts the crossover near $625k/mo of D2C volume. Treat those percentages as a modelling assumption and check them against your own Shopify quote. We also budget $800 to $2,500/mo for ERP, B2B, and search apps, a typical app stack assumption and not a list price.

One fairness note: the 0.20% fee goes away when Shopify Payments is your primary gateway. Option A in the TCO model uses external Adyen on purpose, because the scenario assumes multi-currency acquiring outside Shopify Payments.

Shopify Plus headless: Storefront API, Hydrogen/Oxygen and Shopify Functions

Shopify Plus leads on launch speed when your catalog, tax, and payment flows fit its guardrails. Storefronts run on Hydrogen and Oxygen or on Next.js at Vercel through the Shopify Storefront GraphQL API, while ERP syncs share Admin GraphQL cost quotas.

Checkout tables stay closed. Custom pricing and routing run inside WebAssembly Shopify Functions, capped at 11 million instructions for carts of up to 200 line items, with no direct I/O from Wasm. Network access exists only as the fetch target for custom apps on Plus stores, where responses are cached for up to 300 seconds and the timeout runs from 100 to 2,000 ms. Separately, Shopify caps a product at 2,048 variants. In practice you end up with metafield workarounds for live SAP credit checks or LTL freight rules.

Medusa v2 (Medusa.js, MIT): isolated domain modules, Module Links and Workflows SDK

Medusa v2, still widely called Medusa.js, replaced the coupled v1 entities with isolated TypeScript modules:

  1. Declarative Module Links, no cross-module foreign keys. Each module (Product, Pricing, Cart, Promotion, Inventory, Stock Location, Order, Customer, Fulfillment, Payment, Tax) owns a private schema. Medusa Module Links join domain records and external ERP records declaratively, without SQL coupling.
  2. Saga rollbacks through the Workflows SDK. The Medusa Workflows SDK composes createWorkflow graphs from createStep(invokeFn, compensateFn) primitives. If ERP sync fails at step 4, Medusa runs the compensation functions for steps 3, 2, and 1 in reverse order. These are compensating actions, not a database rollback, and they're how Medusa handles transaction management across systems.
  3. Self-host under MIT or pay for Medusa Cloud. Core Medusa v2 is MIT-licensed and charges no GMV fee. You can self-host on AWS ECS or subscribe to Medusa Cloud at $29 (Develop), $99 (Launch), or $299 (Scale) per the Medusa Cloud pricing docs. Enterprise adds RBAC, SAML SSO, 99.99% SLAs, and BYOC, and its price is negotiated.

Vendure v3 (NestJS + GraphQL) & Saleor (Python + GraphQL)

  • Vendure v3 (NestJS + GraphQL): Vendure is built on NestJS decorators, dependency injection, and TypeORM, with separate Shop and Admin GraphQL APIs, graphql-codegen, and a React and TanStack dashboard (the older Angular Admin UI still exists in 3.x). Channels partition multi-brand catalogs and link to a Seller entity. Full marketplace logic such as payouts needs a plugin.
  • GPLv3 or a commercial license. With v3.0 in July 2024, Vendure moved its core from MIT to GNU GPLv3, plus a Plugin Exception (an additional permission) that lets plugins carry other licenses. GPLv3, unlike AGPL, has no network-use clause, so hosting a web store over HTTPS isn't "distribution" (GNU GPL FAQ). Agencies and ISVs that distribute modified core code, and enterprises whose legal teams bar GPLv3 dependencies during M&A, need the Vendure Commercial License, which Vendure bundles into its paid plans. None of this is legal advice, so ask your counsel. Medusa v2 stays MIT.
  • Saleor (BSD-3-Clause) fits Python teams and extends through GraphQL App webhooks. Next.js and TypeScript teams can share frontend and backend types on Medusa v2 or Vendure v3 instead.
DimensionShopify Plus HeadlessMedusa v2 (OSS / Cloud)Vendure v3 (OSS / Ent.)Saleor 3.x
Runtime & APISaaS + GraphQLNode.js / TS + RESTNestJS / TS + GraphQLPython + GraphQL
Core licenseProprietary SaaSPermissive MITGPLv3 or CommercialBSD-3-Clause
Platform GMV feeVariable fee (modelled 0.40% D2C / 0.18% B2B)0.00% GMV fee0.00% GMV fee0.00% OSS
External PSP fee+0.20% fee0.00% (Adyen/Stripe/ACH)0.00% (any PSP)0.00% (any PSP)
Checkout logicWasm Functions capsWorkflows SDK + SagaNestJS StateMachineGraphQL Webhooks
Multi-vendorPaid 3rd-party appMarketplace Module LinksChannels + Seller entity (plugin)Multi-channel Apps
Checkout DBClosed; API-throttled100% Owned PG17100% Owned PG17100% Owned PG

Owned Medusa v2 on PostgreSQL 17: B2B price isolation and oversell-safe inventory holds

Moving to Medusa v2 on PostgreSQL 17 (and cutting vendor lock-in across your API integration seams) lets the database itself handle three concurrency failures that Shopify Plus keeps behind its API. Everything below uses PostgreSQL 17 syntax and runs unchanged on 18.

  1. B2B price leaks. Contract price tiers are stored per buyer account, and the engine has to enforce tenant boundaries. Filtering in application queries alone isn't enough.
  2. Oversells. If Node.js checks on-hand minus reserved stock in memory before payment authorization, two simultaneous checkouts can sell the same units.
  3. Multi-SKU deadlocks. When one cart locks SKU A then SKU B in a warehouse while another cart locks them in reverse, PostgreSQL aborts one of them with error 40P01.

Here is how we split the work between PostgreSQL and the Medusa workflow:

Design decisionEnforced inWhat it prevents
Contract price tiers, stock levels, and holds sit behind PostgreSQL Row-Level Security with FORCE enabled, a restrictive plus permissive policy pair keyed on the session tenant, and an app role that can't bypass RLSDatabaseA forgotten tenant filter in app code exposing another buyer's prices or stock
A CHECK constraint keeps reserved quantity at zero or above and never above on-hand quantityDatabaseOversells, even when an application check is wrong
Cart lines are merged, sorted by warehouse and then SKU, and locked with SELECT FOR UPDATE inside one transactionMedusa stepLock-order deadlocks (we still retry on 40P01)
A partial unique index on checkout idempotency key, warehouse, and SKU covers active holds, so a retried checkout gets its existing hold backDatabaseDouble reservations when the storefront or PSP webhook retries
Holds expire after 15 minutes by default, and a cleanup worker releases stale onesDatabase plus workerStock stuck in abandoned carts
The compensation function releases holds when payment capture or ERP sync fails, and it only flips rows still marked as heldMedusa Workflows SDKReserved quantity decremented twice by retries or a concurrent cleanup run

Card tokenization stays with the Stripe Payment Element or Adyen Web Drop-in. That can keep you in PCI DSS v4.0.1 SAQ A scope, provided you can confirm the revised SAQ A eligibility criterion that your site isn't susceptible to script attacks.

The part Shopify Functions can't express is the paired invoke and compensate step. In practice the reservation step is one Medusa step with two halves. The invoke half merges and sorts the cart lines in a fixed lock order (warehouse, then SKU), locks the stock rows inside a tenant-scoped transaction, and inserts holds that reuse any existing ones for the same idempotency key. The compensate half runs when a later step such as capture or ERP sync fails, and it releases only the rows still in held status.

Paying $9k+/mo in Shopify Plus platform fees, gateway fees, and brittle ERP apps?
Share your annual D2C and B2B GMV split, payment processor mix, and warehouse architecture. Our commerce engineers will model a Medusa v2 migration with no GMV fee.
Benchmark your headless commerce TCO

Medusa vs Shopify Plus 36-month TCO at $25M annual GMV

Model a hybrid brand over 36 months: $25,000,000/year GMV ($75M over the period), split into $15,000,000/year ($1,250,000/mo) of D2C multi-currency card checkout through Adyen and $10,000,000/year (about $833.3k/mo) of B2B wholesale orders paid by net-30 ACH or wire, synced with NetSuite or SAP across 3 warehouses and 18,000 SKUs. Adyen and ACH interchange is identical in every option, so we leave it out.

Engineering labor uses Idealogic's $75/hr senior CEE billing rate against a $165/hr US agency rate (2.2x). The US figure is our market assumption, not a published statistic. Neither is a labour cost: for context, the EU whole-economy average hourly labour cost was EUR 34.9 in 2025 (Eurostat lc_lci_lev).

Three inputs are modelling assumptions and not list prices: the Shopify variable fee rates in Option A, the $3,100/mo Medusa Cloud Enterprise price in Option B, and the $2,000/mo Vendure license in Option C. Check them before you reuse these numbers.

  1. Option A: Shopify Plus headless + external Adyen gateway + B2B apps
    • Initial build (360 hrs @ $75/hr CEE = $27,000; vs $165/hr US = $59,400): Next.js storefront UI, Shopify Functions Wasm rules, B2B catalog sync, and NetSuite middleware.
    • 36-month fees & apps ($10,500/mo x 36 = $378,000): A modelled variable platform fee of $6,500/mo (0.40% of $1.25M/mo D2C = $5,000, plus 0.18% of $10M/yr B2B = $1,500; this exceeds the $2,500 base, so the base no longer applies), the 0.20% gateway fee on $1.25M/mo of Adyen D2C volume ($2,500/mo), and ERP, search, and tax apps plus edge hosting ($1,500/mo). Add 16 hrs/mo (576 hrs) of ops ($43,200 CEE / $95,040 US) and the modelled Shopify Plus cost at $25M GMV is $448,200 ($532,440 US).
  2. Option B: Medusa Cloud Enterprise + managed add-ons (no GMV fee)
    • Initial build (600 hrs @ $75/hr CEE = $45,000; vs $165/hr US = $99,000): Medusa v2 B2B modules, Workflows ERP/Adyen sagas, and Next.js storefront.
    • 36-month cloud & search ($3,800/mo x 36 = $136,800): Medusa Cloud Enterprise with RBAC, SAML SSO, and a 99.99% SLA at an assumed contract price of $3,100/mo (Enterprise is custom-quoted), plus managed search and CDN ($700/mo) and 12 hrs/mo (432 hrs) of ops ($32,400 CEE / $71,280 US) = $214,200 ($307,080 US).
  3. Option C: Vendure Enterprise (commercial license + self-hosted multi-AZ cloud, no GMV fee)
    • Initial build (680 hrs @ $75/hr CEE = $51,000; vs $165/hr US = $112,200): NestJS B2B channel plugins, GraphQL Next.js UI, Adyen PSP, and ERP sync.
    • 36-month license & cloud ($3,400/mo x 36 = $122,400): An assumed $2,000/mo for the Vendure Commercial License, plus multi-AZ EKS, RDS, Redis, and search ($1,400/mo) and 15 hrs/mo (540 hrs) of ops ($40,500 CEE / $89,100 US) = $213,900 ($323,700 US).
    • This option is understated. Vendure doesn't sell a standalone license. The commercial license comes with its paid plans, listed on the Vendure pricing page at EUR 199/mo (Starter), EUR 599/mo (Growth), EUR 2,499/mo (Scale), and from EUR 60,000/yr (Enterprise). At the Enterprise list price, about EUR 5,000/mo, the license line alone is roughly EUR 180,000 over 36 months, which would put Option C well above Option B. We assume self-hosting on the license. Get a quote before you compare.
  4. Option D: Owned Medusa v2 MIT + PG17 FORCE RLS multi-warehouse stack
    • Turnkey build (840 hrs @ $75/hr CEE = $63,000; vs $165/hr US = $138,600): Medusa v2 MIT, PG17 FORCE RLS B2B tiers and deadlock-resistant holds, Adyen/Stripe SAQ A + ACH net-30, Typesense, SAML RBAC, and a Next.js App Router UI.
    • 36-month Graviton infra ($1,350/mo x 36 = $48,600): Multi-AZ Graviton ECS, RDS PostgreSQL 17, Valkey, Typesense, and CloudFront, with no license and no GMV fee, plus 16 hrs/mo (576 hrs) of ops ($43,200 CEE / $95,040 US) = $154,800 ($282,240 US).
Worked 36-month commerce TCO ($k) at $25M/yr GMV ($15M D2C + $10M B2B), modelled: owned Medusa v2 MIT comes in $59.4k under Medusa Cloud Enterprise and $293.4k (65.5%) under Shopify Plus. The Vendure bar uses an assumed $2,000/mo license, below Vendure's list price
36-month line item ($25M/yr D2C + B2B GMV)Option A: Shopify Plus + AppsOption B: Medusa Cloud Ent.Option C: Vendure Enterprise (assumed license)Option D: Owned Medusa v2 MITPrimary economic driver
1. Initial build & ERP (@ $75/hr CEE)$27,000 (360h; $59.4k US)$45,000 (600h; $99.0k US)$51,000 (680h; $112.2k US)$63,000 (840h; $138.6k US)Option D builds custom B2B, WMS & IaC
2. 36-mo fees, licenses & cloud$378,000 ($10,500/mo, modelled)$136,800 ($3,800/mo, assumed)$122,400 ($3,400/mo, assumed)$48,600 ($1,350/mo)No modelled 0.40%/0.18% GMV fee or 0.20% PSP fee
3. 36-mo commerce & SRE ops (@ $75/hr)$43,200 (16h/mo; 576h)$32,400 (12h/mo; 432h)$40,500 (15h/mo; 540h)$43,200 (16h/mo; 576h)Medusa Cloud trims managed SRE patching
Total 36-Month Commerce TCO$448,200$214,200$213,900$154,800 (CapEx incl.)Saves 65.5% ($293.4k) vs Shopify Plus
Year-2+ Annual Run-Rate$140,400/yr$56,400/yr$54,300/yr$30,600/yrSaves $109,800/yr ongoing vs Shopify Plus
Code & Checkout DB OwnershipClosed SaaS + WasmMIT code + Managed CloudVCL + Owned PG17100% MIT + Owned PG17No GMV fee as volume passes $100M+

Sensitivity check: D2C brands under $5M vs 3.93-month B2B payback

  • Pure D2C under $5M/yr on Shopify Payments: Launch on Shopify or Shopify Plus ($2,300/mo 3-year base, no gateway fee) for the Shop Pay conversion lift. Honestly, an owned stack is hard to justify at this size.
  • Hybrid B2B/D2C ($15M to $50M+/yr GMV): At $25M/yr, Option D's $36,000 of extra CapEx ($63,000 vs $27,000) divided by $9,150/mo of OpEx savings ($11,700/mo vs $2,550/mo) pays back in 3.93 months in our model (8.37 months against Medusa Cloud Enterprise). At $165/hr US rates ($282,240 vs $532,440), owning Medusa v2 saves $250,200, with an 8.66-month payback.

2026 headless commerce platform build costs (senior CEE vs US)

Our JavaScript development, progressive web app development, and custom software development teams build these stacks at $75/hr senior CEE rates. The $165/hr US agency column is our market assumption, there for comparison:

Engagement tierTimelineHoursSenior CEE ($75/hr)US Agency ($165/hr)Scope & deliverables
Shopify Plus Headless (360h)4 to 6 wks280 to 400h$21,000 to $30,000 ($27k)$46,200 to $66,000 ($59.4k)Next.js / Hydrogen UI, Functions & ERP sync
Medusa v2 / Vendure D2C7 to 10 wks480 to 680h$36,000 to $51,000$79,200 to $112,200Multi-currency D2C, Stripe/Adyen SAQ A & search
Owned Medusa v2 B2B (840h)11 to 14 wks760 to 960h$57,000 to $72,000 ($63k)$125,400 to $158,400 ($138.6k)PG17 FORCE RLS B2B tiers, multi-WMS Saga & ERP
Multi-Vendor Marketplace15 to 20 wks1,120 to 1,520h$84,000 to $114,000$184,800 to $250,800Split cart routing, seller onboarding & payouts
Dedicated Commerce PodOngoing240h/mo (2)From $18,000/moFrom $39,600/moSenior Next.js + Medusa/Vendure + PG17 engineers

Inside the worked 840-hour ($63,000 CEE vs $138,600 US) owned Medusa v2 B2B build

Worked model, assumptions in text: 840-hour ($63,000 at $75/hr CEE vs $138,600 at $165/hr US) owned Medusa v2 MIT B2B pricing, multi-warehouse Saga & Next.js build
  • 1. Medusa v2 B2B modules (25% / 210 hrs / $15,750 CEE vs $34,650 US): Company hierarchies, approvals, pallet tiers, quote-to-cart flows, and Vite Admin extensions.
  • 2. Next.js storefront & B2B portal (25% / 210 hrs / $15,750 CEE vs $34,650 US): Multi-locale RSC catalog, CSV/SKU quick-order pad, Typesense search with a sub-50ms target, and regional stock badges.
  • 3. Workflows SDK ERP & multi-WMS (20% / 168 hrs / $12,600 CEE vs $27,720 US): Saga rollbacks across NetSuite/SAP invoices, 3PL split shipments, and dead-letter queues.
  • 4. Adyen, Stripe & ACH SAQ A (15% / 126 hrs / $9,450 CEE vs $20,790 US): Tokenized PCI DSS v4.0.1 SAQ A cards, SEPA/ACH net-30 limits, and idempotent webhooks.
  • 5. PG17 FORCE RLS & k6 load QA (15% / 126 hrs / $9,450 CEE vs $20,790 US): Graviton ECS + RDS PG17 Terraform, SAML RBAC, Shopify migration, and FOR UPDATE load tests against a 500 orders/sec target.

Shopify Plus excels when you sell standard retail SKUs through Shopify Payments. Once you add B2B price books, external Adyen multi-currency acquiring, or multi-warehouse ERP split shipments, you can end up paying six figures a year in platform and gateway fees while still working around WebAssembly checkout limits. Owning Medusa v2 on PostgreSQL 17 makes commerce a fixed cost you control.

Oleksandr Saiko · CEO & Co-Founder at Idealogic

Shipped Idealogic proof & 5-step CTO decision checklist

Idealogic ships B2B marketplaces, escrow settlement, and unified inventory-order platforms in production:

Five questions decide Medusa vs Shopify for most teams in 2026:

  1. Standard D2C under $5M/yr on Shopify Payments? Stay on Shopify or Shopify Plus.
  2. Want no GMV fee on MIT TypeScript with a 99.99% SLA? Pick Medusa Cloud Enterprise.
  3. Standardized on NestJS, GraphQL & multi-vendor Sellers? Pick Vendure v3, and budget for a paid plan with the Commercial License if legal restricts GPLv3.
  4. Python/Django org wanting GraphQL webhooks? Evaluate Saleor.
  5. Scaling $15M to $100M+ B2B/D2C GMV with ERP sagas & external PSPs? Deploy owned Medusa v2 MIT + PG17 FORCE RLS ($1,350/mo infra, 3.93-month payback in our model). Contact our team for a 48-hour TCO audit.
Evaluating Medusa v2 vs Vendure vs Shopify Plus for your 2026 commerce roadmap?
Send your GMV mix, SKU/variant structure, ERP integration list, and payment gateway setup. Our senior CEE architects will return a migration blueprint and fixed-milestone quote within 48 hours.
Get a 48-hour commerce architecture quote

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Oleksandr Saiko
Oleksandr SaikoCEO · Idealogic Development OÜ

CEO and Co-founder at Idealogic. Leading software strategy, systems architecture, and AI-native engineering squads since 2016.

Frequently asked questions

  • Choose Shopify Plus if you run standard direct-to-consumer retail, take most card payments through Shopify Payments, and care more about managed hosting and Shop Pay conversion than about owning the checkout database. Choose Medusa v2 if your roadmap needs B2B contract price lists, multi-warehouse split fulfillment, Adyen or ACH routing without Shopify's third-party gateway fee, ERP workflow sagas, and no GMV platform fee.

  • Shopify Plus pricing starts at $2,300 per month on a three-year contract or $2,500 per month on a one-year contract. Shopify says higher-volume merchants move to a variable platform fee based on revenue and business model, with D2C and B2B treated separately, but it doesn't publish the rates. Our model assumes 0.40 percent of D2C volume plus 0.18 percent of B2B volume, so confirm the numbers against your own Shopify quote. Separately, routing D2C card checkouts through an external processor like Adyen or Stripe instead of Shopify Payments adds a published 0.20 percent third-party transaction fee.

  • Medusa v1 used tightly coupled TypeORM entities. Medusa v2 replaced them with isolated domain modules for Cart, Product, Pricing, Inventory, Promotion, and Order, whose data models run on MikroORM and never join tables across module boundaries directly. Cross-domain relationships resolve through declarative Module Links, and multi-system state changes run through the Medusa Workflows SDK, which executes steps in order and runs Saga compensation functions when a later step fails.

  • Both Medusa v2 and Vendure v3 target TypeScript commerce teams and neither charges a GMV fee. They differ on API style and license. Medusa v2 exposes REST Store and Admin APIs backed by modular services and stays under the permissive MIT license. Vendure v3 builds on NestJS decorators, dependency injection, and GraphQL code generation, and since v3.0 in July 2024 its core is dual licensed: GPLv3, or the Vendure Commercial License that comes with its paid plans.

  • Not by itself. GPLv3, unlike AGPL, has no network-use clause, so running an online store over a network doesn't trigger source distribution, and Vendure's Plugin Exception lets teams keep their plugins under another license. You need the Vendure Commercial License if you distribute modified Vendure core code to clients, embed Vendure in a commercial SaaS product, or work under a corporate policy that bars GPLv3 dependencies. Vendure bundles that license into its paid plans. This isn't legal advice, so check with your counsel.

  • Shopify Plus keeps its checkout database closed and limits custom cart, discount, and routing logic to WebAssembly Shopify Functions. Those functions must finish within an instruction budget and payload size limits, and they can't do direct I/O from Wasm. Complex B2B workflows such as live uncached ERP credit-limit checks, pallet-weight freight bidding, split-shipment tax exemptions, and configurators that exceed Shopify's 2,048 variants per product limit need external workarounds or a composable engine like Medusa v2.

  • A naive checkout reads available stock in application memory and decrements inventory after payment authorization, so concurrent requests can oversell the last units. A production Medusa v2 and PostgreSQL 17 pipeline does four things instead: a CHECK constraint keeps on-hand stock greater than or equal to reserved quantity, cart SKUs are sorted in a fixed order to avoid lock-order deadlocks, SELECT FOR UPDATE takes row locks inside a transaction, and Saga compensation releases the holds if capture fails.

  • With Idealogic's senior Central and Eastern European TypeScript and PostgreSQL engineers at $75 per hour (versus an assumed $165 per hour at US agencies), an 840-hour turnkey Medusa v2 B2B, Next.js App Router, Adyen SAQ A, and multi-warehouse ERP build costs $63,000 ($138,600 at US rates). At $25 million annual GMV, removing the Shopify Plus variable platform and gateway fees pays back the extra build cost in under four months in our model.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.

Related expertise