Method and system for order fulfillment in a distribution center

Abstract
Order allocation techniques pertaining to stops that a container makes in the process of fulfilling a customer order is disclosed. In one embodiment, this is accomplished by first identifying a pod that stocks the largest number of different items in a customer order. Then, a second pod is identified that stocks the largest number of remaining items in the customer order. The collection of pods defines a container path through the distribution center.
Description
BACKGROUND OF THE INVENTION

This invention pertains to fulfilling customer orders from inventory stocked within a distribution center. More specifically, this invention pertains to fulfilling an order by choosing specific pods for container stops in the distribution center.


Distribution centers are buildings or regions where inventory is stored and used to fulfill orders for customers. Customers place orders by various modes such as by telephone, mail, Internet browsers, and the like. To run a distribution center economically it should be run with a high “throughput.”


A distribution center's throughput is defined as the volume of inventory or number of orders fulfilled in a given unit of time. The enterprise running the distribution center attempts to fulfill as many orders as possible in the shortest amount of time. At least two parameters feature prominently in maximizing throughput: (a) useable inventory and (b) load balancing during order fulfillment. Usable inventory simply refers to the amount of inventory that is immediately available for order fulfillment. Obviously, if a distribution center has insufficient inventory to immediately fulfill all its orders, that distribution center cannot realize its potentially highest throughput. Load balancing refers to consistently using all order fulfillment mechanisms available for fulfilling orders. If any of these mechanisms sit idle, throughput drops off rapidly.


A given distribution center may have many order fulfillment mechanisms. In one example, the distribution center includes a conveyor that transports a container to various locations, each of which has an order fulfillment mechanism. One location may have a bank of carousels, each containing numerous bins of inventory. Each bin holds one or more types of inventory. When a container arrives at a carousel, it rotates its inventory into a position where order items can be placed in the container. Another order fulfillment mechanism in the distribution center may have a few aisles each containing multiple bins. A worker moves through the aisles to pick out requested items and place them in the container. Other types of order fulfillment mechanisms may be employed. A “pod” is a group of inventory locations all serviced from the same stop on the transport system (e.g., a conveyor stop). A pod may contain any or more of the various types of order fulfillment mechanism. Each pod has one or more types of inventory available for “picking.” Picking refers to the operation of retrieving an item of inventory from a pod and placing it into a container. The container holds the various items that fulfill a given order.


Given that different customers have very different needs and preferences, different orders provide wide and rather unpredictable variation. Optimal load balancing to meet this variation presents a serious challenge. During a given week, for example, several grocery orders may require milk, but only a few of these require anchovies, a few others require spicy tofu, and still a few others require cotton swabs. In fulfilling these various orders, any one of these items could present a throughput bottleneck. Controlling the position and path of a container used to fulfill an order can at least partially address this problem.


The present invention fills a need for better ways to fulfill customer orders within a distribution center.


SUMMARY OF THE INVENTION

This invention provides a method and associated warehouse management system pertaining to stops that a container makes in the process of fulfilling a customer order. According to one embodiment, this is accomplished by first identifying a pod that stocks the largest number of different items in a customer order. Then, a second pod is identified that stocks the largest number of remaining items in the customer order. The collection of pods defines a container path through the distribution center.


One aspect of this invention provides a method of filling a customer order in a distribution center having a plurality of pods. Each such pod has multiple inventory locations for storing a plurality of items. The method may be characterized by the following sequence: (a) identifying items and quantities of these items contained in the customer order; (b) identifying a first pod having the most items from the customer order; (c) allocating the order items found in the first pod to the first pod; (d) considering remaining order items not allocated to the first pod, identifying a second pod having the most remaining order items; and (e) allocating the remaining order items found in the second pod to the second pod. The process may continue to identify additional pods as necessary to allocate the remaining items in the order. Allocating the order items typically requires designating specific inventory from specific locations in the first pod as belonging to the customer order. It is, of course, possible that all items from a particular order will be contained in the first pod. When this is the case, there is no need to locate a second pod.


Part of the allocation process may generate picking tasks to move the specific inventory from its specific locations to a container for the order. The customer order is fulfilled by stopping a container at least the first and second pods and picking allocated items at these pods and placing them into the container.


Another aspect of the invention pertains to a distribution center having inventory arranged for filling customer order. The distribution center may be characterized by the following features: (a) at least one ambient having a plurality of pods; and (b) a warehouse management system for identifying a first pod and a second pod and allocating customer order items to the first and second pods. The first pod will be the pod within the distribution center (or an ambient within the distribution center) stocking the most items from the customer order. The second pod will be the pod that stocks the most remaining items from the customer order after other items have been allocated to the first pod. In addition to the pods and the warehouse management system, the distribution center typically will have a transport system such as a conveyor that moves a container from pod to pod in order till orders.


The distribution center may further include an automated material handling system that receives instructions from the warehouse management system for fulfilling the customer orders. Specifically, the automated material handling system controls picking of inventory items from specific inventory locations to fulfill the customer order.


Often the distribution center will have a plurality of ambiences, each with its own collection of pods. In such cases, the customer order may be divided into at least a first group of items stocked in a first ambient and a second group of items stocked in a second ambient. The above method may then be performed on the first group of items in the first ambient and separately performed on the second group of items in the second ambient. The distribution center may have separate transportation systems and containers for each ambient. Examples of ambients include refrigerators, freezers, room temperature ambients, humidors, and wine cellars.


Another aspect of the invention pertains to warehouse management systems that may be used as described above. The warehouse management system may be characterized by the following features: (a) a database of inventory within the distribution center; and (b) logic for identifying a first pod and a second pod and allocating customer order items to the first and second pods. Allocating items to the pods may be performed in accordance with an algorithm as outlined in the above discussion of a method of this invention. The database specifies inventory locations where each of the items are stocked. Upon allocating the customer order items the warehouse management system may update the database of inventory.


The inputs to the warehouse management system could include customer orders that may specify at least a product ID and a quantity for each item of the customer order. The outputs to the warehouse management system include picking tasks specifying at least an inventory location and a quantity to pick for the items from the customer orders. The picking task may also specify a specific container into which items from the customer order are to be placed.


These and other features and advantages of the present invention will be described in more detail below with reference to the associated figures.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of a distribution center in which inventory is placed based upon how rapidly it is consumed.



FIG. 2 is a flow chart depicting a high level start-to-finish order fulfillment method that may be used in a distribution center implementing the present invention.



FIG. 3A is a process flow chart depicting a general procedure for allocating customer orders.



FIG. 3B is a process flow diagram depicting a general procedure for allocating specific order items that are subject to expiration.



FIG. 3C is a process flow diagram depicting a general procedure for allocating specific order items that are not subject to expiration.



FIG. 4 is a block diagram of an order fulfillment subsystem that may be employed in accordance with an embodiment of this invention.





DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following discussion presents some terms and concepts pertinent to the operation of a distribution center. The invention is not specifically limited to the examples described hereafter.


Totes are storage containers used to hold products for transportation to the consumer. There may be several different sizes of totes. Additionally, some totes may be designed for holding frozen and refrigerated goods. In some embodiments, the totes are relatively sturdy and have closable lids.


Each tote may have an identifier to support automated movement through the distribution center by conveyor. For example, each tote can have a bar code identifier that can be scanned as it moves past various points in the system. In this manner, a tote can be moved from a tote induction area to a specific pod or other location with the system tracking the location of the tote.


As indicated, the distribution center has a transport system such as a conveyor that moves totes and trays to pods and other locations within distribution center. “Trays” are used to transport new inventory from a receiving station in the distribution center to individual pods within the distribution center. Identifiers on the trays allow them to be automatically routed to specific destinations within the distribution center. In a specific embodiment, conveyors from Buschmann Company, Cincinnati, Ohio, are used. In another specific embodiment, software from SeayCo Integrators, Conyers, Ga. automates conveyor movement.


Generally, a pod is a collection of storage areas (inventory locations or bins) within a distribution center. As mentioned, a single distribution center may have several types of pods. Each of the different pods and pod types may be adapted for different temperatures, e.g., frozen goods mechanized pod. The different pods and pod types may also be adapted for the rate of product movement, e.g., mechanized pods for fast moving items.


Carousel pods include one or more carousels adjacent to one or more conveyors. In one embodiment, each pod has three carousels adjacent to two conveyors for incoming trays and totes. In some embodiments, two additional conveyors are provided: an express conveyor and an empty conveyor. The express conveyor is used to transport totes directly from the carousel pod to the outbound distribution point for totes. The empty conveyor is used to transport empty trays back to the receiving area to receive new incoming products.


Generally, a carousel is a rotating high capacity storage area. Due to the rotating design of the carousels, only items stored in a small section of the carousel can be easily accessed at a given time. This trade-off allows the carousels to store large numbers of items at the expense of rapid access. One suitable carousel for use with this invention is available from Diamond Phoenix, Lewiston, Me.


Mechanized pods, or mechanical pods, are areas designed to hold the faster moving, and also bulkier and heavier, products for easy access. Each mechanized pod may have inbound and outbound conveyors. Received products may be placed directly into the mechanical pod for storing. Because the mechanical pod items may also be bulkier and heavier than other products, totes that include mechanical pod items may be sent to the mechanical pod prior to the other pods.


