Glossary (EDGEBIC)

What Is the Is-Stocked Flag in Inventory Planning? EDGEBIC Definition

User Solutions TeamUser Solutions Team
|
6 min read

The is-stocked flag in inventory planning is a product setting that marks whether the item carries physical inventory. When it is turned off, inventory netting, replenishment, and receipt or issue posting are all skipped for that product, so it never appears in the projected balance and never triggers a stock-based build. It is the clean line between items you hold on a shelf and items that have no physical stock at all, such as a service line or a phantom routing node.

This entry is part of the EDGEBIC by User Solutions glossary series; for the wider vocabulary of planning, see the manufacturing glossary. Whether an item is stocked interacts closely with its build policy, so read it next to make-to-stock vs make-to-order.

How the Is-Stocked Flag Works

The flag is a single yes-or-no setting on the product, and its effect is exclusion. When the flag is on, the product behaves normally: it is netted against demand, it can be replenished, and completed builds or consumed material post receipts and issues to its inventory ledger. When the flag is off, the product is quietly removed from all of that machinery.

That exclusion matters because not everything a plant sells or routes has physical stock. A service line, a labor charge, or a phantom assembly node exists in the data for pricing, structuring, or costing, but there is nothing sitting on a shelf to count. Running netting and replenishment against such an item would generate suggestions to build or buy something that has no meaning, and posting receipts or issues would move phantom quantities that only drift the ledger away from reality.

By skipping non-stocked items entirely, the projection stays focused on the products that genuinely have inventory to manage. The flag is therefore a data-hygiene control as much as a planning one: it keeps the projected balance and the ledger honest by keeping items that have no stock out of both.

A Concrete Example

Consider a shop that sells a physical bracket alongside an installation service. The bracket is a real product: it is machined, held in finished goods, shipped, and its on-hand quantity has to be planned. The installation service has no parts and no shelf; it is billed labor.

If both are flagged as stocked, the service line clutters the inventory projection, appearing in the projected available balance and potentially prompting nonsensical replenishment. The fix is to turn the service line's is-stocked flag off. From then on, netting, replenishment, and posting all skip it. The bracket keeps its full inventory treatment; the service quietly drops out of the stock machinery while remaining fully quotable and sellable.

The same logic applies to a phantom node in a routing that exists only to organize steps but is never held as stock. Flag it non-stocked and it stops pretending to have inventory.

How EDGEBIC Uses It

The is-stocked flag is a product-level switch that several parts of the planning engine consult before acting.

  • Inventory netting skips non-stocked products, so they never enter the projected available balance roll-forward.
  • Replenishment is suppressed for non-stocked items, so they never generate a build-to-stock suggestion regardless of their reorder settings.
  • Receipt and issue posting is bypassed, so completing a build or consuming material for a non-stocked item does not move phantom quantities through the ledger.

A stocked product's movements are recorded in its inventory ledger, the audit trail of every receipt and issue. To see how a stocked product's demand can be satisfied from existing shelf quantity instead of new production, read what is consume-from-stock netting.

The is-stocked flag is a product setting that tells the system whether the item carries physical inventory. In EDGEBIC, when the flag is off the product is skipped entirely by inventory netting, replenishment, and receipt or issue posting, so it never appears in the projected balance and never triggers a stock-based build. It is the switch that separates items you track on a shelf from items that have no physical stock, such as a service line or a phantom node in a bill of routing.

Turn the flag off for anything that has no physical on-hand quantity to manage: a service or labor line, a documentation item, or a phantom assembly node that exists only to structure a routing but is never held in inventory. For those items, netting and replenishment would be meaningless, so skipping them keeps the projection clean and prevents phantom stock movements that would drift the ledger.

No. The flag governs whether the item participates in future netting, replenishment, and posting; it does not erase records. It simply removes the product from the inventory machinery going forward, so a non-stocked item stops being projected, replenished, or posted against without disturbing any history that already exists.

Expert Q&A: Deep Dive

Q: We sell an installation service that has no parts. Why is it cluttering our inventory projection?

A: Because it is still flagged as stocked. A service line with no physical on-hand quantity should have its is-stocked flag turned off. Once it is off, EDGEBIC skips that product in netting, replenishment, and receipt or issue posting, so it drops out of the projected available balance entirely and stops generating meaningless stock signals. The service can still be quoted and sold; it just no longer pretends to have inventory to manage.

Q: A make-to-stock product is not showing up in replenishment suggestions. What could be wrong?

A: Check the is-stocked flag. If a product's build method says make-to-stock but the item is not flagged as stocked, the inventory netting path skips it, so it never generates a replenishment suggestion even though its policy expects one. That mismatch is exactly the kind of inconsistency EDGEBIC's anomaly checks are designed to surface. Turn the flag on so the item participates in netting and its make-to-stock policy can actually drive replenishment.

Frequently Asked Questions

Ready to Transform Your Production Scheduling?

User Solutions has been helping manufacturers optimize their production schedules for over 35 years. One-time license, 5-day implementation.

User Solutions Team

User Solutions Team

Manufacturing Software Experts

User Solutions has been developing production planning and scheduling software for manufacturers since 1991. Our team combines 35+ years of manufacturing software expertise with deep industry knowledge to help factories optimize their operations.

Let's Solve Your Challenges Together