System and method for performing assortment planning

Abstract

A system, method and program product are provided for defining an assortment for use in an operative execution system. The method includes assigning a plurality of articles to the assortment for one or more article validity periods, assigning a plurality of stores to the assortment for one or more store validity periods, and releasing the assortment to the operative execution system. Once released to the operative execution system, the articles and the stores are automatically added to and dropped from the assortment based on the validity periods.

Description

FIELD OF THE INVENTION

The present invention relates generally to the field of merchandise and assortment planning, and more specifically to the use of systems and methods for facilitating assortment planning decisions.

BACKGROUND OF THE INVENTION

In general, business models can involve buying merchandise and services for one price and selling it for another. In the process, sellers can incur spectacular costs marketing to prospective and existing customers, leasing stores, paying employees, buying and maintaining information technology, transporting, and, most importantly, buying and managing the merchandise itself.

Planning, at one level, is a strategic activity. Executives set business objectives and merchandise planners derive strategies to meet them: back to basics to reduce the style count, extended assortments with additional colors and styles, or new lines of business such as health & beauty. On another level, planning is tactical and operational. The plan influences how many styles and colors a merchant will carry. It influences how distributions are planned for stores. It influences when markdowns are expected to be taken for each style and color. It also influences which stores should carry each style.

One of the most important processes of such planning is assortment planning. Assortment planning provides answers to basic questions such as: Which product or service? How much of it? What colors? What sizes? What locations? Who is the target customer? When should it be offered? How long should it be offered? and so forth. Thus, the old adage, the right product, at the right place, at the right time, still holds true in today's marketplace, but with one important change. Sellers—whether traditional brick-and-mortar, e-commerce or a combination of the two—must have a compelling selection of merchandise for the right customer as well. Thus, an effective assortment planning process that provides the right products and services at the right locations at the right time is essential for successful modern business operation.

An effective assortment planning process is ever more necessary in retail environments and particularly in fashion retail environments. Retail environments and fashion retail environments often require that the business adjust to relatively fickle needs of the consumer.

Although assortment planning directly affects product selection, price, timing and micro-merchandising, it has often been de-emphasized due to hectic retail schedules. Extinguishing delivery fires and meeting marketing and financial planning obligations use valuable time, forcing companies to take the easy approach to merchandising: repeating assortment breadth and depth from previous seasons, creating store assortments based on store volume, and ranking items by sales volume alone.

Yet, to attract the right customer in today's increasingly competitive environment, assortment planning must focus on creating appropriate product breadth and depth of products based on the customer's desires and shopping patterns, taking into account lifestyles, climates, trends and more. Furthermore, assortment planning must present a compelling mix of products to illustrate the company's strategic vision.

In view of the foregoing, it would be beneficial to provide a method and system that provides efficient implementation of assortment planning decisions for merchandise. Moreover, it would be beneficial to provide a method and system that allows for more flexible assignments of products and stores to assortments.

SUMMARY OF THE INVENTION

The present invention relates to systems and methods for performing assortment definition/planning (i.e., matching the right articles with the right stores at the right times).

According to a first embodiment of the present invention, a method is provided for defining an assortment in a computerized assortment planning system for use in an operative execution system. The method includes assigning a plurality of articles to the assortment for one or more article validity periods, assigning a plurality of stores to the assortment for one or more store validity periods, and releasing the assortment to the operative execution system. Once released to the operative execution system, the articles and the stores are automatically added to and dropped from the assortment based on the validity periods.

According to another embodiment, a system is provided for defining an assortment for use in an operative execution system. The system comprises a central processing unit (CPU) and a storage device coupled to the CPU. The storage device has information stored therein for configuring the CPU to assign a plurality of articles to the assortment for one or more article validity periods, and to assign a plurality of stores to the assortment for one or more store validity periods. The storage device also has information therein for configuring the CPU to release the assortment to the operative execution system. Once released to the operative execution system, the articles and the stores are automatically added to and dropped from the assortment based on the validity periods.

According to yet another embodiment, a program product for defining an assortment for use in an operative execution system comprises machine-readable program code. The program code, when executed, causes one or more machines to perform method steps. The method steps include assigning a plurality of articles to the assortment for one or more article validity periods, assigning a plurality of stores to the assortment for one or more store validity periods, and releasing the assortment to the operative execution system. Once released to the operative execution system, the articles and the stores are automatically added to and dropped from the assortment based on the validity periods.

Other features and advantages of the present invention will become apparent to those skilled in the art from the following detailed description and accompanying drawings. It should be understood, however, that the detailed description and specific examples, while indicating preferred embodiments of the present invention, are given by way of illustration and not limitation. Many modifications and changes within the scope of the present invention may be made without departing from the spirit thereof, and the invention includes all such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagrammatic representation of an exemplary enterprise structure for a large retail company.

FIG. 2 is a diagrammatic representation of an exemplary sales structure for a large retail company.

FIG. 3 is a diagrammatic representation of an exemplary site structure for a large department store chain.

FIG. 4 is a diagrammatic representation of an exemplary article hierarchy for a large retail company.

FIG. 5 illustrates an exemplary view of a particular business type definition.

FIG. 6 illustrates an exemplary view of a layout for articles in a presentation area.

FIG. 7 is a diagrammatic representation of an exemplary merchandise hierarchy.

FIG. 8 is a diagrammatic representation of an exemplary global assortment that links together a plurality of stores and a plurality of articles at specific times.

FIG. 9 is a data-flow diagram showing an exemplary assortment definition process.

FIG. 10 is a data-flow diagram illustrating the process described with reference to FIG. 9 in the context of a specific store and category.

FIG. 11 is a diagram illustrating a matrix spanned by two strategic dimensions which may be used for performing the assortment definition process illustrated in FIGS. 9 and 10.

FIG. 12 is a diagram illustrating an excerpt of a theme structure including a plurality of standard assortments and a plurality of supplementary assortments.

FIG. 13 is a diagram illustrating another example of a standard business type assortment and several store assortments assigned to particular consumer themes.

FIG. 14A shows an exemplary graphical user interface (GUI) for performing assortment definition including a header (upper) area, a table (lower left) area and a store selection (lower right) area.

FIG. 14B shows the GUI of FIG. 14A with the store selection area turned off and the horizontal scroll bar in the table area moved to the far right to show additional columns.

FIG. 14C shows the GUI of FIGS. 14A and 14B with the header area turned off to show additional rows of store assignments in the table area.

FIG. 15 shows an exemplary view of an article hierarchy having various nodes therein assigned to assortments and another node in the hierarchy assigned to a store as a check on the products that are assignable to the assortment and thus the store.

DETAILED DESCRIPTION OF THE EXEMPLARY EMBODIMENTS

FIG. 1 illustrates a general overview of an enterprise structure 10 for a company or enterprise 12 (e.g., “Enterprise XYZ”) having five segments (or data structures): a sales structure 14, a site or store structure 16, an article hierarchy (or theme structure) 18, a merchandise hierarchy 20, and a purchasing structure 22. Enterprise 12 may be any type of company that regularly needs to perform merchandise and assortment definition and planning, such as a large retail company, a service provider, a non-retail supplier of goods, and the like.

Sales structure 14 represents the different sales channels used by enterprise 12. For example, FIG. 2 illustrates one possible arrangement for sales structure 14 as configured for a large retail chain. Sales structure 14 in this example includes an enterprise level node 24 and four sales channel level nodes. The four sales channel nodes include a retail sales channel 25, a wholesale sales channel 26, a distribution center sales channel 27, and an e-commerce sales channel 28. Sales structure 14 may be customizable by a user to include additional or fewer levels, as well as different names, to better represent the sales channels associated with a particular enterprise.

