[Q&A] Product-Level Costing Is Just Too Hard

When companies evaluate Numen and CBOOK, the question we hear more than any other comes down to this: "How are we supposed to do costing?"

Today, we'll work through the questions companies ask most often about costing.

Q1. I have no idea how to do product-level costing (fixed vs. variable cost, overhead allocation).

We make roughly 20 products in-house. But our ERP only aggregates costs in lumped-together form, so it's hard to see a clear cost structure for each product. For overhead like factory rent and labor, we have no rational allocation basis, we just carry forward the same old rates we've always used.

The result: revenue keeps climbing, yet net income isn't improving the way we'd expect. We can't even tell which products are really driving profitability.

A. You're not alone, this is a struggle for many companies.

Costing is hard for three big reasons.

1. ERP/accounting data built around the general ledger

Most ERPs are designed around financial accounting. They're great at recording "what we bought at what price, and what we sold it for," but their ability to automate per-product cost structure and margin analysis is limited.

The data an ERP surfaces mostly stops at total cost or general-ledger-account aggregation, so seeing the profitability of an individual product takes additional processing and separate analysis. As a result, the ERP alone rarely gets you to the per-product P&L and contribution-margin analysis leadership wants.

1. The difficulty of overhead allocation

Overhead like rent, electricity, and management salaries doesn't tie directly to any one product, so you can only get a per-unit product cost by setting a rational **driver, such as headcount, floor area, or machine-run hours,** and allocating on that basis. But this takes expertise, and the cost result swings heavily depending on how you set the allocation basis.

Most companies apply a simplified estimated rate and rework it in Excel, but that opens a gap with reality and can distort margins by product.

1. Inconsistent inventory (raw-material) unit costs

In the ERP, the inventory-valuation method (average, moving average, FIFO, etc.) and the timing lag in the close process frequently leave raw-material unit costs out of step with actual purchase prices. That distorts per-product cost and COGS and throws off the inventory-asset value too. In industries with volatile raw-material prices especially, it's a leading cause of margin analysis and P&L management drifting far from reality.

For these structural reasons, many companies struggle to run accurate product-level costing. So how do you improve it?

Improvement Checklist 🔧

• Is your inventory ledger connected to your accounting function? (Y/N)

• Are you entering a production ledger based on a BOM? (Y/N)

• Is your overhead allocation basis clearly defined? (Y/N)

• Do you have the internal staff and leadership will to improve the ERP structure? (Y/N)

💡 Hint: Costing isn't something you nail perfectly in one pass. The key is to start with simple bases and refine them step by step.

Q2. Do we really have to get product-level costing exactly right?

"I figured as long as total profit was right, we were fine, but leadership asks for per-product P&L at every month-end. Is it really necessary?"

A. Yes, it's essential.

Product-level costing isn't just an accounting issue, it's directly tied to your growth strategy.

Why product-level costing matters 💡

• You can't set pricing strategy without per-product cost

• You can't judge marketing-investment efficiency without an accurate break-even point (BEP)

• You can't remove inefficiency without knowing your cost structure

If you can't read cost properly, you can't solve the problem.

The answer to "revenue went up, so why isn't there any profit?" almost always comes out of per-product cost-structure analysis.

Common mistakes ⚠️

• Looking only at gross margin and assuming "things are going well"

• A close process that takes 2+ weeks → per-product cost lands a month late, and decisions lag with it

• Setting strategy off average cost instead of per-product cost → bad investment decisions

  
  

Q3. How are other companies doing product-level costing?

"We'd like to try it too, but we don't know where to start. How is everyone else handling it?"

A. Real examples make the approach a lot clearer.

Manufacturer A

• Before: Material and processing costs could be aggregated by product, but overhead like electricity and rent was allocated separately in Excel. Recalculating from scratch each time pushed report delivery more than a month late.

• After: Set rules to map ERP data by product and automated it → the cost structure of high-defect products surfaced, kicking off an improvement project that cut the cost ratio by 5 percentage points.

Retailer C

• Before: Judged per-store P&L on revenue alone. Because rent and overhead weren't factored in, a "store everyone thought was thriving" was actually losing money.

• After: Allocated rent and overhead by revenue share → operating margins by store became visible, underperforming stores were closed, and the overall margin doubled.

👉 The key is breaking aggregate data into manageable units (product, business unit, store) and connecting every piece of needed information in real time so you can act on it.

Q4. Is there a way to automate product-level costing and performance management instead of using Excel?

"Splitting and calculating everything in Excel throws off errors every time, and updates always run late."

A. Yes, you can automate it.

• CBOOK: Standardizes ERP/accounting data and converts it into a P&L structure by product and business unit

• Numen: Uses that data to automatically analyze fixed/variable costs, cost ratio, margins, break-even point (BEP), and even run simulations

In other words, CBOOK builds the foundation of recording and management, and Numen delivers the strategic interpretation on top of it.

Costing isn't just "accounting work", it's the starting point of managerial P&L, showing what strategy you can build for each product. If you have the data but still can't see the costing, it's time to take a hard look at your systems and tools.