Computer-implemented system and method for efficient allocation of orders based on system parameters

Abstract

The present application discloses a computer-implemented system for efficiently allocating orders based on system parameters. The system may include a memory storing instructions; and at least one processor for executing the instructions. The instructions may include: aggregating one or more orders, the order containing one or more quantities of multiple items; allocating a subset of the items to batches, wherein the items are allocated to one or more batches; determining one or more parameters of a transportation system for the batch; determining at least one of a location or orientation of the item in the transportation system based on the parameters of the transportation system; and transmitting the parameters of the transportation system to a user device for display.

Description

Technical Field

[0001] The present disclosure generally relates to computerized methods and systems for allocating customer orders based on system configuration and limitations. In particular, embodiments of the present disclosure relate to a creative and unconventional system that breaks down a set of orders into individual items for pickup while taking into account system configurations such as the location of the items and limitations such as weight limits of the shipping system. Background Art

[0002] With the popularity of the Internet, online shopping has become one of the main avenues of commerce. Consumers and businesses are purchasing goods from online vendors more frequently than ever before, and the number of transactions and sales revenue is expected to grow at an astonishing rate year after year. As the scope and volume of e-commerce continue to grow, the many different products offered online and the average number of purchases in a given time have increased exponentially. Therefore, it has become very important to optimize the order fulfillment process, which begins when a customer submits an order and ends when the order is delivered to the customer.

[0003] For the different processes involved, such as picking up the items included in the order, packaging the items, and shipping, various solutions for picking up items already exist to make the process more efficient. However, existing solutions are primitive because they control the picking tasks based on individual orders. That is, under existing solutions, orders are assigned to workers who pick up items until every item in each order is picked up, no matter where the items may be located in the warehouse. Given the number of items and the typical size of large warehouses, existing solutions may not fully utilize the workers' time and energy. This is especially true when the different items in the order are far apart in the warehouse. In addition, in existing solutions, workers may not be aware of certain limitations of the entire system, for example, a conveyor belt may have a certain weight limit. It is almost impossible for a single worker to take these limitations into account because these limitations must be calculated based on all the products transported at a given point in time, and existing systems cannot take these limitations into account.

[0004] Therefore, there is a need for improved systems and methods for managing orders and assigning them to workers in a controlled manner so that the orders are processed efficiently. Summary of the invention

[0005] One aspect of the present disclosure is directed to a computer-implemented system for efficiently allocating orders based on system parameters. The system may include a memory storing instructions; and at least one processor for executing the instructions. The instructions may include: aggregating one or more orders, the orders including a plurality of items in one or more quantities; allocating a subset of the items to batches, wherein the items are allocated to one or more batches; determining one or more parameters of a transportation system for the batches; determining at least one of a location or orientation of the items in the transportation system based on the parameters of the transportation system; and transmitting the parameters of the transportation system to a user device for display.

[0006] Yet another aspect of the present disclosure is directed to a computer-implemented method for efficiently allocating orders based on system parameters. The method may include: aggregating one or more orders, the orders including a plurality of items in one or more quantities; allocating a subset of the items to batches, wherein the items are allocated to one or more batches; determining one or more parameters of a transportation system for the batches; determining at least one of a location or orientation of the items in the transportation system based on the parameters of the transportation system; and transmitting the parameters of the transportation system to a user device for display.

[0007] In addition, another aspect of the present disclosure is directed to a computer-implemented system for efficiently allocating orders based on system parameters. The system may include a memory storing instructions; and at least one processor for executing instructions. The instructions may include: aggregating one or more orders, the orders including a plurality of items in one or more quantities; allocating a first subset of the items to a first batch, wherein the items are allocated to one or more batches; determining one or more parameters of a transportation system for the first batch; based on the parameters of the transportation system, determining at least one of a position or an orientation of the first subset of the items in the transportation system; transmitting the parameters of the transportation system to a user device for display; receiving a first item identifier associated with a first item in the first subset of the items from the user device; and, in response to the first item identifier, transmitting at least one of a position or an orientation in which the first item is placed in the transportation system to the user device for display.

[0008] Other systems, methods, and computer-readable media are also discussed herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1A A schematic block diagram of an exemplary embodiment of a network including a computerized system for enabling communications for shipping, transportation, and logistics operations according to an embodiment of the present disclosure is shown.

[0010] Figure 1BAn example of a search result page (SRP) according to an embodiment of the present disclosure is shown, which includes one or more search results that satisfy a search request and an interactive user interface element.

[0011] Figure 1C An example of a single display page (SDP) including a product and information about the product and an interactive user interface element according to an embodiment of the present disclosure is shown.

[0012] Figure 1D An example of a shopping cart page according to an embodiment of the present disclosure is shown, which includes items in a virtual shopping cart and interactive user interface elements.

[0013] Figure 1E An example of an order page according to an embodiment of the present disclosure is shown, the page including items from a virtual shopping cart and information about purchase and shipment, as well as interactive user interface elements.

[0014] Figure 2 is a schematic diagram of an exemplary fulfillment center for utilizing the computerized system of the present disclosure according to an embodiment of the present disclosure.

[0015] Figure 3A is a schematic diagram of an exemplary picking area according to an embodiment of the present disclosure.

[0016] Figure 3B is a schematic diagram of the picking operation of a worker in a picking area according to an embodiment of the present disclosure.

[0017] Figure 4 is a schematic block diagram illustrating an exemplary embodiment of a networked environment including a computerized system for efficiently allocating and distributing orders to multiple pickers according to an embodiment of the present disclosure.

[0018] Figure 5 is a diagram of an exemplary order allocation process according to an embodiment of the present disclosure.

[0019] Figure 6 is a schematic block diagram showing an exemplary user equipment according to an embodiment of the present disclosure.

[0020] Figure 7 is a flow chart of an exemplary computerized process for efficiently allocating orders based on system parameters according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] The following detailed description is made with reference to the accompanying drawings. In the drawings and the following description, the same reference numerals are used to refer to the same or similar parts as much as possible. Although several illustrative embodiments are described herein, modifications, improvements and other implementations are possible. For example, the components and steps shown in the drawings can be replaced, added or modified, and the exemplary methods described in the present disclosure can be modified by replacing, reordering, removing or adding the steps of the methods of the present disclosure. Therefore, the following detailed description is not limited to the disclosed embodiments and examples. On the contrary, the proper scope of protection of the present invention is defined by the appended claims.

[0022] Embodiments of the present disclosure are directed to computer-implemented systems and methods for allocating orders based on system parameters by breaking down orders into individual items and assigning various combinations of the items to workers while taking into account system configurations (such as item locations) and constraints (such as the weight capacity of a transportation system).

[0023] refer to Figure 1A , a schematic block diagram 100 is shown illustrating an exemplary embodiment of a system including a computerized system for communications that allows for shipping, transportation, and logistics operations. Figure 1A As shown, system 100 may include various systems, each of which may be connected to each other via one or more networks. These systems may also be connected to each other via direct connections (eg, using cables). The systems shown include a shipment authority technology (SAT) system 101, an external front-end system 103, an internal front-end system 105, a transportation system 107, mobile devices 107A, 107B and 107C, a seller portal 109, a shipment and order tracking (SOT) system 111, a fulfillment optimization (FO) system 113, a fulfillment messaging gateway (FMG) 115, a supply chain management (SCM) system 117, a labor management system 119, mobile devices 119A, 119B and 119C (shown as being inside a fulfillment center (FC) 200), third-party fulfillment systems 121A, 121B and 121C, a fulfillment center authorization (FC Auth) system 123 and a labor management system (LMS) system 125.

