Medusa.js & Mercur Development
Custom shops on Medusa v2 and multi-vendor marketplaces with Mercur — from the architecture decision through data migration to day-to-day operations. I run my own marketplace with 10,000 products and 50 vendors on exactly this stack, so you are not hiring an agency that knows the framework from the docs; you are hiring the developer who has already paid for the production pitfalls: worker mode, WooCommerce migration, commission logic, payouts.
Who Medusa.js & Mercur Are Ideal For
- Companies whose checkout or commission logic is the actual product and does not fit any SaaS builder
- Founders and teams building a multi-vendor marketplace without platform fees on growing revenue
- Shops outgrowing WooCommerce or another legacy system and needing an architecture that will carry them
How a Medusa Project Works
Scope & Architecture
Week 1Clarify requirements and business model: shop or marketplace, commission model, integrations. Decide Medusa alone or Medusa plus Mercur — including an honest SaaS counter-calculation.
Setup & Foundation
Week 2–3Backend in server and worker mode, PostgreSQL, Redis, S3-compatible image storage, Next.js storefront — deployed to Railway or your infrastructure, production-shaped from day one.
Development
from Week 3Custom commerce logic: modules, workflows, checkout; for marketplaces, vendor onboarding, order splitting, and payouts. Iterative, with regular demos.
Migration & Data
project-dependentMove catalog, customers, and images out of the old system (e.g. WooCommerce): remodeling, batched imports, and a parallel run with test orders before switching traffic.
Launch & Operations
final weekGo-live with health checks and monitoring, documentation in the repository, structured handover — with ongoing support if you want it.
Frequently Asked Questions
Planning a shop or marketplace?
Book a free call and we will figure out whether Medusa fits your case — or whether I should honestly point you to SaaS.