Manual pods are areas where “fill to order” items such as produce, bulk foods, pharmacy prescriptions, and/or prepared meals may be prepared and/or stored. The products in the manual pods are typically placed in totes last. Products in manual pods are customer specific preparations. Items are brought from fill to order preparation areas to the manual pods for placement (pick tasks) into totes.


A “pick task” is the retrieval of a product, or multiple quantities of the same product, to fill an order. Thus, an order for ten different products would be comprised of ten pick tasks. However, if the order included five bags of Brand X potato chips, that might be consolidated into a single pick task—depending on the number of bags of potato chips in the pod. For example, if pod two had only two bags of potato chips left and pod three had the last three bags of potato chips, two pick tasks would be required.


Carousel pick tasks may require the coordination of the conveyors to transport the tote to the appropriate pod with the carousels to bring the appropriate storage tray to an accessible position. The pick task may be scheduled, or generated, prior to the actual physical movement of the product, or products, from a carousel location to a tote. Once the pick task is accomplished, the conveyor may move the tote to the next destination automatically. In some embodiments, a push button signal is employed to allow the pick operator to signal that she/he has placed the product, or products, into the tote. Mechanized pick tasks can be accomplished by using carts to move totes received on the inbound conveyor to the products. The products can then be put into the totes for delivery. Once the necessary items are in the totes, the tote is placed on the outbound conveyors. The process for manual pick tasks may be similar to the mechanized pick task. The tote that arrives on the inbound conveyor is scanned. A list of locations with items for the tote is displayed. An operator retrieves the indicated items from the listed locations and then transfers the tote on the outbound conveyor.


A put-away task is the storage of a product in a pod. The product must be stored in a temperature appropriate pod. For example, dairy products must be stored at certain temperatures to avoid spoilage. In addition, depending on the type of product, one of the different types of pods will be selected.


The carousels are used to store items in trays. Once the products have been placed in trays, they can either be sent by conveyor for direct put away in the carousels or held on flow racks for later put away. The scheduling of the put away can be based on product shipments, available inventory, load, and other options.


Once the tray is received by conveyor at the carousel pod, audible and/or visual annunciators may indicate the storage location for the tray. The carousel movements are coordinated with the conveyors so that the appropriate storage area of the carousel is available when the tray is to be stored. Weight planning can be used so that heavier trays are stored at or below waist level while lighter trays are stored at or above waist level in the carousel.



FIG. 1 presents a highly simplified depiction of a distribution center 101. In this figure, a tote 103 is introduced into a tote path in the distribution center and moves about on a conveyor 105. It may stop at various pods as it moves throughout distribution center 101. At each pod, a human being, a robot, or a specialized mechanical device picks items from the pod and places them into the tote 103. At the end of the process, tote 103 is filled with items that are used to fill an order. A given order may require one or more totes filled with ordered items. If more than one tote is required because, for example, the customer order does not physically fit into a container, the order is preferably separated in a manner that keeps all items from one pod stop in the same container if possible. This will minimize the total number of stops made by all containers for the order/ambience.


In the example depicted in FIG. 1, there are two types of pods: a mechanical pod 107 and carousels 109, 111, and 113. Various items, each representing a distinct inventory type, are provided in bins or other portions of the pods. Thus, each pod may contain numerous inventory types. Often these inventory types are referred to as SKUs (Stock Keeping Units). In a carousel, items are provided in particular bins, which are rotated into position next to conveyor 105 to facilitate picking. In the example depicted in FIG. 1, carousel 109 has rotated into a temporary position with the items of SKU 02 available for picking. Likewise, carousel 111 has items from SKU 05 available for picking and carousel 113 has items from SKU 01 available for picking. Typically, when tote 103 stops at a conveyor position, it remains at that location until all items available at the proximate pod are picked and put into the tote (assuming that those items are necessary to fill an order associated with tote 103).


As mentioned, each different item of inventory is associated with a respective SKU. For reference, a “product” is a grouping of SKUs. Product information is higher level information that is pertinent to all SKUs in the grouping. It often defines a brand. A “category” is an even higher level classification based on how customers would expect products to be logically grouped. For example, the category “potato chips” may include the products “Brand X” potato chips and “Brand Y” potato chips. Further, the Brand X potato chip products may include a 16-ounce Brand X potato chips item (associated with a first SKU) and a 20-ounce Brand X potato chips item (associated with a second SKU).


While FIG. 1 shows a distribution center having only one area that contains all the pods, a typical distribution center may have multiple zones or ambiences which dictate special storage or handling. For example, a distribution center may have three main temperature zones for products: ambient, refrigerated, and frozen. And within these three zones, there may be specific ambiences for specialty items, e.g., for flowers, cigars, wines, and chocolates. Wines and cigars can be stocked ambiences having specific temperature and humidity controls. Other items may be deemed fragile and therefore stocked or handled separately from other items. Further, a distribution center may have kitchens, bakeries, deli departments, pharmacies, and other facilities to provide certain products.


In one sense, each ambience may be viewed as a separate distribution center within a larger distribution center that has multiple ambiences. To the extent that this discussion refers to a “distribution center” that discussion applies equally to an ambience within a larger distribution center. Thus, each zone or ambience may have its own collection of pods, conveyance mechanisms, computer systems, etc.


From the above discussion, it should be apparent that the stocked inventory has certain relevant attributes. These may be represented in database records or specialized data structures, for example. A warehouse management system or other logic may use such attributes to facilitate control and analysis of the distribution center. Obviously, each SKU will have its own product ID. Another important attribute of inventory units is the “pod” in which an inventory item is located. Another important attribute of specific inventory locations is the expiration date of items that expire (e.g., milk, yogurt, bacon, etc.). The expiration of a given item may be defined very specifically in terms of a particular day or time within a day. As indicated in the discussion of FIG. 1B, it may sometimes be more appropriate to define an expiration interval over a period of multiple days. For items that do not expire (e.g., canned goods, pretzels, etc.), it is less critical to ensure that these items are distributed before a particular expiration date. However, it is still important to make sure that the oldest items are cleared out of the distribution center. Therefore, another attribute of non-expiry items is the date that they were received within the distribution center.


Another important attribute of items within a distribution center is the number of units of such item at any given inventory location within the distribution center. Some items may be stored at more than one inventory location in the distribution center, possibly over multiple pods. These various inventory locations may contain different numbers of units of the same inventory item.


To run a distribution center economically, throughput should be maximized. Generally, maximizing throughput means maximizing the number of picks per unit time. This can be accomplished by tuning at least three parameters: (1) the distribution of loading over the multiple pods of a distribution center, (2) the number of container stops during the course of filling an order, and (3) the location of frequently purchased items.


A well-balanced loading implies that the picks in a distribution center are relatively evenly balanced over its multiple pods. This means that at any given time, all or most of the pods can be engaged in filling orders. As a result, each of the pods can be productively used over most of the course of a day. As described in U.S. patent application Ser. No. 09/568,570, previously incorporated by reference, this state can be approached by intelligently replicating inventory items over multiple pods.


Generally, each additional container stop further lengthens the amount of time required to fill an order. Thus, an order allocation system should allocate order items in a manner that results in the fewest number of pod stops. A general approach to accomplishing this is described below with reference to FIG. 3A.


Items can be stored at various heights in an aisle, a carousel, or other collection of storage locations in a pod. Typically, a human being picks the items from these storage locations. Certain rules can be formulated to protect workers and increase their efficiency. For example, very heavy items should not be stored at higher storage locations. Fast moving items should be stored in a so-called “golden zone.” Items in this zone are stored at about chest height to allow rapid picking.


To put the present invention in a larger context, one suitable order fulfillment process flow will now be depicted with reference to FIG. 2. Understand that various order fulfillment process flows may benefit from the technology of this invention. In FIG. 2, an order fulfillment flow 201 is depicted. Typically, this flow will be controlled and implemented by one or more computer systems associated with a distribution center. The process begins at 203 with an order arriving for fulfillment. Such order may arrive via mail, telephone, the Internet, etc. In a preferred embodiment, the order is provided as a computer readable file in a standard format.


Next, at 205, order allocation takes place. This typically involves matching an order with particular inventory stored in a distribution center and determining where that inventory is located. It may also involve marking inventory within the distribution center as “outbound” under the assumption that such inventory will be picked to fill the order. Still further, the allocation process may determine the number of totes needed to fulfill the order and design the path for each tote to follow while the order is being filled. This path will specify various pods at which the tote stops to have particular items picked to fill the order. Certain aspects of the allocation process will be elaborated on below in the discussion of FIGS. 3A-3C.