[0024] In some embodiments, the SAT system 101 can be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 can determine whether an order has exceeded its promised delivery date (Promised Delivery Date, PDD), and can take appropriate actions, including initiating a new order, re-shipping items in undelivered orders, canceling undelivered orders, initiating contact with ordering customers, etc. The SAT system 101 can also monitor other data, including output (such as the number of packages shipped in a specific time period) and input (such as the number of empty cardboard boxes received for shipment). The SAT system 101 can also act as a gateway between different devices in the system 100, allowing communication between devices (such as the external front-end system 103 and the FO system 113) (for example, using storage and forwarding or other technologies).

[0025] In some embodiments, the external front-end system 103 can be implemented as a computer system that allows external users to interact with one or more systems in the system 100. For example, in an embodiment where the system 100 is capable of implementing a system display to allow a user to place an order for an item, the external front-end system 103 can be implemented as a network server that receives search requests, displays the item page, and requests payment information. For example, the external front-end system 103 can be implemented as one or more computers that can run software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc. In other embodiments, the external front-end system 103 can run customized network server software that is designed to receive and process requests from external devices (e.g., mobile device 102A or computer 102B), obtain information from databases and other data stores based on these requests, and provide responses to received requests based on the obtained information.

[0026] In some embodiments, the external front-end system 103 may include one or more of a network cache system, a database, a search system, or a payment system. On the one hand, the external front-end system 103 may include one or more of these systems, and on the other hand, the external front-end system 103 may include an interface (e.g., server-to-server, database-to-database, or other network connection) for connecting to one or more of these systems.

[0027] like Figure 1B , Figure 1C , Figure 1D and Figure 1EA set of exemplary steps shown in FIG. 1 will help describe some operations of the external front-end system 103. The external front-end system 103 may receive information from systems or devices in the system 100 for presentation and / or display. For example, the external front-end system 103 may host or provide one or more web pages, including a search result page (SRP) (e.g., Figure 1B ), Single Detail Page (SDP) (for example, Figure 1C ), shopping cart pages (e.g. Figure 1D ) or order pages (e.g. Figure 1E ). A user device (e.g., using mobile device 102A or computer 102B) can navigate to the external front-end system 103 and request a search by entering information in a search box. The external front-end system 103 can request information from one or more systems in the system 100. For example, the external front-end system 103 can request information that satisfies the search request from the FO system 113. The external front-end system 103 can also request and receive (from the FO system 113) a Promised Delivery Date (or "PDD") for each product included in the search results. In some embodiments, the PDD may represent an estimate of when a package containing the product will arrive at the user's desired location, or an estimate of the date on which the product is guaranteed to be delivered at the user's desired location if ordered within a specific time period, such as before the end of the day (11:59 p.m.). (PDD will be discussed further below with respect to the FO system 113.)

[0028] The external headend system 103 can prepare an SRP based on this information (e.g., Figure 1B ). The SRP may include information that satisfies the search request. For example, this may include pictures of products that satisfy the search request. The SRP may also include the corresponding price of each product, or information about advanced delivery options, PDD, weight, size, quotes, discounts, etc. for each product. The external front-end system 103 may send the SRP (e.g., via a network) to the user device that issued the request.

[0029] The user device may then select a product from the SRP (e.g., by clicking or tapping a user interface or using another input device) to select a product represented on the SRP. The user device may formulate a request for information about the selected product and send it to the external front-end system 103. In response, the external front-end system 103 may request information related to the selected product. For example, the information may include information other than that provided for the product on the corresponding SRP. For example, this may include a shelf life, country of origin, weight, dimensions, number of items in a package, handling instructions, or other information about the product. The information may also include recommendations for similar products (e.g., based on big data and / or machine learning analysis of customers who have purchased the product and at least one other product), answers to frequently asked questions, customer reviews, manufacturer information, pictures, etc.

[0030] The external front-end system 103 can prepare an SDP (single product details page) based on the received product information (e.g., Figure 1C ). The SDP may also include other interactive elements, such as a "Buy Now" button, an "Add to Cart" button, a quantity field, an item picture, etc. The SDP may further include a list of sellers offering the product. The list may be sorted based on the price offered by each seller, so that the sellers offering the product at the lowest price may be listed at the top. The list may also be sorted based on the seller ranking, so that the highest ranked sellers may be listed at the top. The seller ranking may be developed based on a variety of factors, including, for example, the seller's past record of complying with the promised PDD. The external front-end system 103 may deliver the SDP to the requesting user device (e.g., via a network).

[0031] The requesting user device may receive the SDP listing the product information. After receiving the SDP, the user device may then interact with the SDP. For example, a user of the requesting user device may click a "Place in Cart" button on the SDP or otherwise interact with it. This will add the product to a shopping cart associated with the user. The user device may transmit a request to add the product to the shopping cart to the external front-end system 103.

[0032] The external front-end system 103 may generate a shopping cart page (e.g., Figure 1D). In some embodiments, the shopping cart page lists the products that the user has added to the virtual "shopping cart". The user device can request the shopping cart page by clicking on an icon on the SRP, SDP or other page or otherwise interacting with it. In some embodiments, the shopping cart page can list all the products that the user has added to the shopping cart, as well as information about the products in the shopping cart, such as the quantity of each product, the price of each product, the price of each product based on the relevant quantity, information about the PDD, the delivery method, the shipping cost, the user interface elements for modifying the products in the shopping cart (e.g., deleting or modifying the quantity), the options for ordering additional products or setting up periodic delivery of products, the options for setting interest payments, the user interface elements for proceeding to purchase, etc. The user can click on the user interface element (e.g., a button displayed as "Buy Now") on the user device or interact with it in other ways to initiate the purchase of the products in the shopping cart. Once this is done, the user device can transmit the request to initiate the purchase to the external front-end system 103.

[0033] The external front-end system 103 may generate an order page (eg, Figure 1E ). In some embodiments, the "Order" page again lists the items in the shopping cart and requests entry of payment and shipping information. For example, the "Order" page may include a section for requesting information about the purchaser of the items in the shopping cart (e.g., name, address, email address, phone number), information about the recipient (e.g., name, address, phone number, delivery information), shipping information (e.g., speed / method of delivery and / or pickup), payment information (e.g., credit card, bank transfer, check, stored credit), a user interface element to request a cash receipt (e.g., for tax purposes), etc. The external front-end system 103 may send the "Order" page to the user device.

[0034] The user device may enter information on the "Order" page and then click or otherwise interact with a user interface element that sends the information to the external front-end system 103. The external front-end system 103 may then send the information to different systems in the system 100 to enable the creation and processing of a new order using the products in the shopping cart.

[0035] In some embodiments, external front-end system 103 may be further configured to allow sellers to transmit and receive information related to an order.

[0036] In some embodiments, the internal front-end system 105 can be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases the system 100) to interact with one or more systems in the system 100. For example, in an embodiment where the network 101 is capable of system presentation to allow a user to place an order for an item, the internal front-end system 105 can be implemented as a network server that enables internal users to view diagnostic and statistical information about the order, modify item information, or view statistical information related to the order. For example, the internal front-end system 105 can be implemented as one or more computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc. In other embodiments, the internal front-end system 105 can run customized network server software that is designed to receive and process requests from the systems or devices shown in the system 100 (and other devices not shown), obtain information from databases and other data stores based on the request, and provide responses to the received requests based on the information obtained.

