Computer-implemented system and computer-implemented method for product intake, stocking, and retrieval

Abstract

This invention discloses a pallet transport system and method for product feeding, storage, and retrieval. The system and method may include performing the following steps: receiving a first user input corresponding to a group identification code; receiving a second user input corresponding to one or more bag identification codes to be loaded onto the pallet; assigning the one or more bag identification codes to a group corresponding to the group identification code; assigning the group identification code to a location based on one or more items associated with the one or more bag identification codes; activating a conveyor to transport a pallet containing one or more items; determining the pallet's transportability using a first sensor input from a weight sensor; and causing a lifting mechanism to transfer the pallet from the conveyor to a self-navigating platform.

Description

Technical Field

[0001] This disclosure generally relates to computerized systems and methods for product feeding, storage, and retrieval. In particular, embodiments of this disclosure relate to inventive and non-traditional systems for receiving articles fed into a warehouse, grouping the articles based on user-defined screening, and using a combination of automated transport systems to transport the articles to a designated location within the warehouse. Prior Technology

[0002] With the explosive growth of e-commerce and the increasing demand for faster delivery times, warehouse management has become a key aspect of supply chain management. What was traditionally sufficient to keep track of goods using basic software and manual labor now requires the assistance of computers and robots to achieve accuracy and efficiency.

[0003] To this end, automation can help warehouses achieve higher levels of efficiency, accuracy, and productivity, while reducing labor costs and minimizing the risk of errors. Automation also provides real-time visibility into inventory levels, order status, and overall warehouse performance, enabling managers to make data-driven decisions and continuously improve operations.

[0004] However, traditional automated warehouse management systems continue to rely heavily on manual labor to move goods from one location to another. For example, manual labor is required to unload items from trailers upon arrival at the warehouse. The items are then transported to different parts of the warehouse for storage and future retrieval. While mechanical systems such as conveyors, pallet chucks, or even robotic arms may be utilized during these processes, they have been decoupled from automated warehouse systems. For instance, the use of mechanical systems has been limited to assisting employees in transporting bulk items, rather than reducing the number of decision points that must be made during the process (e.g., determining where items should be placed, how they should be stored, etc.).

[0005] Therefore, a combination of software and mechanical systems is needed to control the flow of goods within the warehouse. Such a system should be able to transport goods with minimal human intervention and facilitate hierarchical inventory tracking, while simultaneously leveraging the increased strength provided by the mechanical system. Summary of the Invention

[0006] One embodiment of this disclosure relates to a pallet transport system for product feeding, storage, and retrieval. The pallet transport system may include: a memory storing instructions; and at least one processor configured to execute the instructions, wherein the instructions cause the at least one processor to perform the following operations: receiving a first user input corresponding to a group identification code; receiving a second user input corresponding to one or more bag identification codes to be loaded onto the pallet; assigning the one or more bag identification codes to a group corresponding to the group identification code; assigning the group identification code to a location based on one or more items associated with the one or more bag identification codes; activating a conveyor to transport a pallet containing one or more items; determining the transportability of the pallet using a first sensor input from a weight sensor; and causing a lifting mechanism to transfer the pallet from the conveyor to a self-navigating platform.

[0007] Another aspect of this disclosure relates to a method for feeding, storing, and retrieving products. The method may include: receiving a first user input corresponding to a group identification code; receiving a second user input corresponding to one or more shopping bag identification codes to be loaded onto a pallet; assigning the one or more shopping bag identification codes to a group corresponding to the group identification code; assigning the group identification code to a location based on one or more items associated with the one or more shopping bag identification codes; activating a conveyor to transport a pallet containing one or more items; determining the pallet's transportability using a first sensor input from a weight sensor; and causing a lifting mechanism to transfer the pallet from the conveyor to a self-navigating platform.

[0008] Another aspect of this disclosure relates to a pallet transport system for product feeding, storage, and retrieval. The pallet transport system may include: a conveyor configured to transport pallets; a lifting mechanism configured to transfer pallets from the conveyor to a self-navigating platform; a memory storing instructions; and at least one processor configured to execute the instructions. The instructions may cause the at least one processor to perform the following operations: receiving a first user input corresponding to a group identification code; receiving a second user input corresponding to one or more shopping bag identification codes to be loaded onto the pallet; assigning a group identification code to a location based on one or more items associated with the one or more shopping bag identification codes; activating a conveyor located on a first floor to transport a pallet containing one or more items; and using the lifting mechanism to transfer the pallet from the conveyor to a self-navigating platform located on a second floor, the second floor being located above or below the first floor, wherein the second floor is determined based on a designated location.

[0009] This article also discusses other systems, methods, and computer-readable media. Simple Explanation of the Diagram

[0010] Figure 1A is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for communication, which is consistent with the disclosed embodiments and enables shipping, transportation and logistics operations. Figure 1B depicts a sample Search Result Page (SRP) that conforms to the disclosed embodiments, including one or more search results that satisfy a search request and interactive user interface elements. Figure 1C depicts a sample Single Detail Page (SDP) conforming to the disclosed embodiments, including the product and information about the product, as well as interactive user interface elements. Figure 1D depicts a sample shopping cart page conforming to the disclosed embodiments, including items in a virtual shopping cart and interactive user interface elements. Figure 1E depicts a sample order page conforming to the disclosed embodiments, including items from a virtual shopping cart, information about the purchase and shipment, and interactive user interface elements. Figure 2 is a schematic illustration of a configuration conforming to the disclosed embodiments for an exemplary execution center utilizing the disclosed computerized system. Figure 3 is a schematic illustration of an exemplary transportation system and goods flow within another exemplary fulfillment center that conforms to the disclosed embodiments. Figure 4 is a flowchart of an exemplary process for managing the flow of goods in accordance with the disclosed embodiments. Figure 5 is an exemplary graphical user interface for managing different screening rules to facilitate the flow of goods, in accordance with the disclosed embodiments. Implementation

[0011] The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numerals are used in the drawings and the following description to refer to the same or similar parts. While several illustrative embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, components and steps shown in the drawings can be substituted, added, or modified, and the illustrative methods described herein can be modified by substituting, reordering, removing, or adding steps to the disclosed methods. Therefore, the following detailed description is not limited to the disclosed embodiments and examples. Rather, the appropriate scope of the invention is defined by the appended claims.

[0012] The embodiments disclosed herein relate to systems and methods for configuring automated product feeding, storage, and retrieval.

[0013] Referring to FIG1A, a schematic block diagram 100 illustrating an exemplary embodiment of a system including a computerized system for communication, the system implementing shipping, transportation, and logistics operations is shown. As shown in FIG1A, system 100 may include various systems, each of which may be interconnected via one or more networks. Systems may also be interconnected via direct connections (e.g., using cables). The systems described 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 warehouse management system 119, mobile devices 119A, 119B, and 119C (described as being within 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) 125.

