Zoho Inventory was built for companies that buy finished goods and sell them: a distributor, an online store, a wholesaler with a warehouse. A light manufacturer does something the product was not first designed for, which is to make the thing it sells from other things it bought. Most of Zoho Inventory works exactly the same for a manufacturer as for a distributor. The difference shows up in four places, and knowing them is the difference between a setup that runs a small factory well and one that sends the operations manager back to a spreadsheet.
This is a plain explanation of those four places: how items are modelled, how an assembly is built, how stock is held across locations, and how the money reaches Zoho Books. It ends with the edge, the point at which a manufacturer needs something Zoho Inventory does not do, because knowing where that is matters more than any feature.
Everything in Zoho Inventory is an item. A manufacturer has three kinds. Purchased items are the raw materials and components bought from suppliers: sheet, fasteners, a motor, a printed box. Finished items are what customers buy. Composite items are the link between the two: a finished item defined as a list of its components and their quantities, which is Zoho Inventory's version of a bill of materials.
The composite item is the whole game for a manufacturer. Set it up per finished product with the real components and the real quantities, including the packaging and the consumables that are usually forgotten, and everything downstream, from stock valuation to what to order, follows from it. Set it up loosely and the stock counts drift from the first week.
Two practical points. Composite items carry a cost derived from their components, so the finished item's cost is real rather than typed, and the margin on a sale is a number you can trust. And a composite item can itself be a component of another, which is how a sub-assembly is modelled: the motor assembly is a composite of its parts, and the finished machine is a composite that includes the motor assembly.
When a batch is made, Zoho Inventory records it as a bundle: you tell it how many of the composite item were built, it deducts the components from stock and adds the finished items, at a cost carried over from the components. That transaction is the manufacturing event, and it does three things a spreadsheet cannot do reliably. It keeps the component stock honest, it keeps the finished stock honest, and it values the finished goods from what actually went into them.
What it does not do is plan the build. There is no work order that reserves components before the build, no routing, no labor or machine time in the cost, and no schedule. For a light manufacturer building to stock in modest batches this is usually fine: the build is recorded when it happens, and reorder points on the components tell purchasing what to buy. For a manufacturer who needs to promise a date to a customer based on component availability and capacity, it is the first edge.
Zoho Inventory holds stock per warehouse, and a manufacturer typically uses at least two: raw materials and finished goods, sometimes a third for work in progress or a consignment location at a customer. Transfers between them are recorded, and the build can pull components from one location and put finished items into another. Serial and batch tracking are available where a manufacturer needs traceability, and for anyone selling into regulated or warranty-heavy markets, switching batch tracking on from the start is much easier than retrofitting it.
The common mistake is to model the shop floor as a location. Work in progress that sits for an hour does not need a warehouse; work in progress that sits for a week and might be counted does. Keep the locations to places where stock is physically counted.
This is the part most manufacturers get right by accident and most distributors get wrong on purpose. Zoho Inventory and Zoho Books share the same organization: items, customers, vendors, sales orders, purchase orders, invoices and bills are the same records in both. There is no sync to configure, because there is nothing to sync. An invoice raised from a sales order in Inventory is the invoice in Books; a bill received against a purchase order is the bill in Books; the inventory asset and cost of goods sold move with the transactions.
The consequence for a manufacturer is that the composite item's cost, built from the components, is what reaches cost of goods sold when the finished item ships. If the composite is set up honestly, the gross margin in Books is real. If it is not, the accountant will find out at year end, which is the expensive time. We have written about the general CRM to Books flow and about Zoho for e-commerce and 3PL operations, where the same shared organization does the same work for a different kind of business.
Four places, roughly in the order a growing light manufacturer hits them.
Planning. No work orders, no material reservation ahead of a build, no capacity. The workaround is a planning sheet fed by Inventory's stock and reorder data; the real fix, when the sheet becomes a job, is a light manufacturing execution layer alongside Inventory.
Labor and overhead in the cost. The composite cost is components only. A manufacturer whose labor is a large share of cost will see margins that flatter the product. The workaround is a standard labor uplift applied in Books; the fix is job costing, which we discuss in the manufacturing accounting piece for firms whose costs live in three places.
Engineering change. A composite item is one current definition. Revisions, effective dates and which version was built for which order are not tracked. Manufacturers with real change control need it held outside Inventory and referenced from it.
Multi-level planning at volume. Sub-assemblies work; planning across many levels and many products at once does not, because there is no planning engine. This is the point at which the conversation becomes an ERP conversation, and it is worth having it deliberately rather than after the third missed delivery.
For a light manufacturer building a modest catalogue to stock, in batches, with components from a manageable set of suppliers, Zoho Inventory with honest composite items and the shared Books organization is a complete system for stock, cost and margin, at a fraction of what a manufacturing suite costs, and it is what we set up for most of the manufacturers we work with. The four edges are real and they are specific, and a manufacturer who knows where they are can run for years before reaching one. Discovery for that setup is paid for only if you proceed, and the build carries a guaranteed estimate; if we estimate low, we absorb the difference.
In a no-risk discovery we follow an order from sale to shipment to invoice across your systems and show where it breaks and what one connected system would change. You pay only if you proceed. Or see how we approach it.
More on the same problem:
Manufacturing CRM in Zoho: How to Pick a Partner Who Knows the Floor (article)
3PL Inventory Management Software: A Zoho Stack for Ecommerce Operators (article)
Each item carries a reorder level and a preferred vendor, and the system flags items that fall below the level and can raise a purchase order from the flag. For a manufacturer, set the level on components from the composite item's quantities multiplied by the expected batch and the supplier lead time, and review it quarterly. The reorder report, not the composite item, is what tells purchasing what to buy and when.
Zoho Inventory has no scrap field on the bundle transaction, so record scrap as an inventory adjustment on the component after the build, with a reason, and keep the reasons to a short list. Reviewing scrap adjustments monthly by component shows whether the composite item's quantities are realistic or whether a supplier's material is the problem. Without the adjustment, the component count drifts upward and the margin flatters the product.
Count by location on a schedule, enter the counted quantities as inventory adjustments against the system quantity, and keep the adjustment reasons separate from scrap so the two can be reported apart. Cycle counting the highest-value components monthly and everything else quarterly keeps the counts honest without stopping production. A large adjustment on a component usually means a build was recorded with the wrong quantity.
Purchased items are valued by the costing method set for the organization, and a composite item takes its cost from the components consumed in the build at the time the bundle is recorded. That cost flows to cost of goods sold in the shared accounting organization when the finished item ships. Labor and overhead are not part of it, so a manufacturer with significant labor applies an uplift in accounting or moves to job costing.
Yes. Items carry barcodes or SKUs that can be scanned when receiving, picking, transferring between locations, and recording a build, using a scanner or the mobile app. Scanning reduces the mis-keyed quantity that is the usual source of count drift. Print barcode labels for components at receipt and for finished goods at the end of the build, and make scanning the step that records the transaction.
"Something isn't working." "We're outgrowing our tools." "We're afraid to make the wrong move." No-Risk Discovery is a short, practical conversation that gets you clarity before you commit to anything big. We'll tell you if we're a fit. If we're not, we'll tell you that too.
Say who you are and ask. A person replies within one business day.
