Backflushing

Backflushing deducts components from stock automatically when production completes, using the BOM. How it works, when it fails, and when to issue stock instead.

Backflushing

Backflushing deducts component stock automatically when a finished item is recorded as complete, using the bill of materials to work out what must have been consumed, instead of logging each issue to the shop floor as it happens.

By Tibeau De Grauwe, FounderUpdated September 2026

  • 25 products free
  • No credit card
  • 10-min setup

How backflushing works

In a conventional issue-based flow, someone records material leaving stores and entering work in progress at the moment it happens, then records the finished item separately. Two transactions, both requiring a person at the point of the event.

Backflushing collapses that into one. When the production run is reported complete, the system multiplies the quantity produced by the per-unit component quantities on the bill of materials and deducts the result from stock in a single step. Work in progress is inferred rather than tracked.

The name describes the direction of travel: consumption is flushed backwards from the finished-goods transaction, rather than pushed forward from the store issue.

Why smaller manufacturers rely on it

The appeal is entirely about data entry. A workshop building forty assemblies a day with twelve components each would need hundreds of issue transactions to track consumption directly, and in practice those transactions do not get recorded, so the alternative to backflushing is often not careful tracking but no tracking at all.

It also keeps costing simple. Material cost per finished unit falls straight out of the BOM rollup, which is enough for pricing and margin decisions in businesses where variance between the theoretical and the actual build is genuinely small.

For a team moving off spreadsheets, backflushing is usually the first point at which component stock stops drifting, because completing a build finally does something to inventory automatically instead of relying on someone remembering to adjust twelve lines.

Where backflushing goes wrong

Every discrepancy between the bill of materials and what actually happened on the bench becomes an invisible stock error. Scrapped components, an operator substituting a similar part, an extra length of material cut wrong: none of it is recorded, so the system keeps carrying stock that is physically gone.

The errors accumulate quietly and only surface at a physical count, by which point the cause is months old and untraceable. That is why a business relying on backflushing needs cycle counting on its highest-value components rather than an annual count, and needs a way to report scrap against a run.

Long production cycles are the other problem case. If a build takes three weeks, backflushing leaves the components sitting on the books as available stock for three weeks even though they are physically committed and cut, which makes availability figures optimistic exactly when a planner needs them to be honest.

  • Unrecorded scrap leaves phantom stock on the books
  • Component substitutions are never captured
  • Long runs overstate available component stock until completion
  • BOM drift silently corrupts every deduction that follows

Using it without losing accuracy

Treat the bill of materials as a maintained document rather than a one-time setup. A BOM that includes a realistic scrap allowance deducts closer to reality than one that assumes perfect yield, and revising it when a design or supplier changes is the single highest-value habit for anyone backflushing.

Give operators a way to report scrap and substitutions against the run, even if it is a short note. Backflushing plus a scrap entry is a good approximation; backflushing alone assumes an accuracy the shop floor rarely has.

Count the components you cannot afford to be wrong about. A short weekly cycle count on the ten highest-value parts catches drift while the cause is still recent.

In StockFlow, BOM authoring and cost rollup are available on every plan, while automatic stock deduction when a production order completes is part of the Production module, included on Professional and above or available as a $4/month add-on.

Trusted by small businesses

What our customers say

Super Kind! Quick replies from their support and very easy fixes, changed the dashboard a bit and customized it. Also gave me 450 items extra on the free plan just for me. Highly recommend and again great service!

Erasable Trading AU

Best customer service! Stockflow's customer support is fast and extremely helpful. They assisted me with customization of the software to improve my experience as a user.

Justin M.

Co-Owner, Consumer Goods

Frequently asked questions

What is backflushing in manufacturing?
Backflushing is deducting component stock automatically when a finished item is reported as complete, calculating consumption from the bill of materials rather than recording each material issue to the shop floor as it occurs.
What is the difference between backflushing and issuing components to a job?
Issuing records material leaving stock at the moment it is taken, which is accurate but requires a transaction per issue. Backflushing infers consumption after the fact from the BOM and quantity produced, which requires almost no data entry but cannot see scrap or substitutions.
What are the disadvantages of backflushing?
It cannot detect scrap, substitutions, or over-consumption, so any difference between the BOM and the actual build becomes a silent stock error. It also leaves components showing as available during long production runs, which makes availability look better than it is.
When should you not use backflushing?
Avoid it where builds are long, values are high, recipes vary between runs, or full material traceability is required. In those cases the transaction cost of issuing components explicitly is small compared with the cost of an unexplained variance.
How do you keep backflushed stock accurate?
Maintain the bill of materials including a realistic scrap allowance, give operators a way to report scrap and substitutions against the run, and cycle count high-value components frequently enough to catch drift while its cause is still identifiable.