Whose job is the category ranking: from strategy template to free-form command

On a category page the first three pages sell and the rest sit. Where each product sits is therefore a decision; and one renewed every week. In most companies that decision takes a category specialist's week: pull the sales report, put the stock list beside it, flag the new arrivals, check the campaign calendar, order by hand, publish. Next week, from the top.

Ranking is a choice of strategy

The same category wants newness at season opening: new arrivals forward, let the customer see the collection. Mid-season it wants sell-through: what moves forward, what does not moves back. At season end it wants clearance: high-cover products forward, markdowns visible. In campaign week it wants outfits: products bought together side by side.

Each is a different ranking logic. The person knows this but applies it by hand every time. The logic is in their head, not in the system. If the specialist leaves, the logic leaves.

The strategy template

S0 Ecom's Catalog Planning module keeps these logics as strategy templates: sales performance, stock cover, newness, markdown, season, outfit, slow movers and more. Pick a template, the category is ranked. The template reads the living memory in SNR Core: sales, stock, returns, arrival date and campaign calendar sit in one model. No data is pulled by hand from four systems.

The free-form command

When a template is not enough, write a command: "bring new arrivals forward but pull back anything under ten units in stock". "Put campaign products on page one, rank the rest by sell-through". "Move products where we are priced above the competitor below page two". The command is natural language; S0 Ecom turns it into a ranking rule and shows the result with its rationale.

The last example rests on the Market Intelligence module: live in-season products of chosen competitors are pulled by category; the position in the price band reads green, amber, red. The ranking command uses that knowledge.

Your criteria, S0NR0Y's reasoning

The company sets the ranking criteria. S0NR0Y computes how well each product fits them and shows the rationale: why this product is third, why that one dropped to page two. The category specialist does not build the ranking; they approve it and choose the strategy. The job does not change; its level does. This is the third of the four steps: it helps you decide.

Data quality is the ranking's foundation

Ranking rests on attributes: size, colour, fabric, season, collection. If attributes are missing the ranking goes blind. This is why the Product Enrichment module marks every product with a 0–100 data quality score and enriches low-score products first. The ranking template does not push a low-score product forward; it raises the score first.

A ranking that learns

After the ranking goes live, its result is written back: clicks, baskets, sales, returns. Which strategy returned what in which category is known at the next season opening. Last year's specialist may have left; the decision memory stays with the company. This is the loop from decisions, not dashboards, applied to the catalog.

The category specialist's new job

Not ranking, but building the strategy. Which template in which category, which command in which week, which competitor to track. The specialist moves from being the person who ranks one day a week to the person who builds the category's decision architecture. S0 HR's AI handover report measures this shift: which process was handed over, where the freed time went.

This flow is live in the field: the field post. To see it in your own category, book a demo.

Short answers

Summary

• Ranking is a choice of strategy; the logic changes with the season phase.
• Templates cover recurring situations, free-form commands cover specific rules; they work together.
• The company sets the criteria, S0NR0Y computes and explains; the specialist approves.
• The published ranking's result is written back; the decision memory stays with the company.