[0037] In some embodiments, the internal front-end system 105 may include one or more of a network cache system, a database, a search system, a payment system, an analysis system, an order monitoring system, etc. In one aspect, the internal front-end system 105 may include one or more of these systems, while in another aspect, the internal front-end system 105 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

[0038] In some embodiments, the transport system 107 can be implemented as a computer system that enables communication between the systems or devices in the system 100 and the mobile devices 107A-107C. In some embodiments, the transport system 107 can receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, etc.). For example, in some embodiments, the mobile devices 107A-107C can include devices operated by delivery personnel. Delivery workers (who can be fixed employees, temporary workers, or shift employees) can use mobile devices 107A-107C to deliver packages containing user-ordered products. For example, in order to deliver a package, a delivery worker can receive a notification on a mobile device indicating which package to deliver and where to deliver it. After arriving at the delivery location, the delivery person can locate the package (e.g., in the back of a truck or in a package box), use a mobile device to scan or otherwise obtain data related to an identifier on the package (e.g., a barcode, an image, a text string, an RFID tag, etc.), and then deliver the package (e.g., by placing it at the front door, handing it to a security guard, handing it to the recipient, etc.). In some embodiments, the delivery worker can use a mobile device to take a photo of the package and / or can obtain a signature. The mobile device can send information to the transportation system 107, which includes information about the delivery, including, for example, the time, date, GPS location, photo, an identifier associated with the delivery worker, an identifier associated with the mobile device, etc. The transportation system 107 can store this information in a database (not shown) for access by other systems in the system 100. In some embodiments, the transportation system 107 can use this information to prepare tracking data and send it to other systems indicating the location of a particular package.

[0039] In some embodiments, certain users may use one type of mobile device (e.g., a permanent employee may use a specialized PDA with customized hardware such as a bar code scanner, stylus, and other devices) while other users may use other types of mobile devices (e.g., temporary or shift employees may use off-the-shelf mobile phones and / or smartphones).

[0040] In some embodiments, the transportation system 107 may associate a user with each device. For example, the transportation system 107 may store an association between a user (e.g., represented by a user identifier, an employee identifier, or a phone number) and a mobile device (e.g., represented by an International Mobile Equipment Identity (IMEI), an International Mobile Subscription Identifier (IMSI), a phone number, a Universal Unique Identifier (UUID), or a Globally Unique Identifier (GUID)). The transportation system 107 may use the association, in conjunction with data received at the time of delivery, to analyze the data stored in the database to determine the location of the worker, the efficiency of the worker, or the speed of the worker, among other situations.

[0041] In some embodiments, seller portal 109 may be implemented as a computer system that enables sellers or other external entities to electronically communicate with one or more systems in system 100. For example, a seller may utilize a computer system (not shown) to upload or provide product information, order information, contact information, etc. for products that the seller wishes to sell through system 100 using seller portal 109.

[0042] In some embodiments, the shipping and order tracking system 111 may be implemented as a computer system that receives, stores, and forwards information about the location of packages containing products ordered by customers (e.g., by users using devices 102A-102B). In some embodiments, the shipping and order tracking system 111 may request or store information from a network server (not shown) operated by a shipping company that delivers packages containing products ordered by customers.

[0043] In some embodiments, the shipping and order tracking system 111 may request and store information from the systems shown in the system 100. For example, the shipping and order tracking system 111 may request information from the transportation system 107. As described above, the transportation system 107 may receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, etc.) associated with one or more users (e.g., delivery workers) or vehicles (e.g., delivery trucks). In some embodiments, the shipping and order tracking system 111 may also request information from a workforce management system (WMS) 119 to determine the location of various products within a fulfillment center (e.g., fulfillment center 200). The shipping and order tracking system 111 may request data from one or more of the transportation system 107 or the WMS 119, process it, and present it to the device (e.g., user devices 102A and 102B) upon request.

[0044] In some embodiments, fulfillment optimization (FO) system 113 may be implemented as a computer system that stores customer order information from other systems (e.g., external front-end system 103 and / or shipping and order tracking system 111). FO system 113 may also store information describing where specific items are held or stored. For example, certain items may be stored in only one fulfillment center, while certain other items may be stored in multiple fulfillment centers. In other embodiments, certain fulfillment centers may be designed to store only a specific set of items (e.g., fresh produce or frozen products). FO system 113 stores this information as well as associated information (e.g., quantity, size, receipt date, expiration date, etc.).

[0045] The FO system 113 may also calculate a corresponding PDD (promised delivery date) for each product. In some embodiments, the PDD may be based on one or more factors. For example, the FO system 113 may calculate the PDD of a product based on past demand for the product (e.g., the number of times the product has been ordered over a period of time), expected demand for the product (e.g., how many customers are expected to order the product in the future), past demand across the network indicating how many products have been ordered over a period of time, expected demand across the network indicating how many products are expected to be ordered in the upcoming period of time, one or more counts of the product stored in each fulfillment center 200 (which stores each product), expected orders or current orders for the product, etc.

[0046] In some embodiments, the FO system 113 may determine the PDD for each product periodically (e.g., every hour) and store it in a database for retrieval or sending to other systems (e.g., external front-end system 103, SAT system 101, shipping and order tracking system 111). In other embodiments, the FO system 113 may receive electronic requests from one or more systems (e.g., external front-end system 103, SAT system 101, shipping and order tracking system 111) and calculate the PDD on demand.

[0047] In some embodiments, the fulfillment messaging gateway (FMG) 115 can be implemented as a computer system that receives requests or responses in one format or protocol from one or more systems in the system 100 (e.g., the FO system 113), converts them into another format or protocol, and then forwards them in the converted format or protocol to other systems, such as the WMS 119 or the third-party fulfillment system 121A, 121B, or 121C, or vice versa.

[0048] In some embodiments, supply chain management (SCM) system 117 may be implemented as a computer system that performs forecasting functions. For example, SCM system 117 may forecast the level of demand for a particular product based on, for example, past demand for the product, expected demand for the product, past network-wide demand, expected network-wide demand, product counts stored in each fulfillment center 200, expected or current orders for each product, etc. In response to the forecasted level and the quantity of each product in all fulfillment centers, SCM system 117 may generate one or more purchase orders to purchase and stock a sufficient quantity of the product to meet the forecasted demand for the particular product.

[0049] In some embodiments, a workforce management system (WMS) 119 may be implemented as a computer system that monitors workflow. For example, WMS 119 may receive event data indicating discrete events from various devices (e.g., devices 107A-107C or 119A-119C). For example, WMS 119 may receive event data indicating that a package was scanned using one of these devices. As described below with respect to fulfillment center 200 and Figure 2As discussed above, during the fulfillment process, a package identifier (e.g., a barcode or RFID tag data) may be scanned or read by a machine (e.g., an automatic or handheld barcode scanner, an RFID reader, a high-speed camera, a device such as a tablet 119A, a mobile device / PDA 119B, a computer 119C, etc.) at a particular stage. The WMS 119 may store each event indicating a scan or read of a package identifier in a corresponding database (not shown) along with the package identifier, time, date, location, user identifier, or other information, and may provide this information to other systems (e.g., the shipping and order tracking system 111).

[0050] In some embodiments, the WMS 119 may store information associating one or more devices (e.g., devices 107A-107C or 119A-119C) with one or more users associated with the system 100. For example, in some cases, a user (such as a part-time or full-time employee) may be associated with a mobile device if the user owns the mobile device (e.g., the mobile device is a smartphone). In other cases, a user may be associated with a mobile device if the user temporarily takes custody of the mobile device (e.g., the user signs the mobile device out at the beginning of the day, uses it during the day, and returns it at the end of the day).

