Perspectives
Points of view on where apparel operations are heading — and why the connected operating system is the next shape of the category.
Why feature requests die in enterprise planning suites →
A workflow-specific request enters a large vendor’s intake and goes quiet. The mechanism is roadmap allocation, not neglect — what teams do instead, what the workaround costs when its author leaves, and what to ask any vendor about change before signing.
Who actually implements your planning system? →
For most enterprise planning suites, the vendor sells the license and a separately selected systems integrator delivers the implementation. What the two-contract structure means for the buyer, when it genuinely serves, and what to ask before signature.
Two lifecycles, one product →
A fit block moves on one clock and a colourway on another, but by the time they reach the merchandise plan they have collapsed into a single lifecycle. That collapse is why newness goes invisible, exits go wrong, and a real platform change arrives as a surprise.
The second channel changes the company, not just the plan →
Adding wholesale to a DTC brand, or DTC to a wholesale one, is treated as a distribution decision. It is a costing decision, a calendar decision and a pricing-authority decision — and the reverse direction is not the mirror image of the first.
The full-price number nobody owns →
Every brand says it protects full price. Almost none can produce the number on demand. The split survives at transaction grain and dies in aggregation — and permanent markdowns live in one system while promotions live in another, so nothing holds both halves.
The order you meet the number in →
The same plan, met in a different order and framed with different confidence, produces a different buy. Why the presentation layer is an operating decision with a margin consequence — and where that claim stops being true.
The margin is made before the buy →
Apparel margin is not managed during a season; it is constructed before one. Costing, option count and depth, the size curve and the delivery date fix the range the season can still produce — and no in-season lever moves it.
When you cannot chase →
Almost everything written about merchandise planning assumes a correction opportunity — an early read, a reorder, a chase. Take it away, as toys, juvenile hard goods and gifting categories do, and the discipline does not get simpler. It gets less forgiving, and it moves earlier.
The apparel stack pattern doesn’t stop at apparel →
Footwear, accessories, home, beauty, sporting goods, outdoor, toys, baby and juvenile, and jewelry and watch brands hit the same wall apparel did — no shared record between design, plan, buy, and production. The disconnected stack is structural to style-color-season merchandise; apparel just hit it first.
Why apparel needs its own operating system →
Horizontal ERP and generic retail tools were built for stable SKUs and short lead times. Apparel is seasonal, dimensional, and long-lead — and that mismatch is why the category needs its own operating system.
Planning for the season you’ll actually have →
No forecast survives contact with the season. The brands that win don’t forecast better — they react faster. Why in-season agility, not accuracy, is the edge.
Built for smarter apparel teams →
The forecast that’s already wrong, the buy detached from the plan, the size curve that masks the truth, the PO that goes dark — one cause, and how smarter teams solve all of it from a single connected system.
The disconnected apparel stack — and why it leaks margin →
Brands lose margin in the gaps between tools, not inside them. Why the handoff is the problem, and what an operating system changes.