Now that v11 is almost ready, woocommerce is now the only best alternative to the too expensive shopify.
There are few important things missing.
First one is 2 way sync. First reason is for item quantity in stock.
What I’m about to do is:
I want to be able to manage all my products directly in ERPNext and use ERPNext as a PIM (Product Information Management)
Short description, long description, item price, quantity, images, meta tags, categories, attributes and more. Everything needed in woo commerce will be in ERPNext.
Then sync everything with woo commerce automatically so I don’t have to do that again and again and everything update automatically if I change something in erpnext (qty, price, description, pictures).
I already found a company willing to work on this and I’m ready to pay for it. But I’m wondering if I’m the only one looking for that?
I don’t see any other way of having a online store with erpnext. Right now it’s really a pain to sync all order manually, inventory and prices.
I am actually also waiting for v11 and Woocommerce connector to do 2 way sync. If this could be done then it could almost being considered as a “lazy man business” as you can sync your supplier products from their side automatically update ERPNext and Woocommerce sell the goods and receive the fruit of being on auto pilot. This cycle could just repeat . . . .
Thank You for everyones contributions so far and hope all will be done soon.
@Samuel_Gervais Two way Woocommerce integration would be great if you could add it to the main ERPNext codebase when completed. Any quality 2 way integration with 3rd party apps only makes ERPNext a better product.
it is always best practice (in my eyes) to have the code open for everyone from the beginning. Especially in such a case more eyes and brains on the project will either make the result better, or get there faster (or even both).
if the code was published and the repository posted here someone like @birduser would probably just have contributed to it already. Others may involve with it with testing, etc.
So, from the perspective of code quality and speed of delivery releasing the code from the start is always the best idea.
So what you refer to then is documenting say the ‘connector’ code - in that case test side code, to validate and confirm that interfaces still work as expected, and detect what breaks with code changes, makes ideal sense to maintain healthy code.