[0051] In some embodiments, WMS 119 may maintain a work log for each user associated with system 100. For example, WMS 119 may store information associated with each employee, including any assigned processes (e.g., truck unloading, picking from a picking area, rebin wall work, packaging items), user identifiers, locations (e.g., floors or zones in fulfillment center 200), the number of units the employee has moved through the system (e.g., number of items picked, number of items packaged), identifiers associated with equipment (e.g., equipment 119A-119C), etc. In some embodiments, WMS 119 may receive check-in and check-out information from a timekeeping system (such as a timekeeping system running on equipment 119A-119C).

[0052] In some embodiments, third party fulfillment (3PL) systems 121A-121C represent computer systems associated with third party suppliers of logistics and products. For example, although some products are stored in fulfillment center 200 (as described below with reference to Figure 2), but other products may be stored off-site, may be produced on demand, or may not be stored in fulfillment center 200 for other reasons. 3PL systems 121A-121C may be configured to receive orders from FO system 113 (e.g., via FMG 115) and may provide products and / or services (e.g., delivery or installation) directly to customers. In some embodiments, one or more of 3PL systems 121A-121C may be part of system 100, while in other embodiments, one or more of 3PL systems 121A-121C may be external to system 100 (e.g., owned or operated by a third-party provider).

[0053] In some embodiments, fulfillment center authorization system (FC Auth) 123 can be implemented as a computer system with multiple functions. For example, in some embodiments, FC Auth 123 can act as a single sign-on (SSO) service for one or more other systems in system 100. For example, FC Auth 123 can enable a user to log in through internal front-end system 105, determine that the user has similar permissions to access resources in shipping and order tracking system 111, and enable the user to access those permissions without a second login process. In other embodiments, FC Auth 123 can enable users (e.g., employees) to associate themselves with specific tasks. For example, some employees may not have electronic devices (e.g., devices 119A-119C), but may move between tasks within fulfillment center 200 and between areas during the day. FC Auth 123 can be configured to enable these employees to indicate the tasks they are performing and the areas they are in at different times of the day.

[0054] In some embodiments, a labor management system (LMS) 125 may be implemented as a computer system that stores attendance and overtime information for employees (including full-time and part-time employees). For example, the LMS 125 may receive information from FC Auth 123, WMA 119, devices 119A-119C, transportation system 107, and / or devices 107A-107C.

[0055] Figure 1A The specific configurations shown are examples only. Figure 1AThe FCAuth system 123 connected to the FO system 113 is shown, but not all embodiments require this particular configuration. In fact, in some embodiments, the systems in the system 100 can be connected to each other through one or more public or private networks, including the Internet, an intranet, a WAN (wide area network), a MAN (metropolitan area network), a wireless network compliant with the IEEE 802.11a / b / g / n standard, a leased line, etc. In some embodiments, one or more systems in the system 100 can be implemented as one or more virtual servers implemented in a data center, a server farm, etc.

[0056] Figure 2 A fulfillment center 200 is shown. A fulfillment center 200 is an example of a physical location where items are stored to be shipped to customers after being ordered. A fulfillment center (FC) 200 may be divided into a plurality of zones, each having a Figure 2 In some embodiments, these "zones" can be thought of as virtual divisions between different stages of the process of receiving items, storing items, picking up items, and delivering items. Figure 2 The “areas” are shown in FIG. 1 , other divisions of the areas are possible, and in some embodiments, may be omitted, repeated, or modified. Figure 2 The area in.

[0057] Inbound area 203 represents the area in FC200 where you want to use Figure 1A A seller selling a product receives items from system 100. For example, the seller may deliver items 202A and 202B using truck 201. Item 202A may represent a single item that is large enough to occupy its own shipping pallet, while item 202B may represent a group of items that are stacked together on the same pallet to save space.

[0058] The staff receives the items in the inbound area 203 and can optionally use a computer system (not shown) to check the damage and correctness of the items. For example, the staff can use a computer system to compare the quantity of items 202A and 202B with the order quantity of the items. If the quantity does not match, the staff can reject one or more of the items 202A or 202B. If the quantity matches, the staff can move the items to the buffer 205 (using, for example, a trolley, a hand truck, a forklift, or manually). The buffer 205 can be, for example, a temporary storage area for items that are not currently needed in the picking area because the high number of the items in the picking area is sufficient to meet the predicted demand. In some embodiments, the forklift 206 operates to move the items around the buffer 205 and between the inbound area 203 and the unloading area 207. If the items 202A or 202B are needed in the picking area (for example, due to predicted demand), the forklift can move the items 202A or 202B to the unloading area 207.

[0059] The drop-off area 207 may be an area in the FC 200 for storing items before they are moved to the picking area 209. A worker assigned to a picking task (a "picker") may approach the items 202A and 202B in the picking area, scan the barcode of the picking area using a mobile device (e.g., device 119B), and scan the barcodes associated with the items 202A and 202B. The picker may then take the items to the picking area 209 (e.g., by placing the items on a cart or carrying the items).

[0060] The picking area 209 may be an area in the FC 200 where the items 208 are stored on the storage unit 210. In some embodiments, the storage unit 210 may include one or more of physical shelves, bookcases, boxes, bags, refrigerators, freezers, cold storage, etc. In some embodiments, the picking area 209 may be organized into multiple layers. In some embodiments, workers or machines may move items into the picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyor belts, carts, hand trucks, dollies, automatic robots or equipment, or manually. For example, a picker may place the items 202A and 202B on a hand truck or cart in the drop-off area 207 and walk to load the items 202A and 202B to the picking area 209.

[0061] The picker can receive instructions to place (or "stack") an item at a specific point in the picking area 209 (e.g., a specific space on the storage unit 210). For example, the picker can use a mobile device (e.g., device 119B) to scan the item 202A. The device can indicate where the picker should stack the item 202A, for example, using a system indicating aisles, shelves, and locations. The device can then prompt the picker to scan a bar code at the location before stacking the item 202A at that location. The device can send the data (e.g., via a wireless network) to a computer system (e.g., Figure 1A 119 in WMS 119) to indicate that a user using device 119B has stacked item 202A at that location.

[0062] Once the user places an order, the picker can receive instructions on the device 119B to take one or more items 208 from the storage unit 210. The picker can take the item 208, scan the barcode on the item 208, and place the item 208 on the conveying mechanism 214. In some embodiments, although the conveying mechanism 214 is shown as a sliding device, the conveying mechanism can be implemented as one or more of a conveyor belt, an elevator, a cart, a forklift, a hand truck, a dolly, a cart, etc. Then, the item 208 can reach the packaging area 211.

[0063] The packing area 211 can be an area in the FC 200 for receiving items from the picking area 209 and packing the items into boxes or bags for final delivery to customers. In the packing area 211, the staff member assigned to receive the items ("merge staff member") will receive the items 208 from the picking area 209 and determine the order corresponding to the items 208. For example, the merge staff member can use a device (such as a computer 119C) to scan the barcode on the item 208. The computer 119C can visually indicate which order the item 208 is associated with. This can include, for example, a space or "cell" on the wall 216 corresponding to the order. Once the order is completed (for example, because the cell contains all the items for the order), the merge staff member can indicate to the packing staff member (or "packing staff") that the order is completed. The packing staff can take the items from the cell and put the items in a box or bag for shipment. Then, the packing staff can send the box or bag to the hub area 213 (for example, by forklift, cart, dolly, hand truck, conveyor belt, manually or in other ways).

