All services

Services / What we ship

02 · Owned commerce · Composable stack

Medusa JS

Headless commerce with the operating model of an in-house team.

Medusa gives you a composable, owned storefront — you keep control of payments, fulfillment, promotions, and the data. We architect the storefront, integrate the stack (Klaviyo, Algolia, your ERP), ship to production.

Typical scope · 4–12 weeks · replatform

Symptoms we recognise

You should talk to us if…

  • You're paying more in Shopify apps than in licenses.
  • Checkout abandons disproportionately at the address step.
  • Replatforming has stalled because nobody wants to own the data model.
  • You need to ship features faster than the platform's roadmap allows.

What ships

/ 04 deliverables

Concrete deliverables, not vague promises.

Owned storefront

A Next.js storefront in your repository.

Server-rendered product, cart, checkout. SEO and performance you can tune line-by-line. No theme update lottery.

Composable commerce

Modules picked for your operations.

Promotions, inventory, fulfillment, multi-warehouse — each module configured to your reality, not a SaaS template.

App sprawl retired

Fewer apps, more code you control.

Klaviyo, Algolia, Stripe, your ERP — integrated in TypeScript. No Zapier middle layer, no per-app monthly drip.

Migration without drama

A launch day with zero data loss.

Catalog, customers, orders, subscriptions — moved with auditable scripts. Launch on a working URL, never at midnight.

How this engagement runs

Four phases. No bench.

  1. 01

    Weeks 1–2 · Audit & spike

    Read the current store. Ship the hardest piece.

    We instrument the existing Shopify, identify the friction, and ship a working spike of the trickiest unknown — often checkout, pricing, or subscriptions.

  2. 02

    Weeks 3–8 · Storefront sprint

    Build the new storefront, weekly demos.

    Next.js storefront against a Medusa instance. Each Monday: a fresh staging URL with the previous week's work running end-to-end.

  3. 03

    Integrations · Parallel

    Klaviyo, search, ERP, OMS.

    Each integration written in TypeScript with its own tests. We pair with your ops team on what triggers what, before code lands.

  4. 04

    Launch day · Retire

    DNS flip on a quiet weekday.

    Old platform stays read-only for 30 days. You retire the apps you no longer need on day 31. We stay close for the first stable sprint.

Stack we ship against

  • Next.js storefront · Medusa modules
  • Postgres · Redis · Meilisearch or Algolia
  • Klaviyo · Stripe · ERP connectors as needed

We pass when

You need Shopify's checkout rails with no appetite for owning the codebase, or you're not ready to retire app sprawl.

Field questions

Honest answers.

  • How long does a typical replatform take?

    4–12 weeks depending on catalog size and integration count. We give you a fixed-fee range after the audit — not before.

  • Can we keep some Shopify functionality?

    Yes — many clients keep Shopify as a fulfillment backend for the first quarter while the new storefront stabilises. We can wire that up.

  • What happens to subscriptions and recurring orders?

    Migrated via Stripe API plus Medusa's subscription module. Existing subscribers are charged on the same cadence without re-authorisation.

  • Who owns the Medusa instance?

    You do. The repository, the database, the Docker image — all yours from day one. We don't host or resell. Ever.

From the principal engineer

Composable commerce is not a new platform tax. It's the absence of one. The repository is yours; the apps are yours; the customer data is yours.

Related work

Discovery

Pick a door. Or describe what's broken.

We pitch the problem, not the platform.

Start a conversationOr emailkresimir.galic@fronttribe.com

Reply within one business day · No discovery deck tax