Referring again to FIG. 1, site structure 16 represents the local, operative units within which the sale and logistics handling of merchandise (i.e., products or articles) or services takes place. Typical examples of such sites include stand-alone stores as well as department stores, which unify collections of shops or departments representing various consumer themes (e.g., merchandise categories presented to consumers in unified manner, individual shops in department stores, etc.). FIG. 3 illustrates one possible arrangement for site structure 16 as configured for a large department store chain. In this example, site structure 16 includes an enterprise level 30, a geographic region level 31 (e.g., NE, NW, SE, SW), a department store level 32, and a shop level 33. Site structure 16 may be customizable by a user to include additional or fewer levels, as well as different names, to better represent the sites associated with a particular enterprise.

In contrast to conventional stores, department stores typically do not have inventory-managing character for consumer merchandise, because inventory management on an article or value basis usually takes place at the shop level. Nonetheless, the department store can represent an overreaching inventory management level for consumable materials, advertising materials, and additionals. Although the department store conventionally groups shops at a physical address, this is not a requirement. For example, different shops can exist at separate physical locations and still be assigned logically to the same department store. Unless otherwise specified below, the term “store” may refer to a conventional store, a department store, or any of the individual shops or departments unified by a department store.

Referring again to FIG. 1, article hierarchy 18 represents a hierarchy of articles down to the segment level. As will become clear below, article hierarchy 18 represents one of many possible ways to hierarchically organize and view articles and make assortment decisions. In FIG. 1, article hierarchy 18 is illustrated with a hierarchy ID level (e.g., a number) 34, a division level 35, a category level 36, a subcategory level 37, and a segment level 38. Article hierarchy 18 may be customized by a user to include additional levels (e.g., a subsegment level below segment level 38) or fewer levels, as well as different names, to better represent the merchandise (e.g., products or articles) layout associated with a particular enterprise. According to an exemplary embodiment, theme structures may be defined with up to 10 levels.

Although the names and number of levels in article hierarchy 18 can be customized, one level in article hierarchy 18 must be defined as the “category” level. The category level may be selected to represent the independent presentation spaces in a store that are devoted to merchandise categories presented to consumers in a unified manner. In the department store context, for example, the category level in article hierarchy 18 may be selected to represent differentiated groupings of shops in the department stores such as confectionaries, menswear departments, and ladies wear departments. Alternatively, a lower level in article hierarchy 18 may be selected to represent the different independent presentation spaces for subgroups of merchandise (e.g., long-arm blouses, short-arm blouses, trousers) within each shop in a department store. Other criteria for selecting the category level may also be used.

In an exemplary embodiment, the level in article hierarchy 18 selected to be the category level has several additional properties that are unique to that level. One unique property of the category level is that stores can be assigned only to that level. In FIG. 1, for example, the assignment of shops in site structure 16 to nodes in category level 36 of article hierarchy 18 shows that category level 36 has been defined as the category level. These assignments make sense primarily in the context of department stores, wherein the stores that are assigned to a category are the shops in different department stores which (primarily) present goods from this category. For example, in most department stores there is a section for “men's fashion.” Hence, a category may be defined in the system for “men's fashion,” and this section in the department store may be treated as a shop in the system.

Another unique property of the category level in article hierarchy 18 is that the assignment of articles (as described in detail below) to hierarchy 18 must be unique below the category level. That is, each article can be assigned only once to a node at or below a particular category node. By contrast, the same article can be assigned again to a different node at or above the category level (e.g., the division level).

Reference is now made to FIG. 4 to further illustrate how article hierarchy 18 may be used by an enterprise to better represent merchandise based on, for example, the arrangement of articles and products for displayed in the stores and shops. In this example, article hierarchy 18 has been defined to include seven distinct levels, comprising: an enterprise level 40, a consumer field (CF) level 41, a division level 42, a consumer theme (CT) level 43, a theme module (TM) level 44, an assortment module (AM) level 45, and an article level 46. CF level 41 may be selected to represent different high level groupings of merchandise (e.g., fashion, sport). CT level 43 may be selected to represent merchandise categories presented to consumers in unified manner, such as the individual shops in a department store. TM level 44 may be selected to represent the different independent presentation spaces for subgroups of merchandise (e.g., long-arm blouses, short-arm blouses, trousers) within each shop in a department store. AM level 45 may be selected to group articles according to various criteria such as the time periods during which such articles will be displayed, the stores to which they will be assigned, etc.

According to an exemplary embodiment, the relationships between the various nodes in article hierarchy 18 may be as follows. The relationship between the nodes of each level above AM level 45 and the node(s) in the next lower level may be 1:n. That is, each node in TM level 44 may be assigned or linked to one or more child nodes in AM level 45, while each node in AM level 45 is linked to exactly one parent node in TM level 44. In contrast to the nodes above AM level 45, the relationships between the nodes in AM level 45 and the nodes in article level 46 may be n:m. That is, a single node in AM level 45 may be linked to one or more child nodes in article level 46, while each node in article level 46 may be linked to one or more parent nodes in AM level 45 so long as each parent node in AM level 45 is in a different category. Thus, in the embodiment illustrated in FIG. 4, article node 50 may be linked to both AM node 52 and AM node 54 in AM level 45 because nodes 52 and 54 are assigned to different categories. In particular, AM node 52 is assigned to the category represented by CT node 56 and AM node 54 is assigned to the category represented by CT node 58. In some embodiments, individual articles in article level 46 may be assigned directly to nodes above AM level 45. For example, article node 50 may be linked directly to TM node 53. This assignment is permissible because TM node 53 is assigned to a different category than either CT node 56 or 58. In an exemplary embodiment, the user can set a flag to indicate whether the assignment of individual article nodes to more than one parent node in AM level 45 and/or to other higher level nodes is allowable or prohibited.

After a theme structure has been defined for a company such as described above, one or more business types may be defined for each consumer theme (e.g., each shop in a department store) to further facilitate assortment definition and planning as described below. A business type definition may be a grouping of all stores of a consumer theme, grouped according to criteria level and capacity, using a standardized procedure. Hence, the business type may be defined for every reasonable combination of level type and capacity for a consumer theme. As such, business type definitions can be used to provide strategic grid spacing of stores according to presentation capacity and level, in consultation with division and sales, taking account of location-specific circumstances. The aim of the level type is to describe a CT/store (e.g., a shop in a department store) with regard to the level of the assortment (defined, for example, by price level, brands features, and so on). Thus, the level type of a CT/store is determined based on question such as, in which price categories, with which brands, and which special features is an assortment carried. The capacity type aims to describe a CT/store with regard to its capacity size expressed in, for example, a number of template display racks. Thus, the capacity of a CT/store is determined based on questions such as, how many articles can be carried, with which width and depth.

According to an exemplary embodiment, one or more business types (BT) may be defined for each consumer theme. An exemplary view 91 of a business type definition (with a rule set for capacity index) is shown in FIG. 5. The capacity index indicates a capacity relationship between template display racks (TDR) and individual display racks (IDR). Although not illustrated in view 91, each BT definition may include a specific time reference (e.g., valid-from/valid-to dates). In addition, the capacity type and level type of each BT may be defined by numbers N and M. In this case, the number of the capacity type for each business type represents a particular capacity range (e.g., N=1 may correspond to a capacity index between 0 and 1.0, N=2 may correspond to a capacity index between 1.0 (inclusive) through 2.0, etc.). Similarly, the number of the criteria level for each business type represents the “level” of articles offered for sale (e.g., M=0 may correspond to a flagship store, M=1 may correspond to a high end store, M=2 may correspond to a medium end store, and M=3 may correspond to a low end store). Instead of determining business types based on criteria level and capacity, business types may be determined based on or in combination with other relevant criteria such as historical consumption data by price level.