After allocation, one or more tote is inducted (207) into the system and begins passing through the distribution center according to its pre-specified path. As it travels through the distribution center, it stops at various pods where a computer system presents instructions for pickers to pick selected items for the order. In a preferred embodiment, pickers place specified order items into the tote, and verify the order item fulfillment by scanning each item placed into the tote, as well as the tote's license plate ID, with a handheld computing device (e.g., RF gun). Alternatively, or for certain pod types such as carousels, the worker pushes a button to verify order fulfillment. After the picker has confirmed placement of the specified items into the designated tote, the tote is then reintroduced to the automated tote transport system, where it continues to travel along its designated tote path. Information about the picked items is fed back to a central computer system which tracks order fulfillment and inventory. The tote is routed through various pod locations until the order is completely filled. See 209. The tote path may be dynamically and automatically altered if problems are detected in any portion of the DC operations.


After all items have been picked and confirmed for a particular tote, the tote is routed to a shipping spur at 211. At this point, the tote contains all inventory items that are required to fulfill its portion of the order. A shipping component of the distribution center can now take over processing the order. At 213, workers or mechanical systems place the tote onto a dolly, which may include other totes intended for a specific delivery route. At 215, workers or mechanical systems load the dollies and totes onto trucks destined for specified locations. The trucks deliver orders to the customers who have placed orders. At this point, the order fulfillment process is completed. The distribution computer system may be notified of a shipment confirmation.


After the order has been fulfilled and processed for shipment, the OFS provides post fulfillment status data relating to the customer order. The post fulfillment status data may include, for example, the number of totes and the physical license plate ID of each tote associated with the customer order, the ID of each shipping dolly used to transport the totes to and from the delivery trucks, and/or the vehicle ID associated with the shipped order. The post fulfillment status data may be relayed to a front office that interfaces with customers.


Turning now to FIGS. 3A through 3C, one suitable process for allocating an order in accordance with this invention is depicted. As shown in FIG. 3A, the high level process is depicted by reference number 205, which corresponds to the “allocate order” operation illustrated in FIG. 2.


The order allocation process 205 begins at 303 with the order fulfillment subsystem receiving an order having enumerated items and quantities. Such order may arise in a variety of formats such as a flat file, or a specially formatted data structure. The enumerated items may represent individual SKUs and may be identified by product IDs. The order may also include customer information.


After receipt of the customer order, the order fulfillment subsystem next identifies the inventory within the distribution center that is available for allocation to this particular customer order. See 305. In a preferred embodiment, the distribution center is stocked with inventory that is sometimes replicated. In other words, the inventory is stocked at more than one inventory location within the distribution center. As described in U.S. patent application Ser. No. 09/568,570, replicating inventory in this manner can improve the throughput of the distribution center. In any event, the order fulfillment subsystem preferably identifies all available inventory that can be used to fulfill the order in question.


After such inventory has been identified, the order fulfillment subsystem searches for the particular pod within the distribution center that can handle the most items from the customer order. See 307. Because one of the goals of this invention is to ensure high throughput, the order fulfillment subsystem attempts to design a tote path that requires the fewest number of stops. By identifying a pod that can supply many of the order items, the system begins the process of reducing the number of tote stops.


After the search depicted at 307 concludes, the order fulfillment subsystem determines whether any pods are found that can handle at least one item from the customer order. See 309. Typically this will be the case, at least during the first pass through process 205. It may occur in later passes (note that process 205 includes a loop containing operations 307, 309, and 311) that no pods are found having an inventory location with enough units to fulfill an order line.


In any event, assuming that a pod is found at 309 as a result of the search conducted at 307, the order fulfillment subsystem allocates all the order items to the pod located in the search, so long as those items are actually stocked with the pod. See 311. As described in more detail below with reference to FIG. 3B, this allocation process designates specific inventory from specific locations and generates picking tasks for picking the inventory from such locations.


Now, after the specific items stocked within the pod of interest have been allocated, they no longer need to be considered. The process of allocating the remaining order items is handled by looping back to 307 where the order fulfillment subsystem searches for the pod that can handle the most as yet unallocated order items. In a desired scenario, a second pod within the distribution center will stock a number of the remaining unallocated order items. Assuming this is the case, the system will determine that the appropriate pod was found at 309, on the second pass through the system.


The process continues in this manner, looping through operations 307, 309, and 311, until, hopefully, no further order items remain in the customer order at issue. At that point, no pods will be found at 309 (because there are no additional order lines to process). When this is the case, the order allocation process is effectively completed.


Note, however, that in some cases order items may remain, for which no pods can be found to fully satisfy the order. This may occur when, for example, no single inventory location within the distribution center contains a sufficient quantity of the inventory required to satisfy a particular order line. It may be that a sufficient quantity of such item is available within the distribution center collectively over two or more inventory locations in different pods. To address the situation, the order allocation process 205 identifies any pods that can collectively provide the remaining order items. See 313 on the negative path from decision 309. Units of inventory from these pods then can be allocated to fulfill the customer order.


One example of a specific process for allocating order items to a pod is depicted in FIG. 3B. This general process corresponds to operation 311 depicted in FIG. 3A. The goal here is to reserve specific items of inventory from specific inventory locations within a selected pod.


As shown in FIG. 3B, process 311 begins at 319 with the order fulfillment subsystem receiving order items to be allocated to specific inventory locations in the current pod. Next, the order fulfillment subsystem determines whether the current order item is an expiry control item at 321. As indicated, expiry control items are those which have a defined expiration point, typically defined by an expiration date. Examples include milk and most dairy products, produce, meats, etc.


Assuming that the current order item is an expiry control item, the OFS next identifies an available inventory location within the pod that stocks the earliest expiring inventory units. Thus, for example, a pod having two inventory locations stocking Mother Earth brand non-fat milk in one gallon containers would be analyzed by the OFS to determined which of these locations contains the sooner expiring milk. Intuitively, one would expect that the system would always select the earliest expiring inventory to fulfill a current order. In the process of this invention, as depicted in FIG. 3B, however, additional considerations apply.


For example, it is possible that two or more locations within the pod meet this soonest expiring criterion. The order fulfillment subsystem determines whether this is the case at 325. If so, the order fulfillment subsystem chooses the location having the fewest units. See 327. This is done to quickly clear out stock locations that have only a few units of inventory. As such, this algorithm helps make the most of the distribution center's carrying costs. Note, however, that choosing an inventory location having the fewest units can be counter intuitive. Very often, customer orders require multiple units of a particular item (e.g., two six-packs of Coke). By enforcing this algorithm, some times a single location will not supply the entire quantity required by a customer order line.


In any event, after choosing the inventory location at 327, the order fulfillment subsystem next allocates the required order units out of the selected location. See 329. Then the subsystem determines whether the quantity required by the order is satisfied in the chosen location. See 331. If so, process control moves to 333 (described below). If not, the process loops back to 323 where the OFS identifies available inventory locations stocking the “next soonest” expiring inventory units. The process then proceeds to decision 325 as described above (only this time, later expiring inventory units are considered). If two locations contain units meeting the same soonest expiring criteria (e.g., units in both locations expire on the same day), but the chosen location does not have enough units to satisfy the order, then the location having the “next soonest expiring inventor units” identified at 323 is a location having the same expiration window as the previous location. Note that when the OFS determines that only a single location meets the soonest expiring criterion (decision 325 is answered in the negative), process control proceeds directly to allocation operation 329.


After determining that the quantity required by the order is satisfied at 331, the OFS next determines whether any more items remain to be allocated from the current pod. See decision 333. If so, the next order item is considered at 335 and the process loops back to decision 321 where the OFS determines whether this next order item is an expiry control item. When there are no more items to be allocated within the pod under consideration, the process finishes.


Note that when the current order item is not an expiry control item (e.g., decision 321 is answered in the negative), process control moves to 337 where the OFS selects one or more locations for the non-expiry order item. This process is depicted in further detail in FIG. 3C. As shown there, process 337 begins at 343 with the OFS creating an ordered list of inventory locations for the order item under consideration. The ordered list is sorted based on input dates. Thus, for example, a carton of soup arriving at the distribution center in January of a particular year would be sorted above an identical carton of soup arriving at the distribution center in March of the same year.


After creating such ordered list, the OFS next considers the location of the oldest units in the list. See 345. It then determines whether this location has enough units to satisfy the customer order line. See decision 347. If so, it simply allocates the units from the selected location at 349 and the process is then complete for that order item. However, if the location of interest does not have enough units, the OFS may consider the next oldest units in the ordered list. In the algorithm depicted in FIG. 3C, the OFS will do this for a fixed number (M) of times. As illustrated, when decision 347 is answered in the negative, the OFS determines whether it has checked more than M different locations. See decision 351. So long as the OFS has not checked more than M locations in its effort to identify a location having enough units to fulfill the order line, the process loops back to 345. There, the OFS considers the location for the oldest units that were not previously considered.


In order to efficiently allocate orders, the system will not check more than M separate locations. In a specific embodiment, M is configurable, with a default value of 3. After M such checks, decision 351 is answered in the affirmative. At that point, the OFS identifies any pods that can collectively provide the remaining order items. See 353. This operation is analogous to operation 313 described in the context of FIG. 3A. After such pods have been identified, the process is complete.


