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.
SubscriptionsPlans & OffersRenewalsDunningCancellation & RetentionActivity LogAnalytics
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.
- 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
Reorder is meant to be installed into an existing Medusa project.
With npm:
npm install @reorderjs/reorderWith yarn:
yarn add @reorderjs/reorderplugins: [
// other plugins
{
resolve: "@reorderjs/reorder",
options: {},
},
]After adding the plugin, run your normal Medusa setup flow in your store project.
If you want to work on the plugin itself locally:
git clone https://github.com/reorder-js/reorder.git
cd reorderyarn installyarn medusa plugin:publishyarn medusa plugin:add reorderplugins: [
// other plugins
{
resolve: "reorder",
options: {},
},
]yarn installyarn dev
- Minimum: Medusa
2.3+ - Recommended: compatible with
@medusajs/medusa >= 2.4.0
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
Project documentation lives in docs/.
Useful starting points:
docs/README.mddocs/architecture/docs/api/docs/admin/docs/testing/docs/roadmap/implementation-plan.md
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