Merchandise management visualization project
Project Objectives
Sort out the overall business process of commodity management, investigate the use of data, establish dimensional indicators that affect the business: sales, retention, number of sku, broken codes, etc., and establish an intelligent data monitoring system
The scope of work
- Sales Kanban
- Retention Kanban
- SKC Kanban on sale
- Order volume kanban
- Out-of-stock and code-breaking Kanban
- Time-sensitive Kanban
Output product
- finebi visualization signboard
Due time
- Tentative week
- Manpower input: 1-3 people, ABC
- Main tool: finbi
Project Flow
-
Determine the subject
Commodity management operation command room
-
Aggregate data
Understand the underlying data of the business, and complete the development of SQL bottom tables, intermediate tables, and upper tables. The bottom table includes: sales table, product information table, inventory table, order status table, etc. The upper table includes: sales table, retention table, on-sale skc table, order table, out-of-stock and code-breaking rate table, and timeliness table.
-
Analysis data format
-
Sales table
week date Estimated total sales Actual total sales Sales completion rate Sales volume and sales share of each channel... Thursday 20201231 Sales... Wednesday 20201230 …… -
Retention form
Storage week period Number of storage [1-6] Weekly Remaining Number [1-6] Week retention rate 49 11/30-12/6 962159 903319 48 11/23-11/29 -
SKC table
date Subsite Total number of SKCs on sale Each product layer [stocking A/B, non-stocking 1, 2...] SKC number/skc proportion 20201202 www 20201202 us…… -
Order volume
week date Each management department [sc, wx...] [first order, return order] [estimated, actual] order quantity Actual return order quantity of production department The production department is expected to return the order quantity Thursday 2020-12-03 0 479547 -
Out of stock broken code table
-
Bit break rate of each channel
date Various channels [SSH, SH...] 2020/12/3 Broken code rate … 2020/12/2 … -
Code breaking rate of each maintainer
date Each maintainer [children's clothing, men's clothing...] 2020/12/3 Broken code rate … 2020/12/2 …
-
-
Timetable
period Total time limit (ordinary/emergency) Total time limit (normal [12/15/17] / emergency [5/8/10]) * completion rate within a day …… 11/30-12/6 11806 1.03% ……
-
-
Explore expressions
- Sales Kanban
- Sales overview
- Sales completion rate
- Sales by channel
- Fluctuations in the sales proportion of each channel
- Retention Kanban
- Number of retentions for the sixth week
- Sixth week retention rate
- SKC Kanban on sale
- The number of skc on sale at each site
- Percentage of skc on sale at each site at each level
- Order volume kanban
- Order volume fluctuation
- Rebate orders from all channels
- Out-of-stock and code-breaking Kanban
- Bit break rate of each channel
- Code breaking process for each maintainer
- Time-sensitive Kanban
- The total amount of ordinary orders and timeliness
- Total urgent order and timeliness
- Sales Kanban
-
Creative sketch
-
Edit design
-
Sales Kanban
-
Retention Kanban
-
On sale skc Kanban
-
Order board
-
Break rate Kanban
-
Order Aging Kanban
-
-
test
-
advantage
Cover 80% of daily basic data requirements, greatly reduce the time cost of locating abnormal problems, understand the reasons for indicator changes in time, and provide feedback to improve the efficiency of information acquisition;
-
Shortcomings
- The data transmission from data warehouse to BI has not been completely opened up, and an intelligent monitoring system has been established.
- The retention kanban can be specific to the maintainer
- If the data is real-time data, the time selection of the report can be set to dynamic 7 days, 14 days, 30 days
-