Running Medusa?

Medusa commerce engine misbehaving? We ship it properly.

Medusa is the open source commerce engine that replaces Shopify when a store needs behaviours no SaaS platform will bend for. That flexibility comes with a backend to run, a schema to migrate, and workflows to debug. We stand it up, keep it up, and migrate stores onto it from Shopify or WooCommerce without losing orders or SEO.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

medusa.log

still broken

What it is

Medusa at a glance

Medusa is an open source headless commerce engine written in TypeScript and Node, first released in 2021 by a Danish team formerly building Shopify stores. Medusa 2.0, released in 2024, introduced a module based architecture and formal workflows, which is a serious reshape of how customisation lives in the codebase.

The platform separates products, inventory, orders, pricing, payments and shipping into modules that can be swapped or extended. It exposes a storefront API and an admin API, with an optional admin UI, and runs against Postgres and Redis. Payments go through adapters for Stripe, PayPal and others. Medusa Cloud offers managed hosting of the backend. Stores typically pick Medusa when they want behaviours Shopify will not allow, multi region pricing that is not convenient in Shopify, or a code first commerce stack their engineers can own.

Type
Open source headless commerce engine
First released
2021, 1.0 in January 2022, 2.0 in September 2024
License
MIT, open source
Maintained by
Medusa, Inc., plus contributors
Typically used for
Headless storefronts, multi region commerce, custom B2B flows, commerce teams that outgrew SaaS platforms

The honest version

Medusa pros and cons

No technology is all upside. This is where Medusa earns its place and where it tends to cause trouble.

Where Medusa is strong

  • You own the code and dataProducts, orders and customers live in your database on your infrastructure. No vendor lock in on the commerce layer, which matters when a Shopify policy change would otherwise force a rewrite.
  • Module architecture is honestPayment, fulfilment, pricing and tax live as modules that can be replaced. Swapping Stripe for Adyen is a module change, not a fork of the codebase.
  • Workflows are reusableMedusa 2 workflows compose into named, testable units with retries and compensation, which is a meaningful improvement over plain controllers for order flows.
  • Multi region pricing is built inRegions, tax rules, price lists and shipping options are first class concepts, which saves teams from the duct tape most SaaS stores need for multi currency behaviour.
  • Good TypeScript ergonomicsTypes flow through the API, the modules and the admin, so refactors catch mistakes at compile time rather than at the checkout.
  • Reasonable managed hosting optionMedusa Cloud removes the backend ops for teams who want the flexibility without the pager, with an exit path that is standard Node and Postgres.

Where Medusa bites

  • You run a backendPostgres, Redis, workers and a web server are all in your life. This is not Shopify. The flexibility Medusa gives you is paid for in operational time.
  • The migration from Medusa 1 to 2 is a real projectThe module architecture and workflow system in version 2 are a different shape than services in version 1. Migrations are documented but take meaningful engineering time for a store of any size.
  • Ecosystem is smaller than ShopifyApps, themes and plugins are nowhere near Shopify or WooCommerce in count. Common features sometimes need building, which is the trade off for being code first.
  • Admin UI is an engineer's adminIt works, but it is designed for technical teams. Merchandisers coming from Shopify or BigCommerce will need either training or a tailored admin extension to feel at home.
  • Hiring is specialisedDevelopers who know Medusa, commerce domain modelling and Node operations together are rarer than Shopify developers, which makes the hiring pool smaller and more expensive.
  • Payment and tax still need thoughtStripe, PayPal, Avalara and TaxJar adapters exist, but the integration decisions and the reconciliation workflows are yours to design, which is more work than ticking a box in Shopify.

Sound familiar?

Common Medusa problems we fix

The Medusa problems that bring people to us, and what you have once each one is fixed.

Migration failed

Database migration blocks the release

A schema change that depends on a seed order that was never run, or a migration that worked on an empty dev database and times out on production because a table is much larger than expected.

Migrations safe to run on live data

RedisError: Connection to Redis closed unexpectedly

Redis dropouts stall workflows

A managed Redis with a tight connection limit and a Node app that opens a new connection per request, exhausting the pool at peak and taking workflows down with it.

