Every work order in NetSuite consumes components in one of two ways. Backflushing takes them automatically when output is recorded, in the quantities the bill of materials says. A manual issue records what was actually pulled, when it was pulled, by a person who saw it happen. Both are correct in the right place, and choosing wrongly is one of the quietest ways a manufacturer’s inventory and costs drift out of touch with the floor. This guide explains how each works in NetSuite, which manufacturers should use which, how to combine them, and what goes wrong when the choice is made by default.
How the two methods work
Backflush
With backflushing enabled on a component, nothing is consumed until a work order completion is entered. At that point NetSuite multiplies the completed quantity by the BOM quantity for each backflushed component and issues them from the work order’s location in one step. The operator records one number: how many came off the line. Work order completions can be entered at the end of the order or as partial completions along the way; each completion backflushes its share.
Manual issue
A work order issue transaction records specific components and specific quantities against the work order, independently of output. Material can be issued when the job is kitted, when it is pulled from stores, or as it is used, and the quantities can differ from the BOM. For lot-numbered, serialized, or bin-managed components, the issue also captures which lot, serial, or bin was used, which is why those items cannot go negative and why traceability depends on this method.
Which manufacturers should use which
The decision is about variability and value, not about size or industry.
Backflush when consumption is predictable and the components are cheap or plentiful. Repetitive discrete assembly, high-volume runs of standard products, and any component that is used in exactly the BOM quantity every time. Fasteners, labels, packaging, standard brackets. The saving is real: no one keys hundreds of small consumption lines, and the count is right as long as the BOM is right.
Issue manually when consumption varies, when the component is expensive, or when you have to prove what went in. Precious metals, active ingredients, controlled substances, serialized parts, anything lot-tracked for recall or compliance, and any material whose usage moves with the batch. Formula and batch manufacturers fall here almost entirely: the amount of resin, dye, or ingredient used depends on the batch size and the yield, and a fixed BOM quantity is only ever an estimate.
Most manufacturers should use both, by component. Backflushing is set per item, not per work order, so the right configuration is usually a work order that backflushes its standard parts and requires manual issue for the handful of components that carry the cost, the risk, or the traceability. A machine builder might backflush hardware and manually issue the motor and the controller. A food producer might backflush packaging and manually issue every ingredient.
What goes wrong when the wrong one is chosen
Backflushing variable materials
The BOM says 10 kg; the run used 10.8 kg. Backflushing consumes 10, inventory shows 0.8 kg more than the shelf holds, and the cost of the run is understated. Repeat across a month and the physical count comes as a surprise, the margin on the product was never what the report said, and the reorder point fires late. Where usage is recorded as planned rather than actual, the numbers are plans, not facts.
Backflushing before receipt
Backflushing consumes the BOM quantity whether or not the stock exists in the system. If the components arrived but the receipt was not entered, or the previous batch’s output was not recorded, backflushing drives the item negative. This is one of the three causes covered in our guide to negative inventory in NetSuite, and the Stop Negative Inventory preference in the Enhanced Validation and Defaulting bundle is the control that stops it.
Manual issue for everything
The opposite failure is quieter. Requiring a manual issue for every screw and label creates hundreds of transactions per work order that nobody has time to enter accurately, so they are entered late, in bulk, or not at all. Inventory is then wrong in the other direction, and the shop floor learns that the system is something to be fed after the fact rather than used.
Backflushing lot-controlled items
NetSuite requires lot and serial numbers on consumption, so lot-controlled components cannot be backflushed blindly; the completion has to specify which lots were used. Treating them as if they could be backflushed leads to completions that fail at save or, worse, to lot control being switched off to make the error go away. The right answer is to issue those components manually, or to record lot selection at completion with the discipline that implies.
Setting it up correctly
- Classify every component on the BOM as backflush or manual issue, using the value-and-variability test above. Set the backflush flag on the item record accordingly.
- Get the BOM quantities right, including scrap or yield factors, before enabling backflush on anything. Backflushing is only as accurate as the BOM. See the guide to multi-level BOMs for the structural side.
- Decide when completions are recorded. Per shift, per batch, or at the end of the order. More frequent completions keep inventory current; fewer completions are less work. Partial completions are the usual compromise.
- Enable the negative inventory control so a backflush that would take a component below zero is blocked rather than posted.
- Review variances monthly. Compare backflushed consumption to physical counts by component. A component that is consistently over or under is telling you its BOM quantity is wrong, or that it should be issued manually.
For formula and batch manufacturers
In process manufacturing the standard BOM is the wrong instrument for the job, because the quantities depend on the batch. Consule’s ProShop scales the formula to the actual batch size, records substitutions made on the day, and captures the actual yield and consumption per run, so what NetSuite consumes is what was used rather than what was planned. On the discrete side, FactorySync ties completions to the scheduled operation so output is recorded where and when it happened. Getting the completion method right is one of the first things Consule reviews in a NetSuite optimization for manufacturers, because so much else depends on it.
Frequently asked questions
What is backflushing in NetSuite?
Backflushing consumes the components of a work order automatically when output is recorded, in the quantities the bill of materials specifies. The operator enters what was built; NetSuite works out what was used. It is fast and accurate when the BOM is accurate and the process is repeatable.
What is a work order issue in NetSuite?
A work order issue is a manual transaction that records the components actually pulled for a work order, in the quantities actually pulled, before or during production. It takes more effort than backflushing and gives an exact record of consumption, which matters when usage varies or traceability is required.
Can I mix backflush and manual issue on one work order?
Yes. Components are backflushed or not by item, so a work order can backflush its low-value standard parts and require a manual issue for the expensive, lot-controlled, or variable ones. This is the setup most manufacturers should end up with.
Why does backflushing cause negative inventory?
Because it consumes the BOM quantity regardless of what is on hand. If the components were never received, or the BOM overstates usage, backflushing drives stock below zero. Accurate BOMs, timely receipts, and the Stop Negative Inventory preference prevent it.
Inventory that never matches the floor? The completion method is usually where to look first. Talk to Consule.