When a work order closes short, backflush components against the quantity actually produced, not the original order quantity, and route the shortfall to scrap, rework, or a variance account. That keeps on-hand counts, cost of goods, and the next production run's component availability accurate.
Picture a sheet-metal shop running a work order for 500 brackets. The press jams twice, a batch gets rejected on first-article inspection, and the floor reports 420 good units at close. If the backflush still relieves components for 500, the component bins now show less material than actually left the shelf, and the shortfall never shows up anywhere. It just vanishes into the count.
That one bad posting does three things. It delays the next order that needs the same components, because purchasing is working from a number that was never real. It wastes labor, because someone on the floor eventually has to go count the bin by hand and figure out where the gap came from. And it leaves the plant carrying inventory it does not actually have, which throws off reorder points for every part on that BOM until someone catches it.
The same problem shows up at a contract electronics assembler three states over, on a different shift with a different part number. Night shift closes a 1,200-unit work order at 1,140 units because three boards failed in-circuit test and a fourth went to rework. The inventory planner on day shift pulls up the connector screen the next morning expecting enough stock for the next run and finds sixty units short with no explanation attached to the count. She spends forty minutes walking the floor asking who ran that work order, because the system posted a clean, full-quantity backflush overnight and moved on like nothing happened. The variance is real. It just lives in nobody's report, and now it is her problem to find before the next shift starts.
Many shop floor systems show the mismatch after the fact instead of at the moment it happens. The count comes back wrong on a cycle count report weeks later, or the next work order picks short on the line, and tracing it back to the original short close becomes somebody's afternoon. The software recorded a transaction. It did not tell anyone what actually happened on the floor.
Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. For a plant running BOMs, work orders, MRP, production scheduling, or job and labor costing, Fishbowl Advanced Manufacturing is the fit, with data-focused AI built in that tells you what is happening on the floor right now, what is coming due, and what needs your attention before it turns into a shortage.
Fishbowl's cloud side carries a different kind of AI for a different job. In Fishbowl Inventory, the AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. Nothing is saved or changed without the operator's approval. That work lives on the purchasing and fulfillment side of Fishbowl. The data-focused AI inside Advanced Manufacturing is watching something different: the floor, the BOM, and the work order queue, not the PO inbox.
Follow these steps to record the close correctly:
- Confirm the actual finished-good quantity before the work order is closed. Do not close against the planned quantity by default.
- Backflush components against that actual quantity, so component relief matches what really left the shelf.
- Route the shortfall, the gap between planned and actual output, to a scrap, rework, or variance location tied to that work order number.
- Post labor and overhead against the real output, not the original order quantity, so unit cost on the finished good reflects what actually happened.
- Pull the work order variance report before the next run draws on the same components, so purchasing and scheduling start from a number that is true.
A plant that handles this well tends to look the same way on every work order, including the ones that go sideways. Use this as a test for any system you are running or evaluating:
- Can the floor close a work order at a quantity different from the one it was opened with, without a supervisor override or a side spreadsheet?
- Does the backflush transaction show the actual quantity produced, visible on the work order history, not buried in a batch log?
- Is there a dedicated scrap or variance location, separate from good finished-goods inventory, that the shortfall lands in automatically?
- Can you pull a variance report by work order, by part, or by shift, without exporting to a spreadsheet first?
- Does the next work order's component availability reflect the corrected count within the same day, not after a manual adjustment?
If several of those come back no, the gap is not the floor crew. It is a system that was built to record a transaction, not to tell you the truth about what happened on that run.
Brian Garrett at Telluric Companies, a beta tester on Fishbowl's cloud inventory tools, said the purchase order workflow alone saves him at least 45 minutes per purchase order. That is on the inventory side. On the manufacturing side, Velocity Restorations cut scheduling time in half once cascading BOM updates stopped requiring a manual rebuild of every downstream work order, and Mack & Rex took 30 hours a week out of manufacturing transactions after moving off manual postings. Cascadia Motion brought inventory costs down 18 percent with Fishbowl Advanced and its data-focused AI handling demand and procurement visibility. Those are Advanced results, named and attributed, not a guess at what a short close might save a specific plant.
None of this replaces the floor supervisor's judgment about whether a batch is good, scrap, or rework. It just means the system records what they decide, correctly, the first time, instead of asking someone in accounting to reconstruct it three weeks later from a half-remembered shift log.
If the plant also sells finished goods online, Fishbowl Channels is the channel-integrations layer. It works with Fishbowl Inventory, Fishbowl Advanced Manufacturing, or Fishbowl Advanced Warehouse. Advanced customers add ecommerce channels in Fishbowl; they do not also purchase Fishbowl Inventory. Books stay in QuickBooks or Xero either way. Fishbowl does the operational work and syncs; the accounting system keeps the ledger.
A short close is not a failure. Material gets rejected, machines jam, and first-article inspection catches real problems on both the bracket line and the board line. The failure is a system that cannot tell the difference between a clean run and a messy one, and hands the cleanup to whoever is on shift when the numbers stop making sense.
See how Fishbowl Advanced Manufacturing records a short close correctly the first time: get a demo.
Fishbowl does the work. You make the call.
Frequently asked questions
What does backflushing actually do on a work order?
Backflushing relieves raw material and component inventory automatically when a work order is reported complete, based on the bill of materials, instead of requiring a manual issue transaction for every part. It saves transaction time but only reports accurate numbers if the quantity it backflushes against matches what was actually built.
Why does a short close cause a problem if the system still backflushes the full order quantity?
If the system relieves components for the original order quantity instead of the units actually finished, on-hand component counts drop too far, finished goods cost looks wrong, and the next work order that needs those same components starts from a number that is not real.
Where should the shortfall go instead of disappearing into inventory?
Route it to a scrap, rework, or variance location or account, tied to the work order, so the gap between planned and actual output is visible on a report instead of silently absorbed into standard cost or written off at month end.
How long does it take to get a system set up to handle short closes correctly?
Paid setup and training for Fishbowl Advanced Manufacturing typically runs 6 to 8 weeks with expert-led onboarding, but the system is useful from the first live count. BOMs, routing, and backflush rules can be in place before every location is fully converted. Customers can reach a person by phone, email, or chat if a close does not look right during setup.