As indicated, the distribution center, which may include a system of conveyers, carousels, scanners, and hand-held computing units for automating both the order fulfillment (outbound) and inventory restocking (inbound) processes, can be managed by the Order Fulfillment Subsystem. As shown in FIG. 4, an Order Fulfillment Subsystem 401 manages all functionality of the distribution center including a conveyor and associated scanners 415 and pods such as carousels 419. In general, OFS 401 includes appropriate hardware and/or software for managing the distribution facility. Such management hardware and/or software includes, for example, a warehouse management system (e.g. software application) 403 and an automated material handling (AMH) controller component 411, which manages the conveyor, carousel, and scanner components via a conveyor server 413 and a carousel server 417.


In a specific implementation, warehouse management system 403 may be configured with a set of business rules that set forth some or all functions of the present invention. In a very specific example, system 403 is a specially modified and adapted variation of the MOVE warehouse management system provided by Optum, Inc. of Costa Mesa, Calif.


Warehouse management system 403 has at least one database 407 associated therewith and at least a graphical user interface 405. Interface 405 allows certain warehouse personnel to access system 403 and query database 407, for example. It also allows such personnel to monitor distribution center operations and/or manually allocate orders.


Database 407 includes records for all inventory items stocked in the distribution center. In a specific embodiment, the database records may include at least a product ID, an inventory location, a quantity and a state. The state may specify the number of units of the product that are outbound (allocated), inbound (received at the distribution center but not yet putaway to its inventory location) or on hand. On hand items are all items currently physically located in the distribution center, outbound items are on hand items that have been allocated to an order but not yet picked. When an outbound item is picked, the on hand and outbound values for that item are decremented. In a preferred embodiment, database 407 provides inventory information that allows customers to place orders. To determine whether sufficient inventory is present to fill an order line, the system may consider the value of on hand units minus outbound units.


Warehouse management system 403 also communicates with handheld computing devices 409 via a wireless interface such as, for example, a radio frequency (RF) interface. The handheld computing devices 409 are used by the distribution center employees to perform and/or confirm inventory movement operations.


The warehouse system also provides an interface to other distribution system hardware/software, which allows it to receive customer orders for fulfilling. The order data, which is transferred to the OFS subsystem, may include both SKU data (as product IDs), quantities, customer information, and transportation/delivery data (e.g. delivery vehicle routes, stops, etc.). In a specific embodiment, the software interface is implemented using a business host interface (BHI). The interface may also allow other software/hardware components of the distribution center to communicate with the OFS database 407.


The warehouse management system 403 communicates instructions (e.g. task lists) to the automated material handling controller (AMH) 411. Importantly, system 403 outputs picking tasks which specify, for example, an inventory location, a quantity to pick, a container (tote), and an order line for a customer order. The AMH controller 411 processes the instructions and manages the conveyor server 413 and carousel server 417. The carousel server 417 and the conveyor server 413 may each include a respective database. The carousel server 417 issues control signals to the carousel client 419, which drives the carousel hardware and controls the carousel movement. Similarly, the conveyor server 413 processes instructions from the AMH, and issues control signals to the conveyor client 415, which drives and controls the conveyor scanner hardware used for routing inventory and for managing traffic. Additionally, the conveyor client 413 and the carousel client may be configured with an interface for monitoring the status of the conveyor and carousel hardware.


This invention is preferably implemented as software stored or transmitted on a machine-readable medium and executed on a processor. The invention may also be implemented on firmware provided with a processor for executing instructions specified by the firmware. In an alternative embodiment, the invention is implemented on specially designed or configured processing hardware.


Because program instructions and data may be employed to implement the systems/methods described herein, the present invention relates to machine-readable media that include program instructions, velocity data, etc. for performing various operations described herein (e.g., grouping inventory items based on their location on a velocity curve and logically distributing those items in put away regions of a distribution center). Examples of machine-readable media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media; and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM) and random access memory (RAM). The invention may also be embodied in a carrier wave travelling over an appropriate medium such as airwaves, optical lines, electric lines, etc. Examples of program instructions include both machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.


Although certain preferred embodiments of this invention have been described in detail herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to these precise embodiments, and at various changes and modifications may be effected therein by one skilled in the art without departing from the scope of spirit of the invention as defined in the appended claims.

Claims
  • 1. A management system for a distribution center with a plurality of sites, each site having a collection of storage areas to store a plurality of items, the system comprising: a storage device; andat least one processor coupled to the storage device, the at least one processor configured to: analyze at least a first customer order and a second customer order, each of the first and second customer orders indicating a plurality of items;identify a first site of the plurality of sites, and a second site of the plurality of sites;determine a first route through the distribution center to fulfill the first customer order based on the identifying, with the first route going to the first site before going to any of the other sites of the plurality of sites; anddetermine a second route through the distribution center to fulfill the second customer order based on the identifying, with the second route going to the second site before going to any of the other sites of the plurality of sites.
  • 2. A management system as recited in claim 1, wherein at least one site includes a carousel with a collection of storage areas to store a plurality of items, andwherein at least one other site includes mechanical storage mechanisms to store bulkier and heavier items than items stored in the storage areas of the carousel.
  • 3. A management system as recited in claim 1, wherein the at least one processor is further configured to provide an indication as to the location in the first site of an item identified in the first site, so as to help retrieve the identified item from the first site for fulfilling the first customer order.
  • 4. A management system as recited in claim 3, wherein the indication is provided audibly to help manually retrieve the identified item.
  • 5. A management system as recited in claim 3, wherein the indication is provided visually to help manually retrieve the identified item.
  • 6. A management system as recited in claim 1, wherein the first route is configured for a container to follow, with the first route including a stop at the first site to have an identified item at the first site picked and placed into the container to fulfill the first customer order.
  • 7. A management system as recited in claim 6, wherein the at least one processor is further configured to alter the first route dynamically in view of a problem detected in the distribution center while the container is on the first route.
  • 8. A management system as recited in claim 1, wherein the highest number of items in the first customer order is available from the first site, and the highest number of items in the second customer order is available from the second site.
  • 9. A management system as recited in claim 8, wherein the at least one processor is further configured to: determine the items remaining in the first and second customer orders after removing those corresponding items identified as being available from the first site and the second site; andthereafter identify a third site of the plurality of sites with the highest number of the items remaining in the first customer order available from the third site, and a fourth site of the plurality of sites with the highest number of items remaining in the second customer order available from the fourth site, andwherein based on the thereafter identifying, the first route is determined to go to the third site after going to first site to fulfill the first customer order, and the second route is determined to go to the fourth site after going to the second site to fulfill the second customer order.
  • 10. A management system as recited in claim 9, wherein the at least one processor is further configured to identify any one or more sites of the plurality of sites that collectively provide the items remaining in the first customer order after removing all the items previously identified as being available from the first site and the third site.
  • 11. A computer-implemented method to manage a distribution center with a plurality of sites, each site having a collection of storage areas to store a plurality of items, the distribution center having at least a database of inventory associated therewith, the method comprising executing instructions on at least a processor to: analyze by the at least one processor at least a first customer order and a second customer order, each of the first and second customer orders indicating a plurality of items, the at least one processor being coupled to the database of inventory regarding a plurality of items within the distribution center;identify by the at least one processor, a first site of the plurality of sites, and a second site of the plurality of sites;determine by the at least one processor, a first route through the distribution center to fulfill the first customer order based on the identifying, with the first route going to the first site before going to any of the other sites of the plurality of sites; anddetermine by the at least one processor, a second route through the distribution center to fulfill the second customer order based on the identifying, with the second route going to the second site before going to any of the other sites of the plurality of sites.
  • 12. A computer-implemented method as recited in claim 11, wherein the method further comprises providing an indication as to the location in the first site of an item identified in the first site, so as to help retrieve the identified item from the first site for fulfilling the first customer order.
  • 13. A computer-implemented method as recited in claim 11, wherein the first route is configured for a container to follow, with the first route including a stop at the first site to have an identified item at the first site picked and placed into the container to fulfill the first customer order, andwherein the database is configured to at least store inventory locations where a plurality of items are stocked in the distribution center.
  • 14. A computer-implemented method as recited in claim 13, wherein the method further comprises altering the first route dynamically in view of a problem detected in the distribution center while the container is on the first route.
  • 15. A computer-implemented method as recited in claim 11, wherein the highest number of items in the first customer order is available from the first site, and the highest number of items in the second customer order is available from the second site.
  • 16. A computer-implemented method as recited in claim 15 further comprising: determining the items remaining in the first and second customer orders after removing those corresponding items identified as being available from the first site and the second site; andthereafter identifying a third site of the plurality of sites with the highest number of the items remaining in the first customer order available from the third site, and a fourth site of the plurality of sites with the highest number of items remaining in the second customer order available from the fourth site,wherein based on the thereafter identifying, the first route is determined to go to the third site after going to the first site to fulfill the first customer order, and the second route is determined to go to the fourth site after going to the second site to fulfill the second customer order.
  • 17. A computer-implemented method as recited in claim 16, wherein the method further comprises identifying any one or more sites of the plurality of sites that collectively provide the items remaining in the first customer order after removing all the items previously identified as being available from the first site and the third site.
  • 18. A non-transitory computer readable medium including at least executable computer program code stored therein for managing a distribution center with a plurality of sites, each site having a collection of storage areas to store a plurality of items, said computer readable medium comprising: computer program code for analyzing at least a first customer order and a second customer order, each of the first and second customer orders indicating a plurality of items;computer program code for identifying a first site of the plurality of sites, and a second site of the plurality of sites;computer program code for determining a first route through the distribution center to fulfill the first customer order based on the identifying, with the first route going to the first site before going to any of the other sites of the plurality of sites; andcomputer program code for determining a second route through the distribution center to fulfill the second customer order based on the identifying, with the second route going to the second site before going to any of the other sites of the plurality of sites.
  • 19. A computer readable medium as recited in claim 18, wherein the first route is configured for a container to follow, with the first route including a stop at the first site to have an identified item at the first site picked and placed into the container to fulfill the first customer order.
  • 20. A computer readable medium as recited in claim 19 further comprising computer program code for altering the first route dynamically in view of a problem detected in the distribution center while the container is on the first route.
  • 21. A non-transitory computer readable medium as recited in claim 18, wherein the highest number of items in the first customer order is available from the first site, and the highest number of items in the second customer order is available from the second site.
  • 22. A computer readable medium as recited in claim 21 further comprising: computer program code for determining the items remaining in the first and second customer orders after removing those corresponding items identified as being available from the first site and the second site; andcomputer program code for thereafter identifying a third site of the plurality of sites with the highest number of the items remaining in the first customer order available from the third site, and a fourth site of the plurality of sites with the highest number of items remaining in the second customer order available from the fourth site,wherein based on the thereafter identifying, the first route is determined to go to the third site after going to first site to fulfill the first customer order, and the second route is determined to go to the fourth site after going to the second site to fulfill the second customer order.
  • 23. A computer readable medium as recited in claim 22 further comprising computer program code for identifying any one or more sites of the plurality of sites that collectively provide the items remaining in the first customer order after removing all the items previously identified as being available from the first site and the third site.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/387,801, (now U.S. Pat. No. 8,140,183) filed May 6, 2009, and titled “METHOD AND SYSTEM FOR ORDER FULFILLMENT IN A DISTRIBUTION CENTER,” which is hereby incorporated herein by reference for all purposes, and which application is a continuation of U.S. patent application Ser. No. 11,356,870, (now U.S. Pat. No. 7,532,947) filed Feb. 18, 2006, and titled “METHOD AND SYSTEM FOR ORDER FULFILLMENT IN A DISTRIBUTION CENTER,” which is hereby incorporated herein by reference for all purposes, and which application is a continuation of U.S. patent application Ser. No. 09/568,571 (now U.S. Pat. No. 7,139,637), filed May 10, 2000, and titled “ORDER ALLOCATION TO MINIMIZE CONTAINER STOPS IN A DISTRIBUTION CENTER,” which is hereby incorporated herein by reference for all purposes, and which claims priority under 35 U.S.C. 119(e) from U.S. Provisional Patent Application No. 60/133,646, filed on May 11, 1999, and titled “ELECTRONIC COMMERCE ENABLED DELIVERY SYSTEM AND METHOD,” which is hereby incorporated herein by reference for all purposes. This application is also related to the following patent applications: (1) U.S. patent application Ser. No. 09/568,603 (now U.S. Pat. No. 7,177,825), titled “INTEGRATED SYSTEM FOR ORDERING, FULFILLMENT, AND DELIVERY OF CONSUMER PRODUCTS USING A DATA NETWORK,” (2) U.S. patent application Ser. No. 09/568,570 (now U.S. Pat. No. 7,370,005), titled “INVENTORY REPLICATION BASED UPON ORDER FULFILLMENT RATES,” and (3) U.S. patent application Ser. No. 09/568,569, (now U.S. Pat. No. 6,622,127 B1), titled “ORDER ALLOCATION TO SELECT FROM INVENTORY LOCATIONS STOCKING FEW UNITS OF INVENTORY,” all filed on May 10, 2000. Each of the above-referenced US patent applications is incorporated herein by reference for all purposes.

