Quick Response (QR)
In 1985 the American Apparel Manufacturers Association funded a study by Kurt Salmon Associates that asked one question: why does it take a US apparel company 60 weeks to move a garment from raw cotton to a retail rack when a Japanese auto company can move a car from raw steel to a dealer lot in 14 days? The answer they wrote — "Quick Response" — became the most consequential supply-chain methodology in modern apparel. Then American apparel mostly forgot it. And Inditex absorbed it. What we now call "fast fashion" is essentially what the 1985 QR thesis predicted, executed by the one organisation that took the report seriously.
How it works
Quick Response is Toyota's Production System (TPS) translated to the apparel supply chain. The core insight, transposed: the long lead times in apparel are not caused by the actual cut-and-sew work (which takes 2–5 days for a kurta, ~3 weeks for a complex jacket); they are caused by the wait states between functions. Cut a kurta in a week, ship it in a week, store it in a week, allocate it in a week — and the manufacturing time gets buried by the queue.
QR removes the queues. The five core moves:
- Electronic Data Interchange (EDI) between retailer and vendor. The retailer's sell-through data goes directly into the vendor's production plan. No phone calls, no weekly emailed reports, no waiting for the buying-team summary.
- Smaller batch sizes. Instead of one 50,000-unit production run, run twenty 2,500-unit batches. Each batch reads the market's reaction to the previous batch.
- In-season replenishment. Hold back 30-50% of seasonal OTB (Open-to-Buy) for in-season redeployment. Re-order what's selling; cut what's not.
- Vendor capacity blocking. Pre-book vendor capacity for the season; specific styles slot into the blocked capacity as the read comes back from stores.
- POS-up data flow. The cashier's scan in the store is the input to the buy. Not the runway, not the trend deck — the customer's actual purchase.
The architectural insight: QR is not about manufacturing faster. It is about feeding back the market signal faster, so the manufacturing capacity you've already booked produces the right thing. Every step is a function of information flow, not factory speed. A vendor that ships a kurta in 21 days but doesn't know until week 14 what to ship has a 35-week effective cycle. A vendor that ships in 21 days and knows by week 2 what to ship has a 23-week cycle. Same factory, different cycle.
Where it shows up
| Year | Move | What it confirmed |
|---|---|---|
| 1985 | Kurt Salmon QR study published | First formal translation of TPS into apparel terms |
| 1986–1990 | VF Corporation pilots QR with Walmart | Wrangler/Lee jeans hit ~3-week replenishment; benefit accrues mostly to Walmart, not VF |
| 1989 | Levi Strauss "LeviLink" EDI program | Early EDI standardization for apparel |
| 1990s | Most American apparel brands adopt QR rhetoric, abandon in practice | Without organisational discipline, QR becomes a slide deck; the wait states return |
| 1996 | Inditex (Zara) reaches ~2-week design-to-store on European-sourced items | The QR thesis executed end-to-end, not piecemeal |
| 2000s | H&M, Mango, Gap attempt partial QR | Without vertical control of vendor + DC + retail, the model breaks at the seams |
| 2010s | Shein digitises QR with the "5-200-5000" ramp model | QR becomes algorithmic; humans no longer mediate the read-and-react loop |
| 2014 | Trent (Zudio) operational launch | The first true QR-native Indian apparel chain |
| 2020s | Trent's sub-25-day floor-to-shelf cycle becomes the Indian QR benchmark | Indian textile cluster proves capable of QR at scale |
The honest historical pattern: QR is technically simple and culturally hard. The five moves require buying, planning, supply chain, IT, and store operations to share decision rights they previously hoarded. Most organisations cannot survive the political work required to ship QR — and so they ship the slide deck instead.
What's contested
Whether QR can compose with India-only sourcing. Inditex's QR runs on proximity sourcing (Galicia, Portugal, Morocco) where transit times are 2-5 days to European DCs. Indian apparel retail sourcing within India (Jaipur, Surat, Delhi NCR) has 2-7 day transit to Indian DCs — geographically equivalent. The contested view: yes, Indian QR is fully composable; the bottleneck is vendor-side discipline, not geography. The opposing view: India's textile cluster has too many small vendors with inconsistent capacity to support QR's tight feedback loop; the model breaks below a certain vendor scale. The 2026 evidence (Zudio's sub-25-day cycle) favours the optimistic view, but Zudio sources at high volumes per vendor — a higher-fragmentation buyer may have different unit economics.
Whether QR's POS-up signal is degraded by online shopping. The original QR thesis assumed the store cashier scan was the signal. In 2026, ~30-40% of apparel demand in India is online. The contested view: the online cart is a stronger signal than the store cashier (richer metadata, faster aggregation). The opposing view: online demand is more elastic and less indicative of long-term preference — the store cashier scan is "a person literally paid for this", which is the strongest possible signal.
Whether QR scales below sub-Rs 999 price points. At sub-Rs 999, unit margin is thin enough that the upstream investment in EDI + capacity blocking + smaller batches may not pay back. The contested view: QR at value points requires higher volume to amortise the upstream cost; Zudio + Shein prove this works above ~$500M annual revenue. The opposing view: smaller value players struggle to break the QR cost floor — they would be better served by a non-QR buying-house model with lower upstream investment.
How to use it
For any supply-chain conversation in fashion in 2026, the diagnostic is: does this brand do all five QR moves, or just some? Brands that pick three of the five end up with QR theatre (slide decks, dashboards) without QR economics (gross-margin uplift, full-price sell-through, weeks-on-shelf compression).
The brand-by-brand 2026 read:
- Inditex: all five, end-to-end
- Trent (Zudio): four (EDI is partial), but the rest tight
- Shein: all five, digitised
- Most Indian large-format retail through 2024: one or two
- ABFRL (legacy brands): two or three; OWND launch is explicitly designed to add the missing ones
The honest cut: QR's hardest move is (4) vendor capacity blocking — it requires the buyer to commit to a vendor before knowing what to buy. Buyers culturally resist this; planning teams insist on it. The brand that solves the cultural side of QR before it solves the technical side compounds; the brand that solves only the technical side ends up with shelves full of unsold inventory and a dashboard nobody reads.
Related
- concept inditex playbook — the operational template QR underlies
- concept zudio playbook — QR adapted for Indian value retail
- concept toyota production system — the source methodology
- concept vendor as factory floor — the operator-side reframe of QR
- speed to market realm — broader cycle-time discipline
Abhishek's take
I see QR fail at the handoff after the first read, when a bestseller report becomes a meeting instead of a cut ticket. On the floor, speed is not a slogan; it is a vendor keeping greige fabric open until the store scan says which print earns the slot. Compressing a 100-day lead time changes the size of the bet I am willing to make.