JP2023526877A - Computerized system and method for package delivery error detection - Google Patents

Abstract

Embodiments of the present disclosure include computer-implemented systems and methods for package delivery. The method includes receiving a customer order, generating an order identifier, associating each item of the customer order with the order identifier, and determining an intended delivery destination for each item. be able to. The method causes the user device to display first instructions for sorting each item based on storage space associated with the intended delivery destination, and sorting each sorted item based on the delivery route. display a second instruction for placing each sorted item into a container regardless of the status of the other items in the customer order; Regardless, the method can further include displaying fourth instructions for delivering the arranged item of the plurality of items to the intended delivery destination.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation in part of currently pending U.S. Patent Application Serial No. 16/416,909, filed May 20, 2019, which is incorporated herein by reference in its entirety. incorporated into the book.

The present disclosure relates generally to computerized systems and methods for package delivery to fulfill customer orders. In particular, embodiments of the present disclosure utilize the non-disclosure of the present invention to efficiently fulfill customer orders and deliver packages in reduced cycle times while maintaining high worker efficiency across multiple zones within a fulfillment center. Related Art Conventional Computerized Systems, Methods, and User Interfaces.

Fulfillment centers (FCs) allow e-commerce retailers to outsource warehousing and shipping. Inventory management in FC is an essential component for creating the best customer experience for online shoppers. Inventory management may involve many steps, such as receiving goods from sellers, storing received goods for easy access, packing items, confirming orders, and delivering packages. While current existing FCs and systems for inventory control within FCs are configured to handle large volumes of incoming and outgoing merchandise, the efficiency and timeliness of fulfilling customer orders is may be restricted due to inefficient practices of procuring items to Delays in package delivery can cause customer dissatisfaction and, in some cases, can affect the cost and profitability of a business.

With the advancement and widespread acceptance of electronic commerce, Internet shopping offers a one-stop-shop for all your shopping needs, including food, furniture, electronics, clothing, books, and more. Each online order typically includes a combination of items from a wide variety of categories. While current existing order fulfillment practices allow the system to be used to obtain each individual item within an order in an efficient manner, the overall efficiency of order delivery is limited by the ability to For example, items are often stored in different sections of the FC based on categories, and packers may have to wait for pickers to pick them before packing all the items in an order. . This can cause delays in subsequent steps in the process of packaging and delivering packages to customers, which slows the throughput of the system and the efficiency of computerized systems that control the shipping process.

Additionally, the overall efficiency and throughput of the FC can be impacted because items are picked individually but packed together in one container before being loaded as a package onto a delivery truck. Expected or unexpected packing delays can affect picking efficiency if the storage space where the picked items are stored is not accessible. The process of storing and shipping packages from a FC involves several steps such as receiving, stowing, picking, sorting, packing, loading, delivering, and verifying order accuracy at each step. For high overall efficiency, the efficiency of the individual steps must also be high. For example, if the process includes 10 steps and each step has an efficiency of over 90%, the overall efficiency is only 83.9%.

Additionally, current existing FCs use teams of workers to ensure smooth 24-hour operation. One of the technical challenges in warehouses can be the rapid communication of information to floor workers, such as urgent customer orders, expedited shipments, and the like. Current existing logistics and inventory management systems lack the ability to efficiently deal with expected or unexpected urgency in customer orders, which can lead to customer dissatisfaction and associated increased inventory costs. have a nature.

Therefore, there is a need to implement improved methods and systems for efficient package delivery through individualization to reduce cycle and promised delivery times while maintaining high overall throughput and efficient utilization of resources. It is said that

One aspect of this disclosure relates to a computer-implemented method for package delivery. The method comprises: receiving a customer order; generating an order identifier based on the customer order; associating each item of a plurality of items of the customer order with the order identifier; Determining the intended delivery destination of, the storage space associated with the intended delivery destination, and the delivery route. The method includes providing for display to a user first instructions for sorting each item of a plurality of items based on storage space associated with an intended delivery destination using a first sorting process. transmitting to the device; receiving from at least one user device a first input related to the status of the first sorting process; and the intended delivery purpose regardless of the status of the first sorting process. Sending second instructions for sorting each sorted item using a second sorting process based on the delivery route configured to include the location to the at least one user device for display. receiving from at least one user device a second input related to the status of the second sorting process; and placing each sorted item into a delivery route regardless of the status of the second sorting process. transmitting to at least one user device for display a third instruction to put into a container associated with a customer order; transmitting a fourth instruction for delivering the intended item to the intended delivery destination to the at least one user device for display.

Another aspect of the disclosure relates to a computer-implemented method for package delivery. The method comprises: receiving a customer order; generating an order identifier based on the customer order; associating each item of a plurality of items of the customer order with the order identifier; Determining the intended delivery destination of, the storage space associated with the intended delivery destination, and the delivery route. The method includes providing for display to a user first instructions for sorting each item of a plurality of items based on storage space associated with an intended delivery destination using a first sorting process. transmitting to the device; receiving from at least one user device a first input related to the status of the first sorting process; and the intended delivery purpose regardless of the status of the first sorting process. Sending second instructions for sorting each sorted item using a second sorting process based on the delivery route configured to include the location to the at least one user device for display. receiving, from at least one user device, a second input related to the status of the second sorting process; and sending each sorted item to a delivery route regardless of the status of the second sorting process. transmitting to at least one user device for display a third instruction to put into a container associated with the and fourth instructions for delivering the placed item of the plurality of items to the intended delivery destination regardless of the status of other items of the plurality of items in the customer order, as indicated. receiving from the at least one user device a fourth input including information related to a delivery schedule for the arranged items of the plurality of items; Storing the input, the second input, the third input, and the fourth input in a database associated with the computer-implemented system.

Yet another aspect of the disclosure relates to a computer-implemented system for package delivery. The system comprises a memory storing instructions, executing the instructions, receiving a customer order, generating an order identifier based on the customer order, associating each item of a plurality of items of the customer order with the order identifier, at least one processor configured to determine the intended delivery destination of the delivery destination, the storage space associated with the intended delivery destination, and the delivery route. a processor executing instructions to provide first instructions for sorting each item of a plurality of items based on storage space associated with an intended delivery destination using a first sorting process; sending to a user device for display; receiving from at least one user device a first input related to the status of the first sorting process; second instructions for sorting each sorted item using a second sorting process based on a delivery route configured to include a destination on at least one user device for display; and receiving, from at least one user device, a second input relating to the status of the second sorting process, and relating each sorted item to a delivery route regardless of the status of the second sorting process. Sending a third container instruction to at least one user device for display, intended for the placed item of the plurality of items regardless of the status of other items in the plurality of items of the customer order. A fourth instruction for delivery to the specified delivery destination may be sent to the at least one user device for display.

Yet another aspect of the present disclosure relates to a computer-implemented system for sorting packages. The system may include a memory storing instructions and at least one processor, the at least one processor executing the instructions to generate an order identifier based on a received customer order, the order being a plurality of associate each item in a customer order with an order identifier; determine, based on the order identifier, a storage container associated with each item, a container identifier associated with each container, and a delivery route; storing an association between each item of the plurality of items of the order and the container identifier in a mapping table, and a first sorting process for sorting one or more items of the plurality of items based on the mapping; sending first instructions to at least one user device to initiate sorting one or more items of a plurality of items based on a first indication; and status of a first sorting process receiving from at least one user device a first input related to the sorted items based on the delivery route using the second sorting process regardless of the status of the first sorting process; sending a second instruction to sort to at least one user device for display associated with the sorter, and receiving a second input associated with the status of the second sorting process from the at least one user device; receiving, after the second sorting process, comparing the order identifier to the container identifier, detecting, based on the comparison, that an exception event has occurred in the second sorting process; notification that the exception event has occurred; transmitting to at least one user device associated with the sorter.

Yet another aspect of the present disclosure relates to a computer-implemented method for sorting packages, the method comprising using a computer-implemented system to generate an order identifier based on a received customer order; includes multiple items, associates each item in a customer order with an order identifier, and determines, based on the order identifier, a storage container associated with each item, a container identifier associated with each container, and a delivery route. storing in a mapping table an association between each item of the plurality of items of the customer order and the container identifier based on the order identifier; and one or more items of the plurality of items based on the mapping. sending to at least one user device a first instruction to initiate a first sorting process for sorting the items; and based on the first indication, one or more of the plurality of items receiving from at least one user device a first input related to the status of the first sorting process; and regardless of the status of the first sorting process, the second sorting using a process to send second instructions for sorting each sorted item based on a delivery route to at least one user device for display associated with the sorter; receiving second input from the at least one user device related to the status of the sorting process; comparing the order identifier to the container identifier after the second sorting process; and sending a notification that the exception event has occurred to at least one user device associated with the sorter.

Other systems, methods, and computer-readable media are also described herein.

1 is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for communications to enable shipping, transportation, and logistics operations consistent with disclosed embodiments; FIG. FIG. 4 illustrates a sample search results page (SRP) containing one or more search results satisfying a search request, along with interactive user interface elements, consistent with the disclosed embodiments; FIG. 10 shows a sample single display page (SDP) containing products and information about the products along with interactive user interface elements consistent with the disclosed embodiments; FIG. 10 illustrates a sample cart page including items in a virtual shopping cart along with interactive user interface elements consistent with disclosed embodiments; FIG. 10 illustrates a sample order page including items from a virtual shopping cart along with information regarding purchases and shipping, along with interactive user interface elements, consistent with the disclosed embodiments; 1 is a schematic diagram of an exemplary fulfillment center configured to utilize the disclosed computerized system consistent with disclosed embodiments; FIG. 1 is a schematic diagram of an exemplary computerized personalized package delivery system configured to utilize the disclosed computerized system consistent with disclosed embodiments; FIG. FIG. 4 is a schematic diagram of an exemplary process flow for individualized package delivery consistent with disclosed embodiments; FIG. 4 is a schematic diagram of an exemplary process flow for generating a representation of a delivery vehicle's loading arrangement, consistent with disclosed embodiments; FIG. 4 is a schematic diagram of an exemplary process flow for personalized package delivery consistent with disclosed embodiments; FIG. 4 is a schematic diagram of an exemplary notification dashboard consistent with disclosed embodiments;

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers will be used in the drawings and the following description to refer to the same or like parts. Although several exemplary embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the components and steps shown in the figures, and the exemplary methods described herein replace, rearrange, remove, or may be modified by adding Accordingly, 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.

Embodiments of the present disclosure relate to systems and methods configured to reduce cycle time and increase package delivery efficiency by shipping items of the same order separately without waiting for the remaining items, thus avoid slowing down automated systems and processes.

Referring to FIG. 1A, a schematic block diagram 100 illustrating an exemplary embodiment of a network including computerized systems for communications enabling shipping, transportation, and logistics operations is shown. As shown in FIG. 1A, system 100 can include various systems, each of which can be connected to each other via one or more networks. The illustrated systems include a Shipping 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, 107C, a merchant portal 109, a shipment and order tracking (SOT) system. System 111, Fulfillment Optimization (FO) System 113, Fulfillment Messaging Gateway (FMG) 115, Supply Chain Management (SCM) System 117, Warehouse Management System 119, Mobile Devices 119A, 119B, 119C (Fulfillment Center (FC) 200), third party fulfillment systems 121A, 121B, 121C, fulfillment center authentication (FC authentication) system 123, labor management system (LMS) 125.

SAT system 101 may be implemented as a computer system that monitors order status and delivery status in some embodiments. For example, the SAT system 101 determines whether an order is past its Promised Delivery Date (PDD), initiates new orders, reships items in undelivered orders, removes undelivered orders. Appropriate action can be taken, including canceling, initiating contact with the ordering customer, and the like. The SAT system 101 can also monitor other data, including outputs (such as the number of packages shipped during a particular time period) and inputs (such as the number of empty cartons received for use in shipping). . SAT system 101 also acts as a gateway between different devices within system 100, enabling communication (eg, using store-and-forward or other techniques) between devices such as external front-end systems 103 and FO systems 113. can be

