A supplier emails on a Tuesday to say three of your lines are going up by eight per cent. You open ERPNext, update the prices, and get on with your day. Then on Thursday a customer orders one of them at the old price, because nobody remembered that the online store keeps its own copy of everything and that copy is still showing last month’s numbers.
Nothing went wrong, exactly. You updated the system of record, which is what you are supposed to do. The problem is that the storefront is a second system of record, and keeping two of anything in agreement is a job that never finishes. It is also the kind of job that looks small until you count it: every price change, every stock movement, every new product, every photo, entered once properly and then once again somewhere else.
OrderWeave is the bridge between the two. You work in ERPNext, and your store follows. Change a price and the storefront changes. Receive stock and the quantity moves. Add a photo, discontinue a line, put something on sale, and the shop reflects it within seconds, without anyone opening a second admin panel to do it again.
That last part matters more than it sounds. A sale price has to do more than match. It has to appear with the old price struck through, on the right product, at the right moment, and disappear again when the promotion ends. Doing that by hand across a few hundred products is how promotions quietly run a week longer than they were meant to.
Orders come back the other way
The catalogue goes out to the store. Orders come back. When someone buys from your WooCommerce shop, OrderWeave creates the Sales Order in ERPNext, matched to the right customer, and keeps it in step when that order is amended or cancelled. You quote, invoice and pick from the system where the rest of your business already lives, instead of copying order details across so your accounts eventually balance.
Shopify is the exception for now. It keeps your catalogue up to date today, and orders stay in Shopify until we finish the other half. We would rather say that here than let you discover it in your second week.
It will not surprise you
The fastest way for an integration like this to lose your trust is to do something clever that you did not ask for, so it mostly does not. Products OrderWeave creates arrive as drafts, because nobody has looked at them yet and a tick box in your ERP is not a good reason for something to appear in front of customers. You review them and publish them when you are ready.
The same restraint runs the other way. If you unpublish a product in your store, it stays unpublished, and its price and stock keep updating quietly underneath. We never take a visibility decision back off you.
Existing products are the other thing people worry about, reasonably. If your store already has a catalogue, OrderWeave looks for each product before it creates anything, matching first on SKU and then on the product’s web address. When it finds one it takes that product over rather than making a second copy, so you keep the page, the URL that customers have bookmarked, and the reviews underneath it.
Getting started
Connect a store from Settings, decide which products should go to it, and watch the first one arrive. It takes about ten minutes, and most of that is your store’s own permission screen.
WooCommerce, Shopify and MedusaJS are all supported, and a single ERPNext item can feed all three at once. Selling somewhere new should mean a new shopfront, not a second catalogue to maintain.
See pricing or talk to us about yours.
