Resources
Guides and frameworks for running apparel as one connected system — the end-to-end workflow, the case for a connected operating model, the modern software stack, and the spreadsheet habit the category is built on.
The Connected Apparel Workflow Map →
The twelve stages that carry a collection from line plan and OTB through design, product development, assortment, buying, sizing, POs, production, and allocation — and the handoff risk at each seam.
The Apparel OS Manifesto →
Seven beliefs about how apparel should be run — cross-functional by nature, organized around the season, and connected across product, financial, and operational decisions.
The Modern Apparel Software Stack →
A map of the systems that run apparel brands — PLM, ERP, planning, assortment, buying, production, PIM, and analytics — where spreadsheets fill the gaps, and where an Apparel OS fits by company stage.
The Apparel Systems Landscape →
The ten software categories an apparel brand runs — ERP, PLM, PIM and DAM, planning, allocation, WMS, OMS, EDI, ecommerce, and BI — with what each is genuinely the system of record for, what it is repeatedly asked to do that it was not built for, which handoff breaks first, and where the purchase order sits between the plan and the commitment.
The Connected Stack by Vertical →
How the systems stack and its seams differ across ten verticals — apparel, footwear, accessories and bags, home and furniture, outdoor, sporting goods, health and beauty, toys and games, baby and juvenile, and jewelry and watches. The systems actually present in each, the handoff that actually breaks, and the planning consequence that follows.
Apparel EDI in the Connected Stack →
Apparel EDI for the planning side of a wholesale brand: who sends which document to whom, the seven X12 transaction sets — 850, 855, 860, 856, 810, 846 and 852 — and the planning decision each should feed, the apparel complications, and why EDI data stops at the ERP instead of reaching the plan.
Available to Sell in Apparel →
What available to sell (ATS) is at style-color-size by channel, how it differs from available to promise, on hand and free stock, which system holds each input, a size-level worked example, why the figure disagrees across ERP, WMS, ecommerce and partner feeds, and how to agree one definition across teams.
The Apparel Purchase Order Lifecycle →
One purchase order followed from open-to-buy approval to close — buy plan, PO terms, factory confirmation, WIP, amendments, ship notice, receipt, landed cost and three-way match — with the system that holds it at each stage, where it is re-keyed, and a size-level worked example with prepacks and a partial shipment.
What Is an Apparel and Footwear Solution? →
The apparel-specific ERP category defined: why a generic ERP breaks on the style-color-size matrix, the ten records an apparel and footwear solution owns, the processes it runs fully, touches or does not do, the six seams to PLM, planning, WMS, EDI, ecommerce and finance, three deployment shapes, where the plan of record sits relative to it, how footwear and the adjacent verticals change the record set, and an evaluation checklist.
The Apparel Data Model →
What a shared data model for an apparel brand actually contains — the style, colorway, and size hierarchy, the calendar, channels, costs, and plans against actuals — why the hierarchy is the hard part, and five questions that expose a bolt-on integration.
The Handoff Problem →
Why apparel workflows break at handoffs rather than inside functions — the four seams where plans are re-keyed into the next team’s document, the three mechanisms of a handoff failure, why staffing the seams makes them worse, and the judgment transfers software does not remove.
The Operating Cadence →
The five clocks — annual, seasonal, monthly, weekly, daily — by which an apparel company turns its plan into buys, receipts, allocations and markdowns, what each clock is allowed to change, what freezes when a faster clock takes over, and why cadence failures look like data failures.
The Plan of Record →
The single, versioned set of numbers — line plan, assortment, buy, purchase orders, WIP and in-season position — that every function reads and changes through one controlled path: why copies drift, who holds the pen at each stage, how versions and approvals sit beside ERP and PLM, and what makes a merchandising operating system.
Why Apparel Brands Still Run on Spreadsheets →
Why spreadsheets remain common in apparel planning — flexibility, speed, familiarity, and disconnected systems — the risks they create at scale, and how to move gradually to an Apparel OS.
Why ERP and Excel Still Leave Apparel Margins Exposed →
Most brands run on ERP plus spreadsheets, yet margin still leaks in the gap between them. An executive look at where the leakage happens and how connected planning closes it.
The Cost of Disconnected Apparel Workflows →
Apparel brands lose speed and margin between teams, not inside them. Where disconnected workflows cost time, margin, and confidence — and how to reduce that cost without rip-and-replace.
The ROI of Connected Apparel Workflows →
The return side of disconnected work — where connecting apparel workflows recovers margin, speed, and planning confidence, and how to frame the ROI for your own brand without fabricated numbers.
Operating Model Assessment for Apparel Brands →
A structured self-assessment of how connected your apparel operating model is across planning, product, buying, sourcing, production, and allocation — with a score and where to start.
Apparel Software Buyer’s Guide →
A vendor-neutral guide to evaluating apparel software — PLM, ERP, merchandise planning, point solutions, and an Apparel OS — with the questions to ask before you buy.
Connected Planning Implementation Playbook →
How to sequence a connected apparel planning implementation — six phases run against one workflow seam at a time, with an owner per phase, the data each seam needs, the failure modes, and what done actually looks like.
RE:PLAN Europe 2026: A Guide for Merchandise Planning Leaders →
A pre-event guide to the planning-specific conference formerly named PI Apparel Merchandise Planning — the 2026 themes decoded for a planning org, who attends, and the questions worth carrying in.
See how the Apparel OS comes to life in RetailNorthstar — one connected workflow from line plan to production.