We optimize sales of underperforming retail stock.

Y′01.
You see all calculations after login

Y′02.
Main configuration screen

1. Category tree.
2. Inventory type definitions (Dead stock, Slow movers, Fast movers).
3. Identification of inventory that can potentially be sent away.
4. Settings to identify inventory that may be placed and sold in receiving stores.
5. Results overview.
6. Category insights.

Y′03.
Dashboard of precalculated results

When the settings are changed these dashboards show the real impact of the current configuration. On-the-fly regime.

Y′04.
Managing exceptions within categories

• The main configuration is done for all clients categories.
• Client can define exceptions for any category. Such as different definition of deadstock and its configuration for food.
• Special exceptions or exceptions on product level can be defined on the back-end level.

Y′05.
Simple but comprehensive settings

1. Divide portfolio into 3 inventory types (dead stock, slow-movers, fast-movers).
2. Enable selected inventory types for redeployment.
3. Forced redistribution aims to depletethe inventory, that client identified as “not planogramed” or “unwanted” at store, to zero. No protection is applied.
4. Setting protection on novelties and recently replenished inventory.
5. Enabling products with planned promotion for redeployment.
6. Protecting minimum layers (eg. minimum on shelves display, alignment with replenishment, etc.)
7. Managing and controlling Picking & Packing costs (minimum values per picked line)
8. Inventory definition that must be kept in store to ensure the demand is covered within the specified time period. The demand is based on Ydistri probabilistic forecast.
9. The forecast confidence indicates the probability with which the inventory, we keep at store, will cover the demand defined above. The higher the confidence the more remains and the less is redeployed.

1. Determining what is desired to be received at stores.
2. Inventory quantity specification that canbe reached after redeployment. Inventoryis desired to be sold within the specified time period with defined probability. The higher confidence level, the smaller inventory quantity after redistribution.
3. The location can receive the forecasted supply only if the product sales have the specified frequency.
4. Include open purchase orders into available inventory of the receiving store.
5. If enabled the redeployed quantity will always be replenished up to minimum layer (specified by client).
6. Redeployed quantity is sent only to stores where the available inventory is zero.
7. Specification of forced products redeployment size to receiving stores.

Y′06.
Templates with predefined settings

Y′07.
Redistribution configuration

Enable all or selected regions for redeployment. Create groups of regions among which the redeployment may take place.

• To minimize the workload and increase the effectivity a client may set limitations to route size and picking&packing workload.
• The approach may vary based on the size.

Set different approach to product classes or types.

Redeploy only specified list of products or exclude it.

Redeploy only selected brands or excluded them.

Y′08.
Details of the redistribution

Users can visualize and go through the detail of every single product proposed for the redeployment.

Users can visualize and go through the detail of every single product proposed for the redistribution.

Y′09.
Statistics

See statistics of each calculation.

1. Overall statistics: see how much was redistributed, how many stores and products were involved and the values: out-of-stocks resolved, min. layers stocked and forced products.
2. Routes: overview of the values of the routes and number of the routes.
3. Data of redeployed products on the sending store.
4. Data of redeployed products on the receiving store.
5. See redeployment split by region.

Y′10.
Drill down

See the impact on total revenue and inventory turnover in comparison to redeployed inventory.

Y′11.
Detail view with monthly sales