[0014] 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 (PDD) and can take appropriate actions, including: initiating a new order, reshipping items in an undelivered order, canceling an undelivered order, initiating contact with the ordering customer, etc. The SAT system 101 can also monitor other data, including outputs (e.g., the number of packages shipped within a specific time period) and inputs (e.g., the number of empty cardboard boxes received for use in shipping). The SAT system 101 can also act as a gateway between different devices in system 100, enabling communication between devices (e.g., external front-end system 103 and FO system 113) (e.g., using store-and-forward or other technologies).

[0015] In some embodiments, the external front-end system 103 may be implemented as a computer system that enables external users to interact with one or more systems in system 100. For example, in an embodiment where system 100 enables a user to place an order for an item, the external front-end system 103 may be implemented as a web server that receives search requests, presents item pages, and requests payment information. For example, the external front-end system 103 may be implemented as a computer or multiple computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc. In other embodiments, the external front-end system 103 may run custom web server software designed to: receive and process requests from external devices (e.g., mobile device 102A or computer 102B), retrieve information from databases and other data stores based on those requests, and provide responses to the received requests based on the retrieved information.

[0016] In some embodiments, the external front-end system 103 may include one or more of a web caching system, a database, a search system, or a payment system. In one embodiment, the external front-end system 103 may include one or more of these systems, while in another embodiment, the external front-end system 103 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

[0017] A set of illustrative steps illustrated in Figures 1B, 1C, 1D, and 1E 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 within 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), a Single Detail Page (SDP) (e.g., Figure 1C), a shopping cart page (e.g., Figure 1D), or an order page (e.g., Figure 1E). A user device (e.g., using mobile device 102A or computer 102B) may navigate to the external front-end system 103 and request a search by entering information into a search box. The external front-end system 103 may request information from one or more systems within system 100. For example, the external front-end system 103 may request information from system 113 FO to satisfy a search request. The external front-end system 103 can also request and receive a promised delivery date, or "PDD," for each product included in the search results (from the FO system 113). 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, if the product is ordered within a specific time period (e.g., by the end of the day (11:59 p.m.)), the date on which the product is promised to be delivered to the user's desired location (the PDD will be discussed further below with respect to the FO system 113).

[0018] External front-end system 103 can prepare an SRP (e.g., Figure 1B) based on the information. The SRP may include information that satisfies the search request. For example, this could include images of products that satisfy the search request. The SRP may also include the price of each product, or information related to enhanced delivery options for each product, such as PDD, weight, size, price quote, discounts, etc. External front-end system 103 can deliver the SRP to the requesting user's device (e.g., via a network).

[0019] The user device can then select a product from the SRP, for example, by clicking or tapping the user interface, or by using another input device, to select the product presented on the SRP. The user device can make an information request for the selected product and send the request to the external front-end system 103. In response, the external front-end system 103 can request information related to the selected product. For example, the information may include additional information beyond what is presented for the product on the respective SRP. This may include, for example, shelf life, country of origin, weight, dimensions, number of items in the package, instructions for use, 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 this product and at least one other product), answers to frequently asked questions, customer reviews, manufacturer information, images, etc.

[0020] External front-end system 103 can prepare an SDP (Single 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, and images of the items. The SDP may also include a list of sellers offering the product. This list can be ordered based on the price offered by each seller, with the seller offering the lowest price listed at the top. The list can also be ordered based on seller ranking, with the highest-ranked seller listed at the top. Seller ranking can be based on multiple factors, including, for example, a seller's past track record of fulfilling promised PDDs. External front-end system 103 can deliver the SDP to the requesting user's device (e.g., via a network).

[0021] The request allows the user device to receive an SDP listing product information. After receiving the SDP, the user device can then interact with it. For example, the user of the user device can click the "Place in Cart" button on the SDP or otherwise interact with it. This adds the product to the user's associated shopping cart. The user device can then send this request to an external front-end system 103 to add the product to the cart.

[0022] External front-end system 103 can generate a shopping cart page (e.g., Figure 1D). In some embodiments, the shopping cart page lists products that the user has added to a virtual "shopping cart". The user device can request the shopping cart page by clicking on an icon on an SRP, SDP, or other page, or by otherwise interacting with an icon on an SRP, SDP, or other page. In some embodiments, the shopping cart page may list all products that the user has added to the cart, as well as information about the products in the cart, such as the quantity of each product, the price per item of each product, the price per product based on the associated quantity, information about PDD (Product Items), delivery method, shipping costs, user interface elements for modifying products in the cart (e.g., deleting or modifying the quantity), options for ordering other products or setting up recurring delivery of products, options for setting up interest payments, user interface elements for continuing the purchase, etc. The user on the user device can click on a user interface element (e.g., a button read as "Buy Now") or otherwise interact with a user interface element to initiate a purchase of the products in the cart. After doing so, the user device can send the request to external front-end system 103 to initiate the purchase.

[0023] External front-end system 103 may generate an order page (e.g., Figure 1E) in response to receiving a request to initiate a purchase. In some embodiments, the order page relists the items from the shopping cart and requests input of payment and shipping information. For example, the order page may include sections 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., delivery and / or pickup speed / method), payment information (e.g., credit card, bank transfer, check, stored-value card), and user interface elements requesting a cash receipt (e.g., for tax purposes). External front-end system 103 may send the order page to the user's device.

[0024] The user device can enter information on the order page and click on a user interface element that sends the information to the external front-end system 103, or otherwise interact with the user interface element that sends the information to the external front-end system 103. From there, the external front-end system 103 can send the information to different systems in system 100 to initiate the creation and processing of a new order with products in the shopping cart.

[0025] In some embodiments, the external front-end system 103 may also be configured to enable the seller to send and receive information related to orders.

[0026] In some embodiments, the internal front-end system 105 may be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases system 100) to interact with one or more systems in system 100. For example, in an embodiment where system 100 enables the presentation of the system to allow users to place orders for items, the internal front-end system 105 may be implemented as a web server that enables internal users to: view diagnostic and statistical information about orders, modify item information, or review statistical information related to orders. For example, the internal front-end system 105 may be implemented as a computer or multiple computers running software (e.g., Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc.). In other embodiments, the internal front-end system 105 may run custom web server software designed to: receive and process requests from systems or devices described in system 100 (and other devices not shown), retrieve information from databases and other data stores based on those requests, and provide responses to received requests based on the retrieved information.

[0027] In some embodiments, the internal front-end system 105 may include one or more of a network caching system, a database, a search system, a payment system, an analytics system, an order monitoring system, etc. In one embodiment, the internal front-end system 105 may include one or more of these systems, while in another embodiment, the internal front-end system 105 may include interfaces (e.g., server-to-server, database-to-database, or other network connections) connected to one or more of these systems.

