Mapping the apparel data landscape: from PLM to POS
A single black cotton t-shirt, style number WM-2401, exists in six different systems before a customer buys it. In one system it is a "concept sketch," in another a "cost roll-up," in a third a "sellable SKU," and in a fourth a "unit shipped." When those six versions disagree, your assortment planner reorders a color that never sold. This lesson follows WM-2401 across the stack so you know which system owns which truth.
The six systems every apparel business runs on
Fashion data lives in a relay race of specialized systems. Each one owns a stage of the garment's life and hands data to the next.
- PLM (Product Lifecycle Management): where the garment is designed and specced. Owns the tech pack, bill of materials, and target cost.
- ERP (Enterprise Resource Planning): the financial and operational backbone. Owns purchase orders, actual landed cost, and inventory valuation.
- PIM (Product Information Management): the marketing-facing catalog. Owns descriptions, images, and channel-ready attributes.
- WMS (Warehouse Management System): the physical building. Owns on-hand units, bin locations, and putaway.
- OMS (Order Management System): the traffic controller across channels. Owns order state, allocation, and fulfillment routing.
- POS (Point of Sale): the register and e-commerce checkout. Owns the sell-out truth: what actually sold, when, at what price.
Common systems you will meet in the wild: Centric PLM and PTC FlexPLM for design, SAP and Oracle NetSuite for ERPERPA single integrated software backbone that runs core operations: finance, procurement, supply chain, HR and manufacturing on shared data.View full definition →, Salsify and Akeneo for PIM, Manhattan and Blue Yonder for WMS/OMS, and Shopify or NewStore at retail. No single vendor owns all six well, which is exactly why the data disagrees.
Following WM-2401 through the stack
Let's trace the four attributes that matter most: style, size, color, cost, and sell-out.
Style and the SKU explosion
In PLM, WM-2401 is one style: a men's crew-neck tee. But a style is not sellable. Once you add size (XS to XXL) and color (Black, White, Navy), you get SKUs (Stock Keeping Units), the atomic unit of inventory. One style times 6 sizes times 3 colors equals 18 SKUs.
This is the first place data breaks. PLM thinks in styles. WMS, OMS, and POS think in SKUs. If the size run changes late (design drops XS), the systems downstream may still carry a "phantom" XS SKU that shows stock but can never ship.
Rule of thumb: PLM owns the style definition. ERP owns the SKU master. Everyone downstream should read the SKU master, never invent their own.
Color: the messiest attribute in fashion
Color is where governance goes to die. In PLM, the color is a Pantone reference and a mill dye lot. In PIM, marketing renames it "Midnight" for the website. In POS, the receipt just says "BLK."
Now analytics asks: "How did navy sell?" If PIM calls it "Midnight," ERP calls it "NVY," and POS calls it "410," you cannot join those datasets without a color mapping table. Most retailers maintain one; the ones who don't spend Mondays reconciling spreadsheets.
Cost: two numbers, two owners
There are two costs, and confusing them corrupts margin analysis.
- Target cost lives in PLM: the estimate during design (say, $6.20).
- Landed cost lives in ERP: the actual cost after freight, duty, and factory negotiation (say, $7.05).
PLM cost is a plan. ERP cost is the truth. Any margin report should pull cost from ERP, not PLM. The US International Trade Commission tariff schedule drives a chunk of that landed-cost gap for imported apparel, which is why the two numbers rarely match.
Sell-out: the truth POS owns
Sell-out (also called sell-through) is the percentage of received units actually sold. Only POS knows it, because only POS records the sale.
Worked example for WM-2401 in Black, size M:
Units received (WMS): 500
Units sold (POS): 340
Sell-through = 340 / 500 = 68%A 68% sell-through eight weeks into a season is healthy for a basic tee. The danger: if OMS shows 340 sold but POS returns data shows 25 came back, your net sell-through is 315 / 500 = 63%. Returns data (usually flowing POS to OMS) is the attribute teams forget to net out.
Where the truth actually lives
| Attribute | System of record | Common wrong source |
|---|---|---|
| Style definition | PLM | ERP guesses |
| SKU master | ERP | Each channel invents its own |
| Color naming | PIM (display), PLM (spec) | POS abbreviations |
| Cost (landed) | ERP | PLM target cost |
| On-hand inventory | WMS | ERP snapshot (lags) |
| Sell-out / returns | POS / OMS | Manual reports |
The single most useful governance move: publish this table internally and name a data owner for each row. That is governance in practice, not theory.
🎬 [VIDEO: "What is Product Information Management (PIM)?" - youtube.com - a clear 6-minute primer on how PIM sits between your ERP and sales channels]
Data-quality metrics that matter here
Generic data-quality dimensions (completeness, accuracy, consistency, timeliness) get specific in apparel. Track these:
- Attribute completeness: what percent of active SKUs have all required PIM fields (material, care, fit, primary image)? Many teams target 95%+ before a SKU goes live. This is a target, not an industry-verified benchmark; set your own gate.
- SKU match rate across systems: what percent of POS-selling SKUs join cleanly to the ERP master? Below 100% means you are selling things your systems can't fully track.
- Inventory record accuracy (IRA): does WMS on-hand match a physical count? Warehouse operators commonly cite 95 to 99% IRA as a working target; treat any specific figure as an operational goal, not a fixed rule.
- Color/size mapping coverage: every POS color code must mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → to one PIM color. Gaps here silently drop sales from your color analytics.
A simple completeness calculation
Active SKUs: 2,400
SKUs missing primary image: 180
Completeness = (2400 - 180) / 2400 = 92.5%At 92.5% you are below a 95% gate: 180 products would show a broken image online. That is a concrete, fixable data-quality defect, not an abstraction.
Knowledge check
1. An assortment planner reorders a color that never sold at retail. Which system's data should have been treated as the authoritative source to prevent this mistake?
2. Why does the apparel data landscape rely on six specialized systems rather than one unified platform?
3. A garment is 'one style' in PLM but becomes many entries in downstream systems. This 'SKU explosion' is best understood as a consequence of what?
4. Select ALL correct answers. Which statements accurately describe how 'ownership of truth' is distributed across the apparel stack?
Select all the correct answers.
5. Select ALL correct answers. Why can the 'same' t-shirt appear inconsistent across systems?
Select all the correct answers.
Governance: who decides when systems disagree
Governance sounds bureaucratic until WM-2401's navy variant shows 200 units in ERP and 150 in WMS. Which number does the buyer trust to reorder?
Answer: WMS for physical on-hand, ERP for financial valuation. They serve different questions. ERP's number can lag because it updates on a batch cycle (sometimes overnight), while WMS updates in near real time as units move. Neither is "wrong"; they answer different questions at different refresh rates.
Three governance practices that separate mature apparel data teams:
- A published system-of-record map (the table above), reviewed each season.
- Master data governance for new styles: a SKU is not "live" until ERP creates it and PIM completes required attributes. This stops phantom SKUs.
- Reconciliation SLAs: for example, WMS and ERP inventory must reconcile within an agreed tolerance (say 2%) by a set time daily. Set the tolerance to your business; the discipline matters more than the exact number.
Analytics benchmarks to anchor on
Two measurement benchmarks recur across apparel analytics. Treat both as directional, and always compute your own from POS data:
- Sell-through rate: basics run high and steady; fashion/seasonal items are judged on early-season sell-through (first few weeks) to decide markdowns. A weak early read triggers markdown before the season kills margin.
- Full-price sell-through: the share sold before any markdown. This is the cleanest signal of true demand, and it lives entirely in POS price data. If most of WM-2401 sold at a discount, the "68% sell-through" was flattering.
The data lesson: a single headline metric hides the story. Segment sell-through by full-price versus markdown, by color, and by size, all of which require clean joins across the six systems you just mapped.
Key Takeaways
- Style lives in PLM, but SKUs are born in ERP. Everything downstream should read the ERP SKU master, never invent its own.
- Cost has two owners: PLM holds target cost (a plan), ERP holds landed cost (the truth). Margin reports use ERP.
- Sell-out truth lives only in POS, and you must net out returns to get real sell-through. 340 sold minus 25 returned changes the decision.
- Color and size mapping tables are non-negotiable. Without them, "how did navy sell?" is unanswerable across PIM, ERP, and POS.
- Governance is a published system-of-record map plus named owners, reviewed each season, not a one-time document.
Frequently asked questions
Which systems does an apparel company actually need between design and checkout?
Six: PLM for design specs and bill of materials, ERP for purchase orders and landed cost, PIM for the marketing catalog, WMS for physical on-hand units, OMS for order routing across channels, and POS for the sell-out truth. Each owns one stage of the garment's life and hands data to the next. No single vendor covers all six well, which is precisely why the numbers disagree.
What is the difference between a style and a SKU in fashion data?
A style is the design concept as it lives in PLM, for example a men's crew-neck tee. A SKU is the sellable atomic unit once you multiply by size and color: 6 sizes times 3 colors gives 18 SKUs for that one style. PLM thinks in styles, while WMS, OMS and POS think in SKUs, and that translation point is where data first breaks.
Should margin reports use the cost from PLM or from ERP?
From ERP. PLM holds the target cost estimated during design (say $6.20), while ERP holds the landed cost after freight, duty and factory negotiation (say $7.05). The PLM figure is a plan, the ERP figure is what you actually paid. Import duties are a large part of the gap, which is why the two rarely match.
How do you calculate sell-through rate and why does POS data matter?
Sell-through is units sold divided by units received: 340 sold on 500 received gives 68%. Only POS knows the numerator because only POS records the sale. The trap is returns: if 25 units came back, net sell-through falls to 315/500 = 63%, and most teams forget to net them out before deciding on markdowns.
Why can't I answer "how did navy sell?" across my retail systems?
Because each system names the color differently: PLM carries a Pantone reference, PIM renames it "Midnight" for the website, ERP stores "NVY" and POS prints "410" on the receipt. Without a color mapping table that links every POS code to one PIM color, those datasets cannot be joined. Gaps in that table silently drop sales from your color analytics.
ERP shows 200 units and WMS shows 150, which number should the buyer trust?
WMS for physical on-hand, ERP for financial valuation. Neither is wrong, they answer different questions at different refresh rates: ERP updates on a batch cycle, sometimes overnight, while WMS updates in near real time as units move in the building. A buyer deciding whether to reorder should read WMS, and the two should reconcile daily within an agreed tolerance.