A dress card may remain available while the needed size is already gone. For a clothing store, that is different from “the product is in stock.” Overall model availability gives purchasing and advertising teams a picture that is too coarse.
When one number is not enough
A seller with several sales channels needs the same size, color, and offer-availability data in purchasing, advertising, and catalog management. Without a shared process, each employee collects part of that information again.
Count the whole path to a usable summary: reading pages, rechecking results, and consolidating tables. Collection time alone understates the effort needed to make a decision.
Treat each variant as an item
Give each Akmelo source a scenario with agreed fields. A variant key includes model ID, color, and size in the chosen size system. If a page uses another size scale, verify the mapping manually before recording it in the scenario rules.
Collect only what the source actually provides. A missing field must not become zero. If the source shows merely whether an order can be placed, you cannot infer an exact warehouse quantity from it. These limits also matter for size-level stock analysis.
Run collection on a schedule. Then prepare exports for each job: purchasing needs a model-and-size view; catalog managers need uncertain rows. Configure selection and calculations in scenario and export settings. Staff still decide whether to change purchases or campaigns.
Estimate the benefit
Compare the time spent on the whole process before setup with checking time afterward. Suppose manual checks and summaries take 132 hours per month, while reviewing exceptions and results takes 24. That frees 108 hours, or about five team hours per day over 22 working days.
| Parameter | Monthly example |
|---|---|
| Checks and summaries before setup | 132 hours |
| Checks after setup | 24 hours |
| Time made available | 108 hours |
| Estimated fully loaded hourly cost | 1,100 RUB |
| Value of time made available | 118,800 RUB |
| Service and maintenance budget | 13,800 RUB |
| Estimated effect | 105,000 RUB |
Under these assumptions, the effect is about 105,000 RUB per month: 108 hours × 1,100 RUB less 13,800 RUB in recurring costs. That values time released, not increased sales. Staff can work on assortment and purchasing while payroll stays unchanged. If one-time setup costs 32,000 RUB, the first month's effect is 73,000 RUB. Use your real processing and support costs for your own calculation.
Check before expanding
Start with one product group and a few dozen variants. Check different size systems, unknown stock, and missing cards manually. A gap in results does not prove an item is unavailable. Expand gradually when the new file is unambiguous and review time really falls.
