Enterprise Commerce & Marketplace · Distributed Backend & APIs

Medusa.js Plugins and Open Source

npm packages and commerce adapters for Medusa.js

Role: Author and maintainer
Client: Open source and client platforms

Decorative cover art for the Medusa.js Plugins and Open Source case study

Medusa.js plugins I have written for open source and for client platforms: the @jaykanjia/medusa-file-cloudinary storage adapter on npm, fulfilment and payment providers, Payload CMS connectors and ERP inventory synchronisation.

Wrote and published @jaykanjia/medusa-file-cloudinary, which uploads store media to Cloudinary and serves responsive variants from its CDN.
Built fulfilment providers for third-party logistics APIs: shipping labels, live rates and tracking webhooks.
Built payment providers with tokenised checkout, webhook verification and multi-currency reconciliation.
Built ERP and CRM synchronisation with idempotent batch processing and error-recovery queues.
Take part in Medusa community discussions and help other developers debug on GitHub.

Publishednpm package@jaykanjia/medusa-file-cloudinary, a Cloudinary file adapter

5Integration areasMedia storage, fulfilment, payments, CMS and ERP synchronisation

v1 + v2Medusa versionsTyped providers built on the core service contracts

Medusa.js
Node.js
TypeScript
npm
PostgreSQL
Redis
Payload CMS
Docker

Problem and objectives

Most Medusa.js stores need the same integrations sooner or later: media on a CDN, a courier, a regional payment gateway, an ERP. I package these as typed plugins that install cleanly and recover from failures on their own, so each new project starts from working parts.

Architecture

Each plugin implements the provider contract Medusa defines (file, fulfilment or payment service) and is wired in through dependency injection, for both Medusa v1 and v2. Webhook handlers verify signatures, ERP synchronisation runs through retry queues, and the Cloudinary adapter serves transformed images from the CDN.