Skip to main content
Vortex IQ is building Medusa coverage so technical teams running headless storefronts can see the same Nerve Centre signals their Shopify and BigCommerce peers already get.

​
What is Medusa?

Medusa is an open-source headless commerce engine written in Node.js and TypeScript. It ships as a modular backend: orders, products, customers, carts, regions, fulfilment, and payment providers each live in plug-in modules that teams can swap, replace, or extend. There is no bundled storefront. Teams build their own front end (Next.js, Remix, mobile, kiosk) and talk to Medusa over its REST and GraphQL APIs. Medusa is most often picked by engineering-led brands and agencies who want full control of the commerce data model and rejected the constraints of hosted SaaS platforms. The hosted Medusa Cloud offering exists for teams who want managed infrastructure but still want the source code in their own repo.

​
Why Vortex IQ tracks Medusa

Headless setups are the hardest commerce stacks to monitor. Data lives across the Medusa backend, the storefront framework, the payment provider, the search service, and the CDN. Brand teams running on Medusa often have strong engineering, but limited time to wire dashboards, alerts, and revenue at risk views. Vortex IQ Nerve Centre treats Medusa like any other commerce source: pull orders, products, customers, refunds, and stock data through the Admin API, normalise it into the same KPI model used for Shopify, BigCommerce, and Adobe Commerce, then surface the cards, alerts, and Ask Viq narratives the rest of the platform already supports. That means a Medusa team gets revenue trend, refund rate, OOS spike alerts, and cross-channel revenue at risk on the same screen as their ad spend, email, and CrUX data.

​
What you can monitor (when KPI cards launch)

Planned coverage mirrors the executive-grade pulse set already running for Shopify and BigCommerce, scoped to fields the Medusa Admin API exposes:
  • Total revenue, order count, average order value, and trend over 7, 30, and 90 day windows.
  • Refund rate, refunded order count, and refund value for the same windows, with alerting on rate spikes.
  • Out of stock and low stock product counts using Medusa’s inventory module.
  • New vs returning customers and repeat purchase rate using the customer module.
  • Catalogue health: products missing description, image, SKU, or price.
  • Region and currency revenue breakdowns, since Medusa’s region model makes multi-currency a first class concept.
  • Fulfilment status mix and unfulfilled order count, sourced from Medusa’s fulfilment provider data.
Cross-channel cards (revenue at risk on out of stock SKUs, marketplace listing drift, pagespeed-driven cart loss) work the same way they do for Shopify once a Medusa store is connected alongside Google Ads, Amazon, or a website performance source.

​
Detailed KPI cards in active development

The Medusa adapter is on the build queue. Each KPI gets its own card with a definition, the exact Admin API fields used to compute it, why it matters, and the playbook to run when the value moves outside its sentiment band. Cards launch in the same hero / non-hero / cross-channel structure used elsewhere in the Nerve Centre, so a team migrating from Shopify or starting from a fresh Medusa install does not need to learn a second mental model. Until cards ship, Medusa appears in the source picker as planned. Teams who want to be in the early access cohort can register interest and connect a sandbox Medusa instance for schema validation.

​
CTA

Want Medusa coverage live for your store? Tell us which Medusa version, hosting setup (self-hosted or Medusa Cloud), and storefront framework you run, and we will line your store up for the early access build. Talk to the Vortex IQ team or open a connector request from the in-app source picker.