Reorder

Website | Documentation

What is Reorder?

Reorder is an open source Medusa subscription plugin.

It adds recurring commerce capabilities to a Medusa store, including subscriptions, plans and offers, renewals, dunning, cancellation and retention flows, activity logs, and analytics.

Reorder is built as a Medusa plugin with Medusa modules, workflow-backed mutations, Admin API routes, scheduled jobs, and Admin UI extensions.

What it includes

• Subscriptions
• Plans & Offers
• Renewals
• Dunning
• Cancellation & Retention
• Activity Log
• Analytics

Current scope

Reorder currently focuses on recurring commerce operations managed from the Medusa Admin.

Today, the plugin provides strong Admin coverage across the implemented domains. Customer self-service flows will be introduced in the near future as a Reorder Subscription Starter.

Feature highlights

• Subscription lifecycle management
• Configurable plans and offers
• Renewal orchestration
• Dunning retries and recovery tooling
• Cancellation flows with retention offers
• Operational activity logs
• Subscription analytics and reporting

Installation

Reorder is meant to be installed into an existing Medusa project.

1. Install the plugin

With npm:

With yarn:

2. Add the plugin to medusa-config.ts

3. Run Migrations

With npm:

npx medusa db:migrate

With yarn:

yarn medusa db:migrate

4. Start your Medusa app

After adding the plugin, run your normal Medusa setup flow in your store project.

Local development

If you want to work on the plugin itself locally:

1. Clone the repository

2. Install dependencies

3. Publish the local plugin

yarn medusa plugin:publish

4. Add the plugin in your Medusa store

5. Add the plugin configuration to medusa-config.ts

6. Install store dependencies

7. Start your Medusa store

yarn dev

Requirements

• Minimum: Medusa 2.3+
• Recommended: compatible with @medusajs/medusa >= 2.4.0

Architecture

Reorder is organized around Medusa-native building blocks:

• domain modules for subscription data and operational records
• workflows for business mutations and orchestration
• Admin API routes for plugin operations
• Admin UI extensions for management flows
• scheduled jobs for renewals, dunning, and analytics processing

Documentation

Project documentation lives in docs/.

Useful starting points:

• docs/README.md
• docs/architecture/
• docs/api/
• docs/admin/
• docs/testing/
• docs/roadmap/implementation-plan.md

Contributing

Issues and pull requests are welcome.

Before changing behavior:

• read the runtime docs in docs/
• keep implementation aligned with documented behavior
• follow Medusa best practices for modules, workflows, routes, and Admin UI extensions