Odoo case study
Six warehouses on one Odoo inventory system for a textile maker
A multi-site textile manufacturer replaced paper stock records at six locations with a single live Odoo system and ended weekly stock disputes.
Measured across all six sites in the first month
- 99.2%Stock Accuracy Across All SitesFirst month after full go-live · Delivery report
- 3xFaster Dispatch ProcessingFirst month after full go-live · Delivery report
- 15 hrsWeekly Meeting Time RecoveredFirst month after full go-live · Delivery report
- 0Stock Disputes Since Go-liveFirst month after full go-live · Delivery report
The situation
Six warehouses running on six different paper records with no way to see the whole picture.
This textile manufacturer operated six warehouses spread across two regions.Each location kept its own handwritten stock ledger, updated by warehouse staff at the end of each shift. The records were then manually compiled into a central spreadsheet by the inventory team every Friday afternoon.
By Monday morning, the numbers were already wrong. Transfers between warehouses happened over the weekend. Stock moved for urgent orders was not always recorded. Returned goods sat uncounted for days. The Friday compilation was essentially a historical document, not a live tool.
Every week started with a dispute meeting. Warehouse managers would argue over whose numbers were right. Production planning could not start until the dispute was resolved — usually by physically counting the stock. That meeting alone cost an estimated 15 person-hours every single week.
Customer orders were increasingly affected. Promised delivery dates were based on stock figures that turned out to be wrong. Rush procurement drove up costs. The business needed a single source of truth that all six sites could update and access in real time.
Core challenges
- Paper stock records at each site created a week-long lag before central inventory was updated
- Inter-warehouse transfers were recorded inconsistently, with sending and receiving sites often showing different numbers
- Production planning was blocked every Monday waiting for the stock dispute to be resolved
- Rush procurement orders were placed unnecessarily because existing stock could not be located in time
- No visibility into which warehouse held which fabric grades, causing wrong material to be shipped to the factory floor
Odoo Modules Deployed
Real-time Visibility Across All Six Locations
- Inventory and Warehousing: All six sites on one inventory system with live stock levels by location and product variant
- Inter-Warehouse Transfers: Transfers raise and close automatically, updating both locations the moment goods move
- Manufacturing: Production orders draw from live stock, preventing over-commitment of materials
- Purchase Management: Reorder rules trigger purchase requests automatically when any site falls below minimum stock
- Reporting and Analytics: Cross-site stock reports available instantly, replacing the Friday compilation entirely
How it was delivered
All six sites live in 18 weeks.
The rollout ran site by site so that no single warehouse faced a cutover while still processing peak orders.Each team was trained on their own product range using real item codes.
Process Audit and Item Master Build (Weeks 1–4)
We documented stock flows across all six sites, unified item codes that had drifted apart between locations, and built a clean item master covering all fabric grades, variants, and packaging units.
Odoo Configuration and Opening Stock Load (Weeks 5–9)
Multi-warehouse structure, product variants, transfer routes, and reorder rules were configured. Opening stock was entered and verified against a physical count at each site before go-live.
Phased Site Rollout (Weeks 10–15)
Sites went live two at a time. Each team had two full working days of hands-on training before their cutover date. The central inventory team monitored transfers in real time across all active sites.
Full Network Live and Stabilisation (Weeks 16–18)
Final two sites came online. The Friday compilation process was retired. Central team moved from manual reconciliation to exception-based management using Odoo alerts and dashboards.
The outcome
The Monday dispute meeting does not happen anymore. We open Odoo, the numbers are there, and we start production. That is it. The whole team still finds it hard to believe it is this simple. Head of Operations, Textile Manufacturer
Related service
OdooRelated
More case studies and related work
More case studies, and the case studies hub.
- ResourceCase studiesCase studies of ERP, AI and custom software projects delivered by TCB Infotech: the problem…
- Case studySAP S/4HANA for chemicalsHow a process chemicals manufacturer managed formulas, hazardous handling and actual batch costing on SAP S/4HANA.
- Case studyAuto Parts Order CyclesAn automotive parts manufacturer connected sales…
- Case studyDairy PlantA dairy processor put milk intake, batch traceability, quality and cold-chain dispatch on one ERPNext system…
- Case studyERPNext Manufacturing Case StudyA make-to-order manufacturer cut late deliveries 44% and material waste 30% with ERPNext production planning tied…
- Case studyFood processing ERPHow a food processing company replaced batch registers with ERPNext: 38% less wastage…
- Case studyAI Finance AgentA finance AI agent reads supplier invoices, matches them to orders and prepares entries for approval…
- Case studyLead-Gen ChatbotA lead-generation chatbot qualified visitors, captured details into the CRM and booked demos after hours…
- Case studySupport ChatbotA support AI chatbot grounded in the help centre and orders now answers about 70% of routine questions instantly…
- Case studyB2B Ordering AppA self-service B2B ordering web app let trade customers of a distributor order online around the clock…
- Case studyContractor Project CostingA building contractor put BOQ, procurement, billing and cost on one ERPNext system across eight projects…
- Case studyInfrastructure ProjectsAn infrastructure EPC firm ran packages, subcontractors and multi-stage billing on SAP S/4HANA…