After the business types have been defined, one or more layout modules may be assigned to each business type definition to facilitate assortment planning such as described below. The layout module provides a pictorial view of the areas in the stores of the selected business type that are available to sell a particular consumer theme. For example, separate regions of the stores may be shown as separate “blocks” on a computer screen, whereby their respective locations and sizes correspond to their actual locations and sizes in the stores. For example, FIG. 6 shows an exemplary assignment plan including a plurality of layout modules 93 (indicated as rectangles) of various capacities. FIG. 6 also illustrates a space 95 for promotions/close-outs and another space 97 for fashion merchandise. This information is obtained beforehand and is stored in a memory for retrieval when particular stores or business types are selected.

Referring again to the five segments of enterprise structure 10 described with reference to FIG. 1, merchandise hierarchy 20 provides an alternative way of hierarchically organizing and viewing articles and making assortment decisions. An exemplary embodiment of merchandise hierarchy 20 is shown in FIG. 7. Merchandise hierarchy 20 represents a long-term article grouping in a classification structure that is independent of the store structure and merchandise presentation layout. Instead, merchandise is grouped in hierarchy 20 based on common inherent characteristics of the merchandise (e.g., all beverages may be grouped together regardless of their type and how or where they are displayed in the stores).

In FIG. 7, a merchandise (MC) level 100 represents the lowest level in hierarchy 20. This means that different articles that are assigned to the same MC node usually have at least the same characteristic(s) represented by the MC node. For example, articles 102, 104 and 106 (comprising three blazers having different styles, sizes and/or colors) in an article level 108 are assigned to a single MC node 110 and thus have at least the same characteristic(s) (e.g., they are all blazers) represented by MC node 110. According to an exemplary embodiment, each article is assigned to exactly one MC node in hierarchy 20, and multiple MC nodes can be grouped together to form merchandise hierarchy (MCH) levels. For example, merchandise hierarchy 20 is illustrated with a first MCH level 112 (comprising a “jackets” category) immediately above MC level 100, and a higher MCH level 114 (comprising a “jackets/coats” category) above MCH level 112. Similar to article hierarchy 18, the topmost layer in merchandise hierarchy 20 is an enterprise level 116. The nodes in the lowermost level in hierarchy 20 and in similar merchandise group hierarchies may be referred to as merchandise categories. Thus, categories may represent differentiated, independently controllable group of articles and/or services that consumers recognize as different and/or exchangeable to satisfy a need.

A merchandise hierarchy may be formed for various reasons. For example, it may be formed to: (i) plan an assortment (as described in detail below), (ii) enable structured analyses in the information system and the planning of target and actual values at the MC level, and (iii) save common data (such as conditions) at superior levels to reduce storage space. According to an exemplary embodiment, the following information may be defined for each MC node: price, color, and size groups; validity periods; n characteristics, and status values. In this embodiment, colors may be saved hierarchically as main colors or single colors. The main colors can have various characteristic values, which represent the single colors. In this case, the single colors are variant-creating characteristics. Accordingly, a merchandise group hierarchy having this structure would allow for analysis of main colors, single colors, and attribute values.

The characteristics of articles in a merchandise hierarchy may be used for classification. Characteristics represent defined properties of an object, such as the color of a blouse. Characteristics help to differentiate objects from one another and find specific articles in the information system (e.g., list all articles with characteristic value “Red” of the “Color” characteristic). Characteristics can be either variant-creating (i.e., used in the definitions of the article variants) or purely informative. According to an exemplary embodiment, two or three-dimensional variant-creating characteristics can be defined for each MC node.

According to anther embodiment, below the MC level, and thus below the entire merchandise hierarchy, characteristic profiles may be defined to segment or specialize the merchandise hierarchy. This may be done to simplify the creation of new generic articles, variants, and single articles.

In this embodiment, a characteristic profile may be used to define the set of values for a characteristic that are permitted in that particular profile. For example, a characteristic profile called “Ladies' sizes, Germany” could define the sizes 34 to 48. Multiple characteristic profiles can be created for multiple merchandise groups. A characteristic profile can be assigned several times within the merchandise group hierarchy. Thus, every article that is assigned to a merchandise group can optionally be assigned to a characteristic profile. According to an exemplary embodiment, the relationship between characteristic-profiles and merchandise groups is n:m. That is, a single characteristic profile can be linked to multiple merchandise groups, and vice versa.

As persons skilled in the art will appreciate, the use of characteristic profiles provides several advantages. For example, characteristic profiles can be used to (i) group sets of colors and sizes, (ii) assign them to the relevant merchandise groups, and (iii) select the suitable profile when creating articles.

Returning again to FIG. 1, purchasing structure 22 models the areas of responsibility and authority in purchasing. It consists of several buyer groups below each purchasing organization. According to an exemplary embodiment, each article is assigned to a unique buyer group. The unique assignment of buyer groups to merchandise groups is preferred, but not required.

Turning now to FIGS. 8-15, a number of embodiments will be presented for performing assortment definition and planning using the structures, hierarchies, business type definitions, layout modules and other features described above to both speed up and simplify the assortment definition and planning processes. Although the description of assortment definition and planning is presented below in the context of a retail planning cycle, the present application is not limited to retail goods or planning cycles.

In accordance with an exemplary embodiment, assortment definition and planning can be performed for various types of merchandise such as fashion merchandise and regular (e.g., stackable, non-fashion, basic, etc.) merchandise. As persons skilled in the art will appreciate, assortment definition and planning for fashion may differ from assortment definition and planning for regular merchandise for various reasons. For example, assortment definition and planning for fashion generally involves: (1) a higher proportion of new articles; (2) shorter life cycles than the assortment planning horizon, and different, reduced possibilities for short-term replenishment; and (3) capacity use is subject to fluctuations within an assortment planning period. Thus, assortment definition and planning for different types of merchandise may be handled differently. In an exemplary embodiment, for example, assortment planning for regular merchandise may be performed at the theme module level and from month-to-month, while assortment planning for fashion may be performed at the consumer theme level and from season-to-season.

In the various embodiments discussed below, assortment definition and planning for an enterprise may be performed using both local assortments and global assortments. When a store or distribution center is first created, an assortment with the same name is also created. This may be referred to as a local assortment. When articles are listed for these local assortments, they can be managed in the respective store in a single step.

Assortments can also be defined which include several stores. These may be referred to as global assortments. Merchandise quantities can be planned for these global assortments, and thus for a group of stores, in the assortment planning processes described below. Articles that are listed for a global assortment can thus be managed for all assigned stores at one time.

With the foregoing in mind, FIG. 8 illustrates a diagram 117 including a global assortment 118 that links together a plurality of stores 120, 122, 124, 126, 128 and 130 with a plurality of articles 132, 134, 136 and 138. According to an exemplary embodiment, articles are always linked to an assortment (either local or global), rather than directly to retail sites.

Global assortments such as assortment 118 may be classified according to assortment type. Assortment type refers to an assortment attribute that makes it possible to control the strategic direction of the assortment and its handling during assortment design/planning and procurement. In one embodiment, the possible values for the assortment type may be configured by the user. For example, assortments can express the following types: standard assortment-fashion; supplementary assortment-fashion; and regular (e.g., non-fashion) assortment.

