The present invention pertains to order substitution methods and systems that automatically perform substitutions for unavailable items in a customer order. More specifically, the invention allows for the substitution of unavailable items based upon predetermined criteria and set processes, so that the substitutions are made in a manner that optimizes efficiency and customer satisfaction.
Substitution methods in the current art typically use non-systematic and inefficient procedures in order to provide substitute items for unavailable items in a customer order. For example, some Internet-based grocery shoppers, (such as, for example, Peapod Inc., of Skokie, Ill.), send human buyers to one or more stores in order to fulfill customer orders. If a buyer is trying to fulfill an order for Brand A 64 oz. Ketchup, for example, and it is out of stock at the store, the buyer can make a substitution in order to approximate the product that the customer ordered. However, the substituted item may only be chosen from available items on the grocery shelf, which are typically adjacent to the unavailable items on the shelf space. Thus, for example, the buyer might substitute the same brand ketchup in a different size or variety, or a different brand in a similar size or variety, assuming that either is available at the store.
There are several problems with conventional order substitution methods. For one, the buyer's guess often does not result in a satisfactory substitute, particularly since they buyer is typically not an expert on all types of products. Also, the buyer does not have a procedure by which to consider all of his or her or her customer orders in the aggregate in order to make decisions that better maximize customer satisfaction. Further, no procedures exist for aggregating the orders of one buyer with that of other buyers in order to make larger aggregate decisions. Additionally, the buyer also does not have access to data concerning the available inventory of the store before attempting to fulfill his or her orders, and therefore is only able to make ad hoc decisions at the time of fulfillment.
For these, and other reasons, an efficient, automatic system architecture and method is desired to implement substitutions for unavailable items in customer orders.
This invention provides systems and methods for implementing item substitutions with respect to consumer orders in order to implement substitutions of unavailable items in customer orders. In a specific embodiment, this is accomplished by first taking customer orders via a data or computer network. A selected number of customer orders may then be aggregated and analyzed in order to make item substitution decisions. The decisions may be based upon a variety of different criteria, including one or more of the following: data from the selected customer orders, customer preferences, predefined substitution rules for each of the products, and accurate inventory information on the actual availability of products, etc.
Specific embodiments of the invention provide a method and computer program product for effecting, via a computer network, substitution of at least one ordered item of at least one customer order. At least one customer order is received via the computer network. At least a portion of the received customer order is analyzed to determine whether at least one item of inventory has been oversold. According to a specific implementation, the analyzed order data may be compared to available inventory data to determine whether at least one item of inventory has been oversold. Order line items relating to an identified oversold item may then be identified, wherein each order line item may be associated with a respective customer order. According to a specific implementation, order line items for identified oversold items may be selected using at least a portion of the predefined criteria. At least one second item may then be substituted for an identified oversold item in selected customer orders, based upon the predefined criteria. According to one implementation, the item substitution technique of the present invention may be performed by an automated computer process. It may also be performed at a time of fulfilling an order without intervention from a human operator.
According to a specific implementation, the predefined criteria may include a variety of business rules relating to how line items are selected for substitution analysis, and relating to how substitute items are selected. For example, the predefined criteria may include rules relating to minimizing a total number of order substitutions performed for each customer order; rules relating to selecting, for substitution analysis, order line items which have a relatively highest order quantity; sorted list of substitute products from which substitute items are chosen; rules for substituting a specific quantity of a second item for an unavailable item; etc.
An alternate embodiment of the present invention is directed to a system for effecting, via a computer network, substitution of at least one ordered item of at least one customer order. The system may include least one central processing unit, at least one interface configured or designed to receive at least one customer order via the computer network, and memory. The at least one customer order may include at least one order line item relating to an ordered quantity of a particular item of inventory. The memory may be configured to store customer order information and predefined criteria relating to item substitution rules. The system may be configured to analyze at least a portion of the received customer orders to determine whether at least one item of inventory has been oversold. The system may also be configured to identify order line items relating to an identified oversold item, wherein each order line item is associated with a respective customer order. The system may also be configured to substitute, based upon predefined criteria, at least one second item for the identified oversold item in selected customer orders.
Alternate embodiments of the present invention are directed to a method and computer program product for effecting, via a computer network, substitution of at least one ordered item of at least one customer order. At least one customer order is received via the computer network. Each customer order may include at least one order line item relating to an ordered quantity of a particular item of inventory. At least a portion of the received customer orders may then be analyzed to determine whether at least one item of inventory has been oversold. Order line items relating to an identified oversold item may be identified, each order line item being associated with a respective customer order. At least one second item may then be substituted for the identified oversold item in selected customer orders based upon predefined criteria.
Additional objects, features and advantages of the various aspects of the present invention will become apparent from the following description of its preferred embodiments, which description should be taken in conjunction with the accompanying drawings.
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.
For example, system 100 of
According to a specific implementation, the PUB Subsystem 140 may be used for managing SKU inventory and catalog information (e.g. SKUs, UPCs, products, categories, descriptive attributes, etc.), and item substitution information provided by merchants or vendors.
“Inventory” is the stock of SKU items actually available for customer orders. Each different item of inventory is associated with a respective stock keeping unit or SKU, regardless of whether the item is available for customer purchase. A “stock keeping unit” or SKU may be defined as a unique identifier that corresponds to a particular consumer item. A type of product, for example, Brand A ketchup, may have several unique SKUs, each corresponding, for example, to different sizes and/or flavors of Brand A ketchup.
Merchants and content managers 133 may enter and maintain SKU information stored in the PUB database using the PUB Web GUI interface 134 and PUB Bulk Loader interface 136. The SKU information may include SKU attribute values such as, for example, UPCs, vendors, categories, category hierarchy, images, articles, descriptive information, etc. The PUB Web GUI interface 134 allows merchants to edit SKU information, products, and/or categories. The PUB Bulk Loader 136 supports the processing of data files from outside the PUB Subsystem into the PUB database 141. According to a specific embodiment, the PUB Bulk Loader is configured to allow merchants to upload a variety of data file types into the PUB database including flat data files, and image files. The Bulk Loader processes the flat file information to create appropriate database records for the PUB catalog.
Periodically (e.g., minutes, hours, days) the OMS polls the PUB database for new and updated SKU information, and stores the retrieved data into the OMS database 151. According to a specific embodiment, OMS maintains available-to-promise (ATP), price, and inventory (e.g., replenishment and purchasing) information for each SKU. OMS may also capture and/or manage sales and shipment data relating to each SKU. Periodically, OMS passes new and updated SKU information it acquires from the PUB Subsystem to the OFS. The SKU information may be used by OFS, for example, to maintain physical inventory and fulfill orders.
According to a specific embodiment, the PUB Subsystem 140 may be used as an interface to allow merchants/vendors to enter substitution instructions relating to specific SKUs. An example of a set of substitution instructions for selected SKUs is shown in
As shown in the embodiment of
According to a specific implementation, the “substitution rules” for particular SKU indicate how substitutions are to be performed for that SKU. The substitute ratio field 416 may be used to determine how much quantity of a substitute SKU is to be substituted for a specified quantity of an original SKU. According to a specific embodiment, it is preferable to have a substitute ratio included since a substitution may not necessarily be one for one. The “charge rule” or pricing field 420 may be used to determine a price to bill the customer for the substituted item.
For example, if a customer orders a quantity of 1 “Budweiser 6 Pack”, and later it is determined that this SKU is oversold or unavailable, the substitution instructions 400 may be referenced in order to determine which products/items may be substituted for the unavailable item. According to the example of
Another aspect relating substitute item processing concerns pricing for substitute items. As shown in
A different pricing rule is shown in
According to a specific embodiment, the substitution instructions may also include a “not allowed” substitution rule for one or more SKUs. This is shown, for example, in entry 408 of
It will be appreciated that, in an alternate embodiment, the substitution instructions may be entered by merchants, vendors, or other human operators via the Webstore interface 132, or via other desired system interfaces. Further, according to a specific implementation, the merchant or vendor is able to add, rearrange, and remove items from the substitution list. Additionally, according to a specific embodiment, merchants and/or vendors may be provided with information relating to oversold items. For example, a merchant may be provided with information relating to selected oversold items for customer orders which are to be fulfilled the following day. The merchant is then able to analyze the oversold item information, and submit substitution instructions for the selected oversold items before the customer orders are fulfilled. According to one implementation, the oversold item information may be provided to a merchant via the PUB Subsystem 140.
According to at least one alternate embodiment, substitution instructions may be generated automatically using a general set of business and customer preference rules in order to save time and also optimize customer satisfaction. Preliminary substitution lists may also be generated in the same manner to be approved or edited by merchants. In any of these embodiments, the substitution instructions are typically stored in a database for retrieval at the appropriate point of use. In another embodiment, a substitution list can be dynamically generated at the time of use, again by using a general set of business and customer preference rules.
Webstore Subsystem (WS)
According to a specific implementation, the Webstore Subsystem (WS) 132 provides an interface for enabling customers to access an on-line store (e.g. Webstore), which, for example, may be used to provide a customer with an electronic representation of a retail store. In a specific embodiment where the Webstore may be implemented as a website on the World Wide Web, customers 102 may access the Webstore via the Internet 104 or World Wide Web using any one of a plurality of conventional browsers. The Webstore user interface may be designed to provide a rich set of functions without requiring any special browser plug-ins. Thus, according to a specific embodiment, customers may access the Webstore using any client machine, regardless of the machine's operating system platform. Additionally, for security purposes, the Webstore interface also supports data encryption for exchange of any sensitive or private information between the customers and the website. According to a specific embodiment, the secure Webstore interface may be implemented using a secure http protocol (HTTPS), commonly known to those of ordinary skill in the art.
In accordance with a specific embodiment, the Webstore Subsystem 132 may be configured to support a number of customer related features such as, for example, self registration; accessing of customer account information; browsing of product categories and category hierarchy; viewing of product images and product information; keyword searches; delivery scheduling; accessing of customer order history; customizable shopping lists; on-line shopping and ordering; etc.
The Webstore Subsystem (herein referred to as the Webstore) may be implemented using at least one server which is connected to the data network. According to a specific embodiment, the Webstore may be implemented using a plurality of web servers (e.g. a load-balanced web server farm) which helps to minimize server response time and provide real-time failover and redundancy capabilities. Further, according to a specific embodiment, in order to keep the web server response time to a minimum, the Webstore may be configured such that all processing is performed on a single server, within one process. Where a plurality of Webstore servers are used, redundant processing may be performed by at least a portion of the servers so that a single Webstore server may handle all Webstore processing tasks associated with a particular on-line customer. It will be appreciated that the Webstore server boundaries may be crossed where appropriate, such as, for example, when accessing desired databases via the data network.
Order Management Subsystem (OMS)
The Order Management Subsystem (OMS) 150 manages a variety of aspects related to the integrated system architecture of system 100, including, for example, pricing, availability, inventory, vendors, financials, procurement, and data flows between various subsystems.
As shown in
According to a specific implementation, OMS batch processing may be controlled using a process scheduler. The process scheduler is able to manage the number of concurrent processes being run and the date/time at which certain processes are to run or be executed. The process scheduler may also enable central visibility of all processes currently running. Batch processing and reporting may be accomplished using a variety of different technologies commonly known to one having ordinary skill in the art.
The Order Management Subsystem may be configured to support both asynchronous and synchronous interfaces with the other subsystems. In a specific embodiment, the OMS is configured to support an asynchronous interface with each of the other subsystems. Additionally, each OMS interface is configurable, and may be configured to support the running of batch processes as often as is desirable.
Implementation of the various interfaces between OMS and the other subsystems may be accomplished using a variety of different techniques commonly known to one having ordinary skill in the art. The following description provides an example of at least some of the various techniques which may be used for interfacing OMS with the other subsystems. However, it will be appreciated that the specific interfaces described below may be implemented using other techniques commonly known to those of ordinary skill in the art.
The interface between the OMS and the Webstore Subsystem may be implemented, for example, using a plurality of executable programs. A first portion of the executable programs may be responsible for moving data from the Webstore to the OMS. This data may include, for example, new/updated customer data, new/updated order data, order cutoff information, order billing information, customer return information, customer credits and fees (e.g. bill adjustment data), etc. A second portion of the executable programs is responsible for moving data from the OMS to the Webstore Subsystem. This data may include, for example, inventory data, availability data, pricing data, and information about shipped customer orders.
Order Fulfillment Subsystem (OFS)
The Order Fulfillment Subsystem 160 manages all functionality of the distribution center (DC). In the embodiment of
In a specific implementation, the Order Fulfillment Subsystem 160 may be implemented using a warehouse management system such as, for example, the MOVE warehouse management system provided by Optum, Inc. of Costa Mesa, Calif. The warehouse system also provides an interface with the Order Management Subsystem. In a specific embodiment, this interface may be implemented using a business host interface (BHI). The warehouse management subsystem may also provide the interface for allowing the OMS subsystem to communicate with the OFS database 161.
The description is only a partial description of an architecture that is suitable for practicing the current invention, with emphasis on the subsystems that are most directly involved in the substitution procedure of the current invention. For a more complete description of such an architecture, see U.S. patent application Ser. No. 09/568,603.
It will be appreciated that other embodiments of the system of
At 202, a customer enters his or her customer order via the Webstore 132 interface (described above). According to a specific embodiment, a “customer order” includes a list of SKU items that have been ordered, their associated quantities, and other relevant information (e.g., payment information, delivery time information, etc.)
The customer order may include one or more “line item orders,” where each line item order corresponds to a particular SKU and includes a desired quantity of the ordered SKU. According to a specific embodiment, at the time of the customer order, the customer may also specify whether substitutions are allowed for the customer order generally, or alternatively, whether substitutions are allowed with respect to each specific line item order. The customer's general substitution preferences also may be stored in the Webstore database, and may be accessed and/or modified during the current customer order.
According to a specific embodiment, during the customer ordering process, customers will be provided information relating to availability of items. For example, customers may be provided with information relating to particular items which will not be available until after the customer's specified delivery date. In this way, item substitution of customer orders may be minimized.
However, for various reasons, it is possible that ordered items may be oversold or unavailable at the time of fulfillment of the order. For example, it is possible that the quantities of inventory levels for selected SKUs that are anticipated or expected to be available by a specific date are not actually available on that date. If it is not possible to fulfill a customer order because one or more ordered items are unavailable, that order may be said to be incomplete.
Incompletes may occur for a variety of reasons, such as, for example, vendor short shipments, goods found damaged at time of fulfillment, etc. For incompletes which relate to short shelf-life SKUs, such as, for example, bread and milk, it may be preferable, from a customer perspective, to substitute items, rather than to allow the order to be delivered incomplete.
Thus it will be appreciated that, substitution capability provides an opportunity to turn a problem into an improved customer experience. For example, customers may receive larger sizes at the smaller size price, may receive premium brands at non-premium brand prices, or may receive comparable brands at no charge.
Returning to
In the example of
According to a specific embodiment, the quantity of available SKU units may be represented as a quantity of SKU units which are estimated to be available as of a specified date, such as, for example, the customer delivery date. According to a specific implementation, each of the customer orders in a given batch of cutoff customer orders will have the same delivery date.
Further, according to a specific embodiment, only SKUs that have associated “substitution instructions” will be analyzed for substitution analysis. As described previously, the system of the present invention may include a respective set of substitution instructions for each or selected SKUs in the inventory. These instructions may either be statically generated (e.g. created by a human operator) or dynamically generated (e.g. created by a computer system using predetermined business rules). An example of a set of substitution instructions for selected SKUs is shown in
At 306, a determination is made as to whether there are any oversold SKUs identified. If at least one oversold SKU has been identified, then a first oversold SKU is selected (308) for substitution analysis. A determination is then made (309) as to whether substitutions are permitted for the selected oversold SKU. For example, if there are no substitution instructions for the selected oversold SKU, or if there are no substitute SKUs listed in the substitution instructions for the selected oversold SKU, then, according to at least one embodiment, substitutions are not permitted for the oversold SKU. Alternatively, the substitution instructions may specify that substitutions are not permitted for the oversold SKU. This may occur, for example, with respect to restricted SKU items such as alcohol or tobacco products.
If it is determined that substitutions are not permitted for the selected oversold SKU, then a next identified oversold SKU is selected (320) for substitution analysis. Assuming, however, that substitutions are permitted for the selected oversold SKU, line item orders (from the batch of cutoff customer orders) which correspond to the selected oversold SKU are then retrieved (310). According to a specific implementation, retrieved line item orders which correspond to customers who have requested not to received substitutions (either for the selected oversold SKU or generally) may be discarded (312) so that these line item orders are not considered for further substitution analysis. The remaining line item orders may then continue to be processed (314) for substitution analysis. The remaining line item orders may then be sorted (316) according to predefined criteria.
According to a specific embodiment, the predefined criteria may include business rules which define substitution preferences. Some of these business rules include the substitution instructions described previously with respect to
Additionally, according to a specific implementation, business rules may be included which prevent an oversold SKU and the substitute SKU from having different regulation codes (e.g. alcohol, tobacco, etc.). Additionally, business rules may be included which do not attempt to substitute a particular SKU for an oversold SKU if it is determined that the substitute SKU already exists as a line item in the customer order. Such business rules may be applied, for example, during substitute SKU selection as described, for example, with respect to
Once the selected line item orders have been sorted, an Item Substitution Procedure (such as that shown, for example, in
Initially, as shown in the embodiment of
Assuming that the selected oversold SKU has been identified, the Item Substitution Procedure may then retrieve (504) the substitution instructions and other business rules (if any) relating to the identified oversold SKU. Alternatively, according to an alternate embodiment, the substitution instructions may be dynamically generated using predefined business rules specifically configured for generating substitution instructions or rules relating to specific SKUs or classes of SKUs.
As shown at 506 of
As shown at 508, the current oversold quantity is then compared (510) to the ordered quantity specified in the selected line item order. If it is determined that the ordered quantity is less than or equal to the current oversold quantity then a Full Substitution Procedure (such as that described, for example, in
For example, if the current line item order specifies a quantity of 3 Large Red Apples, and the current oversold quantity of Large Red Apples is 4, then a full substitution procedure may be implemented, meaning that the full quantity of the line item order (e.g. 3) may be substituted. Once the substitution has been performed for the selected line item order, the current oversold quantity will be updated to 1 oversold large red apple. Alternatively, if the current line item order specifies a quantity of 3 Large Red Apples, and the current oversold quantity of Large Red Apples is 2, then a partial substitution procedure may be implemented, meaning that only a portion the line item order is to be substituted. In this example, the line item order may be filled by allocating 1 large red apple to the customer order, and substituting 2 Large Red Apples with other items.
After the appropriate substitution procedure has been be implemented for the selected line item order, a determination is then made (513) as to whether the substitution for the selected line item order was successful. If it is determined that the substitution was not successful, then, according to one embodiment, it may be assumed that no substitutions are available for the selected oversold product. Accordingly, the Item Substitution Procedure may end without attempting to perform any further substitutions for the selected oversold SKU.
Assuming, however, that the substitution for the selected line item order was successful, a determination is then made (514) as to whether the current oversold quantity for the identified oversold SKU is equal to zero. If it is determined that the current oversold quantity for the identified oversold SKU is equal to zero, then no further substitutions need be performed for the identified oversold SKU. If, however, the current oversold quantity for the identified oversold SKU is greater than zero, a determination may be made (516) as to whether there are additional line item orders (from the sorted list of line item orders) to be analyzed for item substitution analysis. If so, then a next line item order from the list is selected (506) for item substitution analysis.
Initially, as shown in the embodiment of
Once the selected oversold SKU has been identified, substitution instructions relating to the identified oversold SKU are retrieved (604) and processed in order to select (605) a first preferred substitute SKU for the identified oversold SKU. An example of substitution instructions is shown in
At 606 a determination is made as to whether there is a sufficient available quantity of the selected substitute SKU to be substituted for the identified oversold SKU. If it is determined that there is an insufficient quantity of the selected substitute SKU available, then the substitution instructions may be consulted to determine (607) whether any alternate substitute SKUs are specified for the identified oversold SKU. Assuming that at least one alternate substitute SKU is specified, a next preferred substitute SKU is selected (605) for analysis. If it is determined that none of the substitute SKU(s) specified in the substitution instructions are available to be substituted for the identified oversold SKU, then, according to a specific implementation, the substitution may be reported (614) as being unsuccessful, and no substitution will be made for the identified oversold SKU.
Assuming that sufficient quantities of a selected substitute SKU are available to be substituted for the identified the oversold SKU quantity, then the partial substitution may be performed, for example, by adding (610) a “substitute line item order” to the customer order, specifying the substitute SKU and substituted quantity, and by reducing or modifying (612) the quantity in the selected line item of the customer order (corresponding to the identified oversold SKU) as appropriate. Additionally, the oversold quantity may be set (608) to zero, thereby indicating that the identified oversold SKU is no longer oversold.
For purposes of illustration, an example of the Partial Substitution Procedure will now be described using the substitution instructions illustrated in
If it is determined that 4 Medium Red Apples are available, a new line item specifying 4 Medium Red Apples will be added to the customer order (associated with the selected line item order). According to a specific embodiment, the new line item may be described as a partial substitution for the line item order of 3 Large Red Apples. Additionally, the quantity of the customer's (original) line item order for 3 Large Red Apples will be reduced to 1 Large Red Apples, and the quantity of oversold Large Red Apples will be reduced to zero.
Alternatively, if it is determined that no Medium Red Apples are available, a next preferred substitute SKU is selected (if available) for analysis. In the example of
Initially, as shown in the embodiment of
Once the selected oversold SKU has been identified, substitution instructions relating to the identified oversold SKU are retrieved (704) and processed in order to select (705) a first preferred substitute SKU for the identified oversold SKU. An example of substitution instructions is shown in
At 706 a determination is made as to whether there is a sufficient available quantity of the selected substitute SKU to be substituted for the identified oversold SKU. If it is determined that there is an insufficient quantity of the selected substitute SKU available, then the substitution instructions may be consulted to determine (707) whether any alternate substitute SKUs are specified for the identified oversold SKU. Assuming that at least one alternate substitute SKU is specified, a next preferred substitute SKU is selected (705) for analysis. If it is determined that none of the substitute SKU(s) specified in the substitution instructions are available to be substituted for the identified oversold SKU, then, according to a specific implementation, the substitution may be reported (714) as being unsuccessful, and no substitution will be made for the identified oversold SKU.
Assuming that sufficient quantities of a selected substitute SKU are available to be substituted for the identified the oversold SKU quantity, then the full substitution may be performed, for example, by adding (710) a “substitute line item order” to the customer order, specifying the substitute SKU and substituted quantity, and by reducing or modifying (712) the quantity in the selected line item of the customer order (corresponding to the identified oversold SKU) to zero. In an alternate embodiment, the original line item order may be dropped from the customer order. Additionally, as shown in
For purposes of illustration, an example of the Full Substitution Procedure will now be described using the substitution instructions illustrated in
If it is determined that 6 Medium Red Apples are available, a new line item specifying 6 Medium Red Apples will be added to the customer order (associated with the selected line item order). According to a specific embodiment, the new line item may be described as a full substitution for the line item order of 3 Large Red Apples. Additionally, the quantity of the customer's (original) line item order for 3 Large Red Apples will be reduced to zero Large Red Apples. Further the quantity of oversold Large Red Apples will be reduced by 3, making the new (or current) oversold quantity of Large Red Apples equal to 2.
The substitution technique of the present invention offers many advantages and capabilities over the conventional techniques. For example, technique of the present invention may be used to minimize the total number of substitutions to be implemented for a selected batch of customer orders by first implementing substitutions for line item orders of higher quantities. In addition, technique of the present invention may automatically prioritize line item orders so that customer orders that have already had at least one item substitution performed are less likely to have another item substitution performed. It will be appreciated that either of the above-described features may result in improved customer satisfaction.
Additionally, according to at least one embodiment of the present invention, substitution of ordered customer items may be automatically implemented without involving human decisions and/or human interactions at the time of fulfillment of the customer order(s). In this way, the technique of the present invention may be used to expedite order processing and order fulfillment, for example, by eliminating delays associated with human decisions and/or interactions.
Moreover, the technique of the present invention is highly scalable, and provides for more consistent and reliable substitutions as compared to conventional techniques. This, in turn, may result in improved overall quality control.
Generally, the item substitution technique of the present invention may be implemented on software and/or hardware. For example, it can be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, or on a network interface card. In a specific embodiment of this invention, the technique of the present invention is implemented in software such as an operating system or in an application running on an operating system.
A software or software/hardware hybrid implementation of the item substitution technique of this invention may be implemented on a general-purpose programmable machine selectively activated or reconfigured by a computer program stored in memory. Such programmable machine may be a network device designed to handle network traffic, such as, for example, a router or a switch. Such network devices may have multiple network interfaces including frame relay and ISDN interfaces, for example. A general architecture for some of these machines will appear from the description given below. In an alternative embodiment, the item substitution technique of this invention may be implemented on a general-purpose network host machine such as a personal computer or workstation. Further, the invention may be at least partially implemented on a card (e.g., an interface card) for a network device or a general-purpose computing device.
Referring now to
CPU 62 may include one or more processors 63 such as a processor from the Motorola family of microprocessors or the MIPS family of microprocessors. In an alternative embodiment, processor 63 is specially designed hardware for controlling the operations of network device 60. In a specific embodiment, a memory 61 (such as non-volatile RAM and/or ROM) also forms part of CPU 62. However, there are many different ways in which memory could be coupled to the system. Memory block 61 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, etc.
The interfaces 68 are typically provided as interface cards (sometimes referred to as “line cards”). Generally, they control the sending and receiving of data packets over the network and sometimes support other peripherals used with the network device 60. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various very high-speed interfaces may be provided such as fast Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces and the like. Generally, these interfaces may include ports appropriate for communication with the appropriate media. In some cases, they may also include an independent processor and, in some instances, volatile RAM. The independent processors may control such communications intensive tasks as packet switching, media control and management. By providing separate processors for the communications intensive tasks, these interfaces allow the master microprocessor 62 to efficiently perform routing computations, network diagnostics, security functions, etc.
Although the system shown in
Regardless of network device's configuration, it may employ one or more memories or memory modules (such as, for example, memory block 65) configured to store data, program instructions for the general-purpose network operations and/or other information relating to the functionality of the item substitution technique described herein. The program instructions may control the operation of an operating system and/or one or more applications, for example. The memory or memories may also be configured to include data structures which store customer order information, inventory data, item substitution instructions, substitution business rules, etc.
Because such information and program instructions may be employed to implement the systems/methods described herein, the present invention relates to machine readable media that include program instructions, state information, etc. for performing various operations described herein. 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 such as floptical disks; 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 traveling 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.
This application is a continuation of U.S. patent application Ser. No. 09/750,385, filed Dec. 27, 2000, (now U.S. Pat. No. 7,233,914) and entitled “Technique for Implementing Item Substitution for Unavailable Items Relating to a Customer Order,” which is hereby incorporated herein by reference. This application is related to the following patent applications: U.S. patent application Ser. No. 09/568,603 (now U.S. Pat. No. 7,177,825); U.S. patent application Ser. No. 09/568,570 (now U.S. Pat. No. 7,370,005); and U.S. patent application Ser. No. 09/568,569 (now U.S. Pat. No. 6,622,127), all filed on May 10, 2000. Each of the above-referenced US patent applications is incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
2781643 | Fairweather | Feb 1957 | A |
3406532 | Rownd et al. | Oct 1968 | A |
3670867 | Traube | Jun 1972 | A |
4213310 | Buss | Jul 1980 | A |
4455453 | Parasekvakos et al. | Jun 1984 | A |
4530067 | Dorr | Jul 1985 | A |
4656591 | Goldberg | Apr 1987 | 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 |
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 |
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 |
5710887 | Chelliah et al. | Jan 1998 | A |
5712989 | Johnson et al. | Jan 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 |
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 | Cherney 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 |
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 |
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 |
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 |
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 |
6094642 | Stephenson et al. | Jul 2000 | A |
6101481 | Miller | Aug 2000 | A |
6101486 | Roberts et al. | Aug 2000 | A |
6115690 | Wong | Sep 2000 | A |
6123259 | Ogasawara | Sep 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 |
6182053 | Rauber et al. | Jan 2001 | B1 |
6185625 | Tso et al. | Feb 2001 | B1 |
6215952 | Yoshio et al. | Apr 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 |
6260024 | Shkedy | Jul 2001 | B1 |
6275812 | Haq et al. | Aug 2001 | B1 |
6289260 | Bradley et al. | Sep 2001 | B1 |
6289370 | Panarello et al. | Sep 2001 | B1 |
6292784 | Martin 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 |
6397246 | Wolfe | May 2002 | B1 |
6405173 | Honarvar et al. | Jun 2002 | B1 |
6424947 | Tsuria et al. | Jul 2002 | B1 |
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 |
6484150 | Bllnn 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 |
6549891 | Rauber et al. | Apr 2003 | B1 |
6567786 | Bibelnieks 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 |
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 |
6622127 | Klots et al. | Sep 2003 | B1 |
6654726 | Hanzek | Nov 2003 | B1 |
6697964 | Dodrill et al. | Feb 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 |
6792459 | Elnozahy et al. | Sep 2004 | B2 |
6862572 | de Sylva | Mar 2005 | B1 |
6873970 | Showghi et al. | Mar 2005 | B2 |
6879965 | Fung et al. | Apr 2005 | B2 |
6904455 | Yen | Jun 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 |
7085729 | Kennedy et al. | Aug 2006 | B1 |
7139637 | Waddington et al. | Nov 2006 | B1 |
7139721 | Borders et al. | Nov 2006 | B2 |
7177825 | Borders 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 |
7308423 | Woodward et al. | Dec 2007 | B1 |
7346564 | Kirklin et al. | Mar 2008 | B1 |
7370005 | Ham et al. | May 2008 | B1 |
7383233 | Singh et al. | Jun 2008 | B1 |
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 |
20010047285 | Borders et al. | Nov 2001 | A1 |
20010047310 | Russell | Nov 2001 | A1 |
20010049619 | Powell et al. | Dec 2001 | A1 |
20010049672 | Moore | 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 | Nobilio | 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 |
20070016463 | Borders et al. | Jan 2007 | A1 |
20071074144 | Borders et al. | Feb 2007 | |
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 |
20070250572 | Paila et al. | Oct 2007 | A1 |
20080015959 | Kruglikov et al. | Jan 2008 | A1 |
20090063439 | Rauser et al. | Mar 2009 | A1 |
20090094085 | Kantarjiev et al. | Apr 2009 | A1 |
20090150534 | Miller et al. | Jun 2009 | A1 |
20090164570 | Palla et al. | Jun 2009 | A1 |
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 |
Number | Date | Country | |
---|---|---|---|
Parent | 09750385 | Dec 2000 | US |
Child | 11818010 | US |