Thanks again for this contribution. Do you have plans to make it compatible with Medusa V2?
Has anyone tried and installed this plugin:
Medusa have released v2 so the plugin will not work with v2 therefore it needs us a community to work on upgrading it.
I truly suggest that we keep this Medusa JS integration topic on 
Medusa is also mentioned/talked about here several times: Shopping Cart Logic - #21 by ccraig
Official V2 will be released on October 23rdâŚthough theyâve pushed back the release date a few times already.
However, the release candidate is out, so the new API should finalized. Once itâs released Iâll look into it again. Iâm still leaning towards Vendure.io, but maybe MedusaJS V2 will surprise me 
1 Like
Great! Could you please enlighten us why Vendure poses to be the better one? Have you also tried Saleor?
Thanks for mentioning the official release as I meant to specify the release candidate of V2 which has been released a few weeks ago.
TL;DR: Try both and see what feels better to work with!
Mostly anecdotal evidence as Iâm focusing on a Laravel frontend for Vendure at the moment. A programmer who I respect moved from MedusaJS 1.0 to Vendure. Vendure already has the features MedusaJS is promising and more, but are stable since theyâve been around for a while.
I need to review extensibility in MedusaJS. Itâs quite good in Vendure. Medusa does not offer a way to customize the Admin UI, while Vendure does, though it may be in V2? Still not seeing it in the docs. This would be a good time to mention that Vendure has very good documentation.
Thereâs also the GraphQL vs REST debate. Iâm not normally a fan of GQL, but it does seem like a good fit for this type of API (Shopify uses GQL) since youâre constantly pulling in various related data on single page and donât want to be running multiple requests. That said, Vendure letâs you use REST too! In fact you can do just about anything with it since itâs running on top of NestJS.
Vendure also has an active YouTube Channel where Michael Bromley, the creator of Vendure, posts fairly often and is active daily in the Vendure Discord. MedusaJSâs last video was from 2 years ago! Lots of videos doesnât guarantee a project is better, but it sure is helpful!
MedusaJS also got $9 million in funding. Where did those millions go 
Iâm gonna get an angry message from Nick Gellner of MedusaJS for this post 
That said, Iâm going to use which ever project I feel is best, so please give both a try! I know I came off a bit biased, so I wonât count MedusaJS out just yet 
Edit: Forgot about Saleor. They treat their Open Source version as a second class citizen. Only the paid accounts get âEarly patch releasesâ. I briefly stopped by their site a while ago and wasnât impressed compared to these two. Again, give it a try. Thatâs the beauty of headless since you can keep your frontend and just swap the backend with minimal fuss. Plus itâs written in Python⌠oh wait we have to like Python here 
1 Like
Thanks for the detailed comparison, @ccraig. Perhaps Medusa invested the $9m in Medusa Cloud which they just launched this week 
. Regarding Vendure, I just somehow feel that itâs a bit like WooCommerce (built on WP), when I first used Medusa 1.x I liked how slick and performant it is and I truly believe it has high potential especially the latest release with 17 composable modules. Hopefully we can get one of the opensoure commerce integrated with ERPNext but I am starting to think the other way around.
Let me explain: ERPNext is certainly a lovely product, but I somehow come to see that the POS part is lacking a lot and is not really a priority to Frappe ( at least thatâs what my impression this year is ). So I am starting to think why not build a POS from scratch built on MedusaJS and that way we can manage the inventory from Medusa and have a world class storefront with a POS for instore payments etc. Medusa is also integrated with Stripe and many other payment providers as well.
What do you guys think? Who ever is keen to take this forward DM me and letâs take this offline and perhaps work on it together.
1 Like
BTW I do echo your thought about Medusa JS and the lack of videos⌠However I think they will fairly get better with that. I follow them on X (exTwitter) in which they have been quite active in updates so I believe they will start making some videos.
First off, happy MedusaJS launch day!
A Woo comparison is a low blow haha. Iâve used Woo and itâs hacked together (though well done) on top of Wordpress a blogging program, while Vendure is built from scratch using NestJS, an actual framework for building web services. I do not know much about the custom framework MedusaJS just built, but Vendure using NestJS makes it battle tested and infinitely customizable without having to wait for MedusaJS to add functionality to theirs, while they also work on e-commerce features.
Vendure 2.2 is very fast. V1 did have significant performance issues.
Now let me praise MedusaJS.
- I like the pretty graphics in their docs (thatâs where the $9mill went
) - Version 2.0 is a a major overhaul and probably the newest headless e-commerce framework out there
- Itâs a fresh take so it should not have the technical debt other frameworks may have
- Having a custom framework designed for e-commerce can also speed up development if itâs got what you need (Granted, thatâs also what Vendure is, just they choose not to reinvent the low level stuff)
- AND no need for a GQL code generation so you can use TypeScript. That part is my biggest annoyance with Vendure.
Either way, Iâm excited to try them both now that MedusaJS is ready to play. Iâve been reading through their docs but they do things quite differently so itâs been hard to compare them. Iâm fully prepared to declare MedusaJS my lord and savior if I think itâs better
In the end itâs going to be more like a React vs Vue vs Svelte. All of them can do what you want, it just does it differently. I use SvelteKit btw 
Now changing subjects about a POS. Let me know if I misunderstood what you meant about them.
Well since itâs headless, youâre always building a POS/e-commerce site from scratch (or use their website template). If you are just looking to replace a Square, Clover, etc. type POS device, then you could absolutely do that over a weekend. I have larger inventory/warehousing/accounting needs than those things can handle, so thatâs my interest in ERPNext.
We have a fancy Square POS system we use at events and the Credit Card/Apple Pay/Google Pay/etc. device it comes with is very convenient. You could definitely use your own hardware with a custom app, but it will take more effort to get that ease of use.
When I see a comparison I meant the interface/UI and definitely from a holistic approach. We certainly cannot compare a plugin âWooCommerceâ with a platform âVendureâ.
Agreed on this part. But I believe it would be great to have a built in Medusa POS - which I am planning on working on when i sharpen my tech skills.
Svelte 
1 Like
In more update news, Vendure just announced they are getting some corporate backing from Elevantiq. The plot thickens!
1 Like
I made this so far it still needs more features/blocks. Whoeverâs interested in working on it with me shout me out / DM me.
2 Likes
Great! Now they will have $9m to spill 
Looking good! Is this designed as a Frappe app or a Medusajs module?
Iâm trying out both, to be honest.
Guys - another update.
If anyone is keen on collaborating, DM me or send me an email unifiedcommercehq@gmail.com
2 Likes
A brand new Medusa ERP integration recipe has just dropped on the Medusa documentation.
There is even an example integration, unfortunately its with Odoo. However I believe the recipe example can be reproduced with ERPNext as well. I think for starters following wire diagram is more than sufficient and Ecommerce-ERPNext marriage will be feature rich enough with it.
However personally, I really liked user signup, authentication and account management aspects of ERPNext, that wonât come with Medusa out of the box. Medusa on the other hand with its B2C examples brings a much more robust ecommerce & check out cart experience and actually functional payment integrations, in which users can checkout without login as guests. Which is natural and 90% of my online orders, however it was not possible with ERPNext webshop last time I checked.
How should a guest order on Medusa side be logged in ERPNext? One approach could be to create a customer account using the guestâs email, assign a password, but not send an email. Future guest purchases with the same email would be linked to this account. If the guest later signs up, we could implement a special rule: instead of blocking registration due to an existing email, redirect them to a page saying, âIt looks like youâve ordered with us before. Would you like to import your past orders?â
If they agree, they receive a confirmation email to reset their password. If not, we could delete the auto-created account and allow a fresh sign-up, ensuring email verification first. But this requires a lot of logic programming on ERPNext side, I am also not sure if itâs possible.
But you see, this example is one of many questions that would arise for a true integration and I dont really know how user details and past order data can be past on to Medusa from ERPNext too. Which is a challange on its own.
3 Likes