[0064] Hub area 213 may be an area of ​​FC 200 that receives all boxes or bags ("parcels") from packaging area 211. Personnel and / or machines in hub area 213 may pick up parcels 218 and determine which portion of the delivery area each parcel should go to, and route the parcels to the appropriate camp area 215. For example, if the delivery area has two smaller sub-areas, the parcels will go to one of the two camp areas 215. In some embodiments, personnel or machines may scan the parcels (e.g., using one of devices 119A-119C) to determine the final destination of the parcels. Routing the parcels to the camp area 215 may include, for example, determining (e.g., based on a zip code) a portion of the geographic area to which the parcel is destined, and determining a camp area 215 associated with that portion of the geographic area.

[0065] In some embodiments, the camp area 215 may include one or more buildings, one or more physical spaces, or one or more areas where packages are received from the hub area 213 and sorted into routes and / or sub-routes. In some embodiments, the camp area 215 is physically separated from the FC 200, while in other embodiments, the camp area 215 may form part of the FC 200.

[0066] Workers and / or machines in the camp area 215 may determine which route and / or sub-route the package 220 should be associated with (e.g., based on a comparison of the destination with existing routes and / or sub-routes, a calculation of the workload for each route and / or sub-route, the real time moment, the shipping method, the cost of shipping the package 220, the PDD associated with the items in the package 220, etc.). In some embodiments, workers or machines may scan the package (e.g., using one of the devices 119A-119C) to determine the final destination of the package. Once the package 220 is assigned to a particular route and / or sub-route, the workers and / or machines may move the package 220 to be shipped. In the exemplary embodiment, Figure 2 In the embodiment of the present invention, the camp area 215 includes trucks 222, cars 226, and delivery workers 224A and 224B. In some embodiments, the truck 222 can be driven by the delivery worker 224A, where the delivery worker 224A is a full-time employee who delivers packages for the FC 200, and the truck 222 is owned, leased, or operated by the same company that owns, leases, or operates the FC 200. In some embodiments, the car 226 can be driven by the delivery worker 224B, where the delivery worker 224B is a "flexible" or temporary worker based on delivery needs (e.g., seasonally). The car 226 can be owned, leased, or operated by the delivery worker 224B.

[0067] Figure 3A is a schematic diagram of an exemplary picking zone 300, which may function in conjunction with Figure 2 The picking area 209 has similar functions. Figure 3A As shown, the picking area 300 may be in a warehouse such as FC 200. In the picking area 300, items 320 are stored in a storage unit 310 that may include a location identifier 311. In some embodiments, the storage unit 310 may be a physical shelf, a bookshelf, a box, a bag, a refrigerator, a freezer, a cold storage, etc. In some embodiments, the items 320 may be products for sale, and the items 320 may be picked by a user (e.g., a picker) or an automatic machine when a customer places an order for the items 320 via a website hosted by the external front-end system 103.

[0068] In some embodiments, a storage unit 310 (such as a shelf) may have a location identifier 311 attached thereto. The location identifier 311 may be a unique address of a storage unit 310 at a specific location within the picking area 300. In some embodiments, the location identifier 311 may correspond to a specific item that is shelved at that location. However, in other embodiments, the location identifier 311 may indicate multiple items that are shelved together or in close proximity. The location identifier 311 may be an item barcode, an RFID tag, or a matrix barcode, such as a quick response (QR) code. A camera or scanner in a user device (e.g., mobile device 119B) may scan the location identifier 311 using an input device (e.g., an imaging device, including a camera or a scanner). The scan information may be sent to the WMS 119. Based on the scan information, the WMS 119 may determine and confirm whether the picker is at the location specified by the WMS 119.

[0069] A batch may include one or more items. Pickers may pick items contained in a specified batch in the picking area 300 until every item in the batch is picked. Pickers may move on foot in the picking area 300 (e.g., a warehouse). In some embodiments, pickers may use other devices (such as scooters, robots, and / or vehicles) to assist in movement.

[0070] In some embodiments, a user device (e.g., mobile device 119B) can assist a picker in finding a designated location. In some embodiments, the user device can display a map with navigation to the picker. For example, the user device can notify the picker to turn left when arriving at a certain location. In some embodiments, the user device can provide a signal, including but not limited to a map, sound, vibration, or text message, to help the picker find the designated location.

[0071] Figure 3B is Figure 3ASchematic diagram of the picking operation of a worker (i.e., picker 350) in the picking area 300 shown. In some embodiments, the item 320 may have an item identifier 321 attached to the item 320. However, in other embodiments, the item identifier 321 may not be attached to the item 320, but may be located near the item 320. The item identifier 321 may include one or more of an item barcode, an RFID tag, a matrix barcode (e.g., a Quick Response (QR) code), and the like.

[0072] A camera or scanner in a user device (e.g., mobile device 119B) can scan the item identifier 321. The scanned information can be transmitted to the WMS 119 via a wireless or wired network. Based on the received information, the WMS 119 can confirm whether the scanned item identifier 250 matches the item identifier information stored in the WMS 119. When the WMS 119 confirms that it matches, the mobile device 119B can display instructions to the picker 350 to pick the item 320 and place it in the container 330. The picker 350 can continue the picking operation until the last item in the batch is picked.

[0073] In some embodiments, the container 330 may have a container identifier 331 attached to the container 330. The container 330 may be configured as any holding means for holding one or more items 320, such as a box, a tote, a bag, etc. In some embodiments, the container 330 may be a compartment in an automatic picker. The container identifier 331 may include one or more of an item barcode, an RFID tag, a matrix barcode (e.g., a quick response (QR) code). In some embodiments, there may be more than one type of container 330, and its size, shape, or material may vary. For example, one type of container 330 may be specifically configured for refrigerated items (e.g., produce, meat) and constructed of insulating materials. The types of containers available at FC 200 may vary, and a particular type of container available at one FC may not be available at another FC.

[0074] When picking items in a batch, the picker 350 can place the container 330 on the cart 340. In some embodiments, the cart 340 can have a cart identifier 341 attached to the cart 340. The cart 340 can be configured as any vehicle that can accommodate and transport one or more containers 330, such as a hand truck, a dolly, a drivable cart, etc. In some embodiments, the cart 340 can be driven by fuel or electricity. In some other embodiments, the cart 340 can be an automated robot designed to move between storage units 310 and pick items 320 using mechanical instruments such as articulated arms. The types of carts available in FC200 may be different, and a specific type of cart available in one FC may not be available in another FC.

[0075] After the last item in the batch is picked, the picker 350 can use the cart 340 to move the container 330 to the destination location (e.g., the packaging area 211 or the transportation mechanism 214) according to the instructions displayed in the mobile device 119B. For example, the picker 350 can scan the destination identifier by scanning the destination barcode and transmit the scanned information to the WMS 119. The WMS 119 can share the scanned information with other systems (such as the FO system 113 in the fulfillment center) via a wireless or wired network. The items being sent can be sent as described above. Figure 2 The described process is further processed and finally sent to the customer.

[0076] Figure 4 is a schematic block diagram illustrating an exemplary embodiment of a networked environment 400 that includes a computerized system for efficiently allocating orders and distributing them to multiple users. Environment 400 may include various systems, each of which may be connected to each other via one or more networks. The systems may also be connected to each other via direct connections (e.g., using cables). The systems shown include FO system 113, fulfillment messaging gateway (FMG) 115, workforce management system (WMS) 119, devices 119A-C, and users 350. Figure 4 The FMG 115, WMS 119, devices 119A-C and user 350 are shown with their Figure 1A and 3B The corresponding objects in correspondence, no further description is given here.

