One embodiment is directed generally to a computer system, and in particular to a computer system for optimizing retail pre-packs.
A “pre-pack” is a collection of items used in retail distribution. The pre-pack is a group of multiple units of one or more stock keeping units (“SKU”) that can reduce distribution and handling costs, by reducing the amount of material handled at the origin (e.g., a distribution center), destination (e.g., a retail store), and intermediate points (e.g., a warehouse).
For example, apparel retailers typically construct pre-packs of various sizes of a particular style and color of a t-shirt, rather than directly ship loose quantities of each size to stores. There can be multiple pre-pack “types” or “designs”, each having different quantities of individual products and in different relative proportions, and the collection of the different pre-pack types is referred to as an overall pre-pack “configuration.” An example of one pre-pack type is a pre-pack having 5 extra small t-shirts, 10 small t-shirts, 15 medium t-shirts, 15 large t-shirts, and 10 extra large t-shirts. An example of a second pre-pack type is a pre-pack having 10 extra small t-shirts, 15 small t-shirts, 10 medium t-shirts, 10 large t-shirts, and 5 extra large t-shirts. An example of a pre-pack configuration is 10 of the first pre-pack type and 5 of the second pre-pack type.
The pre-packs are configured when the demand forecast for merchandise items becomes known at the store level. At this point, several similar items are grouped to be jointly delivered to the stores by one or more pre-packs to reduce delivery costs. However, there is a certain tradeoff to pre-packs. Specifically, performing such an aggregation while reducing shipping and handling costs tends to increase the mismatch between the required quantity of each individual merchandise at the destination and what is actually shipped (i.e., either an over- or under-allocation), given that there are typically a maximum number of pre-pack types employed.
For example, suppose there is a demand at a store for fifteen t-shirts of size “small” but the pre-pack type contains ten “small” t-shirts. In this example, either ten or twenty units can be delivered to the store, depending on a configuration of one of these pre-packs or two pre-packs, resulting in either an under- or over-allocation of small t-shirts at the store. As a result, the determination of a pre-pack configuration and pre-pack types should be optimized to minimize the total of delivery and misallocation costs subject to various pre-pack constraints.
One embodiment is a system for determining an optimized pre-pack solution. The system receives demand data and constraints and initializes a current pre-pack configuration comprising a current pre-pack design that comprises a plurality of pre-pack types, each pre-pack type comprising one or more different products. The system optimizes a pre-pack allocation based on the current pre-pack configuration and determines an objective function value improvement comprising, for each product in each pre-pack type, changing a level of the product by one unit and determining if the objective function value has improved. If the objective function value has improved, the system generates a new pre-pack design based on the changed level of the product and assigns the new pre-pack design as the current pre-pack design and re-optimizes the allocation. The system repeats until the objective function value stops improving. The system then outputs an optimized pre-pack configuration and optimized pre-pack allocation.
One embodiment is a computer system that optimizes both the pre-pack types and the pre-pack configuration. The system alternatively optimizes the pre-pack allocation for a given pre-pack configuration to improve the value of an objective function, and based on the allocation, further improves the objective function value by changing the amount of one or two products by one unit in each pre-pack while keeping the allocation constant. An optimized pre-pack configuration is generated when the objective function value can no longer be improved.
In general, a “pre-pack” is a collection of units of various SKUs bundled together, as described above. A pre-pack can be represented as follows: {SKU1: quantity of SKU1, SKU2: quantity of SKU2, SKU3: quantity of SKU3, . . . }. Typically all SKUs from a given pre-pack belong to the same style-color, or to the same style, or to several styles from same class.
A pre-pack “type” is a unique “flavor” of a pre-pack characterized by a certain set of SKUs and a certain set of corresponding unit quantities. A pre-pack “configuration” is a set of unique pre-pack types used as shipment units to allocate a particular style-color (or style, or a group of styles) to all stores.
Pre-pack constraints are certain business constraints on pre-pack types and configurations, such as the total number of units in a pre-pack is within certain min/max or equals certain carton sizes, etc. Constraints can be “hard” or “soft” constraints. Hard constraints are those business rules that must be satisfied (e.g., no more than three pre-pack types must be used in the configuration). Soft constraints are those business rules that must be satisfied to the extent possible. Typically these are equivalent to the objectives and goals of a business (e.g., minimize misallocation to the extent possible).
A feasible pre-pack configuration is a pre-pack configuration that satisfies all pre-pack hard constraints. A pre-pack allocation for a given sku-parent, store, and feasible pre-pack configurations can be represented as follows: {pre-pack type 1: quantity of pre-packs of type 1, . . . , pre-pack type N: quantity of pre-packs of type N}
Embodiments of the present invention perform pre-pack optimization by creating a pre-pack configuration for a given style-color (or style, or a group of styles) that satisfies business constraints (e.g., on the number of unique pre-pack types in pre-pack configuration and on the number of units in a pre-pack configuration) so that the resulting pre-pack configuration can be used to allocate that style-color (or style, or a group of styles) to all stores in such a way that some weighted sum of misallocation (i.e., lost sales, handling costs and markdown losses) is minimized across all stores, while also limiting the number of used unique pre-pack types and the total number of pre-packs allocated, thereby minimizing operational and shipping, and handling costs.
System 10 further includes a memory 14 for storing information and instructions to be executed by processor 22. Memory 14 can be comprised of any combination of random access memory (“RAM”), read only memory (“ROM”), static storage such as a magnetic or optical disk, or any other type of computer readable media. System 10 further includes a communication device 20, such as a network interface card, to provide access to a network. Therefore, a user may interface with system 10 directly, or remotely through a network or any other method.
Computer readable media may be any available media that can be accessed by processor 22 and includes both volatile and nonvolatile media, removable and non-removable media, and communication media. Communication media may include computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
Processor 22 is further coupled via bus 12 to a display 24, such as a Liquid Crystal Display (“LCD”), for displaying information to a user. A keyboard 26 and a cursor control device 28, such as a computer mouse, is further coupled to bus 12 to enable a user to interface with system 10.
In one embodiment, memory 14 stores software modules that provide functionality when executed by processor 22. The modules include an operating system 15 that provides operating system functionality for system 10. The modules further include a pre-pack optimizer module 16 that optimizes pre-pack types and configurations/allocations, as disclosed in more detail below. System 10 can be part of a larger system, such as an overall retail management system or an Enterprise Resource Planning (“ERP”) system. Therefore, system 10 will typically include one or more additional functional modules 18 to include the additional functionality. A database 17 is coupled to bus 12 to provide centralized storage for modules 16 and 18 and store data such as retail pricing and inventory information, other ERP data, etc.
In one embodiment, pre-pack optimizer module 16 receives inputs and generates as outputs an optimized and feasible pre-pack design that includes the design of each of the pre-pack types, and the pre-pack configuration. The inputs can include store-level demands for D stores, for a given set of Q SKUs, specified as a D×Q matrix, and further includes P (variable or fixed number) of pre-packs, pre-pack hard constraints and soft constraints (i.e., objectives and goals). In one embodiment, the input data is in a dense two-dimensional matrix form. In another embodiment, the input data can be in a sparse matrix form that only specifies the non-zero demand values.
The output in one embodiment is a feasible, good-quality pre-pack configuration and pre-pack designs (one solution or a family of solutions for different numbers of pre-pack types used) that satisfies all pre-pack hard constraints (if feasible) and meets soft constraints to the extent possible.
One output of the functionality of
The problem formulation for
SKU set, q=1, . . . , Q
Pack types, p=1, . . . , P; type p contains apq items of sku q
Stores, j=1, . . . , N
Pack-to-store allocations, xjp
Decision variables: apq, xjp,
Objective function: f(apq, xjp)
Minimize: f(apq, xjp)
Subject to constraints
At 202, the demand data, hard constraints and soft constraints are received as inputs. In one embodiment, these inputs can be in the form of a matrix.
At 204, a feasible initial pre-pack configuration, which includes a pre-pack design having a number of different pre-pack types, is determined or received. One embodiment for determining a feasible pre-pack configuration is disclosed below.
At 206, for the current or new pre-pack design, the allocation of pre-packs to each store is optimized. In one embodiment, an allocation algorithm, discussed in detail below, is used to optimize the current allocation based on the new pre-pack design. The result at 206 is a solution to a misallocation minimization problem that can be expressed as:
At 208, an attempt is made to improve an objective function value of the current or initial pre-pack configuration by changing the amount of one or two products by one unit at each pre-pack. This is done using two different methods: (a) for each product q in each pre-pack p, the potential change in the objective function value is determined if the current level apq is changed by ±1; (b) for all product pairs q1, q2 in each pre-pack p, the potential change in the objective function value is determined if apq1 is changed by −1 and apq2 is changed by +1. The highest objective function value-improving change is then determined by determining which resulted in the greatest positive change.
At 210, it is determined if the pre-pack design was improved based on the determinations of 208. If no at 210, the functionality ends and the current design and allocation is the optimized pre-pack solution because the allocation and design can no longer be “improved” in accordance with parameters. If yes at 210, the improved pre-pack design is the new current pre-pack design and the functionality continues at 206.
The functionality of
One embodiment starts with a feasible initial solution (a,x) and attempts to improve current pre-pack design a, while keeping the x-variables constant. Pre-pack a-variables are then fixed, allocation optimization is performed, and the algorithm reiterates.
Embodiments assume the pre-packs are allocated to the stores to satisfy the per-store targets. The amount of per-store-per-SKU misallocation is denoted by yjq− or yjq+ depending on whether it is under- or over-allocation. Consider the effect of increasing a specific pack component apq by one unit, apq→apq+1. In this case, if a store target for a specific SKU is over-allocated, then the over-allocation is increased by xpj; otherwise, if the target is under-allocated, the misallocation is changed depending on the relative sizes of xpj and yjq−: Δjq=max(xpj−yjq−, 0)−min(xpj, yjq−). This also covers the case of over-allocation. If the total change of the objective function associated with apq increase by one unit is denoted as gradpq+, then
Similarly, the total change of the objective function associated with apq decrease by one unit is denoted by gradpq− and
The pseudo-gradient method of
find gradmin=min gradpq−; if gradmin<0, decrease corresponding apq by one unit and re-optimize allocation;
find gradmin=min gradpq+; if gradmin<0, increase corresponding apq by one unit and re-optimize allocation;
The above three steps are iterated as long as at least one of them can be performed successfully. Otherwise, it is determined that the current solution cannot be improved anymore by the pseudo-gradient search method and the method is terminated and the best solution is outputted.
In one embodiment, the following inputs are provided to pre-pack optimizer 16 of
In one embodiment, the following outputs are generated by pre-pack optimizer 16 of
Pack contents 2-D matrix apq, one entry for each sku-pack combination p, q.
Allocations (xpj), one entry for each pack-store combination p, j.
In one embodiment, the following hard constraints are received by pre-pack optimizer 16 of
In one embodiment, the following soft constraints (i.e., business objectives) are received by pre-pack optimizer 16 of
c0*P+c1*U+c2*O+c3*S,
U=Max(0, d−A). Similarly, for a given sku-store combination,
O=Max(0, A−d).
In one embodiment, pre-pack optimizer 16 of
djq=demand for a given sku q at store j.
(m, M)=min and max number of pre-pack pack types allowed.
(Lp, Up)=min and max number of units in pre-pack p.
(lpq, upq)=min and max number of units of sku q in pre-pack p.
Z={Z1, Z2, . . . , ZN} set of feasible carton-sizes.
c0=Dollar cost of introducing an additional pre-pack type.
c1=Dollar cost of one unit of under-allocation of any sku at a store.
c2=Dollar cost of one unit of over-allocation of any sku at a store.
c3=Dollar cost of shipping a pre-pack to a store.
xpj=# of units of pre-pack type p to allocated to store j (integer).
wp=binary (indicator) variable that is positive if pre-pack type p is active (chosen) in the optimal solution.
apq=# of units of sku q in pre-pack type p, and should be within the range (lpq, upq)
For convenient model presentation, an auxiliary decision variables z are used, which are derived from the aggregation of a-variables:
zp=# of units in pre-pack type p.
In one embodiment, the pre-pack planning problem can be expressed as the following nonlinear integer program “PPP”, which includes additional auxiliary variables y+, and y− to represent sku-store level under- and over-allocation amounts respectively.
PPP has a hierarchical nature of decision-making (w→z→a→x→y). A consequence of this daisy-chain of decision variables is that the number of possibilities in the solution space increases exponentially in the length of this chain. Further, the bilinear terms (a, x) in the first set of constraints further complicate the model by injecting increased non-convexity into the model. In general, PPP is difficult to solve to optimality, either directly or even indirectly via integer linear reformulations, including generating-set based approaches (e.g., column generation) for many practical instances. Consequently, embodiments use the pseudo-gradient approach shown in
For a fixed number of pre-pack types (i.e., the number of pre-pack types is known in advance):
P=# of pre-pack types in the configuration,
the w-variables and the constraints involving these variables can be eliminated, and the resultant “working model” PPP(P) is shown below.
In one embodiment, such as 204 of
In one embodiment, a cost for each pre-pack p is determined, such as shown in 208 of
The problem for allocation algorithm ‘A’ can be formulated as:
where Xj is a feasible set of assignment variables associated with store j. It may be determined by such constraints as shipping minimum, presentation maximum, and over-allocation limit. These constraints can be expressed as:
where Sj, Pj, and Oj are shipping minimum, presentation maximum and over-allocation limit, respectively, for store j.
Other, more exotic per-store constraints may be present in the formulation. Since the problem does not have inter-store binding constraints, it can be easily decomposed to be solved on a per-store basis. The per-store allocation problem then becomes:
Since the number of pre-pack types is typically relatively low (at most 10) in some embodiments, the solution to the per-store allocation problem can be obtained by “almost” complete enumeration, which means that in the worst case all feasible solutions will be generated in order to select the optimal solution. However, a number of filters can be applied that significantly reduce the number of the solutions to generate. The solution process starts with x-vector with all zeroes and goes through P iterations. At iteration p, the set of current vectors is doubled by adding vectors with 1 in the p-th position to the vectors in the current set, which by design have 0 in the p-th position. Then the filters are applied and the process reiterates by adding vectors with 1 in the p+1 position. There are three groups of filters that are applied with the objective function and constraints in one embodiment as described below:
then this vector and all descendants are infeasible.
The above procedure assumed that the solution x-vector is binary, which in general may not be practical, as more than one pack of the same type can be allocated to a store. In order to apply the solution approach to the case of general integer variables, each original integer x-variable can be expressed as:
where d1=maxqdqj. As shown, for a given value of integer x-variable there is a single set of binary variables that satisfy the above equation.
Finally, in addition to the optimal solution for the allocation problem the algorithm can potentially return a set of all feasible allocations that can be further used to find overall optimal allocation subject to a limited single resource such as total number of packs or total buy.
As disclosed, embodiments alternatively optimize the pre-pack allocation for a given pre-pack configuration by using the store misallocation as its objective function, and based on the allocation, improves the pre-pack configuration by changing the amount of one or two products by one unit in each pre-pack. An optimized pre-pack configuration is generated when the objective function value can no longer be improved.
One embodiment systematically improves a given feasible pre-pack configuration by decreasing the total cost of product demand mismatching at each individual store in the chain, while also reducing the total shipping and handling costs. Embodiments allow the user to specify constraints such as the total and individual quantities of each product in a pre-pack as well as total product over-allocation, minimum and maximum presentation, and minimum shipping quantities per store. Each iteration of embodiments consists of two phases: In the first phase, or “allocation” phase, an allocation problem is solved for a given fixed pre-pack configuration to determine the optimal number of each pre-pack type allocated to each store to minimize the total cost subject to given constraints. At the second stage, based on the allocation obtained at the first stage, the objective function value associated with the current pre-pack configuration is improved by changing the amount of one or two products by one unit at each pre-pack. After that the algorithm reiterates until no new objective function value-improving solution can be found in the second phase.
Embodiments of the present invention do not require commercial math libraries to efficiently solve a rule-constrained business optimization problem. Further, embodiments provides a user-friendly approach to business decision optimization that is minimally disruptive. Further, embodiments, by balancing supply with the best available forecast of fine-grain demand (i.e., for each product at each store), can very closely balance supply and demand, while also keeping shipping cost to a minimum. Embodiments allow a user to input plausible demand fluctuations and thereby prevent the pre-pack design from being “keyed into” a particular demand snapshot.
Several embodiments are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the disclosed embodiments are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.