Odoo ERP · Garments
Odoo for Garment Manufacturers: Styles, Sizes, and Job Work
· Updated · 2 min read
Garment units drown in style-colour-size combinations and in fabric that went out for stitching and never came back as a countable finished good. Odoo can hold both, if you do not model the entire catalogue on day one.
One style family first
Pick the styles you cut every week. Variants cover size and colour. A bill of materials covers the fabric and the trims the cutting room already knows. The rest of the lookbook can wait.
This is the manufacturing sequence in Odoo MRP, applied to garments rather than to a machine shop.
Job work is a route, not an adjustment
Fabric that leaves and returns as a stitched garment should be subcontracting, so the vendor and the cost stay visible. A stock adjustment hides both. See Odoo for job work.
Units must match the way you buy fabric and the way you count pieces. A conversion invented at go-live shows up as a stock gain.
Keep the first season small
A single family with job work is often a mid-size project, 2–4 months, not a 4–12 month programme. Cost follows scope, typically inside the India range of ₹2–15 lakhs. Heavy custom reports push the upper end.
Bring one style’s cutting list to a free audit, or start from Odoo for manufacturing.
Frequently Asked Questions
Do we need a SKU per size?+
Use variants so stock by size is real without copying the style once per size by hand.
Can job workers log in?+
Not in the first release. Your team records what left and what returned. A vendor portal is later.
Should we load every style ever sold?+
No. Load what you will cut in the next season. History can stay in the old sheets.