Product card set
The planner assembles a set of 5-7 slides for your category: hero shot, benefits, sizes, usage, trust, comparison, details.
What it does
- Assembles a set of 5-7 slides by role: hero shot, benefits, sizes, usage, trust, comparison, details.
- Chooses the roles from the product's category, out of the planner's thirteen.
- Checks every slide against the marketplace's requirements: minimum size, ratio, format, weight.
- Enforces the first-slide rule: the product large, with no text over it.
How it works
The planner is a model call, not a template.
The set is planned by a request to a model: it receives the category, the marketplace and the product description, and returns a list of slides with roles. That is why a pair of trainers and a piece of jewellery get different sets even though the marketplace rules are the same.
Each slide is then checked by a set of pure functions: they compare facts about the card with the marketplace's requirements and return a specific discrepancy rather than a verdict - that the width is 800 where the minimum is 900, for instance. The requirements are stored as data rather than inside the checking code, so a threshold can be updated without touching the logic.
Limits
The planner knows the requirements of Wildberries and Ozon. There are no requirements in the system for Yandex Market, Avito or Kaspi, and a set for those is not checked.
The set is planned from the product description and its category, and the photographs you upload travel to the model with the generation request - so a slide can show your product rather than an invented one. The image is still produced by a model, and it still needs checking before publication.
Other features
See the price list
Every operation with its price on every plan, on one page, from the pricing engine.