In the illustrated embodiment, assortment 118 may also be characterized by one or more assortment dimensions 140. In general, assortment dimensions are attributes of an assortment that can be used during an assortment definition process to group retail sites together to design standardized assortments. That is, the assortment dimensions are used to group together retail sites with similar characteristics to form an assortment that applies to all stores in the group. Retail sites can be grouped differently for different assortment types, i.e., different dimensions can be used as grouping criteria. According to an exemplary embodiment, an assortment can be defined using up to three assortment dimensions. The respective value range or level of the assortment dimensions may be defined and configured by a user. The value range or level of an assortment dimension can be defined differently for each assortment type. By way of example, possible assortment dimensions may include the following retail site characteristics: capacity, price level/grade (high fashion, essential, basic) or sales for a certain group of merchandise, geographical region or location, climactic zone (warm weather, cold weather), demographics (urban, suburban), retail concept, and so on.

With the foregoing in mind, an exemplary assortment may comprise a plurality of retail sites (e.g., store consumer themes or shops in a department store) grouped by category (e.g., consumer theme) with regard to price level/grade and capacity type. Grouping stores by price level and capacity is equivalent to grouping stores by business type as discussed above. In this example, one assortment dimension is the capacity, which may be represented by the following values: “0” to “9” for assortments with type “standard assortment-fashion” and “supplementary assortment-fashion;” and “1” to “6” for assortments with type “regular assortment.” The other assortment dimension in this example is the price level/grade, which may be used only for assortment type “standard assortment-fashion” with the four values “1”—high-priced, “2”—mid-priced, “3”—low-priced, and “0” for exceptional cases (e.g., flagship stores and showpieces).

Referring again to the embodiment illustrated in FIG. 8, assortment 118 may also be characterized by a category 142 (e.g., category level 36 in FIG. 1 or consumer theme level 43 in FIG. 4). Alternatively, assortment 118 may be characterized by another level in article hierarchy 18 such as subcategory level 37 or segment level 38 in FIG. 1. In assortments characterized by store category, two of the three assortment dimensions can be classified as, for example, level type and capacity type. Accordingly, a matrix-like definition of the store types can be mapped. By selecting a certain level type, the corresponding capacity types (e.g., extra small, small, medium, large, extra large) can be planned first. The planned quantities can then be copied to assortments with the same capacity type, but an alternate level type.

Referring once again to FIG. 8, articles 132-138 in the illustrated embodiment are not directly assigned to assortment 118. Instead, articles 132-138 are linked to assortment 118 by assortment versions 144 and 146 during assortment planning. In the illustrated embodiment, each assortment version 144, 146 is active or valid for a specified period of time (e.g., valid-from/valid-to dates). For example, articles 132, 134 and 136 are linked to assortment 118 by assortment version 144, which is active between dates/times T1 and T3. Similarly, articles 132, 134 and 138 are linked to assortment 118 by assortment version 146, which is active between dates/times T3 and T4. As persons skilled in the art will recognize, the foregoing time dependencies of the assignments of articles 132-138 to assortment 118 provides for automatic regular (e.g., every month or six weeks) releases of merchandise in the stores to maintain assortment freshness.

According to an exemplary embodiment, each assortment version 144, 146 may represent one or more shelves 148 in each store assigned to assortment 118. Alternatively, each assortment version 144, 146 may represent one or more display racks (which in turn may comprise a plurality of shelves), or one or more layout modules (which in turn may comprise a plurality of display racks). If desired, a space optimization program (SOP) 150 may be used to determine the optimum layout of articles for each assortment version 144, 146.

In the embodiment illustrated in FIG. 8, the assignment of stores 120-130 to assortment 118 during assortment definition also includes time dependencies. For example, stores 120 and 122 may be linked to assortment 118 between dates/times T1 and T2, while stores 124 and 126 may be assigned to assortment 118 starting at dates/times T2 and T3, respectively. In the illustrated embodiment, the assignments of the latter two stores 128 and 130 to assortment 118 is not time dependent, i.e., stores 128 and 130 will remain in assortment 118 until such time as assortment 118 is canceled or changed. The time dependencies of the store assignments may be stored in a data structure that also stores the store assignments.

As indicated in FIG. 8, the assignment of stores to an assortment (i.e., the upper half of diagram 117) may be referred to herein as assortment definition. By contrast, the assignment of articles to an assortment (i.e., the lower half of diagram 152) may be referred to herein as assortment planning. Of course, persons skilled in the art will recognize that different retail merchants may utilize different terms for referring to these two concepts and hence the specific terms of assortment definition and assortment planning should be understood as provided merely for purposes of facilitating explanation of the various exemplary embodiments.

Referring now to FIG. 9, a data-flow diagram shows an exemplary process 154 for performing assortment definition (i.e., defining assortment objects and the store assignments). According to an exemplary embodiment, process 154 includes a classification algorithm engine 156 that receives inputs such as store information 158, category information 160, and sales information 162. The source(s) of input information provided to engine 156 may comprise a keyboard, mouse, or similar input device. Alternatively, the source(s) of input information provided to engine 156 may comprise one or more storage systems, such as a database. As another alternative, the source(s) of input information to engine 156 may comprise one or more computer systems that are locally or remotely connected to engine 156. In the illustrated embodiment, for example, sales information 162 is shown as being provided from a database which contains historical transaction data (e.g., sales data from a comparable period in a prior year, which may be adjusted for recent sales trends). Sales data may also include forecasted or projected sales transaction data for a future time period (e.g., the upcoming season). Forecasted sales data may also be based on a markdown profile for an article or group of articles. The assignment of a markdown profile to an article or group of articles is described in further detail in a co-pending application entitled “Automated Control Of Pricing Using Markdown Profiles” filed on Jun. 21, 2004, the entire contents of which are incorporated herein by reference.

Regardless of the source(s) of input information 158-162, classification engine 156 performs a classification algorithm that mines the input information to identify one or more dimensions 164 that may be suitable for characterizing the stores that are eligible for inclusion in the assortment. After completing this task, classification engine 156 provides the identified dimension information 164 to an assortment definition engine 166 along with the original input information (e.g., store information 158 and category information 160) or a subset thereof.

Assortment definition engine 166 uses the dimension information (possibly after approval by a user) and other input information (e.g., information 158-160) along with previous and existing store assignments and assortment information 168 to perform a matching process that clusters or groups stores into proposals for store-assortment assignments 170. The matching criterion is based on the similarity of dimension values of stores (e.g., as found by the classification algorithm) to the dimension values, which may be assigned manually to the assortment object. The proposed store-assortment assignments 170 may be presented to management for approval and release and/or used as inputs to one or more downstream processes without review. The foregoing process may be utilized to automatically generate proposals of suitable store groupings (e.g., by business type) for assortments as well as when to implement them.

With reference now to FIG. 10, an example of how assortment definition process 154 may be used to perform store-assortment assignments in a specific context will be provided. In the illustrated embodiment, store input information 158 includes the locations of the stores (e.g., stores in the northeast) and associated category input information 160 (e.g., the consumer theme of “Men's Fashion”). Based on store master and sales ranking information, classification engine 156 identifies the region and sales volume of each store. The particular dimensions (e.g., region and sales volume) used to analyze each store and generate associated dimension information 164 (e.g., that the store is in the region NE and is a high volume store with respect to the category “men's fashion”) may be prescribed by a user.

