Case study · Apparel manufacturing
Risitex (brand: Lamongie)
Dealers and shoppers, one catalogue. — Risitex's case study
Risitex, the clothing manufacturer behind Lamongie, sells export, bulk and retail from one Medusa catalogue synced to ERPNext. We build and run it.
From Separate dealer and retail pricingto Medusa.js 2.0 + ERPNext
- custom modules
- ~30
- channels: export, bulk, retail
- 3
Built and run, no end date.
Module count read from the codebase. Named with written consent.
What changed, area by area
Where Risitex started and what runs now, in three areas. We built it; Risitex runs it.
Pricing
BeforeDealer and retail prices in separate systems, reconciled by hand
NowOne catalogue, prices resolved per company
We built: Medusa 2.0 with about thirty custom modules: B2B pricing, matrix ordering, master‑carton packing
See it live: A dealer orders on their own (opens in a new tab)Stock at order
BeforeOrders placed against a catalogue that didn't know the warehouse position
NowWarehouse position visible at the point of order
We built: Warehouse and logistics modules
One ledger
BeforeCommerce and ERP each held part of the same order
NowCommerce and ERP run as one system
We built: ERPNext sync as a maintained plugin
Run the same process live
Step through the flow here, then run it yourself on our demo company.
The customer's confirmed order: who it's for, the items at price-list rates and when it's due. The next documents are made from it.
- Made from
- Nothing: it starts the flow
- Next
- Pick List
Mith Demo Traders · demo company
Our demo company with sample data, not Risitex's system. No sign-up, no card, no account.
Questions about this case
The one most people ask is answered first. Type to find the rest.
Why does a clothing manufacturer run its store on Medusa?
About this case
Talking to them, and the demo