[0028] In some embodiments, the transportation system 107 may be implemented as a computer system capable of communicating between a system or device of system 100 and mobile devices 107A-107C. In some embodiments, the transportation system 107 may receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smartphones, handheld computers (PDAs), etc.). For example, in some embodiments, mobile devices 107A-107C may include devices operated by delivery workers. Delivery workers (who may be permanent, temporary, or shift employees) may utilize mobile devices 107A-107C to deliver packages containing products ordered by users. For example, in order to deliver a package, the delivery worker may receive notifications on the mobile device instructing which package to deliver and where to deliver it. Upon arrival at the delivery location, the delivery worker can locate the package (e.g., in the back of a truck or in the carton of the package), scan or otherwise capture information associated with identification elements on the package (e.g., barcodes, images, text strings, RFID tags, etc.) using a mobile device, and deliver the package (e.g., by leaving the package at the front door, handing it to security, or delivering it to the recipient). In some embodiments, the delivery worker may use a mobile device to capture a photograph of the package and / or obtain a signature. The mobile device may send information including delivery details (e.g., time, date, GPS location, photograph, identification elements associated with the delivery worker, identification elements associated with the mobile device, etc.) to the transportation system 107. The transportation system 107 may store this information in a database (not shown) for access by other systems in system 100. In some embodiments, the transportation system 107 may use this information to prepare tracking data and send the tracking data to other systems, indicating the location of a specific package.

[0029] In some embodiments, some users may use one type of mobile device (e.g., permanent workers may use a dedicated PDA with custom hardware (e.g., barcode scanners, styluses, and other devices)), while other users may use other types of mobile devices (e.g., temporary or shift workers may utilize readily available mobile phones and / or smartphones).

[0030] In some embodiments, the transportation system 107 may associate a user with each device. For example, the transportation system 107 may store associations between users (represented by, for example, user identification, employee identification, or telephone number) and mobile devices (represented by, for example, International Mobile Equipment Identity (IMEI), International Mobile Subscription Identifier (IMSI), telephone number, Universal Unique Identifier (UUID), or Globally Unique Identifier (GUID)). The transportation system 107 may combine this association with data received during delivery to analyze data stored in a database to determine, among other things, the worker's location, worker efficiency, or worker speed.

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

[0032] 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 a package containing products ordered by a customer (e.g., by a user using devices 102A-102B). In some embodiments, the shipping and order tracking system 111 may request or store information from a web server (not shown) operated by a shipping company that delivers packages containing products ordered by customers.

[0033] In some embodiments, the shipping and order tracking system 111 may request and store information from the systems described in 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, smartphones, 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 warehouse management system (WMS) 119 to determine the location of individual 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 WMS 119, process the data, and present the data to devices (e.g., user devices 102A and 102B) upon request.

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

[0035] The FO system 113 can also calculate the corresponding PDD (Promised Delivery Date) for each product. In some embodiments, the PDD can be based on one or more factors. For example, the FO system 113 can calculate the PDD of a product based on past demand for the product (e.g., how many 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 upcoming period of time), past demand of the entire network indicating how many products have been ordered over a period of time, expected demand of the entire network indicating how many products are expected to be ordered in the upcoming period of time, one or more counts of the products stored in each fulfillment center 200, which fulfillment center each product is stored in, expected orders or current orders for the product, etc.

[0036] In some embodiments, the FO system 113 may periodically (e.g., hourly) determine a Product Development Date (PDD) for each product and store the PDD in a database for retrieval or transmission 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 as needed.

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

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

[0039] In some embodiments, the warehouse management system (WMS) 119 can be implemented as a computer system for monitoring workflows. For example, WMS 119 can receive event data indicating discrete events from various devices (e.g., devices 107A-107C or devices 119A-119C). For example, WMS 119 can receive event data indicating that one of these devices should be used to scan a package. As discussed below with respect to fulfillment center 200 and Figure 2, during the fulfillment process, package identification words (e.g., barcode or RFID tag data) can be scanned or read by machines at specific stages (e.g., automatic or handheld barcode scanners, RFID readers, high-speed cameras, devices (e.g., tablet computer 119A), mobile devices / PDAs 119B, computers 119C, etc.). WMS 119 can store each event indicating the scanning or reading of a package identification word along with the package identification word, time, date, location, user identification information, or other information in a corresponding database (not shown), and can provide this information to other systems (e.g., shipping and order tracking system 111).

[0040] In some embodiments, WMS 119 may store information that associates one or more devices (e.g., devices 107A-107C or devices 119A-119C) with one or more users associated with system 100. For example, in some cases, a user (e.g., a part-time or full-time employee) may be associated with a mobile device because 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 because the user temporarily holds the mobile device (e.g., the user checks out the mobile device at the beginning of the day, will use it during the day, and will return it at the end of the day).

[0041] 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 specified process (e.g., unloading a truck, picking items from a picking area, rebin wall work, packing items), user identification, location (e.g., floor or zone in fulfillment center 200), the number of units moved by the employee through the system (e.g., the number of items picked, the number of items packed), and identification words associated with equipment (e.g., equipment 119A-119C). In some embodiments, WMS 119 may receive check-in and check-out information from a punctuality system (e.g., a punctuality system operating on equipment 119A-119C).

[0042] In some embodiments, third-party fulfillment (3PL) systems 121A-121C represent computer systems associated with cooperating vendors for logistics and products. For example, while some products are stored in fulfillment center 200 (as discussed below with reference to FIG2), others may be stored off-site, may be produced on demand, or may not otherwise be stored in fulfillment center 200. 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 outside of system 100 (e.g., owned or operated by a third-party vendor).

[0043] In some embodiments, the Fulfillment Center Authorization System (FC Auth) 123 can be implemented as a computer system with various functionalities. For example, in some embodiments, FC Auth 123 can act as a single sign-on (SSO) service for one or more other systems within System 100. For instance, FC Auth 123 can enable users to log in via internal front-end system 105, determine that the user has similar privileges to access resources at the shipping and order tracking system 111, and enable the user to access those privileges 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 can instead move from one task and from one zone to another within Fulfillment Center 200 throughout the day. FC Auth 123 can be configured to enable these employees to indicate what task they are performing and which zone they are in at different times of the day.

[0044] In some embodiments, the Labor Management System (LMS) 125 can be implemented as a computer system that stores attendance and overtime information of employees (including full-time and part-time employees). For example, the LMS 125 can receive information from FC Auth 123, WMS 119, devices 119A-119C, transportation system 107 and / or devices 107A-107C.