This dimension information 164 is provided to assortment definition engine 166 along with store input information 158 and category input information 160. At the same time, assortment definition engine 166 also receives information regarding any previous and existing store assignments and assortments 168 that are based on similar dimension and category information. Using this data, assortment definition process 154 is able to provide a closed-loop system that allows for improved refinement over subsequent iterations. As explained above, assortment definition engine 166 performs a matching process and outputs a recommended store-assortment assignment 170. The end result of this process is that a particular input store is in the northeast region and is a high sales volume store for men's fashion, and therefore it is assigned to a certain assortment on this basis. Other stores located in different regions and/or having different sales volumes for the men's fashion category would be matched with similar stores and the results used to provide other proposed store-assortment assignments. In addition, this process may be performed for other categories besides men's fashion to create additional store-assortment assignments.

As persons skilled in the art will appreciate, the foregoing assortment decision process creates proposed store-assignment assortments that allow for more efficient assortment planning (i.e., matching the right articles with the rights stores at the right times). According to one embodiment, the proposed store-assortment assignments generated by process 154 may be presented to a user via an assortment definition graphical user interface (GUI) 224 such as shown in FIGS. 14A-14C and described below.

To further illustrate the concepts described above, an example of how assortment definition process 154 may be used to define an assortment of stores for a particular category of articles (e.g., handbags) is provided with reference to FIG. 11. In this example, the assortment creation process is graphically depicted using an assortment planning matrix that includes two dimensions, labeled: “Price Level” (vertical axis) and “Capacity” (horizontal axis). The assortment definition process may be initiated using this matrix by defining an assortment object for every meaningful combination of price level and capacity. For example, “Assortment 35” may be defined and placed in square 172 to represent stores assigned with the classification price level of “3” (e.g., low price) and capacity of “5” (e.g., medium). In addition, Assortment 35 may be assigned to the category “Handbags.” In this example, Assortment 35 may correspond to a shelf of a particular display rack of a particular layout module carrying low priced handbags for fashionable customers in medium capacity stores. This shelf is typically replanned regularly, and the temporal evolution is captured by the “assortment version” (or layout module version). Similar planning matrices may be created for each additional category of interest (e.g., suitcases, wallets, backpacks, etc.).

Next, stores may be assigned to the assortments (i.e., store clustering) using assortment definition process 154 described above. This is accomplished by analyzing, for every store, all historical sales data for handbags and classifying a capacity type according to the dimension definition. For example, if a particular input store has the capacity to display 100 handbags at a time, it might be classified as a type “5” store. According to an exemplary embodiment, this analysis may be performed automatically using automated classification engine 156 described above.

In addition to classifying each store by capacity, each store in the embodiment of FIG. 11 is also classified along the “price level” dimension. This may be done, for example, by getting feedback from store managers, cash register receipts, or demographic analysis provided by external companies. This information may be held in a store master database and be updated on a periodic but relatively infrequent basis, such as once per year.

The result of considering all stores using the process discussed above is assignments of stores to assortments, which may be used as inputs to an assortment definition engine (e.g., engine 166 in FIG. 9). According to an exemplary embodiment, the temporal validity of the store assignments is specified and proposals can be revised and released. The resulting configuration may be checked for consistency by the system without need for human input.

Referring again to the illustrated example, the stores assigned to Assortment 35 represents a group of similar stores for which it is logical to carry a similar set of articles. This set of articles may be determined in a different step and assigned to Assortment 35 to establish the desired article-assortment-store relation.

The assortment decision/planning process and system described above thus create new layout module versions which automatically become valid and later invalid after predetermined periods of time have elapsed and assigns articles (e.g., handbags) to this version according to the strategic target group (e.g., price level of “3”+capacity level of “5”). For example, an assortment layout module version may be defined to become valid after two months have elapsed and to become invalid after an additional two months have elapsed. After finalizing this plan, the layout module version is released, which means that the ordering process for the relevant articles is started (at least for those articles which are supplied by automatic replenishment).

As explained above, assortment planning for fashion merchandise and assortment planning for regular (e.g., non-fashion, stackable, basic, etc.) merchandise may be handled differently. For example, whereas the grouping—and thus the standardization—in assortment planning for fashion merchandise may be performed primarily using standard assortments from the business type definitions at the consumer theme level, the grouping for regular merchandise typically takes place at a deeper level in the theme structure, e.g., at or below the theme module. This difference is best illustrated in FIG. 12, which shows an excerpt of a theme structure 174. In theme structure 174, a standard (ST) assortment 176 comprising fashion merchandise is linked to a consumer theme (CT) node 178. Theme structure 174 further includes two additional ST assortments 180 and 182, which may be linked to other CT nodes (not shown) in theme structure 174 or to CT node 178 during consecutive time periods in the future. In addition to ST assortments 176, 180, 182, two supplementary assortments 184 and 186 comprising fashion merchandise are linked to one or more CT nodes (not shown).

As explained above, the assortments for regular merchandise are handled somewhat differently in the exemplary embodiment. In particular, assortments 188 and 189 comprising regular merchandise are linked to theme module (TM) level nodes 190 and 191, respectively. Moreover, two additional standard independent assortments 192 and 193 comprising regular merchandise may be assigned to one or more TM nodes (not shown) presently or to TM node 190 in the future. Similarly, another standard independent assortment 194 for regular merchandise may be assigned to another TM node (not shown) presently or assigned to TM node 191 in the future. As illustrated, each of the standard independent assortments 188, 189, 192, 193 and 194 for regular merchandise may comprise a layout module (LM), which in turn is defined by one or more display racks (DRs) of regular merchandise.

According to an exemplary embodiment, a store consumer theme is usually assigned to several assortments. Moreover, each store consumer theme typically has exactly one standard assortment (business type assortment), which is derived from the business type definition as described above. Because the standard assortment contains only fashion articles in this embodiment, business type assortments are not assigned any articles for consumer themes that have only regular merchandise theme modules. Instead, the regular merchandise articles are assigned to the store consumer theme via the assortments in the layout modules.

An illustration of the foregoing embodiment is illustrated in connection with FIG. 13. In this example, a consumer theme 200 identified as “Socks for BT 12” is linked to three assortments 202, 204 and 206. Assortment 202 is a standard assortment for fashion (i.e., a grouping of stores based on business type), which in turn contains links to a number of theme modules. In the illustrated embodiment, standard assortment 202 includes links to a basic theme module 208 along with specialized theme modules for elegance 210, appeal 212, young fashion 214, business fashion 216, casual dress 218, and children's clothing 220. Assortments 204 and 206 are both store assortments 222. In particular, store assortment 204 is a store-specified assortment for a particular brand (e.g., “Fogal”) of products, while store assortment 206 is a supplementary assortment for area coverage (i.e., to fill gaps in a particular store or group of stores). The capacity of each assortment/sub-assortment is expressed in terms of a number of display racks (DRs).

According to an exemplary embodiment, the grouping of stores by business type is sufficient to provide for a large majority (e.g., 95% or more) of the assortment planning for the stores in each group as a whole. That is, the stores of an enterprise are preferably sufficiently uniform when grouped by business type (i.e., the same consumer theme/capacity/level) that most or all of the necessary assortment planning for these stores can be accomplished at the business type level. Then, the assortment planning necessary to link the remaining small amount of articles (e.g., 5% or less) to the right stores at the right times can be accomplished using supplementary store assortments. For example, the remaining articles can be assigned using supplementary (global) assortments (e.g., for store-specific brand management) based on store capacity or, in some cases, using supplementary (local) assortments (e.g., for flagship stores).

Referring now to FIGS. 14A-14C, a graphical user interface (GUI) 224 is illustrated for displaying, revising and approving store-assignment assortments, such as may generated by assortment definition process 154. In an exemplary embodiment, GUI 224 may be configured to perform one ore more of the following functions:

