Make to Order vs Make to Stock for Apparel Brands: How to Choose (2026)

It is Tuesday morning at a $22M contemporary brand. The ops lead is staring at a customer order for two shirts and one made to measure jacket. The shirts can ship today from the New Jersey 3PL. The jacket needs eight weeks at the Portugal factory. The order entry tool treats both lines the same. The customer gets one shipping confirmation in eight weeks, or the team manually splits the order in two systems and hopes the warehouse pick list matches. This is the make to order versus make to stock decision in practice, and it is rarely as clean as the textbook version.

The choice between make to order and make to stock is one of the most consequential operational decisions an apparel brand makes. It shapes capital allocation, lead times, inventory risk, customer experience, and the production calendar. Most brands frame the decision as binary, then discover that running one mode for everything produces problems the other mode would have solved. The practical answer for apparel brands $5M to $100M is almost always a hybrid, and the real question is how to design the hybrid so the operating record does not fracture.

This guide explains the two production models, the four operating model questions that determine fit, the typical hybrid structure most apparel brands run, and how system architecture affects the ability to run a hybrid cleanly.

What is make to order versus make to stock in apparel?

The two models differ on when production happens relative to demand.

Make to stock (MTS). Production runs based on demand forecasts. Finished units enter inventory before any specific customer order has been received. When orders arrive, they ship from existing stock. The model trades inventory risk (units may not sell) for short customer-facing lead times.

Make to order (MTO). Production runs against confirmed customer orders. The order arrives, the production process starts, and the finished unit ships when production completes. The model trades long customer-facing lead times for capital efficiency (no inventory until paid for).

The two models are operational endpoints of a spectrum. Most apparel brands operate somewhere between them, with different products sitting at different points. A brand can run a core tee program as pure MTS, a capsule collection as MTO, and an in-season trend response as something in between. The choice is per product line, not per company.

What are the operational implications of each model?

From the go-lives I have run this year, the pattern is consistent: brands underweight how much of their operating rhythm shifts when they move a product line from one mode to the other. The cash, the calendar, and the customer experience all change at once.

Make to stock implications

Capital tied up in inventory. The brand pays for landed cost, holding cost, and obsolescence risk on units that have not yet generated revenue. For a $15M apparel brand, inventory at cost typically runs $2M to $5M.

Short customer-facing lead times. DTC orders ship in 1 to 7 days. Wholesale orders ship within retailer-specific commitments (often 5 to 30 days from PO).

Inventory risk. Units that do not sell become markdown candidates, then carryover, then write-downs. End-of-season markdown rate for typical apparel categories runs 15 to 35 percent.

Forecasting dependency. Production decisions depend on accurate demand forecasts. Forecast misses produce either stockouts (lost sales) or overstock (margin erosion).

Retailer compliance. Wholesale-heavy operations need MTS to meet retailer commitment dates. Major retailers do not accept MTO lead times on commodity programs.

Make to order implications

Minimal inventory capital. Production capital is committed only when a customer has paid (or committed). For brands running pure MTO, finished goods inventory approaches zero.

Long customer-facing lead times. Production-driven lead time runs 4 to 12 weeks depending on factory location, fabric availability, and complexity.

Eliminated inventory risk. Every produced unit has a buyer. Markdown exposure on the MTO portion is effectively zero.

Customer acceptance dependency. The model only works for customers willing to wait. Impulse DTC purchases typically are not.

Production scheduling complexity. Production runs are smaller and more frequent, which raises per-unit production costs (CMT) and complicates factory relationships that prefer larger committed runs.

The implications cascade through the operating model. MTS produces a different kind of business than MTO, with different cash flow, different customer experience, and different operational rhythm. A brand that started DTC-led on MTO and then won wholesale accounts often discovers six months later that the production calendar built for MTO cannot meet retailer ship windows.

What four operating model questions determine MTO versus MTS fit?

Four questions narrow the choice for apparel brands.

How predictable is demand?

