How return data becomes a production decision
The size × colour return matrix is not a report; it is a production instruction. The level at which returns should be read in fashion retail, three different causes, three different owners, and the path from that level to action.
In fashion retail the return rate is a number everyone knows. Most companies read it at channel and brand level: so much in e-commerce, so much in stores. At that level a return is a cost; an expense line to be managed. One level down, at size × colour, a return is information; a signal that corrects production, visuals and the size chart.
What the matrix says
The same product coming back twice as often in size 38 as in 42 is a pattern problem. The product is cut tight or loose in that size. One colour of the same product returning more than the others is a visual problem: the colour on screen is not the real colour, or that colour sat differently on the model. The same size returning across all products is a size-chart problem: the brand's sizing standard has drifted from customer expectation.
These three problems have three different owners: production, e-commerce, product management. A return rate read at channel level hides all three at once. Everyone sees the number; nobody sees their share of it.
Why nobody goes down to this level
The data exists. Return reason, size and colour sit on every order line. The reason nobody goes there is not missing data but scattered data. The return record is in the OMS, the product attribute in the PIM, the production quantity in the ERP, the customer's comment on the marketplace. Building the matrix means joining four systems by hand; nobody does that every season for every product.
SNR Core's living memory makes that join once and keeps it current. The matrix is not a report; it is the memory itself.
How information attaches to action
S0 Ecom reads the return matrix and classifies the cause: pattern, visual, size chart. The classification is confirmed by marketplace reviews and the call-centre record coming from S0 Customer; a "runs tight" comment strengthens the pattern class.
S0 Supply turns the pattern class into a production decision. The size split changes in the next order: fewer 38, more 42. The pattern correction note goes to the supplier. The order proposal is triggered by approval; without approval, nothing is sent.
The visual class stays in S0 Ecom: the Visual Studio module reshoots that colour or regenerates it on the model. The size-chart class is written onto the product page as a fit note and updates S0 Forecast's size curve.
Three units see the same data; each makes its own decision. One memory, three decision areas. No integration is written, because all of them live on the same core.
The time dimension
The value of this loop is its speed. If the return rate is read at season end, the correction waits for next year. If the matrix is live, the returns of the first two weeks correct the second order within the season. The same pattern error is not produced twice.
In the field
This loop runs in live retail operations across several brands. Return analysis reaches size × colour; the result flows back into the production decision. We do not share numbers, because numbers are shared under contract; we share the loop, because the loop is the product. What is live is listed in the field section and detailed in the field post.
To see this matrix on your own return data, book a demo; twenty of the forty minutes go to this loop.
Short answers
Because the causes separate at that level. At channel level a return is one rate that hides three different problems: pattern, visual, size chart. The size × colour matrix separates the three and sends each to its owner: production, e-commerce, product management.
The OMS for the return record, the PIM for the product attribute, the ERP for production quantity, the marketplace for the customer's comment. SNR Core connects these to the core, not to a product; data connected once is visible in S0 Ecom, S0 Supply and S0 Customer at the same time. Four systems are not joined by hand.
No. S0 Supply prepares the order proposal with the size split and the pattern note; when approved, it goes to the supplier. If not approved, nothing is sent. The decision belongs to the planning team; the computation to the core.
Summary
- At channel level a return is a cost; at size × colour it is information.
- Three causes, three owners: pattern → production, visual → e-commerce, size chart → product.
- S0 Ecom reads and classifies; S0 Supply turns it into a production decision; S0 Customer confirms.
- The loop's value is its speed: the first two weeks' returns correct the second order within the season.