• • (i) Store dimension determination;
  • (ii) Automatic assortment assignment;
  • (iii) Add/change/delete new planned assortments;
  • (iv) Add/change/delete new planned assortment assignments;
  • (v) Master data display of store and assortment; and
  • (vi) Filtering/sorting/layout adjusting the list.

In the illustrated embodiment, GUI 224 includes a header area 226, a table area 228, and a store selection area 250. Header area 226 shows selection criteria for the assortments and the associated store assignments which may be revised. Header area 226 includes a plurality of selection criteria fields including an assortment type field 230, an article hierarchy ID field 232, an article hierarchy node (e.g., a category) field 234, and a validity (or key) date field 236. All assignments of stores to assortments that are valid at the date provided in field 234 are shown in table area 228 (discussed in detail below). In most cases, the validity date entered in field 234 is chosen to be in the future because assortment definition process 154 typically defines the store assignment configuration which should be valid for instances of the next year.

Based on selection data entered into header area 290, all of the actual (i.e., current) and planned assignments of stores to assortments are presented in table area 228. In the illustrated embodiment, table area 228 includes an exception column 238, a plant (or store) column 240, an assortment column 241, a date from column 242, a date to column 244, a capacity type column 246, and a price level type column 248.

Exception column 238 shows the status of each assignment of a store to an assortment. Green indicates an assignment that has already been released to an operative execution system, i.e., the store-assortment assignment is actually in use. Yellow indicates an assignment that has been planned but not yet released. Red indicates an assignment that is incomplete. Assignments that are planned are not visible “outside” the planning system. After a planned assortment is approved and released to operative systems, it receives the status released and the yellow light in column 238 is replaced by a green light. From a planning standpoint, it may be important to know whether the assignments are already used operatively because, if so, changes should be limited. In the illustrated embodiment, operative (e.g., “actual”) assignments are shown in the left side columns of table area. If an operative assortment is being replaced by a new (planned) assignment, the new (planned) assignment is shown in the same row in the far right hand columns (see FIGS. 14B and 14C).

Continuing with the description of table area 228, store column 240 shows the stores, including the technical name (e.g., unique ID) and the associated description. Assortment column 241 shows the actual/planned/incomplete assortment, including the technical name (e.g., unique ID) and the associated description. Date from column 242 and date to column 244 show the validity period for the assignment. Capacity column 246 shows the capacity type of the store, and price level column 248 shows the price level type of the store.

In the illustrated embodiment, GUI 224 may includes a plurality of buttons which may be selected (e.g., by clicking with a mouse) to invoke various functions associated with assortment definition. For example, GUI 224 may include a “Find Assortments” button that may be selected to launch the store matching process and (potentially) propose a new assortment for each store. If this proposal is found acceptable to the user and accepted, a new (planned) assortment is created and the old assignment is terminated.

Store selection area 250 shows all of the stores that match the selection criteria entered into fields 230-236 in header area 224 but have not yet been assigned to an assortment. In an exemplary embodiment, store selection area 250 includes a tree structure 252 that includes all of the eligible stores. In this embodiment, the stores may be dragged from tree 252 and dropped onto an assortment in table area 228 to create a new assignment manually.

With reference now to FIG. 15, an exemplary embodiment of an assortment definition/planning system for restricting the assignment of certain types of products to particular stores is shown and described. In FIG. 15, an article hierarchy 300 is illustrated with a structure such as described above with reference to article hierarchy 18 in FIG. 1. In particular, an uppermost division level node 302 is shown linked to a pair of category level nodes 304 and 306, each of which is shown linked to a pair of subcategory nodes 308, 310, 312, 314. More specifically, category node 304 is shown linked to subcategory nodes 308 and 310, while category node 306 is shown linked to subcategory nodes 312 and 314. In turn, each subcategory node 308, 310, 312 and 314 is shown linked to a number of segment nodes. It will be understood that each segment node may be linked to one or more generic articles or article variants (not shown in FIG. 15). It will also be understood that the particular structure of hierarchy 300 shown in FIG. 15 is merely exemplary and that more or fewer levels could be used, as well as different names for the various levels.

As described above, one or more nodes in hierarchy 300 may be assigned (or linked) to an assortment for purposes of assigning a group of products to that assortment (and thus the stores in that assortment) during assortment planning. For example, subcategory node 312 may be assigned to a pair of assortments 316 and 318 to provide a group assignment of the products under node 312 to assortments 316 and 318. It may be desirable to assign a single node to two assortments, for example, when assortment 316 is for small stores and assortment 318 is for large stores. As another example, subcategory node 314 may be assigned to a pair of assortments 320 (for small stores) and 322 (for large stores) to assign the products under node 314 to assortments 320 and 322. After each of the foregoing assignments of a subcategory node to an assortment is made, one or more products beneath the subcategory node may be excluded (e.g., using a suitable GUI) from the assortment as explained above. Although not illustrated in FIG. 15, nodes above or below the subcategory level could also (or alternatively) be assigned to the assortments.

In addition to the assignments of products to assortments, it is also necessary to assign stores to the assortments so that the desired products are provided to the correct stores at the proper times. Typically, the assignment of the stores to the assortments is performed prior to assigning the products to the assortments using an assortment definition process such as described above in detail. In FIG. 15, a store (or shop) 324 is shown as having already been assigned to assortments 316, 318, 320 and 322.

In an exemplary embodiment, an additional link can be established to create a check or restriction on the types of products that are assignable to a particular store during assortment planning. More specifically, a particular node at one level (e.g., a category level) in an article hierarchy may be assigned to a store to indicate that only products below that node are assignable to that store. In FIG. 15, for example, a link 326 can be established between category node 306 and store node 324 to restrict the types of products that are assignable to store 324 to only those products below node 306. Thus, while the assignment of subcategory 312 to assortment 316 is permissible, the assignment of subcategory 310 to assortment 316 is not permissible (as indicated by a dashed line 328). The assortment planning system may be configured so that any impermissible assignments are completely prevented by the system. Alternatively, the impermissible assignments may simply flagged to users as possible errors in the system but allowed to exist. As yet another possibility, impermissible assignments may be overridden manually, but only when appropriate supervisory approval is given (e.g., by entry of certain passwords).

As persons skilled in the art will recognize, a restriction or check such as described above with reference to FIG. 15 may be particularly beneficial in the context of department stores. For example, if category nodes 304 and 306 represent women's fashion and men's fashion, respectively, and store 324 represents a men's wear shop in a department store, then it may be desirable to establish a link between category node 306 and store 324. When this assignment is made, any attempt to assign women's fashion products to store 324 during assortment planning would be flagged as impermissible.

According to various exemplary embodiments, a replenishment system that receives data regarding one or more articles may be used to replenish items. The data regarding the article may be received from any number of sources. For example, in one embodiment, data regarding one or more articles is received by the replenishment system from an assortment planning system. In another embodiment, data regarding one or more articles is received by the replenishment system from an article master data management system. In another embodiment, data regarding one or more articles is received by the replenishment system from a best seller/slow seller management system configured to periodically identify articles that are selling at a rate faster or slower than a rate determined by a planned sales curve. In another embodiment, data regarding one or more articles may be received by the replenishment system from a combination of these inputs and or additional inputs, including manual input by a user from a keyboard, mouse, or other input device.