[0045] The specific configuration depicted in Figure 1A is merely an example. For instance, while Figure 1A depicts an FC-licensed system 123 connected to FO system 113, not all embodiments require this specific configuration. In fact, in some embodiments, the systems in system 100 can be interconnected via one or more public or private networks, including the Internet, intranet, WAN (Wide Area Network), MAN (Metropolitan Area Network), wireless networks compliant with IEEE 802.11a / b / g / n standards, leased lines, etc. In some embodiments, one or more systems in system 100 can be implemented as one or more virtual servers implemented in a data center, server farm, etc.

[0046] Figure 2 illustrates a fulfillment center 200. A fulfillment center 200 is an example of a physical location where items are stored and shipped to a customer when an item is ordered. A fulfillment center (FC) 200 may be divided into multiple zones, each of which is depicted in Figure 2. In some embodiments, these "zones" can be considered as virtual divisions between different stages of the processes of receiving, storing, retrieving, and shipping items. Therefore, while "zones" are depicted in Figure 2, other divisions of zones are possible, and in some embodiments, the zones in Figure 2 may be omitted, repeated, or modified.

[0047] The receiving area 203 represents the area of ​​FC 200 where a seller wishes to receive items from the system 100 of Figure 1A to sell products. For example, the seller may use truck 201 to deliver items 202A and 202B. Item 202A may represent a single item large enough to occupy its own shipping pallet, while item 202B may represent a group of items stacked together on the same pallet to save space.

[0048] Workers will receive items in inbound area 203 and may optionally check for damage and correctness using a computer system (not shown). For example, workers may use the computer system to compare the quantities of items 202A and 202B with the ordered quantities of the items. If the quantities do not match, workers may reject one or more of items 202A or 202B. If the quantities match, workers may move these items to buffer 205 (using, for example, a trolley, handcart, forklift, or manually). For example, buffer 205 may be a temporary storage area for items not currently needed in the picking area, since there is a sufficiently high quantity of the item in the picking area to meet anticipated demand. In some embodiments, forklift 206 operates to move items around buffer 205 and between inbound area 203 and unloading area 207. If item 202A or 202B is needed in the picking area (e.g., due to anticipated demand), the forklift may move item 202A or 202B to unloading area 207.

[0049] Unloading area 207 may be an area of ​​FC 200 where items are stored before being moved to picking area 209. A worker assigned to a picking task (“picker”) can approach items 202A and 202B in the picking area, scan the barcodes of the picking area using a mobile device (e.g., device 119B), and scan the barcodes associated with items 202A and 202B. The picker can then carry the items to picking area 209 (e.g., by placing the items on a cart or carrying them).

[0050] Picking area 209 may be an area where items 208 are stored on storage unit 210 of FC 200. In some embodiments, storage unit 210 may include one or more of physical shelves, bookshelves, boxes, shopping bags, refrigerators, freezers, cold storage, etc. In some embodiments, picking area 209 may be organized into multiple floors. In some embodiments, workers or machines may move items to picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyors, trolleys, handcarts, trolleys, automated robots or devices, or manually. For example, a picker may place items 202A and 202B on a handcart or trolley in unloading area 207 and walk to pick area 209.

[0051] Pickers can receive instructions to place (or "stack") items at specific points in picking area 209 (e.g., a specific space on storage unit 210). For example, a picker can scan item 202A using a mobile device (e.g., device 119B). The device (e.g., using a system that indicates aisles, shelves, and locations) can instruct the picker where item 202A should be stacked. Then, before stacking item 202A at that location, the device can prompt the picker to scan the barcode at that location. The device can (e.g., via a wireless network) send data to a computer system (e.g., WMS 119 in Figure 1A) informing the user of device 119B that item 202A has been loaded at that location.

[0052] Once a user places an order, the picker can receive instructions on device 119B to retrieve one or more items 208 from storage unit 210. The picker can retrieve item 208, scan the barcode on item 208, and place item 208 on conveyor 214. In some embodiments, although conveyor 214 is represented as a slider, the conveyor can be implemented as one or more of a conveyor belt, elevator, trolley, forklift, handcart, bogie, etc. Item 208 can then reach packaging area 211.

[0053] Packing area 211 may be an area of ​​FC 200 that receives items from picking area 209 and packs the items into boxes or bags for final shipment to the customer. In packaging area 211, a worker assigned to receive the items ("merging worker") will receive item 208 from picking area 209 and determine the order to which item 208 corresponds. For example, the merging worker may use a device (e.g., computer 119C) to scan a barcode on item 208. Computer 119C may visually indicate which order item 208 is associated with. This may include, for example, space or "unit cell" on wall 216 corresponding to the order. Once the order is completed (e.g., because the unit cell contains all items for that order), the merging worker may indicate to the packaging worker (or "packer") that the order is complete. The packer may retrieve the items from the unit cell and place them into boxes or bags for shipment. The packer may then (e.g., via forklift, trolley, wheelbarrow, handcart, conveyor belt, manually, or otherwise) deliver the boxes or bags to hub area 213.

[0054] Hub area 213 may be an area of ​​FC 200 that receives all boxes or bags (“parcels”) from packaging area 211. Workers and / or machines in hub area 213 may retrieve parcels 218 and determine which part of the delivery area each parcel is intended to go to, and send the parcels along a specific route 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, workers or machines may (e.g., using one of devices 119A-119C) scan the parcels to determine their final destination. Sending the parcels along a specific route to camp area 215 may include, for example (e.g., based on a postal code), determining a portion of the geographic area specified by the parcel and determining the camp area 215 associated with that portion of the geographic area.

[0055] In some embodiments, camp area 215 may include one or more buildings, one or more physical spaces, or one or more areas where packages are received from hub area 213 for sorting into routes and / or subroutines. In some embodiments, camp area 215 is physically separate from FC 200, while in other embodiments, camp area 215 may be part of FC 200.

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

[0057] Figure 3 is a schematic illustration of the flow of goods within an exemplary transportation system and another exemplary fulfillment center 300. In some embodiments, the fulfillment center 300 may be implemented as the fulfillment center 200 of Figure 2 and includes multiple floors above and / or below ground, as shown by separator 301. The illustrated portions of the fulfillment center 300 may correspond, for example, to the buffer zone 205, unloading area 207, and picking area 209 of Figure 2.

[0058] The main components of the transportation system may include a conveyor network 310, a lifting system 320, and a self-navigating platform 330. These components can communicate electronically with various networked systems of FIG1A, such as WMS 119, third-party fulfillment systems 121A-C, FMG 115, and FO system 113. Although only a limited number of components are illustrated in FIG3 for illustrative purposes, none of the examples shown in terms of number, location, or configuration are intended to be limiting.