[0077] On the other hand, the FO system 113 and its component systems are shown in more detail. In some embodiments, the FO system 113 includes an order database 411, an inventory database 412, a FC configuration database 413, and a batch generator 414. In these embodiments, the components of the FO system 113 (i.e., the order database 411, the inventory database 412, the FC configuration database 413, and the batch generator 414) can be implemented as one or more functional units executed by one or more processors based on instructions stored in one or more memories. Alternatively, the components of the FO system 113 can be implemented as one or more computerized systems that communicate with each other via a network. In this embodiment, each of the one or more computer systems can include one or more processors, one or more memories (i.e., non-transitory computer-readable media), and one or more input / output (I / O) devices. In some embodiments, each of the one or more computer systems can take the form of a server, a general-purpose computer, a mainframe computer, a special-purpose computing device (such as a GPU), a laptop, or any combination of these computing devices.

[0078] In some embodiments, order database 411, inventory database 412, and FC configuration database 413 may each be implemented as one or more computer systems that collect, accumulate, and / or generate various data accumulated from the other systems described above. In other embodiments, order database 411, inventory database 412, and FC configuration database 413 may be implemented as a single system of databases, where information corresponding to each database is stored in different parts of its storage space (e.g., non-transitory computer-readable media). In some embodiments, the database may include a cloud-based database or a local database that includes one or more hard disk drives, one or more solid-state drives, or one or more non-transitory memories.

[0079] Regardless of the implementation, each component may be dedicated to storing order information, inventory information, and FC configuration information, respectively. More specifically, when a customer places an order for one or more items in inventory, the order database 411 may store order information from the external front-end system 103. For example, the order information may include an order identifier, a list of item identifiers 321 ordered by the customer, the order quantity of each item, customer contact information, payment information, etc.

[0080] Inventory database 412 may store Figure 2For example, the item information may include a list of item identifiers 321 grouped by FC, the inventory quantity of the corresponding items in the FC, the location identifier 311 of the corresponding items in each FC, the size, weight and handling instructions (e.g., fragile, perishable, refrigerated, frozen, etc.) of the corresponding items, etc. In some embodiments, when in a Figure 2 Item information may be updated or generated when items are received from vendors at the inbound area 203 shown to replenish items in the picking area 209, and when pickers pick items at the picking area 209 and ship them out to customers from the business area 215. Various aspects of item information may be frequently updated as various item identifiers are scanned at different locations within the FC 200, and the information is updated by, for example, Figure 1A The above-mentioned networked systems shown (e.g., transportation system 10, SOT system 111, WMS 119) are processed.

[0081] In addition, the FC configuration database 413 can store FC configuration information for each FC. For example, the FC configuration information can include FC-specific information, including the available types and quantities of carts 340, the available types and quantities of containers 330, the specifications of the transport system 214 (e.g., weight limits), the number of pickers 350 currently working at each FC, etc. In some embodiments, the FC configuration information can be collected and updated from time to time as new FCs are established or existing FCs are modified (e.g., more types and quantities of carts 340 or containers 330 are added), or new transport systems 214 are installed.

[0082] In some embodiments, the batch generator 414 may include one or more computing devices configured to aggregate order information from the order database 411 based on the item information and FC configuration information from the inventory database 412 and distribute it to the pickers 350 in batches. The function of the batch generator 414 is described below with reference to Figure 5 and Figure 7 Describe in more detail.

[0083] Figure 5 4 is a diagram of an exemplary order allocation process 500 that aggregates multiple orders into batches. In this example, order A 510A, order B 510B, order C 510C, and order D 510D can be aggregated by batch generator 414 and allocated into batch A 520A, batch B 520B, and batch C 520C. The number of orders and batches and the items shown therein are merely exemplary, and batch generator 414 can aggregate any number of orders with any combination of items and allocate them into any number of batches as desired.

[0084] exist Figure 5 , order A 510A may include item identifiers 321 corresponding to a quantity of five lemonades 501 and a quantity of three ketchup 502, respectively. Order B 510B may include item identifiers 321 corresponding to a quantity of one cheese powder 504. Order C 510C may include item identifiers 321 corresponding to a quantity of one desktop 504, a quantity of one toy tablet 505, a quantity of three hot sauces 506, and a quantity of two hot sauces 507, respectively. Order D 510D may include item identifiers 321 corresponding to a quantity of three toy cars 508 and a quantity of one toy truck 509, respectively.

[0085] The batch generator 414 may merge all of the item identifiers 321 and distribute them into batches AC 520A-C based on, for example, their respective location identifiers 311. For example, batch A 520A may include item identifiers 321 corresponding to location identifiers 311 associated with an area in the picking zone 209 where groceries are stored. Similarly, batch B 520B and batch C 520C may include item identifiers 321 corresponding to location identifiers 311 associated with areas in the picking zone 209 where electronic devices and toys are stored, respectively. In some embodiments, when orders AD 510A-D contain a certain amount (whether by volume, weight, or number) of items associated with a particular area and it exceeds a preset maximum batch size, the batch generator 414 may distribute the items into more than one batch. In some embodiments, each batch may be associated with a particular type of cart 340, and the maximum batch size may be determined based on the size of the available type of cart 340.

[0086] The batch generator 414 may further divide the item identifiers 321 assigned to a particular batch into one or more container groups. For example, the item identifiers 321 assigned to batch A 520A may be further divided into container group A 521A and container group B 521B; the item identifiers 321 assigned to batch C 520C may be divided into container group X 521X and container group Y 521Y. Alternatively, all item identifiers 321 of a batch (such as batch B 520B) may be assigned to a single container group (such as container group P 521P).

[0087] In some embodiments, the decision as to whether to split a batch of item identifiers 321 may be based on a number of factors associated with the items corresponding to the item identifiers 321, such as their total weight, total volume, individual shapes, etc. When a predetermined maximum container group size is reached, the batch generator 414 may compare these factors with the size and / or weight capacity of each container 330 and separate the item identifiers 321. For example, container group A 521A and container group B 521B may contain item identifiers 321 for lemonade 501 and chili 507; and item identifiers 321 for ketchup 502, hot sauce 506, and cheese powder 503, respectively. In other embodiments, when a batch is associated with so many items that the maximum number of container groups for a particular cart 340 associated with the batch is reached, the batch generator 414 may create a new batch and associate the excess item identifiers 321 with the new batch. As described above, the new batch may be similarly divided into one or more container groups.

[0088] Figure 6 1 shows a schematic block diagram of an exemplary user device, such as mobile device 119B. Mobile device 119B may include display 610, I / O device 620, processor 630, and memory 640. Figure 6 A mobile device 119B is shown, but one skilled in the art will appreciate that other devices (eg, tablet 119A or computer 119C) may be implemented in a similar manner.

[0089] The mobile device 119B may be configured with a memory that stores one or more operating systems that are executed by one or more processors to implement known operating system functions. For example, the operating system may include Microsoft Windows, Unix, Linux, Android, Apple Mac OS, iOS, or other types of operating systems. Therefore, the examples of the invention in the present disclosure can operate and implement functions with a computer system running any type of operating system. The mobile device 119B may also include communication software that provides communication with a network when executed by the processor, such as web browser software, tablet computer or smart handheld device networking software, etc.