For products with stable, predictable demand (core basics, replenishment programs, classic styles that sell consistently year over year), MTS is the natural fit. The forecast is reliable, the inventory risk is bounded, and the capital efficiency cost is acceptable.

For products with volatile or unpredictable demand (limited edition drops, trend-reactive collections, customization), MTO reduces the inventory risk that volatile demand creates. The product where last year’s sell-through gives almost no signal for this year’s volume belongs in MTO, not MTS.

How long can the customer wait?

For products where customer-facing lead time matters (impulse DTC, replenishment-driven wholesale, marketplace velocity), MTS is the only operationally viable choice.

For products where customers tolerate longer lead times (luxury, made to measure, high-priced considered purchases, sustainable positioning brands where waiting is part of the value proposition), MTO is acceptable. The wait can even become part of the brand story, but only when the product price and positioning support it.

How constrained is capital?

Capital-constrained brands benefit from MTO’s reduced inventory commitment. Brands with abundant capital can run MTS more aggressively, accepting the inventory risk in exchange for short customer lead times and operational simplicity.

The capital constraint is dynamic. Brands that grow into MTS positions during high-capital periods often need to dial back during tight-capital periods, which creates operational friction if the systems and processes are tuned only for one mode. A brand that raised a Series B and built an MTS-heavy inventory position can find itself, eighteen months later, trying to retrofit MTO discipline into systems that assume finished goods always exist on day one.

What channel mix does the brand run?

Wholesale-heavy operations need MTS to meet retailer commitment dates. Wholesale buyers commit at trade shows, retailers expect deliveries on agreed dates, and any production delay is a chargeback or a cancelled order.

DTC-heavy operations have more flexibility. DTC customers can accept varied lead times if the product positioning supports it. Marketplaces vary. Amazon expects fast shipment, while specialty marketplaces can accommodate longer lead times. A brand that runs 70 percent wholesale and 30 percent DTC has a very different MTO ceiling than a brand with the inverse split.

What does the typical apparel hybrid actually look like?

For apparel brands $5M to $100M, the practical answer is a hybrid that combines both models on the same operating platform.

The typical three-layer structure

MTS layer (60 to 80 percent of revenue): core styles with predictable demand. Year-round basics, replenishment programs, signature pieces that sell consistently. Production runs are larger, lead times are longer (6 to 12 months from design to retail), and inventory commitments are sized to forecasted demand plus safety stock.

MTO layer (10 to 25 percent of revenue): limited edition drops, capsule collections, made to measure or customization, and high-priced items where customers tolerate longer lead times. Production runs against orders or against very small forecasted batches.

Reactive layer (5 to 15 percent of revenue): in-season production that responds to trend signals from social media, retailer feedback, or sell-through data. Lead times are compressed (4 to 8 weeks), batch sizes are smaller, and the model trades higher per-unit cost for the ability to capture trends that emerge after the season was planned.

The proportions vary by brand and category. A wholesale-heavy basics brand may run 90 percent MTS and 10 percent reactive. A DTC-led drop brand may run 30 percent MTS, 50 percent MTO, and 20 percent reactive. A luxury brand may run nearly pure MTO. The right mix is operating model specific, and any benchmark that prescribes a universal split is overfitting.

How the hybrid works in practice

The hybrid is not just a financial allocation. It is an operational reality that touches PLM, production, inventory, orders, and reporting.

PLM must support both deeply spec’d MTS styles (months of design and sample iteration) and faster MTO development (compressed timelines, often customer-input-driven for made to measure).

Production runs MTS in larger batches with longer factory commitments and MTO in smaller batches with faster turnarounds. Factory relationships and capacity have to support both, and the production calendar has to reserve room for reactive batches that did not exist when the season was planned.

Inventory tracks MTS finished goods in normal warehouse stock and MTO in either zero stock (pure made to order) or in-process stock (production has started against confirmed order). The two states need different reporting and allocation logic. An MTO unit that is 60 percent through production is not the same as an MTS unit on the shelf, and treating them as equivalent in reporting hides the truth.

