Inventory & Planning

How a Build-to-Stock Job Replenishes Inventory

User Solutions TeamUser Solutions Team
|
8 min read

A build-to-stock job replenishes inventory by acting as a supply event: its finished quantity is incoming supply that the projection nets into the projected available balance on the job's completion date, lifting the balance from that bucket forward and clearing a below-safety warning if it lands in time. In EDGEBIC by User Solutions a job you run to stock rather than against a specific order is the make equivalent of a purchase receipt, and it plays the same role in the replenishment picture. This post looks at the job from the inventory side: how it lifts the balance, when it lands, and what it takes to clear a breach.

Build-to-stock is one half of a pairing. For how building to stock and consuming from stock work together across a routing, read how build-to-stock and consume-from-stock work together, and for an end-to-end narrative, see the make-to-stock replenishment walkthrough. This post stays on the single idea of the job as a supply event. Inventory features vary by installation, so check which planning capabilities your build exposes.

A Job Is a Supply Event

The projection nets demand against supply in every planning bucket. Purchase receipts are the obvious form of supply: units bought from a vendor that arrive on a date and lift the balance. A build-to-stock job is the other form. Instead of buying units to replenish stock, you produce them, and the finished quantity is incoming supply exactly as a receipt is.

The distinction that matters is what the units serve. A make-to-order job produces for a specific sales order and is consumed by that order. A build-to-stock job produces for general inventory, and its output goes into on-hand to be drawn down by whatever demand consumes it later. That decoupling is the whole value of building to stock: production runs ahead of demand, and later orders pull from a shelf that is already filled.

From the projection's point of view, then, a build-to-stock job is a promise of stock on a date. Until the job completes, the promise is future supply; when it completes, the units are on-hand and the promise is kept. The balance treats the completion the way it treats a receipt landing.

The Completion Date Is What Counts

A build-to-stock job has a start and a finish, but only the finish changes the balance. The job starting consumes capacity and components; the job finishing produces the units. Inventory is replenished when the finished goods are received into stock, which happens on the completion date, not the start.

That timing is the single most important thing to get right when a job is meant to fix a shortage. The projection lifts the balance in the bucket where the job completes and carries the higher balance forward from there. Buckets before the completion see nothing: the units do not exist yet. So a job scheduled to finish in week 6 does nothing for a breach in week 4, no matter how early it started.

This mirrors exactly how a purchase receipt behaves in the projected balance: supply lifts the balance from its arrival forward. The only difference is that a build-to-stock job's arrival date is a completion you control through the schedule, so if the finish lands too late, you can pull the job earlier or start it sooner rather than waiting on a supplier.

Clearing a Below-Safety Warning

A build-to-stock job is the natural response to a below-safety warning. The projection flags a red bucket where the balance drops under the buffer that absorbs demand variability; a build job produces the units to lift the balance back above it.

For the job to clear the warning, two conditions have to hold. First, the completion date must land in or before the first red bucket, so the units arrive before the breach rather than after it. Second, the finished quantity must at least cover the shortfall below the buffer, so the lifted balance clears the safety level rather than falling just short of it. Meet both and the netting adds the finished quantity in on the completion date, and the red clears from that bucket forward.

If the red does not clear, it is almost always one of those two conditions. The job finishes after the red bucket, so its supply lands too late, or the quantity is smaller than the gap, so the balance rises but not above the buffer. A third case is that the job is still a suggestion rather than a committed job: like a purchase suggestion, a proposed build does not change the balance until it is firmed. Firm the MPS quantity into a job and it becomes real supply the projection can net in.

A Worked Example: Building Ahead of a Week-5 Breach

Take a finished assembly you build to stock. On-hand today is 200, forecast demand is 50 a week, and safety stock is 100. No supply is inbound, so the projection walks the balance down: week 1 at 150, week 2 at 100, week 3 at 50. Week 3 breaches the 100 buffer and week 5 would sit at zero, so the projection paints week 3 forward red and names week 3 as the first buffer breach.

You decide to build to stock rather than buy. A build job for 300 units will lift the balance well clear of the buffer. The job takes two weeks to run, so if you start it now it completes at the end of week 2. On the completion date, the projection nets 300 in: week 3's balance jumps from 50 to 350, and the red clears from week 3 forward. The build landed one bucket before the breach, with enough quantity to cover it, so both conditions are met.

Now suppose the schedule cannot start the job until week 3, completing in week 5. Week 3 and week 4 stay red, because the units do not exist until week 5, and the projected stockout still shows week 3. The fix is not a bigger job; it is an earlier finish. Pull the job forward or start it sooner so the completion beats the breach. The quantity was never the problem; the timing was.

Building to Stock as Part of the Plan

A build-to-stock job is where the plan meets the schedule. The projection decides that a part needs replenishing and by when; the schedule decides whether a build can complete in time. When the two agree, the job clears the warning cleanly. When they do not, the projection tells you the finish is too late and the schedule is where you fix it.

That is why building to stock is a planning decision with a scheduling consequence: you choose to produce ahead of demand, and the completion date has to beat the breach for the choice to pay off. For where this fits in the wider workflow, start from the EDGEBIC planning guide, and to see how completing a job and consuming its output net against each other, read how a scheduler nets demand against inventory.

Expert Q&A: Deep Dive

Q: We build a part to stock rather than buy it. When does that job actually lift our projected balance?

A: It lifts the projected balance in the bucket where the job completes and the finished units are received into stock, not when the job starts. A build-to-stock job is incoming supply, so the projection nets its finished quantity in on its completion date the same way it nets a purchase receipt. Confirm the job's scheduled finish lands in or before the bucket that was breaching your buffer, because a job that completes after the breach does not clear it. If the finish is too late, pull the job earlier or start it sooner so the receipt beats the shortage.

Q: Our projected balance still shows red after we created the build job. Why has it not cleared?

A: Most often the job is scheduled to finish after the red bucket, so its receipt lands too late to help, or the quantity is smaller than the shortfall. Check the job's completion date against the first red bucket: the supply only lifts the balance from its finish forward. Also confirm the job is committed rather than a suggestion, and that its finished quantity at least covers the gap below the buffer. Once a firmed job completes in or before the breaching bucket with enough quantity, the netting adds it in and the red clears from that bucket on.

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