When an Order Is Fully Satisfied From Stock in EDGEBIC

An order is satisfied from stock when its entire demand is met from existing inventory, so EDGEBIC schedules no shop-floor work for it. Instead of running operations through a routing, EDGEBIC by User Solutions posts a single issue that lowers on-hand by the order quantity and marks the job satisfied from stock. The order consumes no work-center capacity, appears on no machine, and leaves exactly one trace in inventory. This post explains that outcome, when it fires, and how it differs from an order that has to build.

For the wider planning picture, see the inventory and planning pillar. For how the two halves of stock movement close a loop, see how build-to-stock and consume-from-stock work together.

The Outcome in One Picture

Say a product has 200 units on hand and a customer order arrives for 80. EDGEBIC checks the demand against available stock, finds 200 covers 80 comfortably, and satisfies the whole order from inventory. The result:

• A single issue of 80 posts to the ledger, lowering on-hand to 120.
• The order is marked satisfied from stock.
• No shifts, instances, or capacity are allocated to it.
• The order runs on no machine and appears in no work-center queue.

The order still finalizes as a real, completed job. It simply finalizes by drawing down stock rather than by producing anything. The efficiency is the point: an order you can fill from the shelf should never occupy the floor.

When It Fires, and When It Does Not

The fully-satisfied-from-stock outcome fires only when available stock covers the entire order quantity. Three conditions have to hold:

• The product must be stocked. A product marked not stocked is skipped by netting entirely, covered in what not stocked means for a product's planning.
• The order must not itself be a make-to-stock producer. Producers add supply; they do not consume it.
• The order must not already be in progress. An order with real shop-floor actuals is never retroactively satisfied from stock.

When stock does not cover the full demand, the order does not draw a partial amount and stop. EDGEBIC nets what it can and schedules a build for the remainder through finite capacity. Zero shop-floor work is the reward for a full cover; a partial cover still means a build for the gap. The gates that decide net-versus-build are covered in when to net demand against stock vs build fresh.

The Single Issue Is the Whole Footprint

Because a satisfied-from-stock order runs no operations, its only mark on the system is one issue entry, tagged as a scheduling transaction and pegged back to the order. That peg matters. Months later you can open the order and see exactly which stock movement filled it, and you can open the ledger and trace the issue back to the order that consumed the units. Nothing is lost, and nothing needs a work-center record, because no work center was involved.

This is a clean, auditable outcome, and it is worth recognizing on sight. An order marked satisfied from stock with a single matching issue is not an error or a stub. It is the system telling you that demand was met without production.

No Double-Claiming Within a Run

A subtle guarantee protects the satisfied-from-stock path when several orders compete for the same stock in one planning run. The moment an order is satisfied, EDGEBIC decrements the available stock before evaluating the next order. If on-hand was 100 and the first order took 80, the second order sees only 20 available.

So two orders can never both claim the same units. The first to be netted reserves what it needs, and the second works with what remains. If the remainder cannot fully cover the second order, that order schedules a build for its shortfall rather than falsely reporting itself satisfied. This within-run reservation is covered in the inventory reservation map explained.

Why It Matters to a Planner

Recognizing a satisfied-from-stock order changes how you read your schedule. A demand that vanishes from the shop floor did not disappear; it was filled from stock, and the proof is one issue on the ledger. When you expected a job to appear on a machine and it did not, the first thing to check is whether the product had enough on hand to cover it outright. If it did, the absence of a job is correct.

The broader value is capacity you never spent. Every order filled from stock is a job the floor did not have to run, which frees machines and shifts for the demand that genuinely needs building. That is the quiet return on holding the right inventory, and the satisfied-from-stock status is where you see it land. For the underlying scheduling ideas that decide what does reach the floor, see what is production scheduling.