The replenishment system uses received data regarding the articles to implement a replenishment process. In a first step, the replenishment system determines the articles that are to be included in the replenishment process. For example, in one embodiment, the replenishment system may be configured such that only data regarding articles associated with a particular predetermined “management type” is automatically forwarded to the replenishment system and included in the replenishment process. The management type may be, for example, a predetermined parameter included in data from either an assortment planning system or an article master data management system indicating whether a particular article is to be replenished using the replenishment process or another process and/or system. Accordingly, in one embodiment, all articles for which data is received by the replenishment system are automatically included in the replenishment process. In another embodiment, the articles to be included in the replenishment process are determined in response to user input designating which articles are to be included in the replenishment process, and data regarding these articles is then received by the replenishment system.

In another step (e.g., a second step), the replenishment system determines a supply channel for each article. For example, the replenishment system may determine whether an article is to be sourced directly from a vendor or from an existing supply in a particular warehouse. The replenishment system may also determine the particular routing of the article (e.g., cross-docking, direct delivery, etc.). In one embodiment, the supply channel for each article is determined according to data for each article from either an assortment planning system or an article master data management system indicating a particular supply channel. In another embodiment, the particular supply channel for each article may be determined by the replenishment system in response to user input designating a particular supply channel for each article.

In another step (e.g., a third step), the replenishment system determines the store in which each article is to be replenished. In one embodiment, the replenishment system determines the store in which each article is to be replenished according to a predetermined “business type” parameter. The business type parameter may be a parameter assigned by an assortment planning system which associates a particular article or group of articles with a particular store or grouping of stores based on, for example, a targeted price range or level for the article or group of articles to be replenished and the store or group of stores, and/or a particular capacity level or range associated with the article or group of articles and the store or group of stores. For example, in one embodiment, the replenishment system may receive the business type parameter from the assortment planning system indicating that a group of articles to be replenished using the replenishment process, such as “men's athletic socks,” is associated with a particular store or group of stores carrying products in a mid-level price range and at a high capacity level. The replenishment system then uses this data to determined the store or group of stores in which the article or group of articles is to be replenished. In another embodiment, the particular store in which the article is to be replenished may be determined by the replenishment system in response to user input designating a particular store for each article.

In another step (e.g., a fourth step), the particular method of replenishment is determined by the replenishment system. The replenishment method may be automatic replenishment, manual replenishment, etc. In one embodiment, the replenishment system may be configured such that only data regarding articles associated with a particular predetermined management type indicating automatic replenishment is automatically forwarded to the replenishment system and included in the replenishment process. In this embodiment, all articles for which data is received by the replenishment system are automatically determined as requiring automatic replenishment. In another embodiment, the particular method of replenishment may be determined by the replenishment system in response to user input designating a particular method of replenishment.

In another step (e.g., a fifth step), supply parameters are determined for each store in which the article or group of articles is to be replenished. The supply parameters may include, for example minimum and maximum supply quantities of the article for each store, as well as the validity period of each article for each store. The validity period of each article may be, for example, a range of dates during which an article or group of articles will be displayed and offered for sale at each particular store. In one embodiment, the replenishment system determines the supply parameters for each store in which the article or group of articles to be replenished according to supply parameter data received from, for example, an assortment planning system or article master data management system. In another embodiment, the supply parameters for each store may be determined by the replenishment system in response to user input designating a particular store for each article.

In another step (e.g., a sixth step), a requirement quantity is determined for each article. The actual determination of the requirement quantity depends on the supply parameters as well as sales data for each article or group of articles. Sales data for each article may include, for example, actual sales data (e.g., actual sales and supply of the article) and projected sales data for each article. Actual sales data may be provided to the replenishment system from, for example, a best seller/slow seller management system. Projected sales data may be supplied to the replenishment system in the form of, for example, a markdown profile for a particular article.

In another step (e.g., a seventh step), the replenishment quantity determined for each article by the replenishment system is reconciled against an available budget and with actual store capacity for each article or group of articles to determine whether actual funds and capacity are available to support the replenishment quantity for each article. For example, in one embodiment, the replenishment system may receive one or more budget parameters and/or one or more capacity parameters in the form of merchandised or assortment planning data from an assortment planning system or another system. The replenishment system may then reconcile the replenishment quantity with the budget parameter and the actual capacity parameter.

In another step (e.g., an eighth step), a supply quantity for each article is determined.

In another step (e.g., a ninth step), order optimization is performed.

In another step (e.g., a tenth step), a purchase order is transferred to a central warehouse or vendor according to the determined supply channel or supply source.

In this way, supplies for articles or groups of articles may be efficiently and automatically replenished according to planning and sales data from various sources. The use of actual and projected sales data in the determination of the requirement quantity allows for early identification and automatic replenishment of increased quantities of articles that are selling at rates faster than originally anticipated, as well as decreased replenishment quantities for articles that are selling at rates slower than originally anticipated. The use of actual store capacities in determining the quantity of an item to be automatically replenished ensures that quantities of particular articles are not procured beyond the capacity of a particular store or group of stores.

As noted above, embodiments within the scope of the present invention include program products comprising computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, such computer-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above are also to be included within the scope of computer-readable media. Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.

In some embodiments, the present invention is described in the general context of method steps, which may be implemented in one embodiment by a program product including computer-executable instructions, such as program code, executed by computers in networked environments. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

The present invention in some embodiments, may be operated in a networked environment using logical connections to one or more remote computers having processors. Logical connections may include a local area network (LAN) and a wide area network (WAN) that are presented here by way of example and not limitation. Such networking environments are commonplace in office-wide or enterprise-wide computer networks, intranets and the Internet. Those skilled in the art will appreciate that such network computing environments will typically encompass many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination of hardwired or wireless links) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions of the invention might include a general purpose computing device in the form of a conventional computer, including a processing unit, a system memory, and a system bus that couples various system components including the system memory to the processing unit. The system memory may include read only memory (ROM) and random access memory (RAM). The computer may also include a magnetic hard disk drive for reading from and writing to a magnetic hard disk, a magnetic disk drive for reading from or writing to a removable magnetic disk, and an optical disk drive for reading from or writing to removable optical disk such as a CD-ROM or other optical media. The drives and their associated computer-readable media provide nonvolatile storage of computer-executable instructions, data structures, program modules and other data for the computer.

Software and web implementations of the present invention could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various database searching steps, correlation steps, comparison steps and decision steps. It should also be noted that the word “component” as used herein and in the claims is intended to encompass implementations using one or more lines of software code, and/or hardware implementations, and/or equipment for receiving manual inputs.

It is important to note that the above-described preferred and alternative embodiments of the present invention are illustrative only. Although the invention has been described in conjunction with specific embodiments thereof, those skilled in the art will appreciate that numerous modifications are possible without materially departing from the novel teachings and advantages of the subject matter described herein. For example, although the stores in FIG. 8 above are illustrated and described as being linked directly to the assortments, the assignment could be via assortment versions as with the products. Similarly, the assortment versions used for linking the products to the assortments could be eliminated and instead the products linked directly to the assortments. As another example, the articles described in the foregoing exemplary embodiments could be pre-packed articles that comprise standard collections of sizes and/or colors or other variants of each article. Accordingly, these and all other such modifications are intended to be included within the scope of the present invention. Other substitutions, modifications, changes and omissions may be made in the design, operating conditions and arrangement of the preferred and other exemplary embodiments without departing from the spirit of the present invention.

Claims

