Production

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

Make to Order vs Make to Stock for Apparel Brands: How to Choose (2026)
By Shubham Singh · Reviewed by Ronnell Parale · · 8 min read

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 question becomes how to design the hybrid.

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 operating system architecture affects the ability to run a hybrid cleanly.

What is make-to-order vs make-to-stock?

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 on different points of the spectrum.

What are the operational implications of each model?

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 don’t 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. Retailers do not accept the lead times of MTO.

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.

Customer-acceptance dependency. The model only works for customers willing to wait. Impulse DTC purchases typically aren’t.

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

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.

What four operating-model questions determine MTO vs MTS fit?

Four questions narrow the choice for apparel brands.

Question 1: 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.

Question 2: 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.

Question 3: 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.

Question 4: 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.

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 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.

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.

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.

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.

Reporting rolls up MTS, MTO, and reactive separately so leadership can see how each layer is performing without the layers obscuring each other.

How does the 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.

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.

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 don’t reflect operational truth.

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.

In a connected operating platform, 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.

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.
  • Operating systems designed for a single mode produce drag when brands need to run hybrids; the structural fix is a connected operating platform that handles all three modes.

If your apparel brand is running a hybrid production model and the operational drag is growing, the right next step is a discovery conversation about your specific layer mix rather than a feature comparison. Book a tailored demo and we will map your production model to what an apparel-native operating platform would handle natively.

6 Breakpoints Framework

Where is your operation on the 6 Breakpoints curve?

The assessment scores your apparel operation across all six breakpoints (product data, production, inventory truth, order flow, warehouse execution, reporting) and identifies which one is hurting you most.

Frequently asked questions

S
Written by
Shubham Singh
Solutions Consultant, Apparel Operations, Uphance

Shubham writes about evaluating ERP fit, assessing operational complexity, and how apparel brands can tell whether their current systems are helping or holding them back.

R
Reviewed by
Ronnell Parale
Head of Customer Success and Onboarding, Uphance

Ronnell writes about onboarding, adoption, and operational readiness for apparel brands moving to a connected platform. His articles focus on what it takes to go live with confidence and sustain strong execution across channels, warehouses, and teams.

More from the blog