The Per-Order Build-to-Inventory Override in EDGEBIC

In EDGEBIC by User Solutions a manufacturing order carries a build-to-inventory flag that overrides the product's make-to-stock or make-to-order policy for that one order: blank means inherit the product default, yes means build into stock, and no means ship to a customer, so you set the common case once on the product and handle exceptions order by order. The override is what lets a product you normally stock go direct to a customer on a single special run, without changing anything about how the rest of that product is built.

This post explains the per-order flag, how it resolves against the product's build method, and how the hybrid method turns the whole thing into a default-plus-exceptions pattern. For switching a product's own policy, see how to switch a product between make-to-stock and make-to-order, and for the wider loop start from the EDGEBIC planning guide.

Two Levels of Decision

Whether an order builds into stock or ships to a customer is decided at two levels. The product sets a default; the individual order can override it.

At the product level, the build method is one of three settings. Make-to-order means the product is built only against a real order and never stocked. Make-to-stock means the product is normally built ahead into finished-goods stock. The hybrid, make-to-stock-with-override, means the product defaults to stock but expects some orders to go direct. At the order level, the build-to-inventory flag can be left blank to inherit, or set explicitly to yes or no.

The order flag is the finer control. It exists so a single job can behave differently from the product's default without you touching the product at all.

How the Override Resolves

The resolution rule is simple and always the same: the order flag wins when it is set, and the product policy applies when it is blank.

EDGEBIC checks the order's build-to-inventory flag first. If it carries an explicit yes, the order builds to stock. If it carries an explicit no, the order is make-to-order and ships direct. Only if the flag is blank does the product's build method decide, treating make-to-stock (and the hybrid method) as build-to-stock and make-to-order as ship-direct.

The pattern to remember: an explicit flag always overrides the product; a blank flag defers to it.

What Building to Stock Actually Does

When an order resolves to build-to-stock, two things follow. During planning, the inventory calendar treats the open order as future supply, so it shows up as a scheduled receipt that lifts the projected balance in its completion bucket. On the floor, when the order is marked complete, it posts a finished-goods receipt into the ledger and raises on-hand, ready for the next demand to consume.

An order that resolves to make-to-order does neither. Its output goes to the customer, no receipt posts, and the plan does not treat it as inventory supply. The order still schedules through finite capacity the same way; the only difference is where its output lands.

One caveat sits above all of this. A build-to-stock order still posts no receipt if the product is not marked as stocked, because that setting suppresses inventory posting entirely. So the full read for a missing receipt is: check the order flag, then the product method, then whether the product is stocked at all.

A Worked Example: One Special Run Ships Direct

Take a valve body you normally stock. The product is set to make-to-stock, so every order for it defaults to build-to-inventory and refills finished-goods stock on completion.

Now a customer wants a special run of 40 shipped straight to them, not into your stock. You do not change the product. You open that single order, set its build-to-inventory flag to no, and save. When it schedules and completes, those 40 units ship to the customer and post no receipt. Every other valve-body order still builds to stock exactly as before. You handled the exception at the order level and left your standard stocking behavior untouched.

If special runs became the norm rather than the exception, you might instead put the product on the make-to-stock-with-override method, which anticipates exactly this: default to stock, flag the odd order as direct. Same resolution rule, different starting assumption.

When to Reach for the Hybrid Method

The plain make-to-stock method and the hybrid make-to-stock-with-override method behave identically for a blank order flag: both build to stock. The difference is intent and expectation. Use plain make-to-stock when direct shipments are genuinely rare and you are happy overriding the odd order by hand. Use the hybrid method when you know a meaningful slice of orders will go direct, so the product's policy documents that exceptions are expected and normal.

Either way, the mechanism underneath is the same per-order flag. The hybrid method does not add new behavior; it signals a design where overriding is part of the plan.

Keeping the Override Deliberate

The override is powerful because it is precise: one order, one decision, no ripple to the product or its other jobs. Keep it deliberate. Set the product default to the common case, leave most order flags blank, and reach for an explicit yes or no only when a specific job needs to break from the norm. Read the flag, then the product method, then the stocked setting whenever an order's inventory behavior surprises you.

For how a stock build refills inventory, read how a build-to-stock job replenishes inventory, and to weigh the two policies against each other, read make-to-stock vs make-to-order in EDGEBIC. For the general trade-off, see make-to-stock and make-to-order.