In some embodiments, external front-end system 103 may be implemented as a computer system that allows external users to interact with one or more systems within network 100 . For example, in embodiments where network 100 enables system presentation to allow users to place orders for items, external front-end system 103 receives search requests, presents item pages, It may also be implemented as a web server requesting payment information. For example, external front-end system 103 may be implemented as one or more computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, the external front-end system 103 receives and processes requests from external devices (not shown), retrieves information from databases and other data stores based on those requests, and processes the retrieved information. It can run custom web server software designed to provide responses to requests received based on it.

In some embodiments, 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 aspect, the external front-end system 103 may include one or more of these systems, and in another aspect the external front-end system 103 is connected to one or more of these systems. Interfaces (eg, server-to-server, database-to-database, or other network connections) may be included.

An exemplary set of steps illustrated by FIGS. 1B, 1C, 1D, and 1E help explain some operations of the external front-end system 103. FIG. External front-end system 103 may receive information from systems or devices within network 100 for presentation and/or display. For example, external front-end system 103 may display a search results page (SRP) (eg, FIG. 1B), a single detail page (SDP) (eg, FIG. 1C), a cart page (eg, FIG. 1D), or an order page (eg, , FIG. 1E) can be hosted or served. A user device (eg, using mobile device 102A or computer 102B) can navigate to external front-end system 103 and request a search by entering information in a search box. External front-end system 103 can be requested from one or more systems within network 100 . For example, external front-end system 103 can request results from FO system 113 that satisfy a search request. 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 returned in the search results. The PDD, in some embodiments, is an estimate of when the package will arrive at the user's desired location if ordered within a specified period of time, e.g., by the end of the day (11:59 PM). represents a value. (PDDs are discussed further below with respect to FO system 113.)

The external front-end system 103 can prepare an SRP (eg, FIG. 1B) based on that information. The SRP may contain information that satisfies a search request. For example, this may include pictures of products that satisfy a search request. The SRP may also include information regarding the respective price for each product, or enhanced shipping options, PDD, weight, size, offers, discounts, etc. for each product. The external front-end system 103 can deliver the SRP to the requesting user device (eg, over a network).

The user device can then select a product from the SRP to select a product represented on the SRP, for example by clicking or tapping the user interface or using another input device. The user device can create a request for information regarding the selected product and send it to the external front end system 103 . In response, the external front-end system 103 can request information regarding the selected product. For example, the information may include additional information beyond that presented for products on each SRP. This may include, for example, shelf life, country of origin, weight, size, number of items in a package, instructions, or other information about the product. 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, responses from customers May include reviews, manufacturer information, photos, and the like.

The external front-end system 103 can prepare an SDP (Single Detail Page) (eg, FIG. 1C) based on the received product information. The SDP may also include other interactive elements such as "buy now" buttons, "add to cart" buttons, quantity fields, item pictures, and the like. The external front-end system 103 can deliver the SDP to the requesting user device (eg, over a network).

A requesting user device may receive an SDP containing product information. Upon receiving the SDP, the user device can interact with the SDP. For example, the user of the requesting user device may click an "Add to Cart" button on the SDP or otherwise interact. This adds products to the shopping cart associated with the user. The user device can send this request to the external front-end system 103 to add products to the shopping cart.

External front-end system 103 can generate a cart page (eg, FIG. 1D). In some embodiments, the cart page lists products that the user has added to a virtual "shopping cart." A user device may request a cart page by clicking or otherwise interacting with an icon on an SRP, SDP, or other page. In some embodiments, the cart page displays all the products that the user has added to the shopping cart, as well as the quantity of each product, the price per item of each product, the price of each product based on the associated quantity, information about the PDD, shipping methods, shipping costs, user interface elements for modifying products in the shopping cart (e.g. deleting or modifying quantities), options for ordering other products or setting up recurring deliveries of products; Information about the products in the cart can be listed, such as options for setting interest payments, user interface elements for facilitating purchases, and the like. A user of the user device clicks or otherwise interacts with a user interface element (e.g., a button labeled "Buy Now") to initiate purchase of products in the shopping cart. can do. In doing so, the user device can send this request to the external front-end system 103 to initiate the purchase.

External front-end system 103 can generate an order page (eg, FIG. 1E) in response to receiving a request to initiate a purchase. In some embodiments, the order page relists items from the shopping cart and requests payment and shipping information. For example, an order page may include 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, shipping information), shipping A user interface for requesting information (e.g., speed/method of shipping and/or pickup), payment information (e.g., credit card, bank transfer, check, stored credit), cash receipt (e.g., for tax purposes). May contain sections that require elements, etc. The external front-end system 103 can send the order page to the user device.

The user device can enter information into the order page and click or otherwise interact with user interface elements that send the information to the external front end system 103 . From there, the external front-end system 103 can send information to various systems within the network 100 to enable creation and processing of new orders with the products in the shopping cart.

In some embodiments, external front-end system 103 may be further configured to allow merchants to send and receive information regarding orders.

Internal front-end systems 105 in some embodiments allow internal users (e.g., employees of the entity that owns, operates, or leases network 100) to interact with one or more systems within network 100. It can be implemented as a computer system that enables For example, in embodiments where network 101 enables presentation of systems to allow users to place orders for orders, internal front-end system 105 may be used by users to view diagnostic and statistical information about orders and to It can be implemented as a web server that allows information to be modified or statistics about items to be reviewed. For example, internal front-end system 105 may be implemented as one or more computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, internal front-end system 105 receives and processes requests from devices shown on network 100 (as well as other devices not shown) and retrieves information from databases and other data stores based on those requests. and run custom web server software designed to provide responses to received requests based on the information obtained.

In some embodiments, internal front-end systems 105 may include one or more of web caching systems, databases, search systems, payment systems, analytics systems, order monitoring systems, and the like. In one aspect, internal front-end system 105 may include one or more of these systems, and in another aspect internal front-end system 105 is connected to one or more of these systems. interfaces (eg, server-to-server, database-to-database, or other network connections).

Transportation system 107 may be implemented as a computer system that enables communication between devices in network 100 and mobile devices 107A-107C in some embodiments. In some embodiments, transportation system 107 may receive information from one or more mobile devices 107A-107C (eg, cell phones, smart phones, PDAs, etc.). For example, in some embodiments, mobile devices 107A-107C may include devices operated by delivery personnel. Delivery workers may be full-time, temporary, or alternate workers, and may utilize mobile devices 107A-107C to deliver packages ordered by users. For example, to deliver a package, a delivery worker can receive a notification on their mobile device indicating which package to deliver and where to deliver it. Upon arrival at the delivery location, the delivery crew locates the package (e.g., in the back of a truck, or in a package box) and uses a mobile device to identify data associated with the package identifier (e.g., barcode, barcode, image, text, RFID tag, etc.) can be scanned or otherwise captured and the package delivered (eg, by leaving it at the doorstep, leaving it with a security guard, handing it over to the recipient, etc.). In some embodiments, a delivery worker can capture a photo of the package and/or obtain a signature. The mobile device can send a communication to the transportation system 107 that includes information regarding the delivery including, for example, time, date, GPS location, photo, identifier associated with the delivery worker, identifier associated with the mobile device, and the like. Transport system 107 may store this data in a database (not shown) for access by other systems within network 100 . Transportation system 107 may, in some embodiments, use this information to prepare and transmit tracking data indicating the location of a particular package to other systems.

In some embodiments, a particular user may use one type of mobile device (e.g., a full-time worker may use a dedicated PDA with custom hardware such as barcode scanners, styluses, and other devices). ), but other users may use other types of mobile devices (e.g., temporary or shift workers may utilize off-the-shelf cell phones and/or smart phones). ).

In some embodiments, transportation system 107 may associate users with respective devices. For example, transportation system 107 may identify a user (e.g., user identifier, employee identifier, or telephone number) and a mobile device (e.g., International Mobile Equipment Identity (IMEI), International Mobile Subscriber Identifier (IMSI), telephone number, Universally Unique Identifier (e.g., UUID), or globally unique (GUID)) can be stored. The transport system 107 uses this relationship in conjunction with the data received on the delivery to determine, among other things, the location of the worker, the availability of the worker, or the speed of the worker in the database within the order. The data stored in can be analyzed.

Merchant portal 109 may, in some embodiments, be implemented as a computer system that allows merchants or other external entities to electronically communicate other aspects of information regarding orders. For example, a seller may utilize a computer system (not shown) to upload or provide product information, ordering information, contact information, etc. for products the seller wishes to sell through system 100 .

Shipping and order tracking system 111, in some embodiments, is a computer system that receives, stores, and transfers information regarding the location of packages ordered by customers (eg, by users using devices 102A-102B). MAY be implemented. In some embodiments, the shipping and order tracking system 111 may request or store information from a web server (not shown) operated by the shipping company that delivers the package ordered by the customer.

In some embodiments, shipping and order tracking system 111 may request and store information in the systems shown in network 100 . For example, shipping and order tracking system 111 can request information from transportation system 107 . As described above, transportation system 107 may include one or more mobile devices 107A-107C (eg, cell phones) associated with one or more of users (eg, delivery workers) or vehicles (eg, delivery trucks). , smart phones, PDAs, etc.). In some embodiments, shipping and order tracking system 111 requests information from warehouse management system (WMS) 119 to determine the location of individual packages within a fulfillment center (eg, fulfillment center 200). You can also Shipping and order tracking system 111 requests data from one or more of transportation system 107 or WMS 119, processes it, and presents it to devices (e.g., user devices 102A and 102B) as requested. be able to.

Fulfillment optimization (FO) system 113, in some embodiments, stores information for customer orders from other systems (eg, external front-end system 103 and/or shipping and order tracking system 111). It may also be implemented as a computer system. The FO system 113 may also store information describing where particular items are held or stored. For example, some items ordered by a customer may be stored at only one fulfillment center, while other items may be stored at multiple fulfillment centers. In still other embodiments, a particular fulfillment center may be designed to store only a particular set of items (eg, fresh or frozen products). The FO system 113 stores this information as well as related information (eg, quantity, size, date of receipt, expiration date, etc.).

The FO system 113 can also calculate the corresponding PDD (promised delivery date) for each product. PDD may be based on one or more factors in some embodiments. For example, the FO system 113 may include historical demand for a product (eg, how many times the product was ordered over a period of time), projected demand for the product (eg, how many customers will order the product over a period of time to come). past demand across the network indicating how many products have been ordered over a period of time, projected demand across the network indicating how many products are expected to be ordered over a period to come , one or more counts of products stored at each fulfillment center 200 that stores each product, forecast or current orders for that product, etc., may be used to calculate the PDD for a product.

In some embodiments, the FO system 113 periodically (e.g., hourly) determines the PDD for each product and searches it or other systems (e.g., external front-end system 103, SAT system 101, It can be stored in a database for transmission to the shipping and order tracking system 111). In other embodiments, FO system 113 receives electronic requests from one or more systems (eg, external front-end system 103, SAT system 101, shipping and order tracking system 111) and computes PDDs on demand. be able to.

Fulfillment Message Gateway (FMG) 115, in some embodiments, receives communications from one or more systems in network 100, such as FO system 113, converts the data in the communications to another format, It can be implemented as a computer system that transfers data in the converted format to WMS 119 or other systems such as third party fulfillment systems 121A, 121B, or 121C and vice versa.

Supply chain management (SCM) system 117 may be implemented as a computer system that performs predictive functions in some embodiments. For example, the SCM system 117 may include, for example, historical demand for a product, projected demand for a product, historical demand across the network, projected demand across the network, number of products stored at each fulfillment center 200, A projected level of demand for a particular product can be determined, such as based on forecasts or current orders. Depending on this determined forecasted level and quantity of each product across all fulfillment centers, the SCM system 117 may generate one or more purchase orders to meet the expected demand for the particular product. can.

Warehouse management system (WMS) 119 may be implemented as a computer system that monitors workflow in some embodiments. For example, WMS 119 may receive event data from individual devices (eg, devices 107A-107C or 119A-119C) that indicate individual events. For example, WMS 119 may receive event data indicating the use of one of these devices to scan packages. As described below with respect to fulfillment center 200 and FIG. 2, during the fulfillment process, package identifiers (e.g., barcodes or RFID tag data) can be scanned or read by machines (e.g., automated or devices such as handheld bar code scanners, RFID readers, high speed cameras, tablets 119A, mobile devices/PDAs 119B, computers 119C). WMS 119 can store each event indicating scanning or reading of a package identifier along with the package identifier, time, date and time, location, user identifier, or other information in a corresponding database (not shown) and stores this information. It can be provided to other systems (eg, shipping and order tracking system 111).