[0090] The mobile device 119B may include a display 610. The display 610 may include, for example, a liquid crystal display (LCD), a light emitting diode screen (LED), an organic light emitting diode screen (OLED), a touch screen, and other known display devices. The display 610 may display various information. For example, the display 610 may display how many containers and carts are needed for a batch. The display 610 may display touchable or selectable options that may be selected by a user (e.g., a picker 350), and may receive the user's selection of the options through an I / O device 620 (such as a touch screen).

[0091] The I / O devices 620 may include one or more devices that allow the mobile device 119B to send and receive information to and from a user or another device. The I / O devices 620 may include various input / output devices, such as scanners, cameras, keyboards, mouse-type devices, gesture sensors, motion sensors, physical buttons, voice input devices, touch screens, etc. The I / O devices 620 may also include one or more communication modules (not shown) for sending and receiving information from other components in the WMS 119 (e.g., by establishing a wired or wireless connection between the mobile device 119B and the WMS 119).

[0092] The mobile device 119B may include at least one processor 630, which may be one or more known computing processors, such as those described with reference to FIG. Figure 4 The computing processor 630 depicted in the FO system 113 is shown. The processor 630 may execute various instructions stored in the mobile device 119B to perform various functions, such as processing information related to the item 320 or container 330 received from the I / O device 620.

[0093] The mobile device 119B may include a memory 640, which may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium. The memory 640 may store one or more programs 650. The programs 650 may include an operating system (not shown) that implements known operating system functions when executed by one or more processors. The disclosed examples may operate and implement functions with a computer system running any type of operating system.

[0094] The program 650 may be a workflow management program. The workflow management program may control the picking operation in the FC 200 by providing instructions to the staff. The program 650 may be executed by the processor 630 to implement a process related to fulfilling a batch, including but not limited to receiving an identifier associated with the batch from the mobile device 119B, displaying the determined container quantity through the mobile device 119B, receiving the container identifier from the user device, and picking up one or more items associated with the batch on the list.

[0095] Figure 7 700 is a flow chart of an exemplary computerized process 700 for efficient order allocation based on system parameters. In some embodiments, process 700 can be performed by FO system 113 using information from other networked systems as described above. More specifically, process 700 can be performed by batch generator 414 using information from order database 411, inventory database 412, and FC configuration database 413. In some embodiments, the scope of process 700 can be limited to a specific FC, where FO system 113 can perform process 700 using FC configuration information of the specific FC and item information associated with the specific FC (e.g., the quantity and location of items stored at the FC). Process 700 for other FCs can be performed by another FO system 113 associated with the corresponding FC, or by the same FO system 113 in a separate example of process 700. In addition, as customers place orders through external front-end system 103, FO system 113 can repeat steps 701-706 for each FC 200 multiple times within a given time period. The FO system 113 may also perform multiple instances of steps 701 - 706 for one or more order groups, where the instances may each be at a different step at any given moment.

[0096] In step 701, the batch generator 414 may aggregate one or more orders placed by a customer through the external front-end system 103. In some embodiments, aggregation refers to collecting order information from the order database 411 by order identifier as new order information is generated. When aggregating the orders, the batch generator 414 may also break down the orders to the product level, where the list of item identifiers 321 in each order information, together with the corresponding order quantity of each item, is combined into a master list of item identifiers 321. This order aggregation may continue until a predetermined event occurs, at which time the batch generator 414 may execute step 702 to assign the item identifiers 321 on the master list to one or more batches. The batch generator 414 may also update a set of order information associated with the item identifiers 321 in the master list to include one or more batches. In some embodiments, while the batch generator 414 processes the master list through steps 702-706, it may also start another aggregation for the next set of orders placed by the customer.

[0097] In some embodiments, the scheduled event may be time-based, where the batch generator 414 stops aggregating order information into the master list at predetermined intervals. In other embodiments, the scheduled event may be manually triggered by a user (e.g., a manager at the FC) via an I / O device connected to the FO system 113 by inputting a signal instructing the batch generator 414 to stop aggregating the current group of orders. Further, in other embodiments, the batch generator 414 may automatically trigger the scheduled event based on FC configuration information (e.g., the number of available pickers). For example, the batch generator 414 may trigger the scheduled event when the master list contains a sufficient number of items to create a sufficient number of batches to be assigned to each picker. In some embodiments, the batch generator 414 may trigger the scheduled event when the number of batches that can be created is greater than the number of available pickers by a predetermined factor (e.g., 1.5).

[0098] At step 702, the batch generator 414 may allocate the item identifiers 321 in the master list into one or more batches based on the corresponding item information. In some embodiments, the goal of such aggregation and allocation (i.e., reorganization) of items may be to more efficiently retrieve (i.e., pick) items from the picking area 209 than having each picker retrieve all items for an order regardless of where the items are stored. Assigning batches associated with specific areas in the picking area 209 to specific pickers may familiarize the pickers with the location of the items, increase their speed, and / or reduce the distance the pickers must move to complete a batch.

[0099] In some embodiments, the batch generator 414 may divide the item identifiers 321 based on their respective location identifiers 311, wherein the item identifiers 321 corresponding to items placed in close locations are grouped together based on their respective location identifiers 311. In some embodiments, the picking area 209 may be divided into one or more zones, each zone being assigned to one or more pickers, and the batch generator 414 may divide the item identifiers 321 based on the location of the corresponding location identifiers 311 within the zone. As described above, in some embodiments, the batch generator 414 may further divide the batch into more than one batch based on the type of carts 340 available at a particular FC. In further embodiments, the batch generator 414 may also divide the item identifiers 321 based on predetermined parameters (such as a minimum batch size, a maximum batch size, etc.), which may be retrieved from the FC configuration database 413.

[0100] In step 703, the batch generator 414 can determine the parameters of the transport system available at the particular FC. In some embodiments, the transport system may include at least one of the above-mentioned carts 340, containers 330, and transport mechanisms 214. Therefore, the parameters of the transport system may include various aspects of each system, such as the available number and type of carts 340, the available number and type of containers 330, and the type of transport mechanisms 214. In addition, the parameters associated with the cart 340 may include at least one of its weight capacity and the size of its compartment or cargo space. Similarly, the parameters associated with the container 330 may include at least one of its weight capacity and the size of its storage compartment. The parameters of the transport mechanism 214 may include at least its weight capacity. In some embodiments, the batch generator 414 may retrieve these parameters from the FC configuration database 413.

[0101] In step 704, batch generator 414 may use the parameters determined in step 703 above to generate the batch of Figure 5Each batch is divided into one or more container groups or more batches in the manner shown. More specifically, the batch generator 414 can retrieve the size and weight of each item corresponding to the item identifier 321 assigned to a particular batch and assign each item identifier 321 to a container group until the weight capacity or volume capacity of the corresponding container 330 is reached, or the weight capacity of the transport mechanism 214 is reached, whichever is reached first. In some embodiments, the batch generator 414 can apply a predetermined ratio to each capacity. For example, instead of assigning item identifiers 321 to container groups until the weight capacity of the corresponding container 330 is reached, the batch generator 414 can assign item identifiers 32 until 70% of the weight capacity is reached. The predetermined ratio can be a uniform ratio applied to each capacity (i.e., the weight capacity of the container 330, the volume capacity of the container 330, and the weight capacity of the transport mechanism 214), or the ratio can be different for each capacity or type of transport system.

