The problem
Zoho Inventory's bundle feature works when a kit is one level deep, assembled on the spot, and costed as the sum of its parts. Real manufacturing is not that. A finished good is made from sub-assemblies that are themselves made from components. Production takes labour hours on specific work centres. Scrap happens. Substitutions happen. The cost you quoted from a standard BOM is rarely the cost you actually incurred, and until you can see that variance you are guessing at your gross margin.
Small manufacturers running Zoho hit this wall and face an unattractive choice: leave the suite for a dedicated manufacturing system and lose the integration with Zoho CRM, Books and Inventory, or keep the whole production process in spreadsheets that nobody reconciles. The result is stock that is wrong the moment production starts, WIP that is invisible to finance, and a cost of goods figure in Zoho Books that was typed in rather than derived.
This is a build-to-order engagement. There is no ready-made download. ECOSIRE scopes your specific manufacturing model, quotes a fixed price, and builds the suite into your own Zoho org over a typical two to four week lead time.
What ECOSIRE builds
Multi-level bills of material
We build a BOM application in Zoho Creator with parent and child relationships to any depth, so a finished good can explode through sub-assemblies to raw materials. Each BOM line carries quantity per, unit of measure, scrap or yield percentage, and whether the component is backflushed or issued explicitly. BOMs are versioned with effective-from and effective-to dates, so a change to a formulation does not rewrite the cost history of goods already produced. Alternate and substitute components are held against the line, with the substitution rule and any cost impact recorded.
Items come from your existing Zoho Inventory item master through the REST API — we do not create a parallel product catalogue. Where you sell configurable goods, the BOM can be resolved from options captured on a Zoho CRM Deal or Sales Order.
Routings and work centres
A routing defines the sequence of operations required to produce an item: operation number, description, work centre, setup time, run time per unit, and the labour or machine rate that applies. Work centres are held as their own records with capacity, calendar and overhead rate. Routings and BOMs are linked so a work order created for a parent item knows both what it consumes and what it takes to make.
Work orders as first-class records
We implement the work order lifecycle in Deluge: draft, released, in progress, completed, closed and cancelled. Releasing a work order checks component availability against Zoho Inventory, reserves or issues material depending on your policy, and creates the operation lines from the routing. Shop-floor users record material issues, scrap, completions and operation time against the work order. Completing it posts the finished quantity into Zoho Inventory as a stock receipt and relieves the consumed components, so on-hand quantities reflect reality rather than a nightly correction.
Where you also run batch or serial control, the work order records which component lots were consumed and stamps the resulting output lot, so genealogy survives production.
Actual versus standard cost roll-up
This is the part most small manufacturers are missing. We calculate a standard cost by rolling the BOM and routing up through every level — material at your chosen valuation basis, labour at the work centre rate, overhead at the absorption rule you define. As the work order runs we accumulate actual costs: material actually issued at actual value, actual operation time at rate, scrap and rework. On completion the suite produces a variance breakdown by material, labour and overhead, at the work order and at the item level.
Financial postings go into Zoho Books through the REST API against the accounts you nominate — a WIP account on issue, cost of production on completion, and variance accounts as configured — so your books reflect production without journal entries typed by hand.
Visibility where people already work
Work order status, WIP value and open demand are surfaced through Zoho Creator reports and a Sigma widget embedded in Zoho Inventory or Zoho CRM, so a salesperson can see whether a promised item is in production and a finance user can see WIP without asking the plant.
Who this is for
Job shops and make-to-order manufacturers who quote from a BOM and need to know whether the quote held; process and formulation businesses with yield and scrap that a simple bundle cannot express; assemblers with two or more BOM levels; contract manufacturers who must report cost per customer order. If your production is currently a spreadsheet sitting alongside Zoho Inventory, this replaces it inside the suite.
How delivery works
1. Scoping call. We map your actual production model — how deep your BOMs go, whether you backflush or issue, how you treat scrap, how labour is captured, what your accountant expects to see in Zoho Books, and how work orders are triggered from sales demand.
2. Fixed quote. You get a written scope covering the BOM structure, routing model, work order lifecycle, costing method and Zoho Books posting design, at a fixed price. The listed figure is a starting point; the quote follows the agreed scope.
3. Build. Development happens in a sandbox: Creator applications, Deluge business logic, Zoho Flow orchestration, REST API integration with Zoho Inventory and Zoho Books, and any Sigma widgets. Typical lead time is two to four weeks depending on BOM depth, costing complexity and access to test data.
4. Install in test, then production. We install into your test org, load a representative BOM set and run real scenarios: release a work order, issue material, book scrap, complete it, and reconcile the resulting stock movement and Zoho Books postings against what your accountant expects. Only after sign-off do we promote to production, with an agreed approach for opening WIP.
5. Support. Delivery includes configuration handover, training for planners, shop-floor users and finance, and a defined support window for defect fixes and configuration adjustments. New BOM structures, additional costing rules or further integrations are quoted separately.
Everything built stays in your Zoho org — the Creator apps, the Deluge functions, the flows, the documentation — and continues to run whether or not you engage ECOSIRE again.