US Referenced Citations (342)
Number Name Date Kind
2781643 Fairweather Feb 1957 A
3406532 Rownd et al. Oct 1968 A
3670867 Traube Jun 1972 A
3771679 Theml Nov 1973 A
4213310 Buss Jul 1980 A
4455453 Parasekvakos et al. Jun 1984 A
4530067 Dorr Jul 1985 A
4656591 Goldberg Apr 1987 A
4792273 Specht Dec 1988 A
4799156 Shavit et al. Jan 1989 A
4803348 Lohrey et al. Feb 1989 A
4823984 Ficken Apr 1989 A
4887208 Schneider et al. Dec 1989 A
4936738 Brennan Jun 1990 A
4958280 Pauly et al. Sep 1990 A
5027269 Grant et al. Jun 1991 A
5038283 Caveney Aug 1991 A
5093794 Howie et al. Mar 1992 A
5101352 Rembert Mar 1992 A
5105627 Kurita Apr 1992 A
5113349 Nakamura et al. May 1992 A
5122959 Nathanson et al. Jun 1992 A
5235819 Bruce Aug 1993 A
5237158 Kern et al. Aug 1993 A
5246332 Bernard Sep 1993 A
5265006 Asthana Nov 1993 A
5272638 Martin et al. Dec 1993 A
5273392 Bernard Dec 1993 A
5322406 Pippin et al. Jun 1994 A
5334824 Martinez Aug 1994 A
5362948 Morimoto Nov 1994 A
5363310 Haj-Ali-Ahmadi et al. Nov 1994 A
5371852 Attanasio et al. Dec 1994 A
5395206 Cerny, Jr. Mar 1995 A
5402336 Spiegelhoff et al. Mar 1995 A
5428546 Shah et al. Jun 1995 A
5434394 Roach et al. Jul 1995 A
5444844 Inoue et al. Aug 1995 A
5450317 Lu et al. Sep 1995 A
5479530 Nair et al. Dec 1995 A
5533361 Halpern Jul 1996 A
5535407 Yanagawa et al. Jul 1996 A
5548518 Dietrich et al. Aug 1996 A
5553312 Gattey et al. Sep 1996 A
5568393 Ando et al. Oct 1996 A
5592378 Cameron et al. Jan 1997 A
5593269 Bernard Jan 1997 A
5598487 Hacker et al. Jan 1997 A
5615121 Babayev et al. Mar 1997 A
5640002 Ruppert et al. Jun 1997 A
5664110 Green et al. Sep 1997 A
5666493 Wojcik et al. Sep 1997 A
5687322 Deaton et al. Nov 1997 A
5694551 Doyle et al. Dec 1997 A
5708780 Levergood et al. Jan 1998 A
5710887 Chelliah et al. Jan 1998 A
5712989 Johnson et al. Jan 1998 A
5715314 Payne et al. Feb 1998 A
5758313 Shah et al. May 1998 A
5758328 Giovannoli May 1998 A
5758329 Wojcik et al. May 1998 A
5761673 Bookman et al. Jun 1998 A
5768139 Pippin et al. Jun 1998 A
5774660 Brendel et al. Jun 1998 A
5774668 Choquier et al. Jun 1998 A
5774670 Montulli Jun 1998 A
H1743 Graves et al. Aug 1998 H
5809479 Martin et al. Sep 1998 A
5816725 Sherman et al. Oct 1998 A
5826242 Montulli Oct 1998 A
5826825 Gabriet Oct 1998 A
5831860 Foladare et al. Nov 1998 A
5832457 O'Brien et al. Nov 1998 A
5834753 Danielson et al. Nov 1998 A
5835914 Brim Nov 1998 A
5839117 Cameron et al. Nov 1998 A
5848395 Edgar et al. Dec 1998 A
5870473 Boesch et al. Feb 1999 A
5878401 Joseph Mar 1999 A
5880443 McDonald et al. Mar 1999 A
5884216 Shah et al. Mar 1999 A
5893076 Hafner et al. Apr 1999 A
5894554 Lowery et al. Apr 1999 A
5895454 Harrington Apr 1999 A
5897622 Blinn et al. Apr 1999 A
5897629 Shinagawa et al. Apr 1999 A
5899088 Purdum May 1999 A
5910896 Hahn-Carlson Jun 1999 A
5918213 Bernard et al. Jun 1999 A
5922040 Prabhakaran Jul 1999 A
5943652 Sisley et al. Aug 1999 A
5943841 Wunscher Aug 1999 A
5949776 Mahany et al. Sep 1999 A
5950173 Perkowski Sep 1999 A
5956709 Xue Sep 1999 A
5960411 Hartman et al. Sep 1999 A
5961601 Iyengar Oct 1999 A
5963919 Brinkley et al. Oct 1999 A
5974401 Enomoto et al. Oct 1999 A
5979757 Tracy et al. Nov 1999 A
5983200 Slotznick Nov 1999 A
5987377 Westerlage et al. Nov 1999 A
5991739 Cupps et al. Nov 1999 A
5999914 Blinn et al. Dec 1999 A
6003015 Kang et al. Dec 1999 A
6006100 Koenck et al. Dec 1999 A
6016504 Arnold et al. Jan 2000 A
6023683 Johnson et al. Feb 2000 A
6023722 Colyer Feb 2000 A
6026378 Onozaki Feb 2000 A
6058417 Hess et al. May 2000 A
6061607 Bradley et al. May 2000 A
6070147 Harms et al. May 2000 A
6073108 Peterson Jun 2000 A
6076108 Courts et al. Jun 2000 A
6081789 Purcell Jun 2000 A
6083279 Cuomo et al. Jul 2000 A
6084528 Beach et al. Jul 2000 A
6085170 Tsukuda Jul 2000 A
6087952 Prabhakaran Jul 2000 A
6088648 Shah et al. Jul 2000 A
6094485 Weinstein et al. Jul 2000 A
6094642 Stephenson et al. Jul 2000 A
6098093 Bayeh et al. Aug 2000 A
6098152 Mounes-Toussi Aug 2000 A
6101481 Miller Aug 2000 A
6101486 Roberts et al. Aug 2000 A
6123259 Ogasawara Sep 2000 A
6128279 O'Neil et al. Oct 2000 A
6140922 Kakou Oct 2000 A
6144848 Walsh et al. Nov 2000 A
6157945 Balma et al. Dec 2000 A
6167380 Kennedy et al. Dec 2000 A
6167382 Sparks et al. Dec 2000 A
6178510 O'Connor et al. Jan 2001 B1
6182053 Rauber et al. Jan 2001 B1
6185479 Cirrone Feb 2001 B1
6185601 Wolff Feb 2001 B1
6185625 Tso et al. Feb 2001 B1
6215952 Yoshio et al. Apr 2001 B1
6223215 Hunt et al. Apr 2001 B1
6225995 Jacobs et al. May 2001 B1
6233543 Butts et al. May 2001 B1
6236972 Shkedy May 2001 B1
6236974 Kolawa et al. May 2001 B1
6249773 Allard Jun 2001 B1
6249801 Zisapel et al. Jun 2001 B1
6253292 Jhang et al. Jun 2001 B1
6260024 Shkedy Jul 2001 B1
6275812 Haq et al. Aug 2001 B1
6279001 DeBettencourt et al. Aug 2001 B1
6289260 Bradley et al. Sep 2001 B1
6289369 Sundaresan Sep 2001 B1
6289370 Panarello et al. Sep 2001 B1
6292784 Martin et al. Sep 2001 B1
6295553 Gilbertson et al. Sep 2001 B1
6324520 Walker et al. Nov 2001 B1
6332334 Faryabi Dec 2001 B1
6341269 Dulaney et al. Jan 2002 B1
6343275 Wong Jan 2002 B1
6347322 Bogantz et al. Feb 2002 B1
6351775 Yu Feb 2002 B1
6360256 Lim Mar 2002 B1
6369840 Barnett et al. Apr 2002 B1
6374300 Masters Apr 2002 B2
6385642 Chlan et al. May 2002 B1
6397246 Wolfe May 2002 B1
6405173 Honarvar et al. Jun 2002 B1
6421739 Holiday Jul 2002 B1
6424947 Tsuria et al. Jul 2002 B1
6424992 Devarakonda et al. Jul 2002 B2
6438652 Jordan et al. Aug 2002 B1
6445976 Ostro Sep 2002 B1
6453306 Quelene Sep 2002 B1
6463345 Peachey-Kountz et al. Oct 2002 B1
6463420 Guidice et al. Oct 2002 B1
6466949 Yang et al. Oct 2002 B2
6473802 Masters Oct 2002 B2
6480894 Courts et al. Nov 2002 B1
6484150 Blinn et al. Nov 2002 B1
6490567 Gregory Dec 2002 B1
6496205 White et al. Dec 2002 B1
6505093 Thatcher et al. Jan 2003 B1
6505171 Cohen et al. Jan 2003 B1
6526392 Dietrich et al. Feb 2003 B1
6530518 Krichilsky et al. Mar 2003 B1
6535880 Musgrove et al. Mar 2003 B1
6539494 Abramson et al. Mar 2003 B1
6549891 Rauber et al. Apr 2003 B1
6560717 Scott et al. May 2003 B1
6567786 Bibelnieks et al. May 2003 B1
6567848 Kusuda et al. May 2003 B1
6571213 Altendahl et al. May 2003 B1
6578005 Lesaint et al. Jun 2003 B1
6587827 Hennig et al. Jul 2003 B1
6587866 Modi et al. Jul 2003 B1
6594641 Southam Jul 2003 B1
6594692 Reisman Jul 2003 B1
6595342 Maritzen et al. Jul 2003 B1
6598024 Walker et al. Jul 2003 B1
6598027 Breen, Jr. Jul 2003 B1
6601101 Lee et al. Jul 2003 B1
6609159 Dukach et al. Aug 2003 B1
6622127 Klots et al. Sep 2003 B1
6629079 Spiegel et al. Sep 2003 B1
6629135 Ross, Jr. et al. Sep 2003 B1
6654726 Hanzek Nov 2003 B1
6671818 Mikurak Dec 2003 B1
6691165 Bruck et al. Feb 2004 B1
6697849 Carlson Feb 2004 B1
6697964 Dodrill et al. Feb 2004 B1
6701367 Belkin Mar 2004 B1
6711618 Danner et al. Mar 2004 B1
6718387 Gupta et al. Apr 2004 B1
6721713 Guheen et al. Apr 2004 B1
6741995 Chen et al. May 2004 B1
6748318 Jones Jun 2004 B1
6748418 Yoshida et al. Jun 2004 B1
6763496 Hennings et al. Jul 2004 B1
6772333 Brendel et al. Aug 2004 B1
6779016 Aziz et al. Aug 2004 B1
6788425 Ohtsuka et al. Sep 2004 B1
6792459 Elnozahy et al. Sep 2004 B2
6799165 Boesjes Sep 2004 B1
6801949 Bruck et al. Oct 2004 B1
6826613 Wang et al. Nov 2004 B1
6845503 Carlson et al. Jan 2005 B1
6859834 Arora et al. Feb 2005 B1
6862572 de Sylva Mar 2005 B1
6865601 Cherkasova et al. Mar 2005 B1
6873970 Showghi et al. Mar 2005 B2
6879965 Fung et al. Apr 2005 B2
6879995 Chinta et al. Apr 2005 B1
6888836 Cherkasova May 2005 B1
6901382 Richards et al. May 2005 B1
6904455 Yen Jun 2005 B1
6938079 Anderson et al. Aug 2005 B1
6947992 Shachor Sep 2005 B1
6957186 Guheen et al. Oct 2005 B1
6970837 Walker et al. Nov 2005 B1
6975937 Kantarjiev et al. Dec 2005 B1
6980962 Arganbright et al. Dec 2005 B1
6990460 Parkinson Jan 2006 B2
7010501 Roslak et al. Mar 2006 B1
7028187 Rosen Apr 2006 B1
7035914 Payne et al. Apr 2006 B1
7040541 Swartz et al. May 2006 B2
7043455 Cuomo et al. May 2006 B1
7062556 Chen et al. Jun 2006 B1
7085729 Kennedy et al. Aug 2006 B1
7124101 Mikurak Oct 2006 B1
7139637 Waddington et al. Nov 2006 B1
7139721 Borders et al. Nov 2006 B2
7165041 Guheen et al. Jan 2007 B1
7173177 Gould et al. Feb 2007 B1
7177825 Borders et al. Feb 2007 B1
7181539 Knight et al. Feb 2007 B1
7197547 Miller et al. Mar 2007 B1
7222161 Yen et al. May 2007 B2
7233914 Wijaya et al. Jun 2007 B1
7240283 Paila et al. Jul 2007 B1
7251612 Parker et al. Jul 2007 B1
7275042 Kelly et al. Sep 2007 B1
7299294 Bruck et al. Nov 2007 B1
7308423 Woodward et al. Dec 2007 B1
7346564 Kirklin et al. Mar 2008 B1
7366755 Cuomo et al. Apr 2008 B1
7370005 Ham et al. May 2008 B1
7383233 Singh et al. Jun 2008 B1
7437305 Kantarjiev Oct 2008 B1
7493554 Paila et al. Feb 2009 B2
7509407 Miller et al. Mar 2009 B2
7532947 Waddington et al. May 2009 B2
7603302 Drummond et al. Oct 2009 B1
7792712 Kantarjiev Sep 2010 B2
7801772 Woodward et al. Sep 2010 B2
7853870 Paila et al. Dec 2010 B2
7882501 Carlson et al. Feb 2011 B1
7904975 Kruglikov et al. Mar 2011 B2
7930416 Miller et al. Apr 2011 B2
8010411 Woodward et al. Aug 2011 B2
8090626 Wijaya et al. Jan 2012 B1
8140183 Waddington et al. Mar 2012 B2
8326708 Kantarjiev et al. Dec 2012 B2
20010013007 Tsukuda Aug 2001 A1
20010016828 Philippe et al. Aug 2001 A1
20010037229 Jacobs et al. Nov 2001 A1
20010042021 Matsuo et al. Nov 2001 A1
20010042050 Fletcher et al. Nov 2001 A1
20010047310 Russell Nov 2001 A1
20010049619 Powell et al. Dec 2001 A1
20010049672 Moore Dec 2001 A1
20010052024 Devarakonda et al. Dec 2001 A1
20020002513 Chiasson Jan 2002 A1
20020004766 White Jan 2002 A1
20020007299 Florence Jan 2002 A1
20020010633 Brotherston Jan 2002 A1
20020013950 Tomsen Jan 2002 A1
20020038224 Bhadra Mar 2002 A1
20020038261 Kargman et al. Mar 2002 A1
20020049853 Chu et al. Apr 2002 A1
20020050526 Swartz et al. May 2002 A1
20020065700 Powell et al. May 2002 A1
20020072994 Mori et al. Jun 2002 A1
20020103724 Huxter Aug 2002 A1
20020116279 Nobilo Aug 2002 A1
20020188530 Wojcik et al. Dec 2002 A1
20020194084 Surles Dec 2002 A1
20020194087 Spiegel et al. Dec 2002 A1
20030045340 Roberts Mar 2003 A1
20030065565 Wagner et al. Apr 2003 A1
20030079227 Knowles et al. Apr 2003 A1
20030119485 Ogasawara Jun 2003 A1
20030233190 Jones Dec 2003 A1
20040107125 Guheen et al. Jun 2004 A1
20040236635 Publicover Nov 2004 A1
20050027580 Crici et al. Feb 2005 A1
20050144641 Lewis Jun 2005 A1
20050261985 Miller et al. Nov 2005 A1
20060085250 Kantarjiev et al. Apr 2006 A1
20060142895 Waddington et al. Jun 2006 A1
20070016463 Borders et al. Jan 2007 A1
20070055580 Woodward et al. Mar 2007 A1
20070112647 Borders et al. May 2007 A1
20070136149 Woodward et al. Jun 2007 A1
20070162353 Borders et al. Jul 2007 A1
20070174144 Borders et al. Jul 2007 A1
20070250572 Paila et al. Oct 2007 A1
20080015959 Kruglikov et al. Jan 2008 A1
20080154709 Ham et al. Jun 2008 A1
20090063439 Rauser et al. Mar 2009 A1
20090094085 Kantarjiev Apr 2009 A1
20090150534 Miller et al. Jun 2009 A1
20090164570 Paila et al. Jun 2009 A1
20090222129 Waddington et al. Sep 2009 A1
20100241269 Ham et al. Sep 2010 A1
20100332402 Kantarjiev et al. Dec 2010 A1
20110047210 Paila et al. Feb 2011 A1
20110173090 Miller et al. Jul 2011 A1
20110258074 Woodward et al. Oct 2011 A1
20120095879 Wijaya et al. Apr 2012 A1
20120173449 Waddington et al. Jul 2012 A1
Foreign Referenced Citations (5)
Number Date Country
0 425 405 May 1991 EP
2696722 Apr 1994 FR
2 265 032 Sep 1993 GB
WO9907121 Feb 1999 WO
WO 9909508 Feb 1999 WO
Non-Patent Literature Citations (99)
Entry
“Peapod Interactive Grocery Shopping and Delivery Service Now Delivers via the Internet”, Press Release, peapod.com, Apr. 22, 1996, pp. 1-2.
Anupindi et al., “Estimation of Consumer Demand with Stock-Out Based Substitution: An Application to Vending Machine Product”, Marketing Science, vol. 17, No. 4, 1998, pp. 406-423.
Anon, Automatic ID News, “20/20 Results Achieved with Technology Trio”, Sep. 1995, p. 19.
Chandler, Susan. “The grocery cart in your PC,” Business Week, Iss. 3441, 1995, p. 63, 2 pages.
eShopper: Resources for Web Buying. Savetz, Kevin; Gardiner, Peace, Computer Shopper, 19, 5, 280(1), May, 1999.
Fynes, Brian, et al., The Impact of Electronic Data Interchange on Competitiveness in Retail Supply Chain, IBAR vol. 14, No. 2, pp. 16-28, 1993.
Hiroo Kawata, “Information Technology of Commercial Vehicles in the Japanese Parcel Service Business,” Abstract No., XP-000560489, 1992, pp. 371-382.
Hyten, Todd, “Stop & Shop mulls online grocery store”, Boston Business Journal (Boston, MA, US), Mar. 22, 1996, vol. 16, No. 6, p. 1.
Jaffe, Charles A. “Gas supplier takes timing seriously if deliveries are late, the product is free,” The Morning Call, Allentown, PA, Feb. 5, 1989, pp. 1-4.
Koster, Rene de, “Routing Orderpickers in a Warehouse: A Comparison Between Optimal and Heuristic Solutions,” IIE Transactions, May 1998, vol. 30, No. 5, p. 469.
Maloney, David, “The New Corner Drugstore”, Modern Materials Handling, May 1, 2000, vol. 55, No. 5, p. 58.
Norton, Tim R., “End-To-End Response-Time: Where to Measure?”, Computer Measurement Group Conference Proceedings, CMG99 Session 423, Dec. 1999, pp. 1-9.
“Numetrix Unveils xtr@; an Internet-Designed Solution for Real-Time Supply Chain Collaboration,” Business/Technology Editors, Business Wire, New York: Dec. 16, 1998, pp. 1-4.
Parker, Rachel, “UPS Pioneers a cellular data network”, InfoWorld, ABI/INFORM Global, Jun. 8, 1992, p. S59-S60.
Anon, PC Foods, “Customer Service Agreement,” printed from website: http://www.pcfoods.com, Abstract No., XP-002245026, 1999, pp. 1-2.
Pearce, Michael R. “From carts to clicks”, Ivey Business Quarterly, Autumn 1998, vol. 63, No. 1, p. 69-71.
Sekita, Takashi, “The Physical Distribution Information Network in the Home-Delivery Business,” Japan Computer Quarterly, Abstract No., XP-00.431194, 1990, pp. 23-32.
Smith et al., “Management of Multi-Item Retail Inventory Systems with Demand Substitution”, Operations Research, vol. 48, No. 1, Jan.-Feb. 2000, pp. 50-64.
Fielding et al., “Hypertext Transfer Protocol—HTTP/1.1, RFC 2616”, Network Working Group, Jun. 1999, pp. 1-90.
Saccomano, Ann, “Blue Laws' Still Apply,” Traffic World, LOGISTICS Section, p. 15, Aug. 23, 1999, 2 pages.
Towie, Henry, “On the Fast Track with Totaltracks: UPS Deploys Mobile Date Service,” Abstract No., XP-000560076, Document Delivery World, vol. 9, No. 3, 1993, pp. 30-31.
Van Den Berg, Jeroen P., “A Literature Survey on Planning and Control of Warehousing Systems”, IIE Transactions, Aug. 1999, vol. 31, No. 3, p. 751.
Vass et al., “The World Wide Web—Everything you (n)ever wanted to know about its server”, IEEE, Oct./Nov. 1998, pp. 33-37.
Wilson, Joe, “Selecting Warehouse Management Software (WMS) for Food Distribution Operations”, Frozen Food Digest, Oct. 1998, vol. 14, No. 1, p. 18.
Worth Wren Jr., Fort Worth Star-Telegram Texas, “Albertson's Expects Online Grocery Shopping to Boom”, KRTBN Knight-Ridder Tribune Business News (Fort Worth Star-Telegram, Texas), Nov. 9, 1998.
Wunnava et al., “Interactive Mulitmedia on the World Wide Web”, IEEE, Aug. 1999, pp. 110-115.
www.peapod.com, including Introduction to Peapod; How Peapod Works; Peapod: Choosing a Delivery Time; Peapod: Sending Your Order; Retrieved from Internet Archive (web.archive.org) on Jul. 23, 2006, alleged date Nov. 13, 1996, pp. 1-9.
Hoffman, Thomas, “New UPS CIO eyes cyberdelivery,” Computerworld, Nov. 11, 1996, 30, 46; ABI/INFORM Global, p. 4.
Booker, et al. “Up in the air”, Computerworld, Oct. 11, 1993; 27, 41; ABI/INFORM Global, p. 54.
“Imposing an Objective Viewpoint,” Modern Purchasing, vol. 36, Iss. 3, Mar. 1994, pp. 1-4.
“New Medium, new message,” The Economist, vol. 329, Iss. 7834, Oct. 23, 1993, p. S 16, pp. 1-5.
Restriction Requirement for U.S. Appl. No. 09/568,571, dated Jun. 11, 2002.
Office Action for U.S. Appl. No. 09/568,571, dated Apr. 2, 2003.
Advisory Action for U.S. Appl. No. 09/568,571, dated Jul. 3, 2003.
Office Action for U.S. Appl. No. 09/568,571, dated Jan. 8, 2004.
Office Action for U.S. Appl. No. 09/568,571 dated Jul. 2, 2004.
Office Action for U.S. Appl. No. 09/568,571 dated Jan. 26, 2005.
Office Action for U.S. Appl. No. 09/568,571 dated Jul. 19, 2005.
Notice of Allowance for U.S. Appl. No. 09/568,571 dated Nov. 10, 2005.
Notice of Allowance for U.S. Appl. No. 09/568,571 dated Oct. 17, 2006.
Restriction Requirement for U.S. Appl. No. 11/356,870, dated Nov. 30, 2006.
Office Action for U.S. Appl. No. 11/356,870 dated Mar. 20, 2007.
Office Action for U.S. Appl. No. 11/356,870 dated Nov. 26, 2007.
Office Action for U.S. Appl. No. 11/356,870 dated May 23, 2008.
Notice of Allowance for U.S. Appl. No. 11/356,870 dated Dec. 31, 2008.
Restriction Requirement for U.S. Appl. No. 12/387,801, dated Sep. 15, 2010.
Office Action for U.S. Appl. No. 12/387,801, dated Dec. 22, 2010.
Notice of Allowance for U.S. Appl. No. 12/387,801, dated Jul. 11, 2011.
Notice of Allowance for U.S. Appl. No. 12/387,801, dated Nov. 15, 2011.
Dialog Search Results, re: U.S. Appl. No. 11/705,982 dated Sep. 13, 2010, pp. 1-54.
QuickRef Guide, QuickRefUS, Version 4.0x, U.S. Retail, 1998, 34 pgs.
Consumer Direct Selling Backhome Foods Products—1999: HHT Training Guide, Mar. 29, 1999.
Backhome Foods Review, est 1998.
Consumer Direct HHT Training Guide, Jun. 1998.
Alba et al., “Interactive home shopping: Consumer, retailer, and manufacturer incentives to participate in electronic marketeplaces”, Journal of Marketing, vol. 61, No. 3, Jul. 1, 1997, 18 pgs.
Bloch et al., “On the Road of Electronic Commerce—a Business Value Framework, Gaining Competitive Advantage and Some Research Issues”, Mar. 1996, 20 pages.
Brown Janelle, “Pod People Peapod, the online grocery service, sounds great—but can it deliver?” Salon Media Group, Inc., Dec. 17, 1998, 3 pages.
Corcoran, Cathy, “The Skeptic's Guide to on-line shopping. Who has time to shop for groceries? So we gave Peapod a test run.” The Patriot Ledger, Quincy, Ma, Jul. 7, 1997, 4 pages.
Descartes Licenses Energy V6 Supply Chain Suite to Major Pepsi Bottler . . . News Release, Descartes Systems Group Inc., Waterloo Ontario, Aug. 27, 1998, 2 pages.
Dilger, Karen Abramic, “Warehouse Wonders”, Manufacturing Systems, vol. 15, No. 2, Feb. 1, 1997, 4 pages.
Dyson et al., “Electronic Delivery without the Internet (Digital Delivery of Newspapers)”, The Seybold Report on Publishing Systems, vol. 25, No. 1, ISBN: 0736-7260, Sep. 1, 1995, 9 pages.
Eckerson, Wayne, “Grocers put stock in EDI to streamline deliveries; New electronic data interchange systems offer a wealth of benefits for retailers and suppliers,” Network World, Inc., Aug. 7, 1989, 2 pages.
First Stop—Main Menu, website tour, Peapod, http://web.archive.org/web/19961113150913/www.peapod.com/tourl.html, 13 pages.
Frequently Asked Questions, Peapod, http://web.archive.org/web/19961113150832/www.peapod.com/question.html, 2 pages.
“Here's How Peapod Works,” http://web.archive.org/web/19961113151243/www.peapod.com/work.html, 2 pages.
“Installation and Shopping Tips for the Mac,” Peapod Video, 1993, 1 page.
“Introduction to Peapod,” webpages, Peapod, http://web.archive.org/web/19961113145506/www.peapod.com/intro.html, Nov. 13, 1996, 2 pages.
Ives, Blake et al., “The Information System as a Competitive Weapon”, Communications of the ACM, vol. 27, No. 12, Dec. 1984. 9 pages.
Maeglin, Kathy, “Services Take the 'Shop' Out of Shopping for Groceries”, The Capital Times, Mar. 20, 1997, 2 pages.
Mai et al., “Consumers' Perceptions of Specialty Foods and the Rural Mail Order Business”, 52nd EAAE Seminar—Parma, Jun. 19-21, 1997, pp. 331-348.
Malone et al., “Computers, Networks, and the Corporation,” Center for Information Systems Research, MIT, Aug. 1991, 14 pages.
Marsh, Barbara, “Peapod's On-Line Grocery Service Checks Out Success—Customers Shop Electronic Aisles; Finicky Workers Sack the Goods”, The Wall Street Journal, Jun. 30, 1994, 2 pages.
Meeker et al., The Internet Retailing Report, U.S. Investment Research, Morgan Stanley, May 28, 1997, 241 pages.
Menzies, David, “Checking out the aisles by computer: Cori Bonina, General Manager of Stong's market in Vancouver, has made a virtual success of a meat-and-potatoes business”, National Post, Dec. 1, 1998, 2 pages.
“More Information,” webpages, Peapod, http://web.archive.org/web/19961113145540/www.peapod.com/more.html, Nov. 13, 1996, 2 pages.
“Online Groceries, A Quicker Shopping Cart?” E-Commerce Customers—What, Where and Why They Buy, Standard Media Inc. and Odyssey, LP, Spring 2000, 19 pages.
Patterson, Rebecca H., “No Lines at Britain's First On-Line Grocery Store, but You Still May Wait”, The Wall Street Journal Europe, Jul. 25, 1997, 3 pages.
Peapod, Inc., Telephone Grocery Shopping Guide, Aug. 7, 1992, 3 introductory pages and pp. 1-12.
Podmolik, Mary Ellen, “Groceries Seeing Green From Computer Shopping”, Chicago Sun-Times, May 8, 1996, 1 page.
Poirier, Charles et al., Supply Chain Optimization, Building the Strongest Total Business Network, Berrett-Koehler Publishers, San Francisco, Copyright 1996, 30 pages.
Purpura, Linda, “Getting to House from Order Smooth Transitions from Order, To Pick, To Pack, To Delivery, are a Vital Part of a Successful Home-Shopping Program”, Supermarket News, Oct. 6, 1997, 2 pages.
Reynolds, Janice, “Logistics and Fulfillment for E-Business” ISBN: 1-57820074-1, 2001, 60 pages.
“Shopping-Virtually Hassle-Free”, Computer Weekly, Apr. 10, 1997, 2 pages.
Smart Shopping for Busy People, WEBPAGE, Peapod http://web.archive.org/web/19961113145048/www.peapod.com/ 1 page.
User Manual, Peapod, Inc., Version 3.10, Aug. 7, 1992, 83 pages.
VanMieghem, Jan A., “Peapod: Mass Customized Service”, Kellogg School of Management, Northwestern University, Aug. 28, 2001 (Rev. Nov. 22, 2004), 13 pages.
Coffman, Steve, “Building earth's largest library: Drive into the future,” Mar. 1999, Searcher, 7, 3, 34(1).
BIG-IP® Controller Administrator Guide, version 3.3, ©1997-2000 F5 Networks, Inc., pp. 1-401.
BIG-IP® FireGuard™ Controller Administrator Guide, version 3.3, ©1997-2000 F5 Networks, Inc., pp. 1-168.
Bluestone Software's EJB Technology, A Technical White Paper by TechMetrix Research, Philippe Mougin, ©TechMetrix 2000, pp. 1-24.
Bluestone XML-Server: First Application Server to Recognize XML™ As a Data Type, White Paper, © 1999 NC.Focus, pp. 1-21.
Load-Balancing Internet Servers, IBM International Technical Support Organization, Austin Center, Dec. 1997, © International Business Machines Corporation 1997, pp. 1-162.
Dyck, Timothy, “IBM's WebSphere 3.0 pushes ahead,” PC Week, vol. 16, No. 42, Oct. 18, 1999, 4 pgs.
“IBM Provides the Power for Enterprise e-business Solutions by Launching New Phase of Server Software,” News Release, Las Vegas, Jul. 20, 1999, 2 pgs.
WebSphere Application Server 3.0, Advanced Edition, Programming Documentation, pp. 1-205.
WebSphere Application Server 3.0, Standard Edition, Programming Documentation, pp. 1-188, allegedly dated Oct. 1999.
WebSphere V3 Performance Tuning Guide, First Edition (Mar. 2000), © International Business Machines Corporation 2000, pp. 1-210.
Deshpande, Salil. “Clustering: Transparent Replication, Load Balancing, and Failover,” CustomWare, Jan. 2000, pp. 1-23.
“Enterprise JavaBeans™ Programmer's Guide,” Inprise Application Server™ Version 4.0, ©1999 Inprise Corporation, pp. 1-165.
Related Publications (1)
Number Date Country
20120173449 A1 Jul 2012 US
Provisional Applications (1)
Number Date Country
60133646 May 1999 US
Continuations (3)
Number Date Country
Parent 12387801 May 2009 US
Child 13418527 US
Parent 11356870 Feb 2006 US
Child 12387801 US
Parent 09568571 May 2000 US
Child 11356870 US