[0059] In some embodiments, conveyor network 310 may include a network of conveyors 311 and one or more workstations 312. Conveyors 311 may cover different areas of fulfillment center 300. For example, conveyors 311 may extend from inbound area 203 to lifting system 320, allowing items 313 received in inbound area 203 to be transported to lifting system 320 by employees using disconnecting equipment such as trolleys or stackers with minimal workload. In some embodiments, workstations 312 may be located at various locations close to conveyors 311. One or more workers 315 may be positioned at workstations 312 to scan items 313 and load them onto conveyors 311 as they are transported from inbound area 203. In some embodiments, items 313 may be loaded onto pallets 314 or other shelving units. The process for loading items 313 onto conveyors 311 is described in more detail below with reference to FIG4.

[0060] In some embodiments, the conveyor 311 may include a locking mechanism (not shown) configured to prevent movement of at least a portion of the conveyor 311. One or both software and hardware components may be used to implement the locking mechanism. For example, a software lock may be configured to reject any request from a local (e.g., a computer at workstation 312) or networked system (e.g., WMS 119) to activate the locking portion of the conveyor 311. Alternatively, a hardware lock may include a locking mechanism that engages with one or more gears, chains, pulleys, or any mechanical components used to move the locking portion to prevent any movement of the conveyor 311.

[0061] In some embodiments, the lifting system 320 may include a lifting mechanism 321 or elevator-type mechanism capable of moving up and down between different floors of the fulfillment center 300. This capability allows the fulfillment center 300 to store more items 313 in a limited area. The lifting mechanism 321 may be powered by a network of pneumatic or hydraulic cylinders and / or pulleys (not shown) to be able to lift heavy loads. In some embodiments, the lifting mechanism 321 may include extension arms 322 for transferring pallets 314 or shelf units. For example, the lifting mechanism 321 may include a pair of extension arms configured to extend into slots on the pallet 314 or shelf unit, such that the pallet 314 or shelf unit can be transferred onto the lifting mechanism 321 in one go along with the items 313 loaded thereon.

[0062] In some embodiments, the conveyor network 310 and / or lifting system 320 may include one or more sensors configured to determine the transportability of a loaded pallet 314 or shelf unit. For example, the conveyor 311, lifting mechanism 321, and / or self-navigating platform 330 may include weight sensors configured to generate a signal corresponding to the total weight of the pallet 314 or shelf unit and the items 313 loaded thereon. In some embodiments, two or more weight sensors may be present on a portion of the conveyor 311, allowing weight measurements to be taken at each corner of the pallet 314 or shelf unit. The conveyor 311, lifting mechanism 321, and self-navigating platform 330 may be rated for a maximum weight limit, beyond which the structural integrity or capability of the conveyor 311, lifting mechanism 321, or self-navigating platform 330 may be compromised. Any pallet 314 or shelf unit loaded with items 313 up to a point where the total weight exceeds or is within a predetermined percentage of the maximum weight limit may be determined as not meeting the essential transportability requirements of the pallet 314 or shelf unit.

[0063] In another embodiment, the conveyor 311 and / or lifting mechanism 321 may include a gap sensor configured to generate a signal corresponding to the length, width, and / or height of the tray 314 or shelf unit along with the items 313 loaded thereon. The conveyor network 310, lifting system 320, and / or self-navigating platform 330 may be configured to transport items of certain sizes, exceeding which items may become lodged in structures or other moving or non-moving objects surrounding the conveyor network 310 or lifting system 320. The gap sensor may include one or more optical sensors, ultrasonic sensors, laser sensors, or infrared sensor arrays, each sensor configured to measure the length, width, or height of the items 313 loaded on the conveyor 311 or lifting mechanism 321, or the distance from the nearest point on the item 313 to its respective sensor. In other embodiments, the gap sensor may generate a simple Boolean signal based on whether the sensor detects an obstruction in its detection path. Any pallet 314 or shelf unit loaded with items 313 that extend beyond the acceptable dimensions of the conveyor 311, lifting mechanism 321, or self-navigating platform 330 may be determined to be non-conforming to the essential transportability of the pallet 314 or shelf unit. In some embodiments, various combinations of dimensions may be used to determine transportability, such as the linear sum of the overall dimensions of the pallet 314 or shelf unit loaded with items 313, the minimum value of the dimensions, or the maximum value of the dimensions.

[0064] In some embodiments, one or more self-navigating platforms 330 may be placed on each floor of the fulfillment center 300. The number of self-navigating platforms 330 on a floor may vary based on, for example, the floor's square feet, the number of items, the number of pallets 314 or shelf units to be stored on the floor, the number of pallets 314 or shelf units expected to move simultaneously at any given point in time, etc. As the name suggests, the self-navigating platforms 330 may be configured to navigate around various moving or non-moving objects on the floor, such as other self-navigating platforms 330, any structural elements (e.g., walls, doors, or pillars), people, equipment, or any objects that may be found in the storage areas of the fulfillment center 300. In some embodiments, each self-navigating platform 330 may include an ultrasonic sensor, a light detection and ranging (LiDAR) sensor, an optical sensor, a camera, or an infrared sensor configured to detect objects or structures in its vicinity. The self-navigating platform 330 may be configured to use output signals from those sensors to detect its objects or structures and navigate around other objects or structures. Alternatively, each floor of the fulfillment center 300 may include these sensors, which can be configured to determine the positions of multiple self-navigating platforms 330 and / or objects on the floor. A centralized processing system (not shown) may be configured to guide each self-navigating platform 330 (e.g., using wireless signals to communicate with each self-navigating platform 330) to avoid collisions.

[0065] In another embodiment, the self-navigating platform 330 may be configured to transport pallets 314 or shelf units along with the items 313 loaded thereon. For example, the self-navigating platform 330 may be sized to fit beneath the pallet 314 or shelf unit when unloaded from the lifting mechanism 321 using the extension arm 322. The self-navigating platform 330 may therefore be able to transport the pallet 314 or shelf unit to a designated location within the floor of the fulfillment center 300 via the process described below with respect to FIG4.

[0066] Figure 4 is a flowchart of an exemplary process 400 for managing the flow of goods 313. Process 400 can be performed via a WMS 119 or another networked system (e.g., a warehouse control system (WCS) (not shown)) dedicated to managing automated goods handling equipment in fulfillment centers 300 (e.g., conveyor network 310, lifting system 320, and self-navigating platform 330).

[0067] In some embodiments, the WCS can be implemented as a computer system that receives data from a network database in a connected system, such as WMS 119, and communicates with various automated goods handling equipment to perform process 400 and others, such as inventory movement, order fulfillment, and / or replenishment. In some embodiments, the WCS can be configured to wirelessly send commands to various automated goods handling equipment to control their movement or behavior in a manner that facilitates the flow of goods 313 with WMS 119. For example, the WCS can control the conveyor network 310, the lifting system 320, and the self-navigating platform 330 to move goods 313 from buffer 205 to picking area 209 and update information in WMS 119 to reflect where each goods 313 is stored, how much is present, etc., when it must be sold. Alternatively, the WCS can also control the conveyor network 310, the lifting system 320, and the self-navigating platform 330 to retrieve goods 313 in response to a signal from WMS 119 that certain goods 313 need to fulfill customer orders.

