When Safety Stock Becomes a Hard Floor in EDGEBIC

In EDGEBIC by User Solutions safety stock is a replenishment trigger by default, not a consumption floor, so the plan flags a bucket and fires a suggestion when the projected balance drops below the safety level but still lets real demand consume the buffer and even push the balance negative; an opt-in per-product setting turns safety stock into a hard floor for the few parts that need one. The distinction between a trigger and a floor is easy to miss and important to get right, because it decides whether the plan warns you or blocks you.

This post explains both roles, why the default lets stock fall below safety, and when to make it a hard floor. For the buffer's main job, see how safety stock absorbs demand variability, and for the wider loop start from the EDGEBIC planning guide.

Trigger Versus Floor

Safety stock is a level you set on a product, a buffer meant to cover demand variability. What that level does depends on which role it plays.

As a trigger, the default, safety stock is a warning line. When the projected balance falls below it in a bucket, EDGEBIC flags that bucket and fires a replenishment suggestion. But it does not stop demand from drawing stock down through the line. The balance can sit below safety and can go negative, while the flag and the suggestion tell you to act.

As a floor, the opt-in, safety stock becomes a level the plan will not consume below. Demand cannot draw the buffer down. The buffer is protected rather than merely watched.

The default is the trigger. The floor is a deliberate choice you make per product.

Why the Default Lets Stock Go Below

Letting the balance drop below safety, and even negative, is not a bug. It is the plan being honest about committed demand.

A negative projected balance means committed demand is running ahead of supply in that bucket. That is a real condition, and often an intentional one: you took the orders knowing supply was tight, and you plan to close the gap. The default treats that as planning debt to surface and resolve, not an error to block. It flags the shortfall, suggests a replenishment, and leaves the decision to you.

This matches how the promise math works. A negative available-to-promise is valid information, signaling demand committed ahead of supply, not a forbidden state. The whole calendar leans toward showing you the truth and letting you act, rather than silently refusing to consume real demand. If a genuine order needs to draw into the buffer to ship, the default lets it, and warns you loudly.

A Worked Example: The Same Part, Two Behaviors

Take a part with safety stock set to 50, on-hand of 120, and demand of 45 a week with no incoming supply.

Under the default trigger behavior, the balance walks down: week 1 at 75, week 2 at 30, week 3 at -15. Week 2 crosses below the 50 safety line, so it is flagged and a suggestion fires. Week 3 goes negative. Nothing is blocked. The plan shows you a part running into and then through its buffer, with a clear warning and a suggested order to fix it. You firm the replenishment, later buckets lift, and the balance recovers.

Now suppose this is a critical part you can never ship below its buffer, and you turn on respect-safety-stock for it. Safety stock becomes a floor. The plan will not consume the part below 50, so demand that would draw the buffer down is not satisfied from that stock. You see the constraint enforced rather than a warning, because for this one part you have said the buffer is untouchable.

Same numbers, two very different behaviors, chosen per product.

When to Reach for the Floor

The floor is an exception, and most products should stay on the default. Turn on respect-safety-stock only for parts where you genuinely cannot ship from the buffer: a critical spare that keeps a line running, a safety-critical component, a customer contract that mandates a reserve. For those, a hard floor is exactly right.

For everything else, the trigger behavior serves you better. It warns early, keeps the plan honest about real demand, and lets you decide whether an order should draw into the buffer. A plant-wide floor would turn every buffer into a wall and hide the planning debt you need to see. Reserve the floor for the handful of parts that truly require it.

Keeping the Buffer's Role Clear

The mistake to avoid is assuming safety stock always blocks consumption. By default it does not; it warns. If you see a balance dip below safety or go negative with no error, that is the trigger doing its job, surfacing a shortfall for you to resolve, not the system failing. If you truly need a part protected, make that an explicit, per-part decision with the respect setting, and know that you have changed how demand is satisfied for it.

Read the flag and the suggestion as a prompt to act, firm a replenishment to lift the later buckets, and reserve the hard floor for the parts that cannot live without one. For how a shortfall becomes an order, read why a replenishment suggestion does not lift projected balance until you firm it, and for the buffer level in general terms, see the safety stock glossary. To compare it with the reorder point, read reorder point and safety stock, two lines, two jobs.