Production Costing: From BOM to Finished Goods
A practical walk-through of how a manufacturing order turns into a costed finished good, from bill of materials to inventory value to the ledger. Learn where unit costs drift and how to keep them honest.
In this guide
What to watch for
Use the article to identify repeat work, handoff gaps and places where one source of truth would help.

In this article
Ask a small manufacturer what it costs to produce one unit of their best-selling item and you will usually get a quick, confident answer. Ask where the number came from and the confidence fades a little: it is often a supplier quote for the main material, a rough allowance for labour, and a margin the market seems willing to bear. The gap between the number the sales team quotes and the number the books can actually prove is where a lot of manufacturing profit quietly disappears. Closing that gap is less about better estimating and more about recording what actually happens on the floor.
A bill of materials is a costing document
A bill of materials is usually treated as a production instruction: these are the components, this is how many of each, assemble in this order. It is that, but it is also the backbone of your unit cost. Every component line is a quantity that will eventually be multiplied by a purchase price, and every quantity nobody bothered to specify is a cost that shows up somewhere else, usually as an unexplained gap in raw material stock.
The Production module holds bills of materials alongside the manufacturing units that build them, so the recipe lives in the same system as the stock it consumes. Two disciplines make that worthwhile. First, put everything on the BOM, including the small consumables people wave away: adhesives, packaging, labels. Second, be exact about units of measure. If you buy resin by the sack and consume it by the kilo, decide which unit the BOM speaks in and keep that conversion in one place. A surprising number of unit-cost arguments in a factory turn out to be unit-of-measure arguments.
The production order pins cost to a batch
A bill of materials describes what should happen. A production order records what did. That distinction is most of production costing.
When you raise a production order in the Production module, you are tying a specific BOM to a specific quantity, on a specific date, at a specific manufacturing unit. Consumption is then recorded against that order rather than against the month as a whole. It sounds like a small administrative difference, and it changes what you are able to answer. Without orders, the best you can say is that the factory consumed a certain amount of material in June and produced a certain number of units, so the average cost is whatever the division gives you. With orders, you can say that one batch of 500 consumed more material than the BOM called for, and go find out why while people still remember.
Batch-level records also keep costing usable through a change in product mix. An average that blends a simple product with a complex one is accurate for neither, and it drifts further every time the mix shifts.
Materials leave inventory before finished goods arrive
Production always creates a window where value has left one place and not yet arrived in another. Raw materials have been issued to the floor, the finished goods do not exist yet, and the value sits in work in progress. Manufacturers who only count what is on the racks tend to lose track of that middle state entirely.
The Inventory module tracks stock levels, transfers and adjustments across every location, which is what lets you treat the production floor as a location rather than a black hole. Issuing material to an order should reduce raw material stock at the moment it physically moves, not at month-end when somebody reconciles. Output should increase finished goods stock when the batch is completed and accepted.
Timing matters more here than most teams expect. If issuances are collected on paper and keyed in days later, raw material stock reads high all week and then collapses, and every reorder decision made from that number was made from fiction.
Deciding what belongs in the finished cost
Once a batch is complete, the output has to be valued, and that is a policy decision before it is a system one. Materials are the uncontroversial part. Direct labour and manufacturing overhead, such as power, machine time, factory rent and supervision, are where smaller manufacturers usually stop. Stopping there is defensible as long as it is deliberate and everyone quoting prices knows it.
The Production module costs completed output back into inventory, so finished goods carry a value and not only a count. That link is what turns a stock report into something an accountant can work from.
If material is drawn from the store without being recorded, or entered in round numbers days after the fact, the unit cost that comes out is a tidy-looking guess. Costing discipline starts at the material window, not in the accounting office.
Whatever you decide to include, write the policy down and apply it the same way every period. A unit cost that carries overhead one quarter and drops it the next produces a margin trend that means nothing.
What the ledger should see
Finished goods are an asset. Their cost becomes an expense only when they are sold, which is why production cost and cost of goods sold are never the same figure in a month where stock levels move. A factory that produced more than it sold has spent cash and grown inventory value, and the accounts should show exactly that rather than a phantom loss.
The Finance module carries accounts, expenses, payments and reconciliation, with dynamic reports drawn from the same records the rest of the platform writes to. The practical benefit of running production, stock and accounts on one integrated platform is not that it removes judgement. It is that the inventory value in your financial reports and the finished goods figure in your warehouse are the same number, from the same source, with no spreadsheet sitting in between reconciling them every month.
Where the numbers drift
Even a well-run costing setup drifts, and it drifts in the same few places. Yield and scrap come first: a BOM that assumes perfect conversion will always understate material cost in a process that produces trim, spillage or rejects. Build the expected loss into the BOM quantity where it is predictable, and record it as consumption where it is not.
Substitutions come second. When the usual supplier is short and the floor runs a different grade at a different price, that batch cost something different, and nobody will remember by month-end unless the production order says so.
Purchase price movement is third and the least visible. Material costs move; a unit cost calculated once in January and never revisited will be quietly wrong by mid-year, and the products with the thinnest margins go wrong first. Reviewing costed bills of materials on a schedule, which for most small manufacturers means quarterly, catches this before the price list does.
Start with one product line
You do not have to cost the whole factory at once. Pick one line, ideally a high-volume one where a small per-unit error is expensive, and get its bill of materials complete, its production orders raised for every batch, and its issuances recorded as they happen. Run it for two or three months, then compare the costed output against what you always assumed the product cost. The difference is usually instructive. Once one line runs honestly, extending it to the rest is repetition rather than invention.
Technology decision context
Use "Production Costing: From BOM to Finished Goods" to make a better systems decision
Technology articles are most useful when they help the team decide what to change next. Focus on the process problem first, then choose the tool or integration that removes the most repeated work.
Part 1Start from the workflow, not the tool
A system change should solve a visible operational problem. Map who creates data, who reviews it and who depends on the result.
- Identify repeated encoding, manual exports and duplicate records
- Find handoffs that rely on reminders instead of system status
- Separate must-have controls from nice-to-have interface features
Part 2Integration details to check
A useful system should reduce context switching and make data easier to trust across teams.
- Which records need one source of truth?
- Which reports depend on data from more than one department?
- What permissions, audit logs and backups are required?
Part 3How to judge success
A better technology setup should improve speed, reliability and confidence in decisions.
- Fewer manual workarounds after rollout
- Shorter time from request to approval or report
- Clear ownership when something is missing or incorrect
Chelsea Cuevas
Content & Marketing Associate
Covers business growth, HR best practices, and the technology behind modern operations.



