Standard cost vs actual cost in food manufacturing — which one fits your factory

The three costing methods that any ERP supports — average, standard, and actual — sound like accounting trivia. They’re not. The method you pick determines what your CFO can see and what she can’t. For an F&B factory, the wrong choice means margin compresses for months before anyone notices.

This article walks through when each method fits, what it costs to maintain, and what AION supports in each.

What each method actually does

Different ways to put a number on a unit of inventory.

Average cost continuously recomputes the per-unit cost from the formula opening balance value + value of receipts ÷ opening quantity + receipts. Every issue gets costed at the most recent average. Smooths out price spikes. Mechanical to administer because the system computes the average automatically.

Standard cost holds a pre-set rate for each item and each resource. Production posts at standard. Variance from actual posts to dedicated GL accounts. Requires someone to maintain the standards (typically the cost accountant, annually or quarterly). Returns visibility into margin slippage that average cost hides.

Actual cost tracks every single transaction at its specific cost via cost layers. FIFO/LIFO matching at issue. Theoretically the most accurate. Practically unworkable in continuous-process F&B because batch blending makes “this exact dollar of cost” untraceable to “this exact bottle that came off the line.”

The decision framework

Three questions decide which method fits your factory.

1. How stable are your recipes? If you launch new SKUs every quarter and reformulate existing ones twice a year, standards rot fast. You’ll spend more time maintaining the standards than benefiting from the variances. Use average cost.

If your recipes are stable for a year-plus (most established juice, dairy, water factories), standards stay valid long enough to be worth maintaining. Standard cost gives you variance visibility on top.

2. Is your CFO trying to see margin compression early? Average cost shows you the unit cost at month-end. By the time you see it, the price move has been absorbed into COGS for the whole period.

Standard cost shows you the variance at every transaction. When concentrate price jumps and consumption goes above standard, the variance lands on the financials in days, not weeks. For F&B factories above SAR 50M revenue, this is usually worth the standard-maintenance overhead.

3. Can your finance team maintain standards? Standard costing requires someone — typically a cost accountant — to update standards when raw material prices or labour rates move materially. If you don’t have that bandwidth, standard costs go stale and the variances stop meaning anything.

Be honest about this. A factory with no dedicated cost accountant should not run standard costing.

What AION supports

Both methods are production-ready. The default is average cost (configured at the item level). Standard cost is enabled by setting the costing method on the item master and maintaining a standard-cost rollup that re-runs when component costs change.

Average cost mechanics:

• Period-end average recalculation from opening + receipts (close-costing-period.use-case.ts Step 4)
• Outstanding issues swept to the final period cost (Step 7)
• Opening balance carry-forward to next period (Step 3)
• Per-item, per-period averages tracked in inv_period_average_costs (period-average-cost.orm-entity.ts)

Standard cost mechanics:

• Multi-level rollup explodes the BOM tree, sums component costs + routing labour + overhead (standard-cost-rollup.service.ts — FULL and SIMPLE modes)
• Batch rollup re-runs for every APPROVED/FROZEN BOM in the organisation after a price change (batch-cost-rollup.use-case.ts)
• Material usage variance posts automatically when actual consumption differs from standard for the actual output (variance-calculation.service.ts:34-59)
• Labour efficiency variance for production hours different from routing (variance-calculation.service.ts:61-79)
• Overhead variance for absorbed vs budgeted overhead (variance-calculation.service.ts:81+)

A typical Saudi F&B factory configured for standard cost would set standards on FG and WIP items, leave raw materials on average cost, and let the rollup keep the FG standards current as receipts roll in.

Worked example — Oasis Mango Juice 1L

Take the Oasis Fresh demo BG. Oasis Mango Juice 1L has a standard cost of SAR 10.5 per bottle.

Run a job order for 10,000 bottles. The recipe says 65kg of mango concentrate at SAR 42/kg = SAR 2,730. Actual consumption was 67kg = SAR 2,814. The 2kg over-consumption is material usage variance: 2 × SAR 42 = SAR 84 debit to variance account, credit to WIP.

In average cost, this story doesn’t surface. The 67kg just gets included in the period’s COGS at whatever the period-end average comes out to. The CFO sees a slightly higher COGS for the month but doesn’t see why — was it volume, mix, yield, price? She’d have to dig.

In standard cost, the SAR 84 lands in a Material Usage Variance account that day. End of month, the variance report shows: Job JO-2026-00123 had SAR 84 of material usage variance, broken into mango concentrate (-2kg). The CFO knows immediately: the operator over-issued or there was waste. She can drill in.

For a one-job, SAR 84 variance, it doesn’t matter. For a year of 200 jobs averaging SAR 500 variance each — SAR 100,000 of margin in plain sight — it matters.

What about actual cost?

AION supports actual cost via cost layers (cost-layer.orm-entity.ts). Each receipt creates a cost layer; each issue consumes layers in FIFO or LIFO order based on the per-item configuration.

Practically, we don’t recommend this for F&B SMBs. Reasons:

1. Continuous-process production blends layers. A bulk juice mix tank holds concentrate from three receipts. The FG that emerges can’t be traced to a specific layer. You can compute an average across the layers, but that’s just average cost with extra steps.
2. Batch traceability uses lot tracking, not cost layers. Food safety requires lot tracking — which lot of concentrate went into which lot of finished good. AION handles this via lot transactions independently of costing layers. You don’t need actual cost to comply with SFDA / ETA / EFSA.
3. Reporting complexity isn’t worth it. Actual cost reports per cost layer are operationally hard to read. Most CFOs end up aggregating back to an average, which is what they should have started with.

The exception: if you have a small number of high-value SKUs where each batch is genuinely distinct (e.g., specialty fortified juice with rare ingredients), actual cost via layers makes sense. For mass-market F&B, it doesn’t.

Common mistakes when switching

If you’re moving from a spreadsheet world to a real costing engine, three traps to avoid.

Trap 1: Setting standards that match last month’s average. If you set FG standards equal to the trailing average, the first month’s variance is near-zero and you learn nothing. Standards should reflect engineering expectations — the recipe yield, the routing time, the overhead absorption rate — not historical averages.

Trap 2: Refreshing standards too often. Standards are supposed to be stable for at least a quarter, ideally a year. If you re-baseline standards every month because variances are uncomfortable, you’ve turned standard cost into a delayed average cost and lost all the value.

Trap 3: Ignoring small variances. A 2% variance on a SAR 5M job order is SAR 100,000. A CFO who only investigates variances above SAR 50,000 misses systematic small leaks. Set the threshold low enough to catch real issues; trust the variance report to surface them.

What to do this week

If you’re on average cost today and considering the switch:

1. Pick one item category to start with — finished goods is the right entry point because variance there is most actionable.
2. Compute the recipe-based standard cost for each FG. Don’t use trailing averages; use the engineered recipe and current raw material averages.
3. Configure the items as STANDARD costing method on AION.
4. Run a month of production. Open the variance report. See where the leaks are.
5. Adjust the standards quarterly. Refine as the operation matures.

The reverse migration (standard back to average) is trivial if it doesn’t work for you. The forward migration takes a quarter to bed in.

For the deep dive on how rollup actually mechanically computes the standard, see Multi-level BOM rollup for layered recipes. For how variances are computed and posted, see Material usage variance — spotting recipe drift.