Redis sized and connected properly

Cart could not be found

Carts going missing between pages

Cart cookies not persisted across domains, a session middleware missing a key, or a storefront talking to one region while the cart lives in another.

Checkout state reliable end to end

Invalid webhook signature

Payment webhooks failing after a redeploy

A Stripe webhook secret rotated in the dashboard but not in the production environment, or a proxy that is mangling the body before signature verification runs.

Webhooks accepted and verified

Shipping option not found for region

Checkout breaks in one region

A region without shipping options configured, or a fulfilment provider that was never registered against the region, leaving carts unable to reach shipping selection.

Shipping complete for every region

shopify migration, 12k products

Migration from Shopify to Medusa

A Shopify store ready to move, with products, variants, customers and orders to carry across, and URLs that cannot change without hurting SEO and existing marketing campaigns.

Live on Medusa, URLs and data intact

medusa 1.20, upgrade blocked

Stuck on Medusa 1

A store on Medusa 1 wanting the workflow and module story of version 2, with custom services written against the old plugin API that cannot be lifted one to one.

On Medusa 2 with custom work migrated

inventory_level missing

Inventory and orders drift

An inventory module that is not being updated by the fulfilment workflow, producing oversells on fast moving products and a reconciliation job every morning.

Inventory accurate in real time

What we do

Medusa help, from rescue to migration

Fix one broken checkout, or let us take the whole Medusa stack on.

Rescue
A store refusing checkouts, a worker stuck in a loop, or a migration that will not apply. We get orders flowing first and work backward to the root cause.
Shopify or WooCommerce migration
A measured move onto Medusa, with products, orders, customers and SEO preserved, and a rollback path kept in place until the new stack has run clean.
Medusa 1 to 2 upgrade
The module and workflow migration planned and executed, with custom services lifted across and a staging environment that proves it before the live cut.
Custom modules and workflows
B2B flows, subscription billing, custom pricing rules or integrations with your ERP or OMS, written as proper Medusa modules rather than one off hacks.
Admin extensions
Tailoring the Medusa admin to how your merchandisers actually work, so content and commerce teams can do their jobs without reading developer documentation.
Managed Tech
Hosting, backups, dependency updates, workflow monitoring and an engineer on call who knows your modules when something goes sideways at midnight.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Medusa alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Medusa questions

Something else? Call+1 737 727 7327

Should we move from Shopify to Medusa?

The answer depends on what Shopify is costing you in flexibility. If you are fighting the platform every quarter for B2B flows, multi region pricing, custom checkout rules or features no app can cover, Medusa buys you the freedom and is worth the ops overhead. If you are a small store with standard needs and a modest catalogue, Shopify is probably still cheaper and simpler. We will say so plainly for your case.

How hard is the Medusa 1 to 2 upgrade?

Harder than a regular upgrade and much easier than a full rewrite. Entities map over cleanly, services need to become workflows and modules, and anything that touched events or subscribers needs the new patterns. For a mid sized store we usually scope a few weeks of focused work with a staging cutover before touching production.

Can you run the Medusa backend for us?

Yes, as a managed service. We host the Node processes, the Postgres and the Redis, apply upgrades, run backups and restores, and watch the workflows for anomalies. You keep the code and the data; we take the pager. Medusa Cloud is also an option if you prefer the vendor to run it, and we will set either one up.

How do we add custom pricing or B2B flows to Medusa?

By writing Medusa modules and workflows rather than forking the core. Pricing modules can apply customer group rules, contract prices or quantity breaks, and workflows orchestrate the quote, approval and purchase order steps. The code lives alongside the rest of your Medusa project and upgrades with it, rather than drifting away from the mainline.

Why is our Medusa checkout failing in one region?

The common causes are a missing shipping option for the region, a payment provider that was not registered against the region currencies, and a tax module that was configured for one country and silently returns nothing for the others. Each one shows up as a slightly different error in the logs, and the fix is usually a short configuration change once the specific gap is identified.

How much does Medusa help cost?

Free written estimates. Share the store size, the host and what is giving trouble, and we return a price before any engineering begins.

Free estimate

Medusa giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.