- Home
- Blog
- Glossary (EDGEBIC)
- Make-to-Stock vs Make-to-Order: What Is the Differ…
Make-to-Stock vs Make-to-Order: What Is the Difference?
Make-to-stock builds product ahead of demand and holds it in inventory ready to ship, while make-to-order builds nothing until a customer order exists and then produces to that specific order. The two policies sit at opposite ends of the inventory-versus-lead-time trade. Make-to-stock spends inventory to buy fast delivery; make-to-order spends lead time to avoid holding stock. Which one fits depends on whether the item is standard and predictable or custom and variable.
This entry defines the two policies and shows how they behave inside EDGEBIC by User Solutions. For the wider index of planning terms, see the manufacturing glossary, and for the mechanism that consumes make-to-stock inventory, see consume-from-stock netting. A generic comparison also lives at make-to-stock vs make-to-order; this entry takes the planner-facing view of how the policy drives the plan.
How it works
The book's analogy captures it in two images. Make-to-stock is a supermarket's bread aisle: loaves are baked each morning and sit on the shelf until a customer picks one up. The customer waits seconds because the work was done ahead of the order. Make-to-order is a custom wedding cake: nothing is baked until the couple orders a specific design, and then it is built to that order alone. The customer waits days because the work starts only after the commitment.
That distinction cascades through the whole plan:
- Inventory posting. A make-to-stock order that completes posts a receipt into the ledger, adding finished goods to stock. A make-to-order order posts no receipt; its output ships direct.
- Demand handling. Make-to-stock products carry a projected balance, respond to forecast, and can trigger replenishment when stock runs low. Make-to-order products ignore forecast entirely and are driven only by firm orders.
- Consumption. When demand arrives for a make-to-stock item with stock on hand, the engine can satisfy it from the shelf instead of building. A make-to-order item is always built to its order.
Because the two behaviors are so different, the policy is a first-class product attribute, and most real shops carry a mix of both across their catalog.
A concrete example
Widget A is a standard product set to make-to-stock. A build order for 200 completes and posts a +200 receipt to the ledger, so 200 units now sit in finished goods. A customer order for 80 arrives; because stock exists, the engine satisfies it from the shelf and posts an 80-unit issue, leaving 120 on hand. The customer waited only as long as it took to pick and ship, because the build happened ahead of the order.
Now consider a custom fixture set to make-to-order. No stock is held. When a customer orders three, the scheduler builds exactly three against that order, ships them, and posts no receipt to inventory. The next order will trigger another build from scratch, because nothing was made ahead.
A hybrid case ties the two together. A normally make-to-order shop occasionally needs to build a standard sub-part for stock. Rather than create a second part number, the planner overrides that one order to build to inventory, and its output posts a receipt like any make-to-stock build, while every other order for the part stays make-to-order.
How EDGEBIC uses it
In EDGEBIC, the policy lives on each product as a build method with three settings: make-to-order, make-to-stock, and a hybrid make-to-stock-with-override. The default drives whether the product carries a projected balance and replenishment logic and whether completed builds post receipts. A companion stocked flag gates all inventory activity for the product; a make-to-stock product must be marked stocked or netting is skipped, a mismatch an inventory anomaly check flags.
Individual orders can override the product default through a per-order build-to-inventory setting. Left blank, the order inherits the product policy; set explicitly, it forces make-to-stock or make-to-order for that order alone. The resolution rule is straightforward: the order's flag wins when present, otherwise the product policy applies. This lets one part number serve both a steady make-to-stock stream and the occasional customer-specific build without duplicating master data.
For a full walkthrough of both policies and the override in action, read make-to-stock vs make-to-order in EDGEBIC. To see how make-to-stock inventory is drawn down at schedule time, continue with consume-from-stock netting, and to understand the balance that make-to-stock products carry, see projected available balance.
Expert Q&A: Deep Dive
Q: We build the same bracket both for stock and against specific rush orders. Do I need two part numbers?
A: No. Set the product's default build method to the policy you use most, then override individual orders with the per-order build-to-inventory flag for the exceptions. If the bracket is normally built ahead for stock, leave the product make-to-stock and flag the occasional customer-specific rush order as make-to-order so it ships direct without touching inventory. If it is normally custom, do the reverse. The resolution is simple: the order's flag wins when set, and it inherits the product policy when left blank, so one part number covers both behaviors.
Q: I switched a product from make-to-order to make-to-stock and now it ignores stock I know is on the shelf. What happened?
A: The most likely cause is that the product is not flagged as stocked, so all inventory netting, receipts, and replenishment are skipped for it even though the build method now says make-to-stock. A make-to-stock product that is not marked stocked is a known misconfiguration that an anomaly check watches for, because the netting path silently bypasses it. Confirm the stocked flag is on. Once it is, the projection will count the on-hand and the scheduler will consume from it before building.
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
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.
Share this article
Related Articles
The EDGEBIC Scheduling Glossary Index
A themed index to the EDGEBIC glossary: scheduling engine, capacity and calendars, materials and planning, shop floor, reporting, quoting, and data import terms, defined in plain language.
What Is the Critical Chain in Manufacturing Scheduling?
The critical chain is the longest dependent path through a plan once shared machine contention is counted, not just step precedence. Here is how it differs from the critical path.
What Does Finite Capacity Mean in EDGEBIC?
Finite capacity means the scheduler refuses to book more hours on a machine than that machine actually has. See exactly how EDGEBIC enforces it, day by day and shift by shift.
