Make-to-Stock vs. Make-to-Availability (MTS vs. MTA) §

Concept: Vocabulary that names a phenomenon.

The distinction between producing stock against a forecast and committing to reliable availability for selected repeat items, with stock buffers, buffer status, and replenishment priorities replacing forecast-push execution.

Also known as: MTS vs. MTA; make-to-availability; availability-based replenishment.

Make-to-Availability (MTA) is not a friendlier name for make-to-stock. It changes the promise. Conventional make-to-stock (MTS) produces ahead of demand because the firm expects future orders. MTA commits to availability for a chosen set of repeat items at a chosen location, then builds the production and replenishment rules needed to keep that promise with minimum stock.

That promise matters because customers don’t buy an average forecast. They buy a specific item now, from a specific stock point. If production lead time is longer than the customer’s tolerance time, the producer has to hold finished goods somewhere. MTA says the right question isn’t “how much should the forecast tell us to make?” It is “what stock buffer must sit where, and how will consumption pull it back to target?”

Context §

The distinction sits between Drum-Buffer-Rope, S-DBR, and Replenishment Pull. DBR and S-DBR protect customer due dates in make-to-order environments through time buffers and release rules. Replenishment Pull protects availability in distribution by replacing what was consumed. MTA is the production-side policy that connects those two ideas: stock is produced for availability, but production orders are still controlled by TOC flow logic rather than by local efficiency or forecast batch economics.

Eli Schragenheim’s TOC Handbook chapter on MTS and MTA frames the issue as a planning and execution problem. A stock order doesn’t have the same due-date meaning as a customer order. For most repeat items, the completion date on a stock order is only a priority device. The real priority comes from the finished-goods stock buffer: how much of the target is missing, what is already in the pipeline, and how close the item is to a red or black status.

The TOCICO Dictionary defines MTA as both a marketing commitment and the production policies required to honor it. That pairing is important. Without the market commitment, the company is merely producing for stock. Without the operating policy, the commitment is a sales promise the plant can’t keep.

What It Is §

MTS is a push manufacturing strategy. The firm makes stock ahead of customer orders, usually from a forecast, with lot-sizing rules such as EOQ, min-max, or reorder points shaping how much to make. The method accepts the familiar result: some items have too much stock, other items stock out, and the planner responds by tuning the forecast, changing reorder points, or adding inventory.

MTA is a TOC policy for repeat items whose customer tolerance time is shorter than production lead time. The firm selects the items and locations for which it will promise immediate or near-immediate availability. It defines a finished-goods stock buffer target for each SKU-location pair, keeps the larger useful buffer at the plant or central warehouse, and replenishes downstream points from actual consumption.

The operating rules are simple enough to state and hard enough to hold.

First, define the availability promise. The commitment is not “unlimited quantity at any time.” It applies to selected items, selected locations, and a reasonable maximum immediate demand from one customer. Large one-time orders are treated as make-to-order commitments with quoted lead times.

Second, create the finished-goods stock buffers. The initial targets are rough. Schragenheim argues that an approximate target launched quickly and adjusted through Dynamic Buffer Management beats a precise target calculated slowly. The target is based on expected consumption during replenishment time, adjusted for the unreliability of that time.

Third, replenish what was consumed. A sale from the finished-goods buffer creates the need to bring that SKU-location buffer back to target. The replenishment quantity is the target minus the on-hand and in-transit stock, subject to minimum batch rules when setup time would otherwise consume too much protective capacity.

Fourth, prioritize by buffer status. Production orders for stock are not sequenced by artificial due dates. Green, yellow, red, and black status show how much protection remains. Red and black items get attention before green items. When both MTO and MTA orders are present, the color status supplies the common priority language across time buffers and stock buffers.

Fifth, monitor capacity. MTA needs protective capacity at the capacity-constrained resource. If daily replenishment creates too many setups or the planned load on the CCR rises beyond the replenishment-time limit, the system delays lower-priority releases, uses minimum batches, adds capacity, or narrows the availability commitment. A policy that promises availability while consuming all its protective capacity has stopped being MTA.

How It Is Measured or Recognized §

A practitioner recognizes MTA by looking for five signals.

The market promise is explicit. Sales can say which products are available immediately, where, and up to what one-time demand limit. If the promise is vague, the plant can’t know which buffers deserve protection.

The plant or central warehouse is the control point. Finished-goods stock buffers sit at the point where demand from many downstream links is aggregated. Retailers, distributors, or regional warehouses may hold smaller local buffers, but the plant or central warehouse status drives production priority.

Consumption drives replenishment. The daily question is not whether the forecast was met. It is how much was consumed and how much is missing from the target after on-hand and in-transit stock are counted.

Buffer status drives execution. Open production and replenishment orders carry green, yellow, red, or black status. Operators don’t need to know whether an order began as MTO or MTA to choose the next priority; they need the color and the degree of penetration.

Dynamic Buffer Management changes the target. Too much green signals an oversized target. Too much red signals an undersized target, a supply disruption, a capacity problem, or a demand shift. The organization investigates before changing the target, then gives the change time to settle. It doesn’t let software blindly resize buffers after every fluctuation.

Why It Matters §

MTA is the bridge that prevents supply-chain TOC from splitting into a separate doctrine. The same logic is visible across the system: improve flow, prevent overproduction, manage by the constraint or control point, and read execution through buffers. In MTO the buffer is time. In MTA the buffer is stock. The object changes, but the managerial question stays the same: what protection is being consumed, and what action preserves throughput?

The distinction also dissolves a common false choice. Conventional MTS asks the organization to choose between excess inventory and poor availability. MTA reframes the decision in Throughput Accounting terms. Availability protects Throughput (T). Finished-goods buffers consume Inventory (I). More frequent replenishment, smaller batches, and extra capacity protection may change Operating Expense (OE). The decision is the combined T-I-OE move, not the local cost of one shipment or one setup.

For certification-track readers, the vocabulary boundary is load-bearing. A stock buffer is not a shipping buffer. A stock order doesn’t have the same due-date logic as a customer order. MTA isn’t a kanban loop or a forecast-push policy with TOC colors painted on top. It is a named production and replenishment policy with its own commitment, buffer object, priority rule, and capacity discipline.

Common Misunderstanding §

“MTA is just MTS with better forecasting.” It isn’t. Forecasting may still help with capacity, seasonality, and unusual demand shifts, but daily replenishment is driven by consumption and buffer status. The forecast stops being the execution trigger.

“Availability means every customer gets any quantity immediately.” It doesn’t. MTA requires an explicit limit on immediate demand. A customer who wants a large exceptional quantity receives an MTO quote, or the promise destroys the very protective capacity it depends on.

“The buffer target is the forecast.” It isn’t. The target is an operating protection level. It starts as a rough estimate of consumption during replenishment time and is then adjusted from behavior: too much green, too much red, repeated stockouts, supply instability, or capacity pressure.

“Stock buffers and time buffers are interchangeable.” They aren’t. MTA uses stock buffers to protect availability. DBR, S-DBR, and CCPM use time buffers to protect due-date commitments. Both use Buffer Management, but the managed object differs.

“Every make-to-stock item should become MTA.” Not necessarily. New products, short promotions, very short shelf-life items, products with extreme demand uncertainty, and items whose market position is deliberately “hard to get” may remain MTS. MTA belongs where the organization can make a credible availability commitment and run the operating discipline behind it.

Related Articles §

Sources §