[0068] At step 401, the WCS may receive first user input corresponding to a group identification code. The first user input may be entered, for example, via a mobile device (e.g., device 107A-107C or 119A-119C) utilized at worker 315 workstation 312. The group identification code may be a pre-generated sequence of characters designated for identification and reference purposes. Its use is described below to explain subsequent steps. In some embodiments, the mobile device may be configured to determine that a different type of identification code (e.g., a tote bag identification code) has been scanned instead of a group identification code, and notify worker 315 to try again. This determination may be based on the character sequence or by looking up the input against a list of known group identification codes. The notification from the mobile device may be any combination of auditory, tactile, or visual feedback.

[0069] At step 402, the WCS may receive a second user input corresponding to one or more tote bag identification codes to be loaded onto pallet 314 or shelf unit. Similar to the first user input, the tote bag identification code may be entered via a mobile device utilized by worker 315 at workstation 312. The tote bag identification code may include a plurality of pre-generated character sequences, each character sequence assigning to a tote bag or storage unit containing one or more items 313. The tote bag may contain a unit of items, a plurality of identical items, or any combination of different items. Similarly, the item 313 associated with the tote bag identification code received in the second user input may include a plurality of identical item units or a combination of different items. In some embodiments, having a tote bag identification code may allow the WCS to request or retrieve identification codes (e.g., SKU codes) for one or more items 313 included in the corresponding tote bag or storage unit.

[0070] In some embodiments, step 402 may further include associating a group identifier received in the first user input with a bag identifier received in the second user input, such that the bag identifiers are recorded as grouped together in WMS 119. In this embodiment, the mobile device may be configured to determine whether a different type of identifier (e.g., a group identifier) ​​has been scanned instead of a bag identifier, and notify worker 315 to try again. This determination and notification may be similar to the determination and notification described above with respect to step 401. Alternatively or additionally, the mobile device may be configured to determine whether the bag identifier included in the second user input: (1) has been associated with another group identifier; (2) is one of the bag identifiers included in the second user input; or (3) does not correspond to one of the bags ready to be associated with a group identifier. The mobile device may be configured to notify worker 315 in a manner similar to that described above.

[0071] Furthermore, the mobile device can also be configured to determine if a bag identification code is invalid due to any physical damage to the code itself, such as an erased or covered barcode printed on the bag. In this case, the worker 315 can be prompted to resolve the issue by reprinting the barcode or reconfiguring the bag or item 313. The bag identification code can also be determined to be invalid because there is no record of material intake at the entry area 203 or no request to store the corresponding bag. These issues can be manually resolved by the worker 315 reviewing the logs of events associated with the bag identification code or by configuring the WCS or WMS 119 to re-track the records to identify potential errors.

[0072] At step 403, the WCS may assign a group identification code to a storage location based on one or more items 313 associated with one or more bag identification codes. The storage location may include a specific location designated for storing items 313 in one of the floors of the fulfillment center 300, such as picking area 209. In some embodiments, the actual location of the storage location may be unknown only to the worker 315 referenced by the location identification code. The WCS or WMS 119 may assign a location identification code to each specific storage location without displaying the information to worker 315 or other employees in the fulfillment center 300 unless specifically requested.

[0073] In some embodiments, assigning a group identifier to a storage location may include retrieving item information and storage information from a web database storing information associated with item 313; and classifying one or more items 313 into a common group based on one or more filtering rules 517 (described below). The web database may include, for example, a WCS, WMS 119, FO system 113, SCM 117, or third-party fulfillment systems 121A-C.

[0074] In some embodiments, the categorization of items 313 may be based on user input received via a graphical user interface configured to allow the user to define or adjust one or more filtering rules 517. The graphical user interface may be configured to allow selective activation of filtering rules 517 based on user input, as described below in more detail with reference to FIG5.

[0075] At step 404, the WCS may activate conveyor 311 to transport pallet 314 or shelf unit containing item 313. Subsequently, at step 405, the WCS may use sensor inputs from one or more sensors described above to determine the transportability of pallet 314 or shelf unit. For example, the WCS may use a weight sensor to determine the weight of pallet 314 or shelf unit loaded with item 313, thereby ensuring that pallet 314 or shelf unit remains within the operational limits of conveyor network 310, lifting system 320, and self-navigating platform 330. Alternatively, the WCS may use a gap sensor to determine whether any of pallet 314, shelf unit, or item 313 loaded thereon may interfere with or become stuck on moving or non-moving portions of conveyor network 310, lifting system 320, or self-navigating platform 330 or their surroundings.

[0076] In some embodiments, the WCS can be configured to prevent or block any movement of the portion of conveyor 311 where the particular pallet 314 or shelf unit being analyzed is located. The WCS may use a locking mechanism to prevent or block movement at least until transportability is determined or the pallet 314 or shelf unit is loaded onto the self-navigating platform 330. This can prevent situations where transportability is determined to be insufficient, and the pallet 314 or shelf unit is rejected and recalled for adjustment.

[0077] When the WCS determines that the transportability of pallet 314 or shelf unit is actually insufficient, the WCS may restart (e.g., by disengaging the locking mechanism) a portion of conveyor 311 and return pallet 314 or shelf unit to workstation 312 or another station dedicated to handling rejected pallets 314 or shelf units. Items 313 returned to pallets 314 or shelf units may be divided into multiple subgroups, such that heavier or larger items 313 are distributed across additional pallets 314 or shelf units. In some embodiments, dividing items 313 into subgroups may include moving a subset of items 313 to another tote bag and associating the corresponding item identification code with the tote bag identification code of the new tote bag. This new tote bag containing the subset of items 313 can then be transported and loaded onto another pallet 314 or shelf unit in the same manner as in process 400.

[0078] Alternatively, when the WCS determines that the transportability of pallet 314 or shelf unit meets the minimum threshold, the WCS can restart (e.g., by disengaging the locking mechanism on a portion of conveyor 311) and continue transporting pallet 314 or shelf unit to lifting system 320.

