The Retailers’ Market Manager generates an order template for a specific customer. This template contains all products that the customer can order, with all quantities to zero. The template is then submitted to the customer that in a specific time window must insert the desired quantities and send it back to the Retailer or commit basket by itself on the web app. The Market Manager validates then the order and eventually sends back to the customer the updated template broken down at SKU level (if not already, if the first template was at style level). The customer commits quantities at SKU level and The Retailers’ Market Manager finally approves them (after validating by rejecting/adjusting some quantities). Once approved the basket is sent to the Legacy system (e.g. SAP).

The system manages and classifies order life cycle status according to such statuses’ as size confirmed/committed/approved and bulk confirmed/committed/approved

Two different types of baskets are possible here – Carry Over and Seasonal. The Carry Over basket does not include dropped or inactive styles and has 6 distinct consequent month columns in which to put quantities, whereas the Seasonal basket requires the specification of a season (e.g. Winter 2017, Spring 2018, etc.)

The Retailers’ Market Manager creates a basket. To accomplish that he must specify the customer, if he wants to generate it at Style or SKU level and to specify the basket type. Users have the ability to choose which 6 fields they want to see there. Examples of those fields can be seen below. Styles can be selected by a combination of filters on the following fields: Product Life cycle, Group Type, Label Collection Description, Product Division, Product Category, Product Subcategory etc.