Medusa Setup: Day-Zero Path to a Working Ecommerce Loop

Set up Medusa for day-zero work — seats, one core loop, required integrations, and non-admin proof — before optional hubs.

By Lee M.Updated Aug 18, 20266 min readFact-checked

Quick answer

Set up Medusa in this order: qualify the plan you will actually buy, name one store owner, configure self-host or Cloud Develop/Launch, Stripe or a gateway, and a storefront you will ship, connect the payments and shipping you depend on, then have a non-admin run a developer can publish a SKU and a test buyer can check out without leaving your front-end. Confirm marketplace channels (Open Source (self-host)+) and b2b wholesale (Open Source (self-host)+) are on the package you will actually buy. You’re done when that walkthrough works — not when every optional app is switched on.

Start on Open Source (self-host)
Name one store / ops owner
self-host or Cloud Develop/Launch, Stripe or a gateway, and a storefront you will ship
Connect required payments / shipping / channels
Prove a non-admin can run the loop

What matters in your Medusa setup

What Medusa actually is — Medusa is a headless, JavaScript/TypeScript open-source commerce platform. MIT OSS self-host is free for production. Medusa Cloud (first-party): Develop from list price, Launch from list price (highlighted), Scale from list price, Enterprise custom — no GMV pe…
Configure these first — Research lists online storefront, product catalog, checkout payments, and order management as supported — that is your day-zero surface.
Do not treat it as every ecommerce job — Medusa is headless JS open-source commerce. It is not a substitute for a WordPress plugin cart or a Square POS bundle.
Prove with a real workflow — Worked example: Harbor Labs (JS headless storefront) is done when they can a developer can publish a SKU and a test buyer can check out without leaving your front-end — not after a vendor tour.

Medusa day-zero path

Medusa setup walkthrough for headless JS open-source commerce. — A working Medusa core loop beats a decorated empty workspace.

Medusa must vs nice

Must-have

Core job loop
Plan / hub gates
Integrations

Nice-to-have

AI extras

1. Qualify plan and packaging

Researched plans: Open Source (self-host), Cloud Develop, Cloud Launch, Cloud Scale, Cloud Enterprise. Never invent list prices here — confirm plans, processing, and quote terms on /pricing/medusa/. Worked example: Harbor Labs (JS headless storefront) lists everyone who must log in weekly before they invite “the whole company.”

2. Configure one core loop

Configure self-host or Cloud Develop/Launch, Stripe or a gateway, and a storefront you will ship. Research-supported surfaces include online storefront, product catalog, checkout payments, and order management. Worked example: Harbor Labs (JS headless storefront) refuses optional modules until a developer can publish a SKU and a test buyer can check out without leaving your front-end.

3. Non-admin proof

Our snapshot records no trial length for Medusa, so Open Source (self-host) is your proving ground. Success: a developer can publish a SKU and a test buyer can check out without leaving your front-end. Worked example: Harbor Labs (JS headless storefront) records a 10-minute loom of the walkthrough for stakeholders who skip hands-on time.

Medusa checklist

Bring these questions to every demo

Ask vendors to show the workflow live, not just describe it.

1Name a store / ops ownerCatalog, users, and hygiene need a responsible party.
2Configure one core loopself-host or Cloud Develop/Launch, Stripe or a gateway, and a storefront you will ship
3Complete non-admin proofa developer can publish a SKU and a test buyer can check out without leaving your front-end

4. Connect the integrations Medusa must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.

Research lists Stripe, PayPal, and Zapier for Medusa. Confirm which are native vs API before go-live.

Pick one identity or SSO path if required.
Connect one operational integration the weekly users touch daily.
Document anything left as manual export.

Worked example: JS teams building headless storefronts connects the one integration that prevents double entry before inviting the full team.

5. Train weekly users — not a one-time all-hands

Train the people who must open Medusa every week. Cover: login, the core loop (online storefront, product catalog, and checkout payments), and where to log blockers.

Worked example: JS teams building headless storefronts runs a 30-minute working session on live data and includes one sceptic who will actually use the tool.

6. Write the setup note stakeholders can audit

Document plan tier, admin owner, integrations live, and the non-admin proof (online storefront, product catalog, and checkout payments). Link to /pricing/medusa/ for commercial detail.

Worked example: JS teams building headless storefronts stores a one-page note finance and IT can read without joining another demo.

7. Connect the integrations Medusa must have on day one

Native connector
Prefer OAuth paths IT can audit.
API / webhook
Name an owner when the sync breaks.
Manual export
Accept only for low-volume, low-risk data.