WMS 119 may, in some embodiments, store information that associates one or more devices (eg, devices 107A-107C or 119A-119C) with one or more users associated with network 100. . For example, in some situations, a user (such as a part-time or full-time employee) may be associated with a mobile device in that the user owns the mobile device (eg, the mobile device is a smart phone). . In other situations, the user is temporarily under the control of the mobile device (e.g., the user rents the mobile device at the beginning of the day, uses it during the day, and returns it at the end of the day). in that it may be associated with a mobile device.

WMS 119 may maintain a work log for each user associated with network 100 in some embodiments. For example, WMS 119 can be any assigned process (e.g., unloading a truck, picking an item from a pick zone, living wall work, packing an item), user identifier, location (e.g., floor or location within fulfillment center 200). zones), number of units moved through the system by employees (e.g., number of items picked, number of items packed), identifiers associated with devices (e.g., devices 119A-119C), etc. Information related to each employee can be stored. In some embodiments, WMS 119 may receive check-in and check-out information from a timekeeping system, such as the timekeeping system operating on devices 119A-119C.

Third party fulfillment (3PL) systems 121A-121C represent, in some embodiments, computer systems associated with third party providers of logistics and products. For example, while some products are stored at fulfillment center 200 (as described below with respect to FIG. 2), other products may be stored offsite or produced on demand. , or otherwise unavailable for storage at fulfillment center 200 . 3PL systems 121A-121C may be configured to receive orders from FO system 113 (eg, via FMG 115) and provide products and/or services (eg, delivery or installation) directly to customers. good too.

Fulfillment center authentication system (FC authentication) 123 may be implemented as a computer system with various functions in some embodiments. For example, in some embodiments FC authentication 123 may operate as a single sign-on (SSO) service for one or more other systems within network 100 . For example, FC authentication 123 allows a user to log in via internal front-end system 105 and determines that the user has similar privileges to access resources in shipping and order tracking system 111. and allow users to access those privileges without requiring a second login process. In other embodiments, FC authentication 123 may allow users (eg, employees) to associate themselves with specific tasks. For example, some employees do not have electronic devices (such as devices 119A-119C) and instead move from task to task and zone to zone within fulfillment center 200 during the day. may FC authentication 123 may be configured to allow their employees to indicate what tasks they are doing and what zone they are in at various times.

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

The specific configuration shown in FIG. 1A is merely an example. For example, although FIG. 1A shows FC authentication system 123 connected to FO system 113 via FMG 115, not all embodiments require this particular configuration. Indeed, in some embodiments, systems within network 100 may be the Internet, an intranet, a WAN (Wide Area Network), a MAN (Metropolitan Area Network), a wireless network conforming to the IEEE 802.11a/b/g/n standard, a private They may be connected together via one or more public or private networks including wires and the like. In some embodiments, one or more of the systems in network 100 may be implemented as one or more virtual servers implemented in data centers, server farms, and the like.

FIG. 2 shows fulfillment center 200 . Fulfillment center 200 is an example of a physical location that stores items for shipment to customers upon ordering. A fulfillment center (FC) 200 can be divided into multiple zones, each of which is shown in FIG. These "zones" can in some embodiments be considered virtual divisions between various stages of the process of receiving items, storing items, retrieving items, and shipping items. Thus, although "zones" are depicted in FIG. 2, other divisions of zones are possible, and in some embodiments the zones of FIG. 2 may be omitted, duplicated, or modified.

Inbound zone 203 represents the area of FC 200 that receives items from merchants seeking to sell products using network 100 of FIG. For example, a seller may use truck 201 to deliver items 202A and 202B. Item 202A can represent a single item large enough to occupy its own shipping pallet, while item 202B is a set stacked together on the same pallet to save space. can represent items of

A worker receives the item at the inbound zone 203 and can optionally inspect the item for damage and accuracy using a computer system (not shown). For example, a worker can use a computer system to compare the quantity of items 202A and 202B to the ordered quantity of the items. If the quantities do not match, the worker can reject one or more of items 202A or 202B. If the quantities match, the worker can move the items to the buffer zone 205 (eg, using a trolley, wheelbarrow, forklift, or manually). Buffer zone 205 may be a temporary storage area for items that are not currently needed in the picking zone, for example, because there are sufficient quantities of items in the picking zone to meet expected demand. In some embodiments, forklifts 206 operate to move items around buffer zone 205 and between inbound zone 203 and drop zone 207 . If item 202A or 202B is needed in the picking zone (eg, due to anticipated demand), the forklift can move item 202A or 202B to drop zone 207 .

Drop zone 207 may be an area of FC 200 that stores items before they are moved to picking zone 209 . A worker assigned to the picking task (“picker”) approaches items 202A and 202B in the picking zone, scans the picking zone barcode, and uses a mobile device (eg, device 119B) to pick up items 202A and 202B. 202B can be scanned. The picker can then bring the item to the picking zone 209 (eg, by placing it on a cart or carrying it).

Picking zone 209 may be an area of FC 200 where items 208 are stored in storage unit 210 . In some embodiments, storage unit 210 may include one or more of physical shelves, bookshelves, boxes, totes, refrigerators, freezers, cold storage, and the like. In some embodiments, the picking zone 209 may be organized into multiple floors. In some embodiments, workers or machines move items into picking zone 209 in a number of ways including, for example, forklifts, elevators, conveyor belts, carts, wheelbarrows, trolleys, automated robots or devices, or manually. can be moved. For example, a picker can load items 202A and 202B onto a wheelbarrow or trolley at drop zone 207 and carry items 202A and 202B to picking zone 209 .

A picker may receive instructions to place (or “stow”) an item at a particular spot within picking zone 209 , such as a particular space in storage unit 210 . For example, a picker can scan item 202A using a mobile device (eg, device 119B). The device can indicate where the picker should store the item 202A using, for example, an aisle, shelf, and position indicating system. The device can then prompt the picker to scan the barcode at that location before storing item 202A at that location. The device may send data (eg, over a wireless network) to a computer system such as WMS 119 of FIG. 1 indicating that item 202A was stored there by the user using device 119B.

Once the user has placed the order, the picker can receive instructions on device 119B to retrieve one or more items 208 from storage unit 210 . A picker can pick an item 208 , scan the barcode on the item 208 , and place it on the transport mechanism 214 . Although the transport mechanism 214 is depicted as a slide, in some embodiments the transport mechanism is implemented as one or more of conveyor belts, elevators, carts, forklifts, wheelbarrows, trolleys, carts, and the like. good too. Items 208 can then reach packing zone 211 .

Packing zone 211 may be the area of FC 200 where items are received from picking zone 209 and packed into boxes or bags for eventual shipment to customers. In packing zone 211, workers assigned to receive items ("living workers") receive items 208 from picking zone 209 and determine which order it corresponds to. For example, a living room worker can use a device such as computer 119C to scan a bar code on item 208 . Computer 119C can visually indicate which order item 208 is associated with. This may include, for example, spaces or "cells" on wall 216 that correspond to orders. Once the order is completed (eg, because the cell contains all the items for the order), the living worker can indicate to the packing worker (or "packer") that the order is complete. Packers can remove items from cells and place them in boxes or bags for shipment. Packers may then manually or otherwise deliver the boxes or bags to hub zone 213 via, for example, forklifts, carts, trolleys, wheelbarrows, conveyor belts.

Hub zone 213 may be an area of FC 200 that receives all boxes or bags (“packages”) from packing zone 211 . Workers and/or machines within the hub zone 213 can pick up the packages 218 , determine the portion of the distribution area to which each package should be sent, and route the packages to the appropriate camp zone 215 . For example, if the distribution area has two smaller sub-areas, the package goes to one of the two camping zones 215 . In some embodiments, a worker or machine (eg, using one of devices 119A-119C) can scan the package to determine its final destination. Routing the package to camp zone 215 may involve, for example, determining a portion of the geographic area to which the package is directed (eg, based on a zip code) and camps associated with the portion of the geographic area. and determining the zone 215 .

A camp zone 215 may, in some embodiments, include one or more buildings, one or more physical spaces, or one or more areas, where packages are routed and/or subrouted. are received from hub zone 213 for sorting into. In some embodiments, camp zone 215 is physically separate from FC 200 , but camp zone 215 may form part of FC 200 in other embodiments.

Workers and/or machines within camp zone 215 can, for example, match destinations with existing routes and/or subroutes, calculate workload by route and/or subroute, time of day, shipping method, and ship package 220. It can be determined which route and/or subroute the package 220 should be associated with, based on the cost to do so, the PDD associated with the items in the package 220, and the like. In some embodiments, a worker or machine (eg, using one of devices 119A-119C) can scan the package to determine its final destination. Once a package 220 has been assigned to a particular route and/or subroute, workers and/or machines can move the package 220 to be shipped. In exemplary FIG. 2, camp zone 215 includes truck 222, automobile 226, and delivery workers 224A and 224B. In some embodiments, truck 222 may be driven by delivery crew 224A, who is a full-time employee who delivers packages of FC 200, truck 222 owns and leases FC 200, or owned, leased or operated by the same company that operates In some embodiments, the vehicle 226 may be driven by a delivery worker 224B, who is a "flex" or temporary worker who delivers on an as-needed (eg, seasonal) basis. Vehicle 226 may be owned, leased, or operated by delivery crew 224B.

FIG. 3 shows an exemplary schematic diagram of a computer-implemented system 300 for personalized package delivery. In some embodiments, the system 300 includes a living room worker 301, a picked item 208 having an order identifier 305 (e.g., barcode, label, tag), and a user interface device 302 (e.g., mobile device/PDA 119B). ) and . The system 300 includes a first storage location 320 (e.g., packing zone 211) that includes storage cells 324 (e.g., 324_1, 324_2) and a second storage location 340 (herein referred to as a campsite) that includes storage cells 344. ) and a delivery truck 201 . First storage location 320 and campsite 340 (eg, campzone 215) may sort items based on different information about the final destination. As an example, first storage location 320 sorts items (e.g., items 208) based on the geographic area to which the package is directed (e.g., based on zip code), and campsite 340 sorts items into delivery routes or sub-routes. Items may be sorted based on (eg, based on route number). (Other sorting methods are possible.) Delivery routes or sub-routes may be predetermined by one or more computer-implemented systems of system 100 . In some embodiments, one or more of computer-implemented system 100 (eg, SAT 101, WMS 119, SCM 117) may be configured to communicate with user interface device 302 to indicate sorting of items. .