Orders distinguish between standard orders (drawing from MTS inventory, ship in days) and custom orders (triggering MTO production, ship in weeks). The customer experience and the internal workflow are different, and the order management layer has to surface both correctly.

Reporting rolls up MTS, MTO, and reactive separately so leadership can see how each layer is performing without the layers obscuring each other. A blended sell-through number that mixes all three layers is operationally useless.

How does operating system architecture affect hybrid execution?

The hybrid only works cleanly when the operating system handles all three layers simultaneously. Most apparel brands have systems designed primarily for one mode and adapted with workarounds for the others. This is where the hybrid model meets the second breakpoint (production and supply execution drifting from the plan) and the fourth (order flow becoming harder to trust).

In a fragmented stack, MTS lives in the inventory and order systems, MTO lives in a separate production management tool or spreadsheets, and reactive production lives wherever the operations team can fit it. The fragmentation produces three problems:

Order acceptance complexity. A customer orders one MTS item and one MTO item. The order should ship the MTS portion immediately and the MTO portion when production completes. Without unified order workflow, the team manually splits orders, which introduces error and customer experience friction. Multiply that by a few hundred mixed orders a month and the customer service burden becomes structural.

Inventory reporting opacity. Total inventory at cost includes finished MTS goods, in-process MTO production, and reactive batches in various stages. Without unified inventory states, the reports do not reflect operational truth. The CFO sees one number, the warehouse sees another, and the production lead sees a third.

Production planning conflicts. MTS forecasts and MTO orders compete for the same factory capacity. Without unified production planning, the team chooses between hitting MTS commitments and meeting MTO deadlines. The choice gets made on the loudest email of the week rather than on operating logic.

In a connected operating platform like Uphance, all three layers share the operating record. MTS forecasts, MTO orders, and reactive production all flow through the same production planning. Inventory states distinguish finished, in-process, and reserved stock. Order workflow handles split orders natively. Reporting shows the three layers separately and combined.

For apparel brands trying to run a hybrid model on systems designed for a single mode, the operational drag eventually forces a system change. The brands that run hybrid cleanly typically either started with apparel-native operating platforms or migrated to one specifically because the hybrid became unmanageable. The trigger is rarely a strategic decision. It is usually a missed retailer ship window or a customer complaint that exposes how much of the operation was being held together by one person’s spreadsheet.

Key takeaways

Make to order produces against confirmed orders; make to stock produces ahead of demand into inventory. The choice is rarely binary for apparel brands $5M to $100M. Most run a hybrid combining MTS, MTO, and reactive production. Four questions determine fit per product: demand predictability, lead time tolerance, capital constraint, and channel mix. The typical apparel hybrid is 60 to 80 percent MTS for core styles, 10 to 25 percent MTO for limited editions, and 5 to 15 percent reactive for in-season trend response. Hybrid execution requires PLM, production, inventory, orders, and reporting that handle all three modes simultaneously.

What this means for an apparel operations team

The operational question is not whether to choose MTO or MTS. It is whether the systems can hold the hybrid without forcing the team to reconcile it manually every week. Three diagnostic checks usually settle it. First, can the order management layer split a single customer order into an MTS line that ships today and an MTO line that ships in eight weeks, without anyone keying the split into a second system? Second, does the inventory report distinguish finished, in-process, and reserved stock by mode, or does it collapse them into one number? Third, can production planning see MTS forecasts and MTO orders competing for the same factory slot, or does the planner discover the conflict only when the factory pushes back?

If the answer to any of the three is the spreadsheet, the operation is running on workarounds. The structural fix is a connected operating record that treats MTS, MTO, and reactive as first-class modes rather than exceptions. That is where the 6 Breakpoints framework points: production drift, inventory truth, and order flow are the three breakpoints most likely to fail first under hybrid load, and they fail together.