[0079] At step 406, the WCS enables the extension arm 322 to transfer the pallet 314 or shelf unit from the conveyor 311 to the lifting mechanism 321, moves the lifting mechanism 321 to the floor corresponding to the location of the group identification code assigned to the item 313 loaded on the pallet 314 or shelf unit, and transfers the pallet 314 or shelf unit from the lifting mechanism 321 to the destination floor via a self-navigating platform. In some embodiments, the starting floor (i.e., the floor where the conveyor 311 is located) and the destination floor may be different, wherein the destination floor is located above or below the starting floor in the multi-level fulfillment center 300. For example, the starting floor may be located on the same ground plane as the inbound area 203, buffer zone 205, and / or unloading area 207, while the destination floor may be located on a different floor of the picking area 209.

[0080] In some embodiments, once the self-navigation platform 330 has transported the pallet 314 or shelf unit to the designated location, the self-navigation platform 330 may return to the lifting system 320 or other segmented areas to prepare for the transport of other pallets 314 or shelf units, such as those received from the lifting system 320. In another embodiment, the WCS may be configured to send an acknowledgment signal to the WMS 119 once the pallet 314 or shelf unit has been safely transported to the intended location. The acknowledgment signal may include other information, such as the quantity of items 313 stored on the pallet 314 or shelf unit and / or the earliest expiration date of the items 313.

[0081] Furthermore, the stored pallet 314 or shelf unit can be retrieved from its location using at least one of a group identification code, an associated tote bag identification code, or an item identification code for one or more items associated with a tote bag identification code. For example, the WCS can receive a signal from the WMS 119 to fulfill a customer order that includes item 313 stored in one of the stored pallets 314 or shelf units. The WCS can then guide the navigation platform 330 to retrieve the specific pallet 314 or shelf unit containing the customer-ordered item 313 and transport the specific pallet 314 or shelf unit to a picking station (not shown), where a worker can pick the appropriate number of items 313 from the pallet 314 or shelf unit.

[0082] In some embodiments, process 400 may also include reporting storage failures. For example, worker 315 may be able to report any problems that occur during process 400, such as damaged items in any of the handbags, insufficient number of items, etc. The WCS may activate conveyor network 310, lifting system 320, and / or self-navigating platform 330 to transport the problematic handbag, pallet 314, or shelf unit to the collection buffer, where the problem can be resolved. For example, a shortage of items 313 or a shortage of damaged items 313 can be addressed by retrieving an additional number of corresponding items and adding the required number of items to the handbag, pallet 314, or shelf unit.

[0083] In some embodiments, handbags, trays, or shelving units containing items 313 that are disproportionately damaged may be marked for return to the corresponding supplier. In one embodiment, for example, 315 may open the box containing items 313 and locate the majority of items damaged upon arrival. In other embodiments, worker 315 may update records in a network database (e.g., WMS 119) to mark the item identification codes associated with the damaged items as damaged. WMS 119 may then be configured to determine the percentage of defective or damaged items 313 received from a particular supplier and notify an administrator that the corresponding batch of items 313 should be returned. In some embodiments, WCS may control conveyor system 310 to transport items 313 marked as damaged, defective, or awaiting return, or handbags, trays, or shelving units containing such items 313, to a designated area in fulfillment center 300.

[0084] Figure 5 is an exemplary graphical user interface 500 for managing different screening rules 517 used to facilitate the flow of items 313. In some embodiments, the graphical user interface 500 may be displayed on a computing device connected to the WCS and WMS 119, such as an internal front-end system 105. In another embodiment, the graphical user interface 500 may be software running on a computing device that can access and modify operating parameters of the WCS. Furthermore, the graphical user interface 500 may be configured to display data received from different networked systems, such as those described above with respect to Figure 2. This information may include, for example, SKU codes for each item 313, item type (e.g., dairy, general, refrigerated, fresh, frozen, etc.) barcodes, weight, dimensions, expiration date, manufacturing date, or any other parameters or information recorded. The WCS may use this information to determine which bags should be grouped together, and / or where the trays 314 or shelf units containing the groups should be assigned, as in step 403 above.

[0085] In some embodiments, the graphical user interface 500 may include different tabs, various filter tabs 510, a tray filter tab 520, and a location configuration tab 530. Each filter tab 510 may display and allow manipulation of a set of filter rules 517 applicable to classifying items 313 to be loaded together with different items. The tray filter tab 520 may display and allow manipulation of another set of filter rules 517 applicable to classifying items 313 to be loaded in bulk without other items. For example, WCS may apply the filter rules displayed in the various filter tabs 510 to classify (i.e., group) different numbers of items A, B, and C such that they can be loaded onto a single tray 314 or shelf unit and stored together; and apply the filter rules displayed in the tray filter tab 520 to classify multiple items A into a group and load them individually onto another tray 314 or shelf unit without any of items B or C. The Location Configuration tab 530 can display several settings and parameters for different storage locations in the fulfillment center 300, such as whether a specific location is available for storage or closed for maintenance.

[0086] In some embodiments, each filter tab 510 may include a table 540 having a priority column 511, a usage column 512, a name column 513, a SKU type column 515, and a delivery code column 516, wherein each filter rule 517 is displayed in a column. The tray filter tab 520 may also include a similar table with similar columns.

[0087] The information shown in the priority column 511 indicates the priority of applying the corresponding filter rule 517. For example, a first filter rule 518 can be applied to any given tote bag to determine its group before applying a second filter rule 519. Column 512 may include a series of check boxes indicating whether the corresponding filter rule 517 is applied. The information shown in the zone type column 514 indicates the zone where the tote bag to be sorted will be stored. In some embodiments, the zones listed in the zone type column 514 may correspond to the zones described above with respect to FIG. 2. For example, tote bags sorted using filter rule 517 will be assigned to a location in buffer 205 or picking zone 209. The information shown in the SKU type column 515 indicates the type of SKU suitable for the corresponding filter rule 517. For example, a first filter rule 518 may only be applied to tote bags containing items 313 of SKU type S or A. The information shown (or to be illustrated) in the conveyor code 516 indicates the conveyor identification code to be used for transporting the tote bag. The values, names, types, or numbers shown in Table 540 are merely illustrative and not intended to be limiting. Any other values, names, types, or numbers may be used to cater to the needs of different fulfillment centers.

[0088] In some embodiments, WCS may apply a set of basic rules to each filtering rule 517. An exemplary set of basic rules is described below, but these rules are not intended to be restrictive and may be added, removed, or modified to suit the needs of different fulfillment centers.

[0089] First, screening rule 517 may require only one type of item to be loaded for each pallet 314 or shelf unit. For example, refrigerated items may not be grouped with frozen or non-refrigerated items to be loaded onto the same pallet 314 or shelf unit. Second, screening rule 517 may require all items 313 in a group to have the same expiration date or usage date. Third, screening rule 517 may limit each group to a maximum number of dissimilar items, with or without considering the quantity of any particular item. Fourth, screening rule 517 may require items 313 in each group to have the same intended customer base (e.g., retail and wholesale).