FIG. 3 is a diagram illustrating an exemplary personalized package delivery system. As used herein, the term "individualization" refers to the singular shipment of items in a customer order containing multiple items without waiting for the customer order to be fully filled before shipping. Package delivery by individualization can have many advantages over existing systems for package delivery. Package delivery by individualization may, among other things, have some or all of the advantages discussed herein.
i. Improved packing efficiency - In today's existing package delivery system, the living room worker can wait for all items in an order to be packed into a single package, which is then ready for further processing, including sorting or shipping. can be placed in the living wall space associated with a particular order for In contrast, in the individualized package delivery system 300, the packer individually sorts the items in the storage cell (eg, 324_1) without waiting for the other items in the order to arrive at the packer station or packing zone. thus reducing the packer's idle time. Reducing idle time for each packer allows for an overall improvement in packing efficiency.
ii. Increased Picking Density—Currently existing package delivery systems allow pickers to pick items to sequentially fill customer orders. For example, a picker may pick all items for order 1 before picking items for order 2. This sequential approach to picking results in loss of time and efficiency because the picker spends more time traveling than picking items. In contrast, the individualized package delivery system 300 can enable improved picking density because pickers can be tasked with picking items based on their location rather than based on customer orders. For example, a picker may be tasked with picking items that are located in close proximity to their current physical location but may be associated with other customer orders. This parallel approach to picking can increase picking density by reducing the time spent by moving pickers.
iii. Improved Traceability—As shown in FIG. 3, in a personalized package delivery system 300, a worker (eg, worker 301) can track a package (eg, package 208) before starting the process and after completing the process. ) (eg, order identifier 305 and/or location identifier) can be scanned. Additionally, barcodes may be scanned during the process, periodically, or when a prompt is received. For example, information recorded by scanning can be stored in a database of system 100, allowing tracking of packages as they undergo processing. Barcodes on containers or totes can also be scanned, providing information related to the location of items contained in the container during processes such as picking, sorting, packing and shipping, enabling traceability of containers and packages to
iv. Faster Sorting - When receiving items from the packing zone at a campsite (e.g. Camp Zone 215), sort items based on sub-routes or delivery routes without waiting for other items in the order to arrive at the campsite. can do. Because items are sorted based on the sub-root rather than the customer order to which they belong, the shelf life of items can be reduced, thus improving the sort rate. It can also enable better space utilization, improve worker efficiency, shorten cycle times and enrich the customer experience.
v. Reduced storage time - individualizing items allows items to be processed regardless of the status of other items in the order, so items are shelved waiting to be picked, packed, sorted or shipped period can be shortened. Reducing the shelf life of items can reduce associated costs associated with inventory management and reduce the risk of mishandling and misplacement of items.
vi. Reduced “prepare to load” time – In existing package delivery and shipping systems, employees such as workers, drivers, loaders, managers and floor supervisors spend a significant amount of time at the start of a shift or work session. to ensure, for example, that all items belonging to the order are loaded. Such systems can be inefficient in utilizing resources such as manpower and time, both of which can add operational costs and affect throughput. Individualization of items can reduce load preparation time as employees load containers or container carriers, such as totes, cages, etc., onto delivery trucks based on planned delivery areas and delivery routes.
vii. Improved loading and delivery efficiency—Items are placed in large, standardized totes or containers based on delivery routes so they can be loaded more efficiently into delivery trucks. Additionally, items remain in standardized containers until delivery, thus minimizing damage or misplacement due to handling. Large standardized totes or containers allow loaders to follow easy directions for loading trucks and drivers to easily map items and deliver orders more efficiently do.

In some embodiments, system 100 may be configured to receive customer orders. A customer order may include multiple items. In some embodiments, each customer order may include multiple suborders, and each suborder may include multiple items. For example, a customer order may contain three suborders. A first suborder may be a rush order for toothpaste, toothbrush, and mouthwash, a second suborder may include regular delivery for cheese, crackers, and chips, and a third suborder. may include delayed delivery of beverages. System 100 can receive customer orders and generate an order identifier 305 associated with each item ordered. In some embodiments, system 100 identifies a unique suborder identifier associated with each suborder (eg, first suborder suborder identifier 305A, second suborder suborder identifier 305B, and third suborder identifier 305B). can generate a suborder identifier 305C) for the suborder of the .

In some embodiments, the order identifier 305 and sub-order identifiers (eg, 305A, 305B or 305C) include the number of items ordered, the urgency of the items to be delivered, and the destination of the items to be delivered. It can include information that is not limited to these. In some embodiments, order identifier 305 may also include information regarding the number of suborders within a single order. System 100 can send an indication to user interface device 302 that the order includes a number of sub-orders and the urgency associated with each sub-order. Pickers can fulfill orders or suborders accordingly.

In some embodiments, one or more pickers may receive an indication regarding the urgency of suborders while picking items for other customer orders. A picker can pick items for urgent suborders and send the items to packing zone 211 based on their current location within picking zone 209 . For example, if an urgent suborder includes a toothbrush and a pair of socks, then a picker in or near the oral hygiene section can pick up a toothbrush and a picker in or near the clothing section can pick up a pair of socks. resulting in improved picking density. Items may be transported to the packing zone 211 once the container or tote is full. This approach can increase picking efficiency by picking items based on picker location and not based on customer orders, thus reducing cycle time and improving overall delivery efficiency.

In some embodiments, system 100 can send instructions to a user device (eg, smart phone 119B, or computer 119C) to instruct the picker to print order identifier 305 to the device. In some embodiments, the user device can include a handheld device such as a PDA configured to print labels. Alternatively, system 100 may include a printing device (not shown) such as a label printer, inkjet printer, or laser printer. The printing device may be configured to receive instructions from one of the computer-implemented systems of system 100 to print labels, instructions, notes, and the like. The instructions may further include requesting the picker to associate the printed order identifier 305 with the item of the customer order, for example, by affixing the printed order identifier 305 to the picked item 208. In some embodiments, system 100 may be configured to electronically associate order identifier 305 with an item in a customer order. For example, system 100 may update a database containing information related to all incoming customer orders.

Living room worker 301 can receive picked items 208 in packing zone 211 . In some embodiments, living room worker 301 can receive information related to customer orders from system 100 using user interface device 302 (eg, smart phone 119B). User interface devices 302 can include handheld display devices (eg, tablet 119A), smartphones (eg, mobile device/PDA 119B), computers (eg, computer 119C), body-mounted displays, head-mounted displays, etc. is not limited to User interface device 302 may be substantially similar to a mobile device, such as computer 119C of FIG. 1A. User interface device 302 can, for example, communicate with WMS 119 and exchange information.

In some embodiments, user interface device 302 may be configured to display information on a user interface display (not shown in FIG. 3). The user interface display may contain information including information related to the customer order, such as the number of items ordered, the urgency of delivery of the ordered items, the destination location of the items to be delivered, and the like. In some embodiments, the user interface display may be a visual display or an audiovisual display. For example, user interface device 302 may receive an audiovisual message to indicate a request to expedite fulfillment of an order if the order is "urgent." In some embodiments, user interface device 302 may be configured to receive user input and provide feedback to the user via one or more interactive elements of the user interface display. For example, the user interface device 302 can provide an audible, visual, or tactile notification to the user and indicate a request to confirm receipt of the notification via one or more interactive elements of the user interface display. In some embodiments, user interface device 302 may include data recording capabilities, such as barcode scanning, optical character reading devices, etc., to record order identifier 305 information. User interface device 302 may be configured to temporarily store recorded information and later upload it to a database of one of the computer-implemented systems of system 100 . In some embodiments, the user interface device 302 can automatically upload recorded information to a database.

In some embodiments, the user interface device 302 can receive instructions presented via interactive elements of the user interface display to review the order identifier 305 associated with the picked item 208. For example, one of the computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, or SAT 101) causes user interface device 302 to display an instruction for the user to initiate review of order identifier 305 associated with item 208. You can generate instructions to Scrutinizing order identifier 305 can include, for example, by scanning or reading order identifier 305 to determine the final destination for delivery of item 208 . For example, scanning order identifiers (e.g., barcodes) using a barcode scanning device may capture information associated with the order identifier such as the final destination of the items in the order, the urgency of delivery, the number and description of the items ordered. can be displayed. In some embodiments, a customer order may contain several sub-orders and each sub-order may further contain several items. It is understood that items 208 may include packages containing one or more items of a customer order.

Upon determining the final destination for delivery of item 208, living clerk 301 may place item 208 in first storage location 320 based on the determined final destination. First storage location 320 may include storage cells 324 . Each storage cell 324 of the first storage location 320 may be associated with a sortation location. In some embodiments, the first storage location 320 may include a living wall, a storage unit, a storage rack with cells, or a cabinet. Other organized storage means can be used as well.

In some embodiments, items 208 are sorted within storage cells 324 of first storage location 320 based on their destination without regard to the status of the order or other items in the order with which the items may be associated. obtain. In current existing systems, living workers may wait for all items in an order to be picked before the order is sorted for delivery. In contrast, in the disclosed embodiment, each item is treated as an individual order and can be sorted based on destination regardless of the status of other items in the order. This shortens the free time of the living room worker and improves the packing efficiency. In some embodiments, packing efficiency as disclosed herein may be referred to as the number of items packed in a particular time period. For example, package efficiency can be expressed as units per hour (UPH). Other efficiency metrics can be used as well. Item individualization can also reduce the shelf life of an item, defined herein as the length of time that an item is shelved before it is picked, packed, sorted, or shipped, thus reducing inventory management. Reduce associated costs and reduce risk of mishandling or misplacement of items.

In some embodiments, each storage cell 324 may be associated with a campsite 340 . In some embodiments, campsite 340 may be an onsite storage or sorting facility on the premises of FC 200 . In some embodiments, campsite 340 may be a remote off-site storage or sorting facility. The association of each storage cell 324 (eg, 324_1 or 324_2) with a corresponding campsite can be identified using a campsite identifier. Campsite identifiers may include, but are not limited to, labels, barcodes, numbers, or tags. Although only a limited number of storage cells 324 are shown, it is understood that first storage location 320 may include any number of storage cells 324 .

In some embodiments, user interface device 302 instructs living room worker 301 through instructions to place item 208 in corresponding storage cell 324 based on determining the destination location of item 208 . can be notified. For example, based on a customer order, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) can determine campsites to which item 208 may be directed. A living clerk 301 can place an item 208 in a corresponding storage cell 324 .

In some embodiments, living room worker 301 may receive instructions via user interface device 302 to associate item 208 with the corresponding storage cell 324 in which item 208 is located. For example, the living clerk 301 may be required to scan the order identifier 305 and the campsite identifier in order to establish an association between the item 208 and the campsite for sorting. Information relating to the order identifier of the placed item and the campsite identifier of the storage cell in which the item was placed can be automatically updated to a database containing information relating to customer orders and delivery plans for customer orders.

In some embodiments, if campsite 340 is an on-site facility, items may be transported using transportation means such as, for example, conveyor belts, forklifts, pallets, trolleys, or totes. At the offsite facility, delivery trucks and the like may be used to transport the items.

In some embodiments, storage cells 324 may contain one or more items to be transported to corresponding campsites. In some embodiments, a campsite can be referred to as a storage location. For example, campsite 340 may be associated with storage cell 324_1, indicating that items (eg, item 208) placed in storage cell 324_1 may be directed to campsite 340.

In some embodiments, campsite 340 may include one or more storage spaces 342 . The storage space 342 can include, but is not limited to, walls with storage cells, storage units, storage racks with cells, or cabinets. Other organized storage means can be used as well. For example, storage space 342 may include walls with storage cells 344 . Each storage cell 344 may be associated with a subroute for delivery of items 208 .

Workers at campsite 340 may receive one or more items 208 from storage location 320 . A worker (eg, sorter) can peruse the order identifier 305 associated with the picked item 208 . In some embodiments, a worker may receive a notification on user interface device 302 to review order identifier 305 . For example, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) is displayed on user interface device 302 for a worker to initiate review of order identifier 305 associated with item 208. Instructions can be generated. Examining order identifier 305 may include determining the final destination of item 208 .

Once the worker determines the final destination for delivery of the item 208 , the worker can place the item (eg, the item 208 ) in the storage cell 344 based on the determined subroute for the final destination of the item 208 . Each storage cell 344 of campsite 340 may be associated with a subroute.

In some embodiments, the user interface device 302, via instructions, notifies the worker to place the item 208 in the corresponding storage cell 344 based on the determined final destination of the item 208. can be done. For example, based on a customer order, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) can determine storage cell 344 to which item 208 may be directed. Workers can place items 208 into corresponding storage cells 324 based on instructions from user interface device 302 .

The association of each storage cell 344 with a corresponding subroot can be identified using a subroot identifier. A subroute identifier can include, but is not limited to, a label, barcode, number, or tag. Although only a limited number of storage cells 344 are shown, it is understood that campsite 340 may include any number of storage cells 344 .

In some embodiments, items may be sorted within storage cells 344 based on the determined sub-route of final destination for delivery, regardless of the status of the order or other items in the order with which the item may be associated. In current existing delivery systems, sorters may wait for all items in an order to be received before the order is ready for delivery. In contrast, in the disclosed embodiment, each item is treated as an individual order and can be sorted based on the subroute determined for delivery regardless of the status of the other items in the order. This can reduce sorter idle time in the camp zone, thus increasing sorting efficiency and overall package delivery efficiency.

