In this article: how to log what was actually used in a production run, and why it matters.

Plan vs actual

When you allocate an order, AssetBlaze records the planned quantity for each component. When you actually build, the amount you use may be higher or lower. The Execution / Actuals tab on an order is where you record what really happened.

For each component, log:

• Planned quantity — already filled in from the allocation.

• Actual quantity — what you truly consumed.

• Waste quantity — what was scrapped or wasted, tracked separately from actual.

Why this matters

Two big things depend on actual quantities:

1. Stock accuracy. On completion, AssetBlaze deducts the actual quantity from on-hand stock, not the planned quantity.

2. Finished item cost. The cost of the finished item is rolled up from the real cost of the inputs actually consumed — so if you used more (or fewer, or different batches), the cost reflects that.

What if I don't log anything?

If the order had allocations but you record no consumption at all, you won't be able to complete the order — you'll be prompted to record actual usage first. If consumption is logged for some components but not others, the missing ones fall back to the reserved quantity on completion.

Tips

• Log consumption as you go, not at the end. It's easier to remember, and if you pause the run you don't have to reconstruct it.

• Use the waste field rather than padding actual — it keeps your yield and scrap analysis clean.