Ecommerce & Omnichannel · Fashion

Size Curve Correction

Size curve mismatched to demand. Re-balances buy and availability.

Target KPI Size accuracy
Executes in ≤ 24 hours
System of record PIM · Shopify
Trigger condition

A style sells out of its centre sizes while the tails still hold more than 40% of units, or size-related returns exceed the category norm.

Write-back

Revised size curve written to the PIM against the style; availability rules updated in Shopify.

Every write is gated on an approver role you name. Nothing runs unattended.

Procedure
  1. Compare the bought curve to realised demand by size, correcting for the fact that a sold-out size stops generating demand data.
  2. Test whether it is a curve problem or a fit problem, because size-related returns look identical from the sales data alone.
  3. Recompute the curve per cluster or channel, since online and store size profiles rarely match.
  4. Open a case to the buyer for the next buy, and to merchandising for the current one, gated on approval.
  5. Close when the next buy sells through with the tails clearing at full price.
Outcome metric

Full-price sell-through by size on the next buy vs. the prior curve, plus the change in size-related returns.

The case closes on this number, not on the action being taken. A playbook without a close condition is a dashboard.

Run Size Curve Correction on your data.

Pick three playbooks from the catalog. We wire them against your system of record for the pilot.

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3
What are your goals?
Step 2 of 3
About your operation
Step 3 of 3
Your contact info