[0102] One or more items in an order may have an irregular shape, which may cause the corresponding container 330 to be filled faster than expected when the picker places the actual items into the container 330. In some embodiments, a heavy object placed on top of a fragile or soft item may also damage the fragile or soft item. Therefore, at step 705, the batch generator 414 may determine the optimal position or orientation of each item within the container 330 based on the item information retrieved from the inventory database 412, using considerations such as those listed above. Alternatively or additionally, the batch generator 414 may also determine the optimal position or orientation by using other known or conventional methods for packaging multiple items.

[0103] Based on the container groups determined in step 704 above, the batch generator 414 can determine the number and type of containers 330 and the type of carts 340 required for a particular batch. This information can enable the picker 350 to begin the batch assigned to him or her with the correct number and type of transport required for the batch, thereby preventing the picker 350 from having to make multiple trips back and forth within the picking area 209 because he or she runs out of space to carry the items 320. Therefore, in step 706, the batch generator 414 can transmit this information associated with the particular batch to the WMS 119 and to the user devices (e.g., devices 119A-C) belonging to the pickers assigned to the particular batch. The user devices can then display the information in the manner described above.

[0104] Although the present disclosure is shown and described with reference to specific embodiments, it should be understood that the present disclosure can be implemented in other environments without modification. The above description is for illustrative purposes. It is neither exhaustive nor limited to the precise form or embodiment disclosed. Those skilled in the art can obviously make modifications and adjustments by considering the above description and practicing the disclosed embodiments. In addition, although various aspects of the disclosed embodiments are described as being stored in a memory, those skilled in the art will understand that these aspects can also be stored on other types of computer-readable media, such as auxiliary storage devices, such as hard disks or CD ROMs, or other forms of RAM or ROMs, USB media, DVDs, Blu-ray or other optical drive media.

[0105] Computer programs based on the above written description and disclosed methods are within the skill of experienced developers. Various programs or program modules can be created using any technology known to those skilled in the art, or can be designed in conjunction with existing software. For example, program parts or program modules can be designed using or through .Net Framework, .Net Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML / AJAX combinations, XML, or HTML with accompanying Java applets.

[0106] In addition, although illustrative embodiments are described herein, the scope of any and all embodiments should include equivalent elements, modifications, omissions, combinations (e.g., combinations of various aspects in various embodiments), adjustments and / or substitutions, which are known to those skilled in the art based on this disclosure. The limitations in the claims should be interpreted broadly based on the language used in the claims, and are not limited to the examples described in this specification or during the examination of this application. These examples should be interpreted as non-exclusive. In addition, the steps of the disclosed method can be modified in any way, including reordering and / or inserting or deleting the steps. Therefore, this specification and embodiments should be regarded as illustrative only, and the true scope and spirit of the invention are indicated by the full scope of the attached claims and their equivalents.

Claims

1. A computer-implemented system for efficiently allocating orders based on system parameters, the system comprising: a memory for storing instructions; and At least one processor configured to execute the following instructions: Aggregating one or more orders containing one or more quantities of a plurality of items; assigning a subset of the items to batches, wherein the items are assigned to the one or more batches based on the item information and based on a weight capacity and a volume capacity of each of one or more containers of a transportation system; determining one or more parameters of a transport system for the batch; determining at least one of a position or an orientation of the item in the transport system based on a parameter of the transport system; and transmitting the parameters of the transport system to a user device for display, Wherein, when the number of created batches exceeds the number of available workers by a predetermined factor, the aggregating of one or more orders is stopped.

2. The computer-implemented system of claim 1, wherein: A summary order includes at least one of the following: Summarize the orders within the preset time; Aggregate orders until user input is received; or Orders are aggregated based on the number of available workers.

3. The computer-implemented system of claim 1 , wherein: Allocating the subset of items to the batch includes allocating a first item to the batch based on at least one of: a location of the first item, a size of the first item, and a combined weight of the subset of items.

4. The computer-implemented system of claim 1, wherein: The parameters include at least one of the following: the type of containers included in the transportation system; the number of containers included in the transportation system; and the carrying capacity of the transportation system.

5. The computer-implemented system of claim 1 , wherein: The combined weight of the subset of items is less than the carrying capacity of the transportation system.

6. The computer-implemented system of claim 1, wherein: The transport system includes the one or more containers, each container having a weight capacity and a volume capacity.

7. The computer-implemented system of claim 6, wherein: Allocating the subset of items to the batch includes allocating a portion of the subset of items to a first container.

8. The computer-implemented system of claim 7, wherein: A total weight or a total volume of a portion of the subset of items allocated to the first container is less than a first weight capacity and a first volume capacity of the first container by a predetermined ratio.

9. The computer-implemented system of claim 1, wherein: The instructions also include transferring the batch from the first location to the second location using an automated transport system.

10. The computer-implemented system of claim 9, wherein: Assigning the subset of items to the batch is based on the weight capacity of the automated transport system.

11. A computer-implemented method for efficiently allocating orders based on system parameters, the method comprising: Aggregating one or more orders containing one or more quantities of a plurality of items; assigning a subset of the items to batches, wherein the items are assigned to the one or more batches based on the item information and based on a weight capacity and a volume capacity of each of one or more containers of a transportation system; determining one or more parameters of a transport system for the batch; determining at least one of a position or an orientation of the item in the transport system based on a parameter of the transport system; and transmitting the parameters of the transport system to a user device for display, Wherein, when the number of created batches exceeds the number of available workers by a predetermined factor, the aggregating of one or more orders is stopped.

12. The computer-implemented method of claim 11, wherein: A summary order includes at least one of the following: Summarize the orders within the preset time; Aggregate orders until user input is received; or Orders are aggregated based on the number of available workers.

13. The computer-implemented method of claim 11, wherein: Allocating the subset of items to the batch includes allocating a first item to the batch based on at least one of: a location of the first item, a size of the first item, and a combined weight of the subset of items.

14. The computer-implemented method of claim 11, wherein: The parameters include at least one of the following: the type of containers included in the transportation system; the number of containers included in the transportation system; and the carrying capacity of the transportation system.

15. The computer-implemented method of claim 11, wherein: The combined weight of the subset of items is less than the carrying capacity of the transportation system.

16. The computer-implemented method of claim 11, wherein: The transport system includes the one or more containers, each container having a weight capacity and a volume capacity.

17. The computer-implemented method of claim 16, wherein: Allocating the subset of items to the batch includes allocating a portion of the subset of items to a first container.

18. The computer-implemented method of claim 17, wherein: A total weight or a total volume of a portion of the subset of items allocated to the first container is less than a first weight capacity and a first volume capacity of the first container by a predetermined ratio.

19. The computer-implemented method of claim 11, wherein: Also includes: The batch is transferred from the first location to the second location using an automated transport system, wherein assigning the subset of items to the batch is based on a weight capacity of the automated transport system.

20. A computer-implemented system for efficiently allocating orders based on system parameters, the system comprising: a memory for storing instructions; and At least one processor configured to execute the following instructions: Aggregating one or more orders containing one or more quantities of a plurality of items; assigning a first subset of the items to a first batch, wherein the items are assigned to the one or more batches based on the item information and based on a weight capacity and a volume capacity of each of one or more containers of a transportation system; determining one or more parameters of a transport system for the first batch; determining at least one of a position or an orientation of the first subset of items in the transport system based on a parameter of the transport system; sending the parameters of the transportation system to a user device for display; receiving, from the user device, a first item identifier associated with a first item in the first subset of items; and responsive to the first item identifier, transmitting at least one of a location or an orientation of the first item in a transportation system to a user device for display, Wherein, when the number of created batches exceeds the number of available workers by a predetermined factor, the aggregating of one or more orders is stopped.

Images