[0090] In another embodiment, the graphical user interface 500 may include a filtering rule configuration interface (not shown) that allows the user to input different parameters to define or modify filtering rule 517. For example, the graphical user interface 500 may accept values ​​from the user including the following parameters: SKU type, storage temperature, volume, weight, length of any side, linear sum of all sides, length of the longest side, length of the shortest side, length of the middle-sized side, whether the SKU is new or unknown, previously specified group identifier priority, and / or maximum number of dissimilar items.

[0091] WCS can compare these parameters with item information extracted from a networked system (e.g., WMS 119) to determine whether item 313 in the tote bag matches the parameters of filter rule 517, and assign groups based on this determination. For this purpose, each parameter can be paired with a Boolean or mathematical operator that specifies whether the parameters of a particular item should match the set of parameters in filter rule 517, should be greater than, less than, or equal to the set of parameters, etc.

[0092] While this disclosure has been shown and described with reference to specific embodiments thereof, it should be understood that this disclosure can be implemented in other environments without modification. The foregoing description is presented for illustrative purposes. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adjustments will be apparent to those skilled in the art upon consideration of the description and practice of the disclosed embodiments. Furthermore, although the embodiments disclosed are described as being stored in memory, those skilled in the art will understand that such embodiments can also be stored in other types of computer-readable media, such as auxiliary storage devices (e.g., hard disks or CD-ROMs), or other forms of RAM or ROM, USB media, DVDs, Blu-ray discs, or other optical disc drive media.

[0093] Computer programs based on written descriptions and disclosures are within the skill level of experienced developers. Various programs or program modules can be created using any techniques known to those skilled in the art, or various programs or program modules can be designed in conjunction with existing software. For example, program parts or program modules can be designed in or through methods such as: .NET Framework, .NET Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML / AJAX combination, XML, or HTML containing Java applets.

[0094] Furthermore, while illustrative embodiments have been described herein, the scope of any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., patterns across multiple embodiments), adaptations, and / or alterations will be understood by those skilled in the art based on the technology of the invention. Limitations in the claims will 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. Moreover, the steps of the disclosed method can be modified in any way, including by reordering steps and / or inserting or deleting steps. Therefore, the specification and examples are to be considered illustrative only, and their true scope and spirit are indicated by the full scope of the appended claims and their equivalents.

[0095] 100: Block Diagram / System 101: Shipment Authorization Technology (SAT) System 102A: Mobile Devices / User Devices 102B: Computer / User Equipment 103: External Front-End System 105: Internal Front-End System 107: Transportation System 107A, 107B, 107C: Mobile devices / equipment 109: Seller Portal 111: Shipment and Order Tracking (SOT) System 113: Execution Optimization (FO) System 115: Execution Message Gateway (FMG) 117: Supply Chain Management (SCM) System 119: Warehouse Management System (WMS) 119A: Mobile devices / tablets 119B: Mobile Devices / Devices / PDAs 119C: Mobile Device / Equipment 121A, 121B, 121C: Third-Party Implementation (3PL) Systems 123: Fulfillment Center Authorization System (FC Auth) 125: Labor Management System (LMS) 200, 300: Fulfillment Center (FC) 201, 222: Trucks 202A, 202B, 208, 313: Items 203: Entrance Area 205: Buffer 206: Forklift 207: Unloading Area 209: Picking Area 210: Storage unit 211: Packaging Area 213: Hub Area 214: Transmission Mechanism 215: Camp Area 216: Wall 218, 220: Packages 224A, 224B: Delivery workers 226: Cars 301: Separator 310: Transmission Network 311: The Teleporter 312: Workstation 314: Pallet 315: Workers 320: System Upgrade 321: Upgrading mechanism 322: Extender Arm 330: Self-navigation platform 400: Process 401, 402, 403, 404, 405, 406: Steps 500: Graphical User Interface 510: Filter tab 511: Priority bar 512: Use column 513: Name Field 514: Area Type Column 515: SKU column 516: Transmitter code field 517: Filtering Rules 518: First Screening Rule 519: Second Screening Rule 520: Tray Screening Tab 530: Location Configuration Tab 540: Table

Claims

1. A computer-based method for product feeding, storage, and retrieval, the method comprising: Receive the first user input corresponding to the first code; Receive second user input corresponding to one or more second codes, each second code associated with a tote bag; assign the one or more second codes to a group corresponding to the first code; assign the first code to a location based on one or more items associated with the one or more second codes; determine the transportability of a pallet containing the one or more items; cause a lifting mechanism to transfer the pallet; and prevent the conveyor from moving until the pallet is loaded onto a self-navigating platform, wherein the conveyor is locked using a mechanical lock or a soft lock, the mechanical lock being configured to prevent the movement when engaged, and the soft lock being configured to reject a request to move the conveyor.

2. The computer implementation method as described in claim 1, wherein assigning the first code to the location includes: Extract item information and storage information from a web database storing information associated with the one or more items; classify the one or more items into common groups based on one or more filtering rules.

3. The computer implementation method as described in claim 2 further includes: The display is configured to receive user input for defining or adjusting one or more filtering rules, and includes a graphical user interface.

4. The computer implementation method as described in claim 3 further includes: Selective activation based on one or more filtering rules input by the user is received via the graphical user interface.

5. The computer implementation method as described in claim 1 further includes: The transportability of the pallet is further determined using sensor input from a gap sensor, wherein the gap sensor is configured to determine the size of the pallet.

6. The computer implementation method as described in claim 5, wherein further determining the transportability of the pallet using the gap sensor includes: The width, length, height, linear sum of the dimensions, maximum value of the dimensions, or minimum value of the dimensions are compared with one or more constraints of the conveyor or the self-navigation platform.

7. The computer implementation method as described in claim 1 further includes: The conveyor is restarted to return the pallet based on the determination that the pallet's transportability does not meet one or more requirements, wherein the returned pallet is divided into multiple subgroups, each subgroup being associated with a subset of the one or more second codes.

8. The computer implementation method as claimed in claim 1, wherein the first code includes a group identification code and the one or more second codes include a tote bag identification code, and wherein the tray can be retrieved from the location using at least one of the group identification code, any one of the one or more tote bag identification codes, or at least one of the one or more item identification codes of the items.

9. The computer implementation method as claimed in claim 1 further includes activating the conveyor to transport the pallet containing the one or more items, wherein determining the transportability of the pallet containing the one or more items is based on a first sensor input from a weight sensor, and wherein causing the lifting mechanism to transfer the pallet includes causing the lifting mechanism to transfer the pallet from the conveyor to the self-navigating platform.

10. A computer-based implementation system for product feeding, storage, and retrieval, the system comprising: Memory stores instructions; And at least one processor configured to execute the instructions to perform the steps of any one of the requests 1-9.

Images