A Make-to-Stock Product Cannot Hold Inventory: Causes and Fixes

A product with a make-to-stock build method but the stocked flag turned off cannot hold inventory: receipt and issue posting, demand netting, and replenishment are all skipped for it, so builds complete and on-hand never moves. EDGEBIC by User Solutions treats build method and stocked status as two separate decisions, and the plant-wide anomaly scan flags the combination that cancels itself out.

This post covers what the flag actually switches off, how the mismatch usually arises, and how to correct it without inventing history. It belongs with the inventory symptoms in the EDGEBIC troubleshooting guide. For the concept see what is the is-stocked flag in inventory planning, and for the planning consequences see what not stocked means for a product's planning.

The symptom is quiet, which is what makes it expensive. Nothing errors, no job fails, and the plan looks normal, so a plant can run this way for months while every consumer of the part builds from scratch and every replenishment review shows nothing to do.

What You Are Seeing

The product is set up to build to stock. Jobs for it schedule and complete normally. But the on-hand quantity stays at zero, no consuming job ever nets against it, and no replenishment suggestion appears no matter how low the balance goes. A plant-wide anomaly scan lists it as a warning saying the product cannot hold inventory.

Why It Happens

Cause 1: The Stocked Flag Is Off

This is the cause in the large majority of cases. Build method says how the product is planned. The stocked flag says whether the product participates in inventory at all. With stocking off, three things stop happening:

Nothing errors. The product simply sits outside the inventory system while looking like it belongs to it.

How to tell: the product's build method is make-to-stock and its stocked flag is off.

Cause 2: The Product Was Imported With Defaults

An import that maps a build method but not a stocking flag can land a product in exactly this state. The build method looks right because it was mapped; the stocking flag carries whatever the import left behind.

How to tell: several products share the same combination and they arrived in the same import batch.

Cause 3: The Flag Was Turned Off Deliberately and Never Revisited

A product that used to be a pass-through part may have had stocking switched off on purpose. When its role later changes to a stocked build, the build method gets updated and the flag does not.

How to tell: one product, not a batch, and the change tracks a change in how the part is used.

How to Fix It

• Turn the stocked flag on in the product's inventory planning fields. This is the whole fix for the configuration. While you are in those fields, confirm the yield is above zero and no higher than one, because a product yield value that is out of range breaks the suggested build quantity in its own quiet way.
• Bring the balance up to reality. Builds completed while the flag was off posted nothing, and turning the flag on does not backfill them. Post an opening balance or an adjustment for the physical count, with a reason line that says what it is, as covered in how to make an inventory adjustment.
• Re-run scheduling so consumers can net against the corrected balance instead of building from scratch.
• Re-open the anomaly report on a plant-wide scan to confirm the row cleared. This check is plant-wide, so a job-filtered run will not show it, which is the trap covered in why anomaly checks show nothing when you filter to one job.

How to Diagnose It, in Order

1. Run a plant-wide anomaly scan and read the inventory rows.
2. Open the flagged product and compare its build method against its stocked flag.
3. Check the transaction history for the product. No receipts at all despite completed builds confirms the diagnosis, and how to audit the inventory ledger for a part covers the reading.
4. Correct the flag and post the true balance.
5. Re-run scheduling and re-scan so the row clears and consumers start netting.

The Combination That Is Fine

A make-to-order product that is also stocked raises no flag and is a normal setup: semi-finished parts often build to order and still sit in stock between operations. The check is specifically about the pairing that contradicts itself, a stock build method with nowhere for the stock to go. Do not turn stocking off on make-to-order parts to make a report quieter.

How to Prevent It

• Map the stocked flag in every product import, not just the build method. The two settings travel together.
• Audit after every import with a plant-wide scan, which catches the whole batch in one pass rather than one shortage at a time.
• Treat a change of build method as a two-field change. Whenever a product moves to a stock build, confirm stocking is on in the same edit.
• Watch for the symptom, not just the flag. A product that builds regularly and never shows on-hand is telling you something even before the report does, and a related reading appears in inventory on-hand looks wrong after a reschedule.