1. One or more non-transitory machine-readable media for defining an assortment plan in a computerized assortment planning system using an automated process, the machine-readable media comprising program code stored therein executable by one or more machines to perform the automated process, the automated process comprising: assigning a first article to the assortment plan, the assortment plan being configured to match products to stores based on a store type, a store capacity, a store space on, product data, and timing data, the first article being assigned to the assortment plan for a first article validity period;assigning a second article to the assortment plan, the second article being assigned to the assortment plan for a second article validity period;assigning a first store to the assortment plan, the first store being assigned to the assortment plan for a first store validity period;assigning a second store to the assortment plan, the second store being assigned to the assortment plan for a second store validity period;adding the first article to the assortment plan based on the first article validity period;adding the second article to the assortment plan based on the second article validity period;determining that the first article will be in a first delivery based on the assortment plan;determining that the second article will be in a second delivery based on the assortment plan;determining an automatic replenishment procedure based on the assortment plan;storing a determination of the assortment plan;determining a requirement quantity for the first article based on both actual sales data and projected sales data associated with the first article as well as one or more supply parameters of the automatic replenishment procedure, wherein the projected sales data is based on a markdown profile associated with a sales period of the first article, the sales period being divided into a plurality of predetermined markdown time periods, the markdown profile including a plurality of proposed markdowns, wherein each proposed markdown in the plurality of markdowns is associated with one of the predetermined markdown time periods during the sales period, wherein each proposed markdown is based on a difference between a target sales quota and an actual sales quota at the predetermined markdown time period with which the proposed markdown is associated, and wherein the markdown profile is established prior to the sales period of the first article and the markdowns are automatically applied over the course of the sales period based on comparison of actual sakes with target sales for each predetermined markdown time period;reconciling the determined requirement quantity against available budget and store capacity; andcrating a purchase order for the first article based on the reconciling step.

2. The one or more non-transitory machine-readable media of claim 1, wherein the assortment plan comprises assortment dimensions.

3. The one or more non-transitory machine-readable media oaf claim 2, wherein the assortment dimensions comprise a demographic data and a retail concept data, the assortment dimensions further comprise at least one of a retail site capacity, a retail site price level, a location data, and sales data for a group of merchandise.

4. The one or more non-transitory machine-readable media of claim 3, wherein the first store validity period and the second store validity period are the same.

5. The one or more non-transitory machine-readable media of claim 3, wherein the first store validity period and the second store validity period are different.

6. The one or more non-transitory machine-readable media of claim 1, wherein the assortment plan comprises assortment dimensions, the assortment dimensions comprising a level type and a capacity type.

7. An assortment planning system for determining an assortment plan, comprising: a central processing unit (CPU); anda storage device coupled to the CPU and having information stored therein for configuring the CPU to:assigning a first article to the assortment plan, the assortment plan being configured to match products to stores based on a store type, a store capacity, a store space utilization, product data, and timing data, the first article being assigned to the assortment plan for a first article validity period;assigning a second article to the assortment plan, the second article being assigned to the assortment plan for a second article validity period;assigning a first store to the assortment plan, the first store being assigned to the assortment plan for a first store validity period;assigning a second store to the assortment plan, the second store being assigned to the assortment plan for a second store validity period;adding the first article to the assortment plan based on the first article validity period;adding the second article to the assortment plan based on the second article validity period;determining that the first article be in a first delivery based on the assortment plan;determining that the second article will be in a second delivery based on the assortment plan;determining an automatic replenishment procedure based on the assortment plan;storing a determination of the assortment plan;determining a requirement quantity for the first article based on both actual sales data and projected sales data associated with the first article as well as one or more supply parameters of the automatic replenishment procedure, wherein determining the requirement quantity for the first article based on both actual sales data and projected sales data comprises comparing an actual sales rate of the first item with a protected sales rate and determining the requirement quantity based on the comparison, wherein the projected sales data is based on a markdown profile associated with a sales period of the first article, the sales period being divided into a plurality of predetermined markdown time periods, the markdown profile including a plurality of proposed markdowns, wherein each proposed markdown in the plurality of markdowns is associated with one of the predetermined markdown time periods during the sales period, wherein each proposed markdown is based on a difference between a target sales quota and an actual sales quota at the predetermined markdown time period with which the proposed markdown is associated, and wherein the markdown profile is established prior to the sales period of the first article and the markdowns are automatically applied over the course of the sales period based on comparison of actual sales with target sales for each predetermined markdown time period;reconciling the determined requirement quantity against available budget and store capacity; andgenerating a purchase order for the first article based on the reconciling step.

8. The system of claim 7, wherein the assortment plan comprises assortment dimensions.

9. The system of claim 8, wherein the assortment dimensions comprise a demographic data and a retail concept data the assortment dimensions further comprise at least one of a retail site capacity, a retail site price level, a location data, and sales data for a group of merchandise.

10. The system of claim 9, wherein the first store validity period and the second store validity period are the same.

11. The system of claim 9, wherein the first store validity period and the second store validity period are different.

12. The system of claim 7, wherein the assortment plan comprises assortment dimensions, the assortment dimensions comprising a level type and a capacity type.

13. The system of claim 7, wherein determining the requirement quantity based on the comparison of the actual sales rate with the projected sales rate comprises reducing the requirement quantity when the actual sales rate is lower than the projected sales rate and increasing the requirement quantity when the actual sales rate is higher than the projected sales rate.

14. A program product for defining an assortment plan in an assortment planning system, the program product comprising one or more non-transitory machine-readable media having machine-readable program code stored thereon for causing, when executed, one or more machines to perform the following method steps: assigning a plurality of articles to the assortment plan, the assortment plan being configured to match products to stores based on a store type, a store capacity, a store space utilization, product data, and timing data, each of the articles being assigned to the assortment one or more article validity periods;assigning a first article to the assortment plan, the first article being assigned to the assortment plan for a first article validity period;assigning a second article to the assortment plan, the second article being assigned to the assortment plan for a second article validity period;assigning a first store to the assortment plan, the first store being as assigned to the assortment plan for a first store validity period;assigning a second store to the assortment plan, the second store being assigned to the assortment plan for a second store validity period;adding the first article to the assortment plan based on the first article validity period;adding the second article to the assortment plan based on the second article validity period;determining that the first article will be in a first delivery based on the assortment plan;determining that the second article will be in a second delivery based on the assortment plan;determining an automatic replenishment procedure based on the assortment plan;storing a determination of the assortment plan;determining a requirement quantity for the first article based on both actual soles data and projected sales data associated with the first article as well as one or more supply parameters of the automatic replenishment procedure, wherein the projected sales data comprises a markdown profile associated with a sales period of the first article, the sales period being divided into a plurality of predetermined markdown time periods, the markdown profile including a plurality of proposed markdowns, wherein each proposed markdown in the plurality of markdowns is associated with one of the predetermined markdown time periods during the sales period, wherein each proposed markdown is based on a difference between a target sales quota and an actual sales quota at the predetermined markdown time period with which the proposed markdown is associated, and wherein the markdown profile is established prior to the sales period of the first article and the markdowns are automatically applied over the course of the sales period based on comparison of actual sales with target sales for each predetermined markdown time period;reconciling the determined requirement quantity against available budget and store capacity; andgenerating purchase order for the first article based on the reconciling step.

15. The program product of claim 14, wherein the assortment plan comprises assortment dimensions.

16. The program product of claim 15, wherein the assortment dimensions comprise a demographic data and a retail concept data, the assortment dimensions Further comprise at least one of a retail site rapacity, a retail site price level, a location data, and sales data for a group of merchandise.

17. The program product of claim 16, wherein the first store validity period and the second store validity period are the same.

18. The program product of claim 16, wherein the first store validity period and the second store validity period are different.

19. The program product of claim 14, wherein the assortment plan comprises assortment dimensions, the assortment dimensions comprising a level type and a capacity type.