In some embodiments, user interface device 302 may be configured to display instructions for associating item 208 with the corresponding storage cell 344 in which item 208 is located. For example, the instructions may include a request to scan the order identifier 305 and the subroute identifier to establish an association between the item 208 and the subroute for delivery. Information relating to the order identifier 305 of the placed item and the sub-root identifier of the storage cell 344 in which the item was placed can be automatically updated to a database containing information relating to customer orders and delivery plans for customer orders. .

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, tote). All items (eg, item 208 ) in storage cell 344 may be placed within container 350 . In some embodiments, container 350 may be identified using container identifier 355 . Container identifier 355 may include information related to subroots, including subroot identifiers. In some embodiments, container identifier 355 may include information related to campsites and subroutes. For example, the container identifier may include the label CS3_SR1, where CS indicates the origin campsite and SR indicates the designated subroute for delivering the items within the container. Container identifiers 355 can include, but are not limited to, labels, barcodes, numbers, or tags.

In some embodiments, the user interface device 302 is configured to display a notification or instructions for placing the item 208 within the corresponding container 350 based on the determined final destination of the item 208. may For example, based on a customer order, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) can determine containers 350 in which item 208 can be placed. Workers can place items 208 in corresponding containers 350 based on instructions from user interface device 302 .

In some embodiments, the user interface device 302 directs via one or more interactive elements of the user interface display to associate the item 208 with the corresponding container 350 in which the item 208 is placed. may be configured to display For example, the instructions may include a request to scan order identifier 305 and container identifier 355 to establish an association between item 208 and container 350 for package delivery. Information relating to the order identifier 305 of the placed item 208 and the container identifier 355 of the container 350 in which the item was placed can be automatically updated to a database containing information relating to customer orders and delivery plans for customer orders. can.

In some embodiments, one or more containers 350 may be loaded onto a delivery vehicle (eg, delivery truck 201) for delivery to customers. Containers 350 may be placed on delivery trucks 201 based on subroutes. For example, a package or item (eg, item 208) to be delivered at a destination near the beginning of a subroute may be placed near an access door so that a delivery crew can access the package directly. In some embodiments, a container 350 containing expedited orders can be placed near the access door to allow quick access of the package. In some embodiments, subroutes can be adjusted based on order type and urgency or PDD. In some embodiments, both the sub-route and the placement of containers within the delivery truck 201 can be adjusted based on customer orders and PDDs.

Container 350 may be placed on container carrier 360 prior to loading onto delivery truck 201 . Container carriers 360 may include carts, trolleys, cages, baskets, and the like. In some embodiments, container carrier 360 may include an identifier such as a barcode, label, or tag. In some embodiments, user interface device 302 may, via instructions, notify a delivery operator or truck loader to place container 350 on delivery truck 201 based on a predetermined placement. . For example, based on the PDD, one of the computer-implemented systems of system 100 (e.g., transportation system 107) may determine placement of container 350 on container carrier 360, or one or more container carriers 360 on delivery truck 201. placement can be determined. A delivery worker or truck loader places container 350 or container carrier 360 on delivery truck 201 based on decisions made by one of the computer-implemented systems of system 100 (e.g., transportation system 107). be able to. The user interface device 302 may present a representation of the placement of the container 350 within the container carrier 360 and/or the placement of the container carrier 360 within the delivery truck 201 to the delivery operator or truck loader.

In some embodiments, user interface device 302 may be configured to display a representation of placed container 350 and one or more container carriers 360 within delivery truck 201 . Presentation formats may include one of visual, tabular, audio, audiovisual, or a combination thereof. In some embodiments, the user interface display may include a representation of the placed container 350 and container carrier 360 within the delivery truck 201 for the delivery crew.

In some embodiments, the delivery crew is generated by one of the computer-implemented systems of system 100, such as transport system 107, to begin driving on the subroute after delivery truck 201 is loaded. can receive instructions. The delivery crew can receive instructions via a user interface display on user interface device 302 .

Reference is now made to FIG. 4, which illustrates an exemplary flowchart of a process 400 for personalized package delivery, consistent with disclosed embodiments. The process includes receiving a customer order, generating an order identifier based on the customer order, determining an intended final destination for items in the customer order, and picking at least some of the items in the customer order. sorting the picked items based on a two-step sorting process; loading the picked items of the customer order onto a delivery truck without waiting for the rest of the items of the customer order; and shipping the item to the customer.

Overall package delivery efficiency is a metric that depends on the efficiency of each step in the process of shipping packages. Shipping a package from a FC to a customer for fulfillment of an order typically involves multiple steps, most of which must be performed in linear succession. For example, orders can be received and order identifiers can be generated prior to picking, picking can precede sorting, sorting can precede packing, and items are loaded onto delivery trucks. and so on. In other words, each step of the process begins with the completion of the previous step. In such process flows, the overall efficiency of the process is determined by the efficiency at each step. Overall efficiency can be improved by increasing the efficiency of each step, or by increasing the efficiency of at least one step while maintaining the efficiency of other steps. As noted above, "individualization" herein refers to the individual shipment of items in a customer order containing multiple items without waiting for the customer order to be fully filled before shipping, thus reducing cycle time. , can improve package delivery efficiency by reducing idle time for employees involved in the process. In some embodiments, one or more steps of process 400 may be performed by one or more user interface devices (eg, each operated by a user in a different zone of FC 200).

At step 410, one or more computer-implemented systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) may receive a customer order. A customer order may include multiple items. In some embodiments, a customer order may include multiple suborders, and each suborder may include multiple items. One or more computer-implemented systems of system 100 review customer orders and identify information such as the total number of items ordered, a description of each item ordered, requested delivery times, and final destination of the items. may be configured to In some embodiments, one or more computer-implemented systems of system 100 can determine a promised delivery date or time for a customer order based at least on the requested delivery time. For example, in the case of an urgent order request from a customer, the system can determine a promised delivery time of several hours or delivery within 24 hours to the intended final destination. In some embodiments, the system may be configured to individually determine a promised delivery date and time for each item in a customer order. For example, a customer order may include some items for urgent delivery and the remaining items for normal delivery. The system may be configured to determine the promised delivery time based on the requested delivery type.

In some embodiments, one or more computer-implemented systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) can receive multiple customer orders. Each customer order can include multiple items. One or more computer-implemented systems of system 100 may be configured to review and identify common items among multiple customer orders. The user interface device may be configured to display instructions regarding the common item, requesting input from the user, eg, acknowledgment of receipt. The instructions may include information regarding item descriptions, quantity of items ordered, and the like. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders contain a common item, such as water bottles. A worker (eg, a picker) may receive an indication via a user interface device that 50 bottles of water need to be picked. Implementation of this approach can increase picking efficiency and the overall efficiency of the process.

At step 420, one or more computer-implemented systems of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifiers can include barcodes, labels, tags, alphanumeric codes, quick response (QR) codes, and the like. The order identifier may be a machine-readable optical label containing information regarding the customer order. Information included in the order identifier may include, but is not limited to, final destination of the order, total number of items in the customer order, requested delivery type, customer information, promised delivery date and time, and the like. In some embodiments, the system for generating order identifiers determines the storage location (e.g., camp zone 215, hub zone 213) and delivery route to which items in the customer order can belong based on the final destination information of the customer order. can be determined. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or area identified in the final destination, the system can store the items in the customer order. can determine the delivery route of

For example, upon scanning or reading an order identifier using a user interface device with barcode scanning capabilities (eg, user interface device 302), the user interface device can display information associated with the order identifier. . For example, upon scanning or reading an order identifier, the user interface device can display the number of items picked, the number of items remaining to be picked, the promised delivery time, and the time remaining to fulfill the order. .

At step 430, one or more computer-implemented systems of system 100 may instruct the user interface device to display instructions for associating each item of the customer order with an order identifier. The user interface device may be configured to display indications or alerts regarding received customer orders and request input from the user, eg, confirmation of receipt. Upon receiving input from the user, the user interface device can display some or all of the customer order and information related to the customer order. A worker (e.g., a picker) picks one or more items of a customer order and subjects each picked item to one or more computer-implemented It can be associated with an order identifier received from the system. In some embodiments, associating the items of the customer order with the order identifier may include physically printing the order identifier using a label printer or barcode printer. Printed labels or barcodes may be attached or affixed to items, for example, to allow all employees easy access to information related to ordering and delivery schedules. For example, a worker who did not receive or have access to the original order identifier can scan the printed and attached order identifier on the item.

At step 440, one or more computer-implemented systems of system 100 may determine the intended final shipping destination for each of the items in the customer order. As an example, a customer may order a bouquet of flowers to be delivered to a friend's house before 8:00 pm and a battery pack to be delivered to a parent's house within 24 hours. One or more computer-implemented systems of system 100 may generate two separate order identifiers representing the two orders. Each of the items can be directed to a storage location and sorted into a delivery route at the storage location based on the intended final destination.

In some embodiments, one or more computer-implemented systems of system 100 store an intended delivery destination, a storage space (eg, 324/344 in a storage cell) associated with the intended delivery destination, and A delivery route can be determined for delivering customer ordered items at the intended delivery destination.

In some embodiments, the sorting process may be a two-step sorting process. A first step may include sorting the picked items based on the campsites to which the items may be directed. Campsites may be determined, for example, based on the zip code intended as the final delivery destination for items in a customer order. A second step may involve sorting the picked items at the campsite based on the delivery routes that the items can be sent for delivery. Delivery routes may be determined, for example, based on neighborhoods or streets within an area represented by a postal code.

At step 450, one or more computer-implemented systems of systems 100 select a pre-allocated storage space determined by one or more computer-implemented systems of systems 100 (e.g., storage location 320). Based on cell 324), instructions for sorting the picked items of the customer order or instructions for displaying an alert can be sent to the user interface device. Pre-allocated storage space can represent a campsite where items can be directed for further sorting. In some embodiments, campsites may be assigned to one or more storage spaces. For example, storage spaces 1-12 are assigned to campsite 1 represented by storage cell 324_1, storage spaces 13-23 are assigned to campsite 2 represented by storage cell 324_2, and campsite 3 is represented by storage cell 324_2. may be allocated storage space 24 to.

Each sorted item may be transported to a corresponding campsite. In some embodiments, the campsite may be an on-site storage facility on the FC 200 property (eg, camp zone 215). Sorted items can be transported to camp zone 215 using transport devices such as, for example, conveyor belts, forklifts, wheelbarrows, trolleys, carts, and the like. In some embodiments, the campsite may be an offsite storage facility such as a warehouse or storage unit separate from the FC 200 . The sorted items may be transported to an offsite storage facility using, for example, delivery trucks. Sorted items belonging to a customer order can be transported to the campsite without waiting for the remaining items in the customer order, reducing idle time.

At step 460, one or more computer-implemented systems of system 100 send instructions to the user interface device to display instructions or alerts for sorting the items picked at the campsite based on the delivery route. can do. The delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer order. Workers can sort the items picked at the campsite by placing the items in storage cells (eg, storage cell 344) based on delivery routes. Workers can obtain delivery route information, for example, by scanning an item's order identifier. Each storage cell 344 may be identified by a root identifier or a subroot identifier.

At step 470, one or more computer-implemented systems of system 100 issue user interface instructions to display instructions or warnings to place sorted items from storage cell 344 into a container (e.g., container 350). can be sent to the device. Each storage cell 344 may be associated with a container configured to receive items stored in the corresponding storage cell. In some embodiments, each container may be identified with a container identifier that includes information identifying the campsite and storage cell. Picked items belonging to a customer order can be placed in containers without waiting for remaining items of the same customer order to reduce idle time.

Container 350 or container carrier 360 may be loaded into a delivery vehicle (eg, delivery truck 201) configured to receive containers, totes, wheeled cages, carts, trolleys, and the like. Containers may be loaded in configurations based on, for example, delivery routes to reduce unloading time during delivery of items. Placement of containers on delivery trucks may also be based on factors including, but not limited to, urgency of delivery, promised delivery time, whether the item is perishable food, and the like. In some embodiments, the storage compartment of the delivery truck can include built-in storage spaces such as cabinets, cells, shelves, racks, cages, or cages on wheels. Each container carrier within a delivery truck may be identified by a container carrier identifier (eg, barcode). A container carrier identifier may include information relating to the location of the container carrier within the storage bay of the delivery truck. For example, four container carriers 360 may be positioned against the rear wall of the storage compartment and labeled 360_1-360_4 from left to right. Thus, the container carrier located in the left rear corner of the storage bay of the delivery truck may be identified as container carrier 360_1, and the container carrier located in the right rear corner of the storage bay of the delivery truck may be identified as container carrier 360_4. be able to. A visual or tabular representation of the arrangement of container carriers 360 may be generated by one or more computer-implemented systems of system 100, such as transportation system 107, for example.

In some embodiments, the loading arrangement of containers on the container carrier 360 may be recorded to generate a representation of the delivery truck loading arrangement. For example, the transport system 107 scans the container identifiers (e.g., barcodes) of all containers placed on container carriers and instructs the user interface device to display instructions to scan the corresponding container carrier identifiers. can be sent. The system can generate a representation of the loading arrangement based on the scanned information. In some embodiments, the loading arrangement may be presented to the user in tabular or visual form. The stacking arrangement may be printed on a sheet of paper, displayed on a user interface device, or presented to the user prior to beginning the delivery round.

At step 480, one or more computer-implemented systems of system 100, such as transportation system 107, for example, send instructions to a user interface device (eg, one of mobile devices 107A-107C) to can display instructions for shipping items stored in containers loaded into The user interface device can display instructions requesting input from a user (eg, a delivery worker or loader) to verify completion of the loading process before leaving for delivery of the item. . A user interface device can receive input from a user and store the received input in a database associated with system 100 .

In some embodiments, one or more computer-implemented systems of system 100 send instructions to the user interface device to direct recording information associated with the order identifier, such as by scanning the order identifier. can be displayed. After the items are picked, the user interface device sorts the picked items based on storage location in the first step of the sorting process, and before transporting the sorted items to the campsite. After arriving, after sorting the picked items based on the delivery route in the second step of the sorting process, after placing the sorted items in the container, and after loading the container onto the delivery truck, the order identifier. Instructions for recording information can be displayed. Information recorded at all steps of the process may be stored and updated in a database associated with system 100 (eg, associated with or connected to WMS 119 or transportation system 107).

In some embodiments, the system 100 can generate status update notification messages in response to customer inquiries regarding the status of orders based on updated information stored in the database. In some embodiments, the system 100 can proactively generate status update notification messages for customers based on updated information stored in the database.

Reference is now made to FIG. 5, which illustrates an exemplary flowchart of a process 500 for generating a visual representation of a delivery vehicle's loading arrangement, consistent with the disclosed embodiments. It is understood that the flowchart is an exemplary sequence of process steps and that the steps may be performed in other sequences. Additionally, steps may be added, omitted, skipped, repeated, or modified based on application and user requirements.

At step 510, one or more computer-implemented systems of system 100 may identify a delivery vehicle (eg, delivery truck 201) that contains storage space. In some embodiments, transportation system 107 of system 100 may identify delivery vehicles based on, for example, storage space requirements, delivery route characteristics, delivery truck operator experience or ratings, or other data. For example, transportation system 107 may identify small delivery vehicles for delivery routes with narrow roads, and delivery truck operators (eg, truck drivers) only have valid driving permits for small transportation vehicles. may In some embodiments, transportation system 107 may identify delivery vehicles based on storage space requirements. For example, if there are 20 containers full of items to be delivered over a delivery route or subroute, system 100 may recommend a larger delivery vehicle with more storage space.

At step 520, one or more computer-implemented systems, such as transportation system 107 of system 100, send instructions to the user interface device to display instructions for determining the placement of storage spaces within the delivery truck. can be done. In some embodiments, delivery trucks may include built-in storage space within storage compartments, such as cabinets, racks, shelves, cages, and the like. A delivery truck may include storage compartments for accommodating removable storage units, such as wheeled cages.

In some embodiments, each storage space within a delivery truck may be identified using a storage space identifier or container carrier identifier. Container carrier identifiers may include barcodes, labels, tags, or QR codes. The container carrier identifier may include information related to the location of the container carrier 360 within the storage bay of the delivery truck. For example, four container carriers 360 may be positioned against the rear wall of the storage compartment labeled 360_1-360_4 (not shown in FIG. 3) from left to right. Thus, the container carrier located in the left rear corner of the storage bay of the delivery truck may be identified as container carrier 360_1, and the container carrier located in the right rear corner of the storage bay of the delivery truck may be identified as container carrier 360_4. be able to. In some embodiments, the delivery truck may include built-in storage spaces, each storage space having a storage space identifier.

In some embodiments, a delivery truck operator (eg, driver or loader) can record the placement of built-in storage spaces within the delivery truck, eg, by scanning storage space identifiers. In some embodiments, the database of system 100 may include information related to the placement of storage spaces within delivery trucks. For example, the database may contain information related to the placement of 24 storage spaces within delivery truck 14 .

At step 530, one or more computer-implemented systems, such as transportation system 107 of system 100, may generate a container identifier for each container. Container identifiers can include barcodes, labels, tags, or QR codes. The container identifier may include information relating at least to the campsite and delivery route of the items contained in the container. In some embodiments, one or more containers may be assigned to a delivery route based on the number of items delivered along that route. The container identifier can serve as a quick reference or indication of the final intended delivery destination of the items within the container.

At step 540, one or more computer-implemented systems, such as transport system 107 of system 100, may send instructions to a user interface device to display instructions to load the container into the storage space of the delivery truck. Containers can be loaded onto delivery trucks to enable quick access to items to be unloaded during delivery.

At step 550, one or more computer-implemented systems, such as transportation system 107 of system 100, send instructions to the user interface device to display instructions for associating each container with the storage space in which it is located. can do. For example, the transport system 107 scans the container identifiers (e.g., barcodes) of all containers placed in the storage space and instructs the user interface device to display instructions to scan the corresponding storage space identifiers. can be sent. In some embodiments, the instructions may include step-by-step instructions for associating containers with storage spaces and uploading the information to a database of system 100 .

At step 560, one or more computer-implemented systems, such as transportation system 107 of system 100, may generate a visual representation of the container and storage space loading arrangement based on the associations established at step 550. . In some embodiments, the loading arrangement may be presented to a user (eg, delivery truck driver) in tabular or visual form. The loading arrangement may be printed on paper, displayed on a user interface device, or presented to the user prior to beginning the user's shipping round.

In some embodiments, the loading arrangement of the delivery truck may be displayed on the delivery vehicle's user interface display, eg, the delivery truck's graphical user interface display screen. In some embodiments, the visual representation of the loading arrangement may be updated as deliveries are made. For example, if a delivery truck driver delivers an item to a customer and the container is empty, an indication of the loading arrangement may indicate that the item in the container placed in that storage space has been delivered. This information may be updated in the database so that transportation system 107 and/or system 100 can determine whether promised delivery dates and times have been met.

Referring now to Figure 6, Figure 6 is an alternative embodiment of the process 400 described above, showing additional steps performed during the second step of the sorting process. For example, during the second step of the sorting process, items may be picked from campsites and final destinations for delivery, regardless of the order in which the items may be associated or the status of other items in the order. may be sorted based on the determined sub-route of

In some embodiments, the sorting process may be a two-step sorting process. A first step may include sorting the picked items based on the campsites to which the items may be directed. Campsites may be determined, for example, based on the zip code intended as the final delivery destination for items in a customer order. A second step may involve sorting the picked items at the campsite based on the delivery routes that the items can be sent for delivery. Delivery routes may be determined, for example, based on neighborhoods or streets within an area represented by a postal code.

In some embodiments, a mis-sort reduction procedure is performed during the second step of the sorting process, i.e. when the picked items are sorted based on the delivery route/sub-route in the second step of the sorting process. can do. For example, when items are picked from a campsite and placed in containers that are sorted based on delivery routes or subroutes, items can be placed in the wrong container and then in the wrong delivery vehicle. be. This can make it difficult for delivery truck drivers to search and try to find the correct item to the correct destination. One or more computer-implemented systems of system 100 may be configured to provide real-time notifications or alerts to workers (e.g., sorters) 301 when missorts occur, which may indicate missorts. is advantageous for detecting and reducing Reducing mis-sorting can help drivers map items more easily and deliver orders more efficiently.

In some embodiments, one or more computer-implemented systems of system 100, such as transportation system 107, compare destinations to existing routes and/or subroutes, determine the workload of each route and/or subroute, for example. calculation, time of day, shipping method, shipping cost, etc., can determine which route and/or subroute the item 208 should be associated with. In some embodiments, worker 301 or machine can scan item 208 or package 220 (eg, using user interface device 302) to determine its final destination. Once the worker has determined the final destination for delivery of the item 208 , the worker can place the item (eg, item 208 ) within the container 350 based on the determined subroute for the final destination of the item 208 . In some embodiments, items may be sorted based on the determined sub-route of final destination for delivery, regardless of the status of the order or other items in the order with which the item may be associated. For example, upon receipt of items at a campsite (e.g., campsite 215) from a packing zone, the items may be sorted based on sub-routes or delivery routes without waiting for other items in the order to arrive at the campsite. can. Because items are sorted based on the subroute rather than the customer order to which they belong, the dependency on waiting for all items in the customer order can be reduced, thus improving the sort rate. For example, a customer order may include T-shirts, which are less labor intensive and may require less space on the delivery vehicle. Customer orders may also include dining table sets, which are labor intensive and may require longer times to be delivered to campsites for sorting, and also larger delivery vehicles. may need it. Once the items have been sorted at the campsite, the t-shirts may be sorted based on their destination and loaded into delivery vehicles based on the determined delivery area and/or delivery route. In this case, the t-shirts are loaded onto the delivery vehicle in front of the dining table set without waiting for the dining table set, and the t-shirts are placed on the shelf waiting for the dining table set to be picked, packed, sorted, or shipped. You can shorten the time it is placed. In this case, the T-shirts may be delivered to the customer before the dining table is set. This can enable better space utilization, shorter shelf life, improved efficiency, shorter cycle times, and a better customer experience.

In some embodiments, one or more computer-implemented systems of system 100 store items 208 , order identifiers 305 , containers 350 , container identifiers 355 , identification of workers 301 assigned for sorting items 208 . , the user interface device 302 assigned to the worker 301, and the subroute for delivery. In some embodiments, a worker (eg, worker 301) scans a barcode (eg, order identifier 305 and/or location identifier) associated with a package (eg, package 208) before beginning the process. can be scanned. Worker 301 can scan the barcode using user interface device 302 . Upon receiving the barcode from user interface device 302, system 100 processes container 350, container identifier 355, worker 301 assigned to sort item 208, user interface device 302 assigned to worker 301, and item 208 and A subroute for delivery associated with the order identifier 305 can be identified. The system 100 can store an identified information system 100 that can maintain a mapping table, which includes all identified information, such as associated items 208, order identifiers 305, containers 350, container Identifier 355, identification information of worker 301 assigned to sort item 208, and user interface device 302 assigned to worker 301 may be stored in a tabular format. The mapping table can be stored in a database containing information related to customer orders and delivery schedules for customer orders.

In some embodiments, items 208 may arrive at a campsite where they are sorted into delivery vehicles. Worker 301 can scan the bar code and order identifier 305 of item 208 in a customer order. Upon scanning, system 100 can retrieve information associated with item 208 from the mapping table, which can be sent to worker 301 . This information can include the container 350 in which the item 208 needs to be sorted. Worker 301 may receive instructions from system 100 specifying containers 350 in which items 208 need to be sorted. Worker 301 can then use user interface device 302 to place item 208 into container 350 and scan container identifier 355 . For example, information recorded by scanning can be stored in a database of system 100, allowing tracking of packages as they undergo processing. A barcode on the container (e.g., container identifier 355) or tote can also be scanned to provide information related to the location of the items contained in the container during processes such as picking, sorting, packing, shipping, and the like. In some embodiments, system 100 can maintain a mapping table that maps all scanned information to, for example, item 208, order identifier 305, container 350, container identifier 355, and item 208. The identities of the workers 301 assigned to sorting and the user interface devices 302 assigned to the workers 301 can be recorded in tabular form. The mapping table may be automatically updated in real-time as worker 301 scans the order identifiers and containers 305 in which items are sorted using user interface device 302 . In some embodiments, one or more computer-implemented systems of system 100 use the scan data from worker 301 to determine whether an exception event has occurred, and the data stored at the start of the process. Data can be analyzed. In some embodiments, the exception event is the information stored and the item 208, the order identifier 305, the container 350, the container identifier 355, and the worker 301 assigned for sorting the item 208 and the worker 301 can occur when there is a mismatch between the scanned information associated with one or more of the scanned inputs from . In some embodiments, the associations between items 208, order identifiers 305, containers 350, container identifiers 355, and identities of workers 301 assigned to sort items 208 are stored in system 100. It can be accessed, stored, updated or modified in one or more connected databases.

In some embodiments, workers 301 can oversee the sorting of items 208 into containers 305 associated with container identifiers 355 . In some embodiments, worker 301 using user interface device 302 may receive instructions to scan item 208 and container identifier 355 in which item 208 is located. Worker 301 can scan item 208 and container identifier 355 using user interface device 302 . In some embodiments, the exception event is the information stored and the item 208, the order identifier 305, the container 350, the container identifier 355, and the worker 301 assigned for sorting the item 208 and the worker 301 can occur when there is a mismatch between the scanned information associated with one or more of the scanned inputs from . In an exemplary embodiment, system 100 can compare scanned information, such as order identifier 305 and container identifier 355, to stored information to determine whether an exception event has occurred. This can occur if the items 208 are missorted and placed in a container not intended for the items 208 . When an exception event occurs, the worker 301 overseeing the sorting of the items 208 can be notified in real time that a sorting error has occurred. This notification or warning may be provided by system 100 to worker 301 on user interface device 302 . Alternatively, the exception event notification can be displayed on a large display screen that can be viewed by worker 301 or the floor manager/supervisor.

At step 610, one or more computer-implemented systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) may receive a customer order. A customer order may include multiple items. In some embodiments, a customer order may include multiple suborders, and each suborder may include multiple items. One or more computer-implemented systems of system 100 review customer orders and identify information such as the total number of items ordered, a description of each item ordered, requested delivery times, and final destination of the items. may be configured to

At step 620, one or more computer-implemented systems of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifiers 305 can include barcodes, labels, tags, alphanumeric codes, quick response (QR) codes, and the like. Order identifier 305 may be a machine-readable optical label containing information regarding the customer order. Information included in the order identifier 305 may include, but is not limited to, final destination of the order, total number of items in the customer order, requested delivery type, customer information, promised delivery date and time, and the like. .

In some embodiments, the system 100 for generating order identifiers determines the storage location (e.g., camp zone 215, hub zone 213) to which items in a customer order can belong as well as the delivery location based on the final destination information of the customer order. Roots and/or subroots can be determined. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or area identified in the final destination, the system can store the items in the customer order. can determine the delivery route of

As described above with reference to FIG. 4, upon scanning or reading the order identifier using, for example, a user interface device with barcode scanning capabilities (eg, user interface device 302), the user interface device reads the order. Information associated with the identifier can be displayed. For example, upon scanning or reading an order identifier, user interface device 302 may display the number of items picked, the number of items remaining to be picked, the promised delivery time, and the time remaining to fulfill the order. can.

At step 630 , one or more computer-implemented systems of system 100 may associate each item of the customer order with an order identifier 305 . User interface device 302 may be configured to display indications or alerts regarding received customer orders and request input from a user (eg, worker 301), eg, confirmation of receipt. Upon receiving input from the user, the user interface device 302 can display some or all of the customer order and information related to the customer order. A worker 301 (e.g., picker) picks one or more items of a customer order and sends each picked item to one or more computers, e.g., by scanning the item's order identifier and barcode. It can be associated with the order identifier 305 received from the implementing system. In some embodiments, associating the items of the customer order with the order identifier may include physically printing the order identifier using a label printer or barcode printer. Printed labels or barcodes may be attached or affixed to items, for example, to allow all employees easy access to information related to ordering and delivery schedules. For example, a worker who did not receive or have access to the original order identifier can scan the printed and attached order identifier on the item.

In some embodiments, a worker 301 (eg, sorter) assigned to sort items receives item 208 and determines which customer order it corresponds to. For example, worker 301 can scan a barcode on item 208 using a device such as user interface device 302 . When worker 301 scans item 208, one or more computer-implemented systems of system 100 process all items in the customer order for sorting based on container 350, container identifier 355, and the item's determined final destination. Determines the root or subroot of the items in . Items 208 may be sorted based on delivery routes or sub-routes. A delivery route or subroute may be predetermined by one or more computer-implemented systems of system 100 . In some embodiments, one or more of computer-implemented system 100 (eg, SAT 101, WMS 119, SCM 117) may be configured to communicate with user interface device 302 to indicate sorting of items. .

At step 640, one or more computer-implemented systems of system 100 may determine the intended final shipping destination for each of the items in the customer order. In some embodiments, one or more of the computer-implemented systems of system 100 include an intended delivery destination, a storage space container (e.g., storage cell 324/344) associated with the intended delivery destination, a corresponding A container 350 configured to receive the items stored in the storage cell, and a delivery route for delivering the customer ordered items at the intended delivery destination can be determined.

As an example, a customer may order a bouquet of flowers to be delivered to a friend's house before 8:00 pm and a battery pack to be delivered to a parent's house within 24 hours. One or more computer-implemented systems of system 100 may generate two separate order identifiers representing the two orders. Each item may be directed to a storage location (eg, storage cell 344) and sorted into delivery routes at the storage location based on the intended final destination. Each storage cell can be associated with a container configured to receive items stored in the corresponding storage cell. In some embodiments, each container may be identified with a container identifier that includes information identifying the campsite and storage cell.

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, tote). All items (eg, item 208 ) in storage cell 344 may be placed within container 350 . In some embodiments, container 350 may be identified using container identifier 355 . Container identifier 355 may include information related to subroots, including subroot identifiers. In some embodiments, container identifier 355 may include information related to campsites and subroutes. For example, the container identifier may include the label CS3_SR1, where CS indicates the origin campsite and SR indicates the designated subroute for delivering the items in the container. Container identifiers 355 can include, but are not limited to, labels, barcodes, numbers, or tags.

At step 650, process 600 may include additional steps by which one or more computer-implemented systems of system 100 may store information associated with customer orders based on order identifiers 305 in a mapping table. . Information may include containers 350 associated with items 208, container identifiers 355 associated with each container 350, and delivery routes or subroutes. In some embodiments, a worker (eg, worker 301) can scan a barcode (eg, order identifier 305 and/or location identifier) associated with a package (eg, package 208). Worker 301 can scan the barcode using user interface device 302 . Upon receiving the barcode from user interface device 302 , system 100 processes container 350 , container identifier 355 , worker 301 assigned to sort item 208 , user interface device 302 assigned to worker 301 , and order identifier 305 . can determine a route or subroute for delivery associated with the . The system 100 can maintain a mapping table, which can store, for example, in tabular form all the determined information, mapping item 208 to order identifier 305, container 350, container identifier 355, item 208, and so on. , a route or subroute for delivery, and a user interface device 302 assigned to the worker 301 .

At step 660, one or more computer-implemented systems of systems 100 select a pre-allocated storage space determined by one or more computer-implemented systems of systems 100 (e.g., storage of storage location 320). Based on cell 324), instructions for sorting the picked items of the customer order or instructions for displaying an alert can be sent to the user interface device. Pre-allocated storage space can represent a campsite where items can be directed for further sorting. In some embodiments, campsites may be assigned to one or more storage spaces. For example, storage spaces 1-12 are assigned to campsite 1 represented by storage cell 324_1, storage spaces 13-23 are assigned to campsite 2 represented by storage cell 324_2, and campsite 3 is represented by storage cell 324_2. may be allocated storage space 24 to.

Each sorted item may be transported to a corresponding campsite. In some embodiments, the campsite may be an on-site storage facility on the FC 200 property (eg, camp zone 215). Sorted items can be transported to camp zone 215 using transport devices such as, for example, conveyor belts, forklifts, wheelbarrows, trolleys, carts, and the like. In some embodiments, the campsite may be an offsite storage facility such as a warehouse or storage unit separate from the FC 200 . The sorted items may be transported to an offsite storage facility using, for example, delivery trucks. Sorted items belonging to a customer order can be transported to the campsite without waiting for the remaining items in the customer order, reducing idle time.

At step 670, one or more computer-implemented systems of system 100 sort the items picked at the campsite based on the delivery route, and sort the sorted items from storage cells 344 into containers (e.g., containers 350). Instructions can be sent to the user interface device to display instructions or warnings to enter. The delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer order. Workers can sort the items picked at the campsite by placing the items in storage cells (eg, storage cells 344) based on delivery routes. Workers can obtain delivery route information, for example, by scanning an item's order identifier. Each storage cell 344 may be identified by a root identifier or a subroot identifier. Each storage cell 344 may be associated with a container configured to receive items stored in the corresponding storage cell. In some embodiments, upon receiving input from a user (eg, a scanned order identifier), the user interface device 302 can display some or all of the customer order and information related to the customer order. A worker 301 (e.g., sorter) identifies an order identifier 305 based on container identifiers 355 received from one or more computer-implemented systems, such as by scanning order identifiers 305 and item 208 barcodes. One or more items of the customer order in the associated container 350 can be sorted. To reduce idle time, one or more items can be placed in a container without waiting for the remaining items of the same customer order.

In some embodiments, worker 301 can receive a single customer order with multiple items to be shipped to the same shipping address. It may be desirable that items within an order can be shipped separately so that certain items may arrive before other items. In some embodiments, the sorting instructions may include additional details such as the sorting and shipping order required to most efficiently place all items in the designated container. In some embodiments, if one or more items in an order are not immediately available, the remaining items in the order can be shipped to the customer first, and the missing items will be It can be shipped later after it becomes available. For example, in situations where one or more of the items in the order are perishable, the system 100 may need to deliver these items to their intended final destination within hours, and the missing items later. It can be determined that it can be delivered. In this situation, system 100 can present this to worker 301 along with information related to the customer order, including the container identifier. Workers 301 (eg, sorters) can then sort one or more of the customer-ordered perishable items in designated containers 350 . One or more items can be placed in a container for loading onto a delivery truck without waiting for other items in the customer order. In some embodiments, system 100 may be configured to determine a promised delivery date and time for each item in a customer order individually. For example, a customer order may include some items for urgent delivery and the remaining items for normal delivery. The system may be configured to determine the promised delivery time based on the requested delivery type. In this situation, system 100 can show worker 301 the items listed for previous deliveries. A worker 301 (eg, a sorter) can then sort one or more of the customer ordered items in the container 350 . One or more items can be placed in a container for loading onto a delivery truck without waiting for other items in the customer order. By implementing this technique of individual shipment of items in a customer order containing multiple items without waiting for the customer order to be fully filled before shipping, the sorting efficiency and overall efficiency of the process can be increased. can. Implementation of this approach can also improve package delivery efficiency by reducing cycle time and reducing employee idle time involved in the process.

At step 680, one or more computer-implemented systems of system 100 use the scanned order identifier 305 and the container identifier 355 of the container 350 in which the item was placed to determine if an exception event has occurred. Information stored in a mapping table can be compared for the same customer order. In some embodiments, as described above, the exception event is the stored information and the work assigned for the sorting of item 208, order identifier 305, container 350, container identifier 355, and item 208. This can occur when there is a discrepancy between the worker 301 and the scanned information related to one or more of the scanned inputs from the worker 301 . For example, worker 301 may sort item 208 into the wrong container, i.e., a container not intended for item 208, if a discrepancy between order identifier 305 and container identifier 355 is detected. , so an exception event may occur.

In some embodiments, worker 301 may place item 208 at a designated location, but may scan the next order identifier instead of scanning the container identifier in which item 208 is placed. . In this case, a discrepancy between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 may scan items associated with different order identifiers and sort them into containers 350 associated with order identifier 305 . In this case, a discrepancy between order identifier 305 and container identifier 355 may be detected. In some embodiments, instead of scanning container identifier 355, worker 301 may scan order identifier 305 multiple times. In this case, a discrepancy between order identifier 305 and container identifier 355 may be detected. In some embodiments, operator 301 may scan container identifier 355 multiple times instead of first scan order identifier 305 before scanning container identifier 355 . In this case, a discrepancy between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 can scan items 208 associated with transparent order identifiers instead of order identifiers 305 . In this case, a discrepancy between order identifier 305 and container identifier 355 may be detected.

At step 690, one or more computer-implemented systems of system 100 send a notification to user interface device 302 that an exception event has occurred. In some embodiments, the notification may be displayed on the screen of user interface device 302 . Notifications displayed may include miss-scan standards due to exception events occurring. In some embodiments, notifications may be sent and displayed on user interface device 302 in real time. In some embodiments, user interface device 302 can set off an alarm or warning message when notification of an exceptional event is received. In some embodiments, the notification may be displayed on a large monitor screen in the camp zone, campsite, or any other area within the fulfillment center. It can alert the floor manager/superintendent when an exception event occurs and notify the respective sorter/operator of the error.

In some embodiments, worker 301 can receive reports on user interface device 302 . One or more computer-implemented systems of system 100 may execute applications, including primary or native application software. When an exception event occurs, the system 100 displays on the dashboard via a large monitoring screen one or more of the picking zone, packing zone, hub zone, camp zone, or any other area within the fulfillment center. Notifications can be displayed. System 100 can send a notification to user interface device 302 that an exception event has occurred. In some embodiments, system 100 for worker 301 to deliver notifications or alerts on user interface device 302, including but not limited to text messages, SMS, phone calls, or in-app notifications. can provide multiple channels of Notifications can be displayed on the user interface device 302 in the form of icons, badges on application icons, status bar formats, reports, or tabular formats, or as more detailed messages on the user interface device 302.

FIG. 7 is a schematic diagram of an exemplary notification dashboard consistent with the disclosed embodiments; The notification dashboard can be displayed to workers 301 (eg, sorters) and floor supervisors or managers on user interface devices 302 or large display screens within the camp zone. In an exemplary embodiment, the dashboard displays notifications in miss-scan standards because an exception event has occurred. In some embodiments, the mapping table may include an association between order identifier 305a, container identifier CS3_SR1_a, and worker 301a based on the root or sub-root of item 208. Once worker 301a scans the item associated with order identifier 305a, user interface device 302 may direct worker 301a to place item 208 in the container (or tote) associated with container ID CS3_SR1_a. . This information may be stored in a mapping table. For exceptional events, there may be discrepancies between these identifiers, as shown in FIG. For example, in some embodiments, worker 301a can place item 208 in a container associated with container identifier CS3_SR1_b. Worker 301 can scan the container identifier CS3_SR1_b in which item 208 is located. When system 100 receives the scanned data, system 100 compares the information stored in the mapping table with the scanned data received from worker 301a and determines that there may be a mismatch between the two. , in which case an exception event is raised.

In some embodiments, an exception event may occur when operator 301 scans the wrong container (or tote). For example, worker 301a may place item 208 in the container associated with container identifier CS3_SR1_a, but may scan an unrelated container, namely the container associated with container identifier CS3_SR1_b. In this case, system 100 can compare the scanned data to the data stored in the mapping table and determine that there may be a mismatch. The mapping table may contain data with an association between the order identifier 305a and the container identifier CS3_SR1_a, which is different from the scanned data and exception events may occur.

In some embodiments, an exception event may occur when worker 301a scans an order using the wrong device. For example, worker 301a may use interface device 302 assigned to worker 301b. Worker 301 may place item 208 in the container associated with container identifier CS3_SR1_a, but may scan a different container, namely the container associated with container identifier CS3_SR1_b. In this case, system 100 can detect discrepancies between container identifiers, order identifiers, and worker identifiers. The system 100 can alert the floor manager/supervisor by displaying a notification on the large display screen that an exceptional event may have occurred.

In some embodiments, an exception event may occur when operator 301a may miss scanning a container after scanning the order identifier. For example, worker 301a can place item 208 in the container associated with container identifier CS3_SR1_a, but when scanning a different order identifier 305b or rescanning a previous order identifier, e.g., order identifier 305a. There is In this case, system 100 may determine that there may be an exception event due to missing container (or tote) scans.

In some embodiments, an exception event may occur when worker 301 may miss scanning the next order identifier. For example, worker 301a can scan order identifier 305a and place item 208 in the container associated with container identifier CS3_SR1_a. After this, instead of scanning order identifier 305b, operator 301a may rescan the container associated with container identifier CS3_SR1_a. In this case, system 100 may determine that there may be an exception event due to a failed invoice scan.

Although the disclosure has been shown and described with reference to specific embodiments thereof, it will be appreciated that the disclosure may be practiced in other environments without modification. The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations will become apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments. Furthermore, although aspects of the disclosed embodiments are described as being stored in memory, those skilled in the art will appreciate that these aspects may be stored in secondary storage, such as a hard disk or CDROM, or other forms of RAM or ROM; It will be appreciated that it may be stored on other types of computer readable media such as USB media, DVDs, Blu-rays, or other optical drive media.

Computer programs based on the descriptions and disclosed methods are within the skill of an expert developer. The various programs or program modules may be created using any of the techniques known to those skilled in the art, or may be designed in conjunction with existing software. For example, a program section or program module may be . Net Framework, . .NET Compact Framework (and related languages such as Visual Basic, C), Java, C++, Objective-C, HTML, combined HTML/AJAX, XML, or HTML, including Java applets. can.

Moreover, while exemplary embodiments have been described herein, equivalent elements, modifications, omissions, (e.g., changes in aspects across the various embodiments) will be understood by those skilled in the art based on this disclosure. ) Any and all ranges of embodiments with combinations, adaptations, and/or modifications are possible. Claim limitations should be construed broadly based on the language used in the claims and not limited to the examples set forth herein or interpreted during prosecution. shall be The examples should be construed as non-exclusive. Additionally, the steps of the disclosed methods may be modified in any manner, including reordering steps and/or inserting or deleting steps. It is therefore intended that the specification and examples be considered as exemplary only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.

Claims (20)

A computer-implemented system for sorting packages, comprising:
The computer-implemented system comprises:
memory storage for storing computer-executable instructions;
one or more processors that execute the stored instructions;
including
The plurality of instructions are
generating an order identifier based on a received customer order, the order including a plurality of items;
associating each item of the customer order with the order identifier;
determining a storage container associated with each item, a container identifier associated with each container, and a delivery route based on the order identifier;
storing in a mapping table an association between each item of the plurality of items of the customer order and the container identifier based on the order identifier;
transmitting to at least one user device a first instruction to initiate a first sorting process for sorting one or more items of the plurality of items based on the mapping;
Sorting the one or more items of the plurality of items based on the first representation;
receiving from at least one user device a first input related to the status of the first sorting process;
Associated with the sorter are second instructions for sorting each sorted item based on the delivery route using a second sorting process regardless of the status of the first sorting process. transmitting to at least one user device for display;
receiving second input from at least one user device related to the status of the second sorting process;
comparing the order identifier to the container identifier after the second sorting process;
detecting, based on the comparison, that an exception event has occurred in the second sorting process;
sending a notification that the exception event has occurred to at least one user device associated with the sorter;
A computer-implemented system, comprising: The processor further
determining an order identifier;
determining a container identifier;
correlating the order identifier to the container identifier using the mapping table, the mapping table for each of the plurality of items of the customer order mapped to the container identifier based on the order identifier; correlating the order identifier, including a list of items, with the container identifier;
determining that there is a mismatch between the order identifier and the container identifier;
2. The computer-implemented system of claim 1, wherein the computer-implemented system is configured to: The processor further
Based on the detected mismatch between the order identifier and the container identifier, send instructions to at least one user device to resort one or more items of the plurality of items. 3. The computer-implemented system of claim 2, wherein the computer-implemented system is configured to: The processor further
3. The computer implementation of claim 2, configured to perform sending information associated with the detected exception event to a display device separate from the at least one user device for display. system. 5. The computer-implemented system of claim 4, wherein the information related to the detected exception event includes the cause of the exception event in real time. The processor further
2. The computer-implemented system of claim 1, configured to detect successful completion of the second sorting process and generate a status update. The processor further
7. The computer-implemented system of claim 6, configured to perform sending the updated status-related information to a display device separate from the at least one user device for display. . The processor further
configured to perform, upon successful completion of said second sorting process, deleting said mapping between each item of said plurality of items of said customer order and said container identifier based on said order identifier; 7. The computer-implemented system of claim 6, wherein: The processor further
2. The computer-implemented system of claim 1, configured to perform receiving input from at least one user device including information related to at least one of the order identifier or the container identifier. The exception event is
receiving scan events that include invoice identifiers and scan events that include unrelated container identifiers;
receiving a first scan event including a first order identifier from a first user device followed by a second scan event including a second order identifier from said first user device; ,
receiving a scan event including a first bill identifier followed by a second scan event including a second bill identifier;
receiving a scan event including a first container identifier followed by a second scan event including a second container identifier;
Receiving a first scan event including a first order identifier from a first user device followed by a second scan event including the first order identifier from the first user device. and,
2. The computer-implemented system of claim 1, triggered upon detecting one or more of: A computer-implemented method for sorting packages, comprising:
The computer-implemented method comprises:
using the computer-implemented system to generate an order identifier based on a received customer order, the order including a plurality of items;
associating each item of the customer order with the order identifier;
determining a storage container associated with each item, a container identifier associated with each container, and a delivery route based on the order identifier;
storing in a mapping table an association between each item of the plurality of items of the customer order and the container identifier based on the order identifier;
transmitting to at least one user device a first instruction to initiate a first sorting process for sorting one or more items of the plurality of items based on the mapping;
Sorting the one or more items of the plurality of items based on the first representation;
receiving from at least one user device a first input related to the status of the first sorting process;
Associated with the sorter are second instructions for sorting each sorted item based on the delivery route using a second sorting process regardless of the status of the first sorting process. transmitting to at least one user device for display;
receiving second input from at least one user device related to the status of the second sorting process;
comparing the order identifier to the container identifier after the second sorting process;
detecting, based on the comparison, that an exception event has occurred in the second sorting process;
sending a notification to the at least one user device associated with the sorter that the exception event has occurred;
A computer-implemented method, comprising: Detecting the exception event includes:
determining an order identifier;
determining a container identifier;
correlating the order identifier to the container identifier using the mapping table, the mapping table for each of the plurality of items of the customer order mapped to the container identifier based on the order identifier; correlating the order identifier, including a list of items, with the container identifier;
determining that there is a mismatch between the order identifier and the container identifier;
12. The computer-implemented method of claim 11, comprising: The computer-implemented method comprises:
Based on the detected mismatch between the order identifier and the container identifier, send instructions to at least one user device to resort one or more items of the plurality of items. 13. The computer-implemented method of claim 12, further comprising: The computer-implemented method comprises:
12. The computer-implemented method of claim 11, further comprising transmitting information associated with the detected exception event to a display device separate from the at least one user device for display. 15. The computer-implemented method of claim 14, wherein the information related to the detected exception event includes the cause of the exception event in real time. The computer-implemented method comprises:
12. The computer-implemented method of claim 11, further comprising detecting successful completion of the second sorting process and generating a status update. The computer-implemented method comprises:
17. The computer-implemented method of claim 16, further comprising transmitting the updated status-related information to a display device separate from the at least one user device for display. The computer-implemented method comprises:
17. Further comprising upon successful completion of said second sorting process, deleting said mapping between each item of said plurality of items of said customer order and said container identifier based on said order identifier. A computer-implemented method as described in . The computer-implemented method comprises:
12. The computer-implemented method of claim 11, further comprising receiving input from at least one user device including information related to at least one of the order identifier or the container identifier. The exception event is
receiving scan events that include invoice identifiers and scan events that include unrelated container identifiers;
receiving a first scan event including a first order identifier from a first user device followed by a second scan event including a second order identifier from said first user device; ,
receiving a scan event including a first bill identifier followed by a second scan event including a second bill identifier;
receiving a scan event including a first container identifier followed by a second scan event including a second container identifier;
Receiving a first scan event including a first order identifier from a first user device followed by a second scan event including the first order identifier from the first user device. and,
12. The computer-implemented method of claim 11, triggered upon detecting one or more of:

Images