KR20210147814A - Computerized systems and methods for package delivery error detection - Google Patents

Abstract

Embodiments of the present disclosure include computer-implemented systems and methods for package delivery. The method may include receiving a customer order, generating an order identifier, associating each item in the customer order with the order identifier, and determining an intended shipping address for each item. The method comprises the steps of: displaying a first indication to cause the user device to classify each item based on a storage space associated with the intended shipping address; displaying a second indication to classify each item classified based on the delivery route; displaying a third indication to place each item sorted into a container, regardless of the status of other items in the customer order; and displaying a fourth indication to deliver the contained one of the plurality of items to the intended delivery address, regardless of the status of other items in the customer order.

Description

COMPUTERIZED SYSTEMS AND METHODS FOR PACKAGE DELIVERY ERROR DETECTION

This application is a continuation-in-part of now-pending U.S. Patent Application No. 16/416,909, filed on May 20, 2019, all of which are incorporated herein by reference in their entirety.

The present disclosure relates generally to computer systems and methods for package delivery for fulfilling customer orders. In particular, embodiments of the present disclosure provide creative and non-traditional computer systems, methods and users for efficiently fulfilling customer orders and delivering packages with reduced cycle times, while maintaining high operator efficiency in multiple areas within a fulfillment center. It's about interfaces.

Fulfillment centers (FCs) allow e-commerce merchants to outsource warehousing and shipping. FCs inventory management is essential to building the best customer experience for online shoppers. Inventory management can include many steps from receiving goods from a seller, to loading received goods for easy pickup access, packing items, validating orders, and delivering packages. Although existing FCs and systems for inventory management within FCs are configured to handle incoming and outgoing goods in bulk, there may be limitations to the efficiency and timeliness of fulfillment of customer orders, which may, in part, be in order to fulfill orders. This is due to inefficient practices in obtaining items. Delays in package delivery can cause customer dissatisfaction and, in some cases, affect the cost and profitability of the business.

With the development and widespread acceptance of e-commerce, internet shopping provides a one-stop shop for all your shopping needs, including food, furniture, electronics, clothes, books and more. Each online order typically includes a combination of a wide variety of categories of items. In existing order fulfillment practices, the system may be utilized to obtain each individual item belonging to an order in an efficient manner, but the overall effectiveness of order delivery is limited by the ability to obtain each individual item. For example, items are stored in different sections of the FC primarily based on category, and the packer may have to wait for the picker to pick up all the items in the order before all items in the order are packed. This can delay the packing and subsequent steps in the process of delivering the package to the customer, which can delay the throughput of the system and the effectiveness of the computerized system controlling the shipping process.

Also, since items are picked up individually, but packed simultaneously into one container before being loaded as packages on a delivery truck, this can affect the overall efficiency and throughput of the FC. Expected or unexpected delays in packing can affect pickup efficiency if the storage space where the picked up items are stored is not accessible. The process of storing a package and shipping it out of FC includes multiple steps such as receiving, loading, picking up, sorting, packing, loading, delivering, and verifying order accuracy at each step. For a high overall efficiency, the individual step efficiency must also be high. For example, if a process includes 10 steps, and each step is more than 90% efficient, the overall efficiency is only 83.9%.

Additionally, existing FCs employ teams of workers to ensure smooth 24-hour operation. One of the technical challenges of a warehouse may be to quickly communicate information such as urgent customer orders, priority shipments, etc. to workers on that floor. Existing logistics and inventory management systems lack the ability to efficiently handle anticipated or unexpected urgency for customer orders, which can increase customer dissatisfaction and associated inventory costs.

Therefore, there is a need to implement an improved method and system for efficient package delivery by singulation in order to reduce cycle time and promised delivery time while maintaining high overall throughput and efficient use of resources.

One aspect of the present disclosure relates to a computer implemented method for package delivery. The method receives a customer order, generates an order identifier based on the customer order, associates each item of a plurality of items in the customer order with the order identifier, and based on the order identifier, an intended shipping destination for each item. , determining the storage space and delivery route associated with the intended delivery location. The method includes: sending, to a user-device for display, a first indication to classify each item of the plurality of items based on a storage space associated with an intended shipping address, using a first sorting process; receive, from the at least one user-device, a first input related to a state of a first classification process; a second to classify each sorted item based on a delivery route configured to include the intended delivery destination, using the second sorting process, regardless of the state of the first sorting process, to the at least one user-device for display. transmit an indication; receive, from the at least one user-device, a second input related to a state of a second classification process; sending, to the at least one user-device for display, a third indication to place each classified item in a container associated with the delivery route, regardless of the state of the second sorting process; and sending, to the at least one user-device for display, a fourth indication to deliver the contained item of the plurality of items to the intended delivery location, regardless of the status of the remaining ones of the plurality of items in the customer order. can

Another aspect of the present disclosure relates to a computer implemented method for package delivery. The method receives a customer order, generates an order identifier based on the customer order, associates each item of a plurality of items in the customer order with the order identifier, and based on the order identifier, an intended shipping destination for each item. , determining the storage space and delivery route associated with the intended delivery location. The method includes sending, to a user-device for display, a first indication to classify each item of the plurality of items based on a storage space associated with an intended shipping address, using a first sorting process; receive, from the at least one user-device, a first input related to a state of a first classification process; a second to classify each sorted item based on a delivery route configured to include the intended delivery destination, using the second sorting process, regardless of the state of the first sorting process, to the at least one user-device for display. transmit an indication; receive, from the at least one user-device, a second input related to a state of a second classification process; sending, to the at least one user-device for display, a third indication to place each classified item in a container associated with the delivery route, regardless of the state of the second sorting process; receive, from the at least one user-device, a third input comprising information associated with a container identifier of the container; sending, to the at least one user-device for display, a fourth indication to deliver the contained one of the plurality of items to the intended delivery location, regardless of the status of the remaining ones of the plurality of items in the customer order; receive, from the at least one user-device, a fourth input comprising information associated with a delivery schedule of the contained item of the plurality of items; and storing the first input, the second input, the third input, and the fourth input in a database associated with the computer implemented system.

Another aspect of the present disclosure relates to a computer implemented system for package delivery. The system includes a memory storing instructions, and at least one processor configured to execute the instructions, the instructions receiving a customer order, generating an order identifier based on the customer order, and each of a plurality of items in the customer order. Associating the items with the order identifier, and determining for each item an intended delivery destination, a storage space associated with the intended delivery address, and a delivery route. The processor is configured to send, to the user-device for displaying, a first indication to classify each item of the plurality of items based on a storage space associated with the intended shipping address, using the first sorting process; receive, from the at least one user-device, a first input related to a state of a first classification process; a second to classify each sorted item based on a delivery route configured to include the intended delivery destination, using the second sorting process, regardless of the state of the first sorting process, to the at least one user-device for display. transmit an indication; receive, from the at least one user-device, a second input related to a state of a second classification process; sending, to the at least one user-device for display, a third indication to place each classified item in a container associated with the delivery route, regardless of the state of the second sorting process; and send, to the at least one user-device for display, a fourth indication to deliver the contained one of the plurality of items to the intended delivery location, regardless of the status of the remaining ones of the plurality of items in the customer order; can

Another aspect of the present disclosure relates to a computer implemented system for classifying packages. The system may include a memory storing instructions and at least one processor, the processor generating an order identifier based on the received customer order, the order comprising a plurality of items; 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; store, in a mapping table, an association between each item of the plurality of items in the customer order and the container identifier based on the order identifier; send a first indication to the at least one user-device to initiate a first sorting process to classify the one or more items of the plurality of items based on the mapping; classify one or more of the plurality of items based on the first indication; receive, from the at least one user-device, a first input related to a state of a first classification process; send a second indication to the at least one user-device for display associated with the classifier to classify each sorted item based on the delivery route, using the second sorting process, regardless of the state of the first sorting process do; receive a second input related to a state of a second classification process from the at least one user-device; compare the order identifier with the container identifier after the second sorting process; detecting that an exception event has occurred in the second classification process based on the comparison; and execute the instructions to send a notification to at least one user-device associated with the classifier that an exception event has occurred.

Another aspect of the present disclosure relates to a computer-implemented method for classifying a package, the method comprising: using the computer-implemented system to generate an order identifier based on a received customer order, the order comprising a plurality of items —; 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; store, in a mapping table, an association between each item of the plurality of items in the customer order and the container identifier based on the order identifier; send a first indication to the at least one user-device to initiate a first sorting process to classify the one or more items of the plurality of items based on the mapping; classify one or more of the plurality of items based on the first indication; receive, from the at least one user-device, a first input related to a state of a first classification process; send, to the at least one user-device for display associated with the classifier, a second indication to classify each sorted item based on the delivery route, using the second sorting process, regardless of the state of the first sorting process do; receive, from the at least one user-device, a second input related to a state of a second classification process; compare the order identifier with the container identifier after the second sorting process; detecting that an exception event has occurred in the second classification process based on the comparison; and sending a notification that an exception event has occurred to at least one user-device associated with the classifier.

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

1A is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system for communications to enable delivery, transportation, and logistical operations, in accordance with disclosed embodiments.
1B illustrates a sample of a Search Result Page (SRP) that includes one or more search results satisfying a search request along with interactive user interface elements, in accordance with disclosed embodiments.
1C illustrates a sample Single Display Page (SDP) comprising a product and information about the product along with interactive user interface elements, in accordance with disclosed embodiments.
1D illustrates a sample shopping cart page including items placed in a virtual shopping cart along with interactive user interface elements, in accordance with disclosed embodiments.
1E 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, in accordance with disclosed embodiments.
2 is a schematic diagram of an exemplary fulfillment center configured to utilize the disclosed computerized system, in accordance with disclosed embodiments.
3 is a schematic diagram of an exemplary computerized personalized package delivery system configured to utilize the disclosed computerized system, in accordance with the disclosed embodiments.
4 is a flowchart of an exemplary process flow for personalized package delivery, in accordance with disclosed embodiments.
5 is a flowchart of an exemplary process flow for creating a representation of a loading arrangement of a delivery vehicle, in accordance with disclosed embodiments.
6 is a flowchart of an example process for personalized package delivery, in accordance with disclosed embodiments.
7 is a schematic diagram of an exemplary notification dashboard, in accordance with the present embodiments.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description below to refer to the same or like parts. Although several exemplary embodiments are described herein, variations, adaptations, and other implementations are possible. For example, substitutions, additions, or variations may be made to the components and steps shown in the drawings, and the exemplary methods described herein may be substituted, reordered, or eliminated with respect to the disclosed methods. Or it can be modified by adding. Accordingly, the detailed description below is not limited to the disclosed embodiments and examples. Instead, the suitable scope of the invention is defined by the appended claims.

Embodiments of the present disclosure provide systems and methods configured to reduce cycle times and improve the efficiency of package delivery by individually shipping items of the same order without waiting for the remaining items, thereby avoiding slowing down computerized systems and processes. is about

1A , shown is a schematic block diagram 100 illustrating an exemplary embodiment of a network including computer systems for communications that enable shipping, transportation, and logistical operations. As shown in FIG. 1A , system 100 may include a variety of systems, each of which may be connected to one another via one or more networks. The illustrated system is a shipping authority technology (SAT) system 101 , an external front end system 103 , an internal front end system 105 , a transportation system 107 , and mobile devices 107A, 107B, 107C. , merchant portal 109, shipping and order tracking (SOT) 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) shown), a third party fulfillment system 121A, 121B, 121C, a fulfillment center authorization system (FC Auth) 123, and a labor management system (LMS) 125 ) is included.

In some embodiments, the SAT system 101 may be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 may determine if an order has passed a Promised Delivery Date (PDD), initiate a new order, reship items in an undelivered order, and You can take appropriate action, including canceling an order that has not been placed, and starting contact with the ordering customer. The SAT system 101 may also monitor other data including outputs (such as the number of packages shipped over a specified period of time), and inputs (such as the number of empty cardboard boxes received for use in shipping). . SAT system 101 also enables communication (eg, using store-and-forward or other techniques) between devices such as external front end system 103 and FO system 113 . It can act as a gateway between different devices in the system 100 to

In some embodiments, external front end system 103 may be implemented as a computer system that enables external users to interact with one or more systems within network 100 . For example, in an embodiment where the network 100 enables the presentation of the system to allow a user to place an order for an item, the external front end system 103 receives the search request, presents the item page, and , it can be implemented as a web server that requests payment information. For example, the external front end system 103 may be implemented as a computer or computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, and the like. In another embodiment, the external front end system 103 receives and processes requests from external devices (not shown) or computer 102B), obtains information from databases and other data storage devices based on these requests, and , may run custom web server software designed to provide responses to received requests based on the obtained information.

In some embodiments, the external front end system 103 may include one or more of a web caching system, a database, a search system, or a payment system. In one aspect, the external front-end system 103 may include one or more of these systems, while in another aspect the external front-end system 103 is an interface (eg, server to server) coupled to one or more of these systems. server, database-to-database, or other network connection).

An exemplary set of steps represented by FIGS. 1B , 1C , 1D and 1E will help explain some operation of the external front end system 103 . The external front end system 103 may receive information from a system or device within the network 100 for presentation and/or display. For example, the external front end system 103 may include a Search Result Page (SRP) (eg, FIG. 1B), a Single Detail Page (SDP) (eg, FIG. 1C), It may host or provide one or more webpages including a Cart page (eg, FIG. 1D ), or an order page (eg, FIG. 1E ). (eg, mobile device 102A ) or using the computer 102B) can request a search by going to the external front end system 103 and entering information in a search box. The external front end system 103 may request information from one or more systems within the network 100 . For example, the external front end system 103 may request a result satisfying the search request from the FO system 113 . The external front end system 103 may also request and receive (from the FO system 113) a Promised Delivery Date or “PDD” for each product returned in the search results. In some embodiments, the PDD may represent an estimate of when the package will arrive at the user's desired location if ordered within a certain time period, for example by the end of the day (11:59 PM) (PDD is the FO system ( 113), discussed further below).

The external front end system 103 may prepare an SRP (eg, FIG. 1B ) based on the information. The SRP may include information that satisfies the search request. For example, it may include photos of products that satisfy the search request. The SRP may also include information about each price for each product, or improved delivery options for each product, PDD, weight, size, offer, discount, and the like. The external front end system 103 may deliver the SRP to the requesting user-device (eg, via a network).

The user-device may select a product from the SRP, for example by clicking or tapping the user interface, or using another input device to select a product presented in the SRP. The user-device may make a request for information about the selected product and send it to the external front end system 103 . In response, the external front end system 103 may request information regarding the selected product. For example, the information may include additional information beyond what is presented for the product on each SRP. This may include, for example, expiration date, country of origin, weight, size, number of items in the package, handling instructions, or other information about the product. The information may also include recommendations for similar products (based on big data and/or machine learning analysis of customers who have purchased this product and at least one other product, for example), answers to frequently asked questions, customer reviews; May include manufacturer information, photos, and the like.

The external front-end system 103 may prepare a Single Detail Page (SDP) (eg, FIG. 1C ) based on the received product information. The SDP may also include other interactive elements such as a “Buy Now” button, an “Add to Cart” button, a quantity field, a picture of an item, and the like. The external front end system 103 may forward the SDP to the requesting user-device (eg, over a network).

The requesting user-device may receive an SDP listing product information. Upon receiving the SDP, the user-device can interact with the SDP. For example, the requesting user-user of the device may click or interact with the "Place in Cart" button of the SDP. This will add the product to the shopping cart associated with the user. The user-device may send this request to the external front end system 103 to add the product to the shopping cart.

The external front end system 103 may create a shopping cart page (eg, FIG. 1D ). In some embodiments, the shopping cart page lists products that the user has added to a virtual "shopping cart." A user-device may request a shopping cart page by clicking or interacting with an icon of an SRP, SDP, or other page. In some embodiments, the shopping cart page provides information about all products 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 relevant quantity, information about the PDD, delivery method, shipping cost, User interface elements for modifying products in the shopping cart (eg, deleting or modifying quantities), options for ordering other products or setting up regular delivery of products, options for setting up interest payments, making purchases You can list information about the products in the shopping cart, such as user interface elements to proceed. User- A user of the device may click or interact with a user interface element (eg, a button labeled "Buy Now") to initiate a purchase of a product in the shopping cart. In doing so, the user-device may send such a request to the external front end system 103 to initiate a purchase.

The external front end system 103 may generate an order page (eg, FIG. 1E ) in response to receiving a request to initiate a purchase. In some embodiments, the order page reorders items from the shopping cart and requests entry of payment and shipping information. For example, the order page may contain information about the purchaser of the items in the shopping cart (eg name, address, email address, phone number), information about the recipient (eg name, address, phone number, delivery information). , shipping information (eg, delivery and/or pickup speed/method), payment information (eg, credit card, bank transfer, check, stored credit), user interface element requesting a cash receipt (eg, for tax purposes), etc. The external front end system 103 may send the order page to the user-device.

The user-device may enter information on the order page and click or interact with user interface elements that send information to the external front end system 103 . From there, the external front end system 103 transmits information to other systems in the network 100 so that it can create and process new orders with products in the shopping cart.

In some embodiments, the external front end system 103 may be further configured to enable merchants to send and receive information related to orders.

In some embodiments, internal front end system 105 enables internal users (eg, employees of an organization that owns, operates, or leases network 100 ) to interact with one or more systems within network 100 . It may be implemented as a computer system. For example, in an embodiment where the network 100 enables the presentation of a system that allows a user to place an order for an item, the internal front end system 105 allows the user to view diagnostic and statistical information about an order. It can be implemented as a web server that allows users to do this, edit item information, or review statistics about an order. For example, the internal front end system 105 may be implemented as a computer or computers running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, and the like. In another embodiment, the internal front end system 105 (as well as other devices not shown) receives and processes requests from devices represented within the network 100 and information from databases and other data storage devices based on such requests. , and based on the obtained information, it is possible to provide a response to the received request (run the designed custom web server software).

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

In some embodiments, transportation system 107 may be implemented as a computer system that enables communication between mobile devices 107A-107C and devices within network 100 . In some embodiments, transportation system 107 may receive information from one or more mobile devices 107A- 107C (eg, cell phones, smartphones, PDAs, etc.). For example, in some embodiments, mobile devices 107A- 107C may comprise devices operated by a delivery person. Delivery men, who may be full-time, temporary, or shift workers, may use mobile devices 107A- 107C for delivery of packages ordered by a user. For example, to deliver a package, the delivery man may receive a notification on the mobile device indicating the package to deliver and a location to deliver. Upon arrival at the delivery location, the delivery person can place the package (eg, in the back of a truck or on the crate of the package) and use the mobile device to store data associated with the identifier on the package (eg, barcode, image, text string, RFID tags, etc.) may be scanned or captured, and the package may be delivered (eg, by putting it on the front door, leaving it with a security guard, passing it on to a recipient, etc.). In some embodiments, the delivery person may take a photo(s) of the package and/or have it signed. The mobile device sends a communication to the transportation system 107 that includes information about the delivery including, for example, time, date, GPS location, photo(s), an identifier related to the delivery person, an identifier related to the mobile device, and the like. ) can be sent to The transportation system 107 may store this data in a database (not shown) for access by other systems in the network 100 . In some embodiments, the transportation system 107 may use this information to prepare and transmit tracking data indicating the location of a particular package to another system.

In some embodiments, a particular user may use one type of mobile device (eg, a full-time employee may use a professional PDA with custom hardware such as barcode scanners, styluses and other devices), while other users may use other types of mobile devices (eg, temporary or shift workers may use off-the-shelf cell phones and/or smartphones).

In some embodiments, transportation system 107 may associate a user with each device. For example, the transportation system 107 may include a user (eg, delineated by a user identifier, employee identifier, or phone number) and a mobile device (eg, International Mobile Equipment Identity (IMEI), International Mobile Subscription Identifier). (depicted by an IMSI), a phone number, a Universal Unique Identifier (UUID), or a Globally Unique Identifier (GUID)). Transportation system 107 may use these relationships in connection with data received upon delivery to analyze data stored in a database to determine the location of the operator, the effectiveness of the operator, or the speed of the operator, among others.

In some embodiments, the merchant portal 109 may be implemented as a computer system that enables a merchant or other external entity to communicate electronically with other aspects of information related to an order. For example, the seller may use a computer system (not shown) for uploading or providing product information, order information, contact information, and the like, for a product to be sold through the system 100 .

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

In some embodiments, shipping and order tracking system 111 may request and store information from systems represented in network 100 . For example, the shipping and order tracking system 111 may request information from the shipping system 107 . As described above, the transportation system 107 may include one or more mobile devices 107A-107C (eg, a cell phone) associated with one or more of a user (eg, a delivery man) or a vehicle (eg, a delivery truck). , smart phone, PDA, etc.). In some embodiments, the shipping and order tracking system 111 may also include a warehouse management system (WMS) 119 to determine the location of individual packages within a fulfillment center (eg, fulfillment center 200). You can request information from Shipping and order tracking system 111 requests data from one or more of shipping system 107 or WMS 119, processes it, and on request to devices (eg, user-devices 102A, 102B). can provide

In some embodiments, the fulfillment optimization (FO) system 113 receives information about customer orders from other systems (eg, external front end system 103 and/or shipping and order tracking system 111 ). It can be implemented as a computer system that stores. The FO system 113 may also store information indicating where a particular item is maintained or stored. For example, some items ordered by customers may be stored in only one fulfillment center, while other items may be stored in multiple fulfillment centers. In another embodiment, a specific fulfillment center may be configured to store only a specific set of items (eg, fresh produce 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 may also calculate a corresponding PDD (Promised Delivery Date) for each product. In some embodiments, PDD may be based on one or more factors. For example, the FO system 113 may determine a past demand for a product (eg, how many orders for that product have been ordered over a period of time), an expected demand for the product (eg, how many customers will purchase the product over an upcoming period). expected to be ordered), 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 the coming period, and each store each product is stored in. The PDD for a product may be calculated based on the number of one or more products stored in the fulfillment center 200 , an expectation for the product, or a current order, and the like.

In some embodiments, the FO system 113 periodically (eg, hourly) determines and retrieves the PDD for each product or other system (eg, external front end system 103 , SAT system (eg, 101), shipping and order tracking system 111), which may be stored in a database for transmission. In another embodiment, the 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 responds to the request. PDD can be calculated accordingly.

In some embodiments, fulfillment messaging gateway (FMG) 115 receives messages from one or more systems in network 100 , such as FO system 113 , converts data within the messages to another format, and converts the converted It forwards the formatted data to another system, such as WMS 119 or a third party fulfillment system 121A, 121B, or 121C, and vice versa.

In some embodiments, supply chain management (SCM) system 117 may be implemented as a computer system that performs a predictive function. For example, the SCM system 117 may include, for example, past demand for a product, a projected demand for a product, a network-wide past demand, a network-wide expected demand, and products stored in each fulfillment center 200 , for example. The predicted level of demand for a particular product may be determined based on the number of In response to these determined predicted levels and quantities of each product through all of the fulfillment centers, the SCM system 117 may generate one or more purchase orders to satisfy the anticipated demand for the particular product.

In some embodiments, warehouse management system (WMS) 119 may be implemented as a computer system that monitors the workflow. For example, WMS 119 may receive event data representing a single event from an individual device (eg, devices 107A-107C or 119A-119C). For example, WMS 119 may receive event data indicating that it used one of these devices to scan the package. As discussed below with respect to the fulfillment center 200 and FIG. 2 , during the fulfillment process, a package identifier (eg, barcode or RFID tag data) is stored in a particular stage of a machine (eg, automatic or handheld). barcode scanner, RFID reader, high-speed camera, tablet 119A, mobile device/PDA 119B, device such as computer 119C, etc.). WMS 119 may store each event representing a scan or read of a package identifier in a corresponding database (not shown) along with package identifier, time, date, location, user identifier, or other information, and store this information in other systems. (eg, shipping and order tracking system 111 ).

In some embodiments, WMS 119 may store information associating one or more devices (eg, devices 107A-107C or 119A-119C) with one or more users associated with network 100 . For example, in some circumstances, a user (such as a part-time or full-time employee) may be associated with a mobile device in that it owns the mobile device (eg, the mobile device is a smartphone). In another situation, in that the user temporarily stores the mobile device (eg, the user will rent the mobile device from the start of the day, will use it for the day, and return it at the end of the day), the mobile device can be related to

In some embodiments, WMS 119 may maintain an activity log for each user associated with network 100 . For example, the WMS 119 may include any assigned process (eg, unloading from a truck, picking up an item at a pickup area, living wall work, packing an item), a user identifier, a location (eg, a full fill floor or area of the apartment center 200), the number of units moved through the system by staff (eg, the number of items picked up, the number of packed items), the device (eg, the device 119A- 119C))) and may store information associated with each employee, including identifiers associated with them. In some embodiments, WMS 119 may receive check-in and check-out information from a timekeeping system, such as a timekeeping system running on devices 119A-119C.

In some embodiments, third-party fulfillment (3PL) systems 121A-121C represent computer systems associated with logistics and third-party providers of products. For example, some products may be stored in the fulfillment center 200 (as described below with respect to FIG. 2 ), while others may be stored off-site or on demand. It can be produced according to, and cannot otherwise be stored in the fulfillment center 200 . The 3PL systems 121A-121C may be configured to receive orders from the FO system 113 (eg, via the FMG 115 ) and directly to the customer for products and/or services (eg, delivery or installation) can be provided.

In some embodiments, the fulfillment center authentication system (FC Auth) 123 may be implemented as a computer system having various functions. For example, in some embodiments, FC Auth 123 may operate as a single-sign on (SSO) service to one or more other systems within network 100 . For example, FC Auth 123 allows the user to log in through the internal front end system 105 and determines that the user has similar permissions to access resources in the shipping and order tracking system 111 , Allows users to access those privileges without requiring a second login process. In another embodiment, FC Auth 123 allows a user (eg, an employee) to associate themselves with a particular task. For example, some employees may not have electronic devices (such as devices 119A- 119C) and may instead move between jobs and between zones within fulfillment center 200 during the day. FC Auth 123 can be configured to indicate the work these employees are performing at different times and the zone they belong to.

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

The specific configuration shown in FIG. 1A is merely exemplary. For example, while FIG. 1A shows the FC Auth system 123 coupled to the FO system 113 via the FMG 115 , not all embodiments require this specific configuration. Indeed, in some embodiments, the systems within network 100 are Internet, intranet, Wide-Area Network (WAN), Metropolitan-Area Network (MAN), wireless network conforming to IEEE 802.11a/b/g/n standard, lease They may be connected to each other through one or more public or private networks including lines 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 a data center, server farm, or the like.

2 shows a fulfillment center 200 . The fulfillment center 200 is an example of a physical place that stores items for delivery to customers upon ordering. The fulfillment center (FC) 200 may be divided into a number of zones, each of which is illustrated in FIG. 2 . In some embodiments, these “zones” can be thought of as virtual divisions between the different stages of the process of receiving items, storing items, retrieving items, and shipping items. Thus, although “zones” are shown in FIG. 2 , in some embodiments, other divisions of zones are possible, and zones in FIG. 2 may be omitted, duplicated, or modified.

Inbound zone 203 represents an area of FC 200 where items are received from sellers who wish to sell products using network 100 of FIG. 1A . For example, the seller may use the truck 201 to deliver the items 202A, 202B. Item 202A may represent a single item large enough to occupy its shipping pallet, and item 202B may represent a set of items stacked together on the same pallet to save space.

An operator may receive the item in the inbound area 203 and optionally use a computer system (not shown) to check if the item is damaged and correct. For example, an operator may use the computer system to compare the quantity of items 202A, 202B to the ordered quantity of the item. If the quantities do not match, the worker may reject one or more of the items 202A, 202B. If the quantities match, an operator may transport the items (eg, dolly, handtruck, forklift, or manually) to buffer area 205 . Buffer zone 205 may be, for example, a temporary storage area for items that are not currently needed in the pickup zone, for example, because there are sufficient quantities of those items in the pickup zone to meet expected demand. In some embodiments, forklift 206 operates to transport items around buffer zone 205 and between inbound zone 203 and drop zone 207. Pickup zone (eg, due to anticipated demand) If item 202A, 202B is needed, the forklift may transport item 202A, 202B to drop zone 207 .

Drop zone 207 may be an area of FC 200 that stores items prior to being transported to pickup zone 209 . An operator assigned to a pickup operation (“picker”) accesses an item 202A, 202B in the pickup area, scans a barcode for the pickup area, and holds a mobile device (eg, device 119B) can be used to scan barcodes associated with items 202A, 202B. The picker may then take the item to the pickup area 209 (eg, by placing or transporting it on a cart).

The pickup zone 209 may be an area of the FC 200 where the items 208 are stored in the storage unit 210 . In some embodiments, the storage unit 210 may include one or more of a physical shelf, a bookshelf, a box, a tote, a refrigerator, a freezer, a cold store, and the like. In some embodiments, pickup area 209 may be organized into multiple floors. In some embodiments, an operator or machine picks up an item from the pickup area 209 in a variety of ways, including, for example, by a forklift, elevator, conveyor belt, cart, hand truck, cart, automated robot or device, or manual operation. can be transported to For example, the picker may place the items 202A, 202B on a hand truck or cart in the drop zone 207 , and may take the items 202A, 202B to the pickup zone 209 .

The picker may receive a command to place (or “stow”) the item at a specific spot in the pickup area 209 , such as a specific space on the storage unit 210 . For example, the picker may scan the item 202A using a mobile device (eg, device 119B). The device may indicate where the item 202A should be loaded, using, for example, aisles, shelves, and systems that indicate locations. The device may then cause the picker to scan the barcode at that location before loading the item 202A at that location. The device may send (eg, over a wireless network) data indicating that the item 202A has been loaded into its location by a user using the device 119B to a computer system, such as WMS 119 of FIG. 1A . .

Once the user places an order, the picker may receive instructions from the device 119B to retrieve one or more items 208 from the storage unit 210 . The picker may retrieve the item 208 , scan a barcode on the item 208 , and place it on the transport vehicle 214 . In some embodiments, the transport mechanism 214 is depicted as a slide, however, the transport mechanism may be implemented as one or more of a conveyor belt, elevator, cart, forklift, hand truck, wagon, cart, and the like. Item 208 may then arrive at packing area 211 .

Packing zone 211 may be an area of FC 200 where items are received from pickup zone 209 and packed into boxes or bags for final delivery to a customer. At the packing area 211 , a worker assigned to receive the item (“rebin worker”) will receive the item 208 from the pickup area 209 and determine which order it corresponds to. For example, a rebining operator may use a device such as computer 119C to scan a barcode on item 208 . Computer 119C may visually indicate which spell the item 208 is associated with. This may include, for example, a space or “cell” on the wall 216 that corresponds to the order (eg, since the cell contains all the items in the order). When done, the rebining operator can notify the packing operator (or "packer") that the order is complete. The packer can retrieve items from the cell and place them in boxes or bags for shipping. The packer may then send the box or bag to the hub area 213 via, for example, a forklift, cart, cart, hand truck, conveyor belt, hand or other method.

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 in the hub area 213 may retrieve the packages 218 , determine to which part of the delivery area each package is intended for delivery, and direct the packages to the appropriate camp area 215 . For example, if the delivery area has two small sub-areas, the package will be sent to one of the two camp areas 215 . In some embodiments, an operator or machine may scan the package (eg, using one of devices 119A- 119C) to determine its final destination. Sending the package to the camp area 215 may include, for example, determining (based on the zip code) the portion of the geographic area to which the package is directed, and determining the camp area 215 associated with the portion of the geographic area. can

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

Operators and/or machines in camp area 215 may, for example, compare destinations with existing routes and/or sub-routes, calculate workload for each route and/or sub-routes, time of day, delivery It may be determined which route and/or sub-route the package 220 should be associated with based on the method, the cost to ship the package 220 , the PDD associated with the item in the package 220 , and the like. In some embodiments, an operator or machine may scan the package (eg, using one of devices 119A- 119C) to determine its final destination. Once the packages 220 are assigned to a particular route and/or sub-route, workers and/or machines can transport the packages 220 to be shipped. In exemplary FIG. 2 , camp area 215 includes truck 222 , automobile 226 , and deliverymen 224A, 224B. In some embodiments, deliveryman 224A may drive truck 222 , where deliveryman 224A is a full-time employee delivering packages for FC 200 and truck owns FC 200 . , owned, leased, or operated by the same company that leases or operates it. In some embodiments, delivery man 224B may drive automobile 226, where delivery man 224B is a "flex" or emergency worker who delivers as needed (eg, seasonally). am. Automobile 226 may be owned, leased, or operated by deliveryman 224B.

3 is an exemplary schematic diagram of a computer implemented system 300 for personalized package delivery. In some embodiments, the system 300 includes a live operator 301 , a picked up item 208 with an order identifier 305 (eg, barcode, label, tag), and a user-interface device 302 (eg, a user-interface device). for example, mobile device/PDA 119B). System 300 includes a first storage location 320 (eg, packing zone 211 ) that includes storage cells 324 (eg, 324_1 , 324_2 ), storage cells 344 (eg, It may further include a second storage location 340 (represented herein as a camp-site) and a delivery truck 201 . The first storage location 320 and the camp-site 340 (eg, camp area 215 ) may classify the items based on other information associated with the final destination. As an example, in the first storage location 320 , an item (eg, item 208 ) may be classified based on a geographic area (eg, zip code) to which the package will be directed, and a camp-site (eg, zip code). At 340, classification may be based on a delivery route or sub-route (eg, route number). (Other classification methods are possible, of course.) The delivery route or sub-route may be predetermined by one or more computer implemented systems of system 100 . In some embodiments, one or more systems of computer implemented system 100 (eg, SAT 101 , WMS 119 , SCM 117 ) are configured to communicate with user-interface device 302 , classification can be shown.

3 illustrates an exemplary personalized package delivery system. As used herein, the term “singulation” refers to individual shipping of an ordering customer's items, including multiple items, without waiting for the customer's order to be fully fulfilled prior to shipping. Package delivery by individualization may have many advantages over existing systems for package delivery. Package delivery by individualization may particularly have some or all of the advantages discussed herein.

i. Improved Packing Efficiency - In existing package delivery systems, a living worker can wait for all items in an order to be packed in one package, which package is then associated with a particular order for further processing including sorting or shipping. can be placed in space. In contrast, in the personalized package delivery system 300, the packer can sort items individually in storage cells (e.g., 324_1) without waiting for other items in the order to arrive at the packer station or packing area, It is possible to reduce the idle time of the packer. The reduced idle time for each packer improves the overall packing efficiency.

ii. Improved Pickup Density—In existing package delivery systems, pickers can pick up items to sequentially fulfill customer orders. For example, the picker may pick up all items in order 1 before picking up items in order 2. This sequential pickup method loses time and efficiency because the picker spends more time moving than picking up the item. In contrast, the personalized package providing system 300 may improve pickup density because pickers may perform the task of picking up items based on the location of the picker rather than based on customer orders. For example, a picker may perform the task of picking up items that are located proximate to their current physical location but may be associated with other customer orders. This parallel approach to pickups can improve pickup density by reducing the time the picker spends moving.

iii. Improved trackability—as shown in FIG. 3 , in an individualized package delivery system 300 , an operator (eg, operator 301 ) performs a package (eg, a package) prior to initiating the process and after completing the process. For example, a barcode (eg, order identifier 305 and/or location identifier) associated with the package 208 may be scanned. Additionally, barcodes may be scanned during the process, periodically or upon receipt of a prompt. For example, information recorded by scanning may be stored in a database of system 100, which allows packages to be tracked as they are processed. Barcodes on containers or totes can also be scanned, providing information associated with the location of items contained in the container during the process of pickup, sorting, packing, shipping, etc., enabling container and package traceability.

iv. Faster Sorting - Upon receipt of items from a packing area at a camp-site (eg, camp area 215 ), the items are placed in a sub-route or It can be classified based on the delivery route. Since the items are sorted based on sub-route rather than based on the customer order to which they belong, the display time of the item can be shortened, thereby improving the sorting speed. It can also improve space utilization, improve operator efficiency, shorten cycle times, and enrich the customer experience.

v. Reduced shelf-time - Personalization of items can reduce the amount of time an item is placed on a shelf and waiting for pickup, packing, sorting, or shipping, as the item can be processed regardless of the status of other items in that order. have. Reducing the display time of an item may reduce the associated costs associated with inventory management, and may reduce the risk of item handling and misplacement.

vi. Reduced "Ready to Load" Time - In existing package delivery and delivery systems, employees such as workers, drivers, loaders, managers, floor supervisors, etc. take turns to ensure that, for example, all items belonging to an order have been loaded. Alternatively, you may spend a significant amount of time at the start of your work session. Such systems can be inefficient in utilizing resources such as manpower and time, which can increase operating costs and affect throughput. Individualization of items can reduce load preparation time as employees load containers or container carriers, such as totes, cages, etc., into delivery trucks based on planned delivery areas and delivery routes.

ⅶ. Improved Loading and Delivery Efficiency - Delivery trucks can be loaded more efficiently as items are placed in large standardized totes or containers based on delivery routes. In addition, since items remain in standardized containers until shipped, damage or misplacement due to handling can be minimized. Large standardized totes or containers allow loaders to follow easy instructions to load onto trucks, and allow drivers to easily find items and deliver orders more efficiently.

In some embodiments, system 100 may be configured to receive customer orders. A customer order may include a plurality of items. In some embodiments, each customer order may include a plurality of sub-orders, and each sub-order may include a plurality of items. For example, a customer order may include three sub-orders. The first sub-order may be an urgent delivery of toothpaste, toothbrush and mouthwash, the second sub-order may include normal delivery of cheese, crackers and chips, and a third A sub-order may include a delayed delivery of the beverage. The system 100 may receive a customer order and generate an order identifier 305 to be associated with each item ordered. In some embodiments, system 100 provides a unique sub-order identifier associated with each sub-order (eg, sub-order identifier 305A for a first sub-order, sub-order identifier 305A for a second sub-order). - an order identifier 305B, and a sub-order identifier 305C for the third sub-order).

In some embodiments, order identifier 305 and sub-order identifier (eg, 305A, 305B or 305C) include the number of items ordered, the urgency of the item to be delivered, the destination of the item to be delivered, etc. However, it may include information that is not limited to these. In some embodiments, the order identifier 305 may also include information regarding the number of sub-orders within a single order. The system 100 may send an indication to the user-interface device 302 indicating that the order includes multiple sub-orders and that the urgency associated with each sub-order is. The picker may fulfill orders or sub-orders accordingly.

In some embodiments, one or more pickers may receive an indication related to the urgency of a sub-order while looking for items for another ordering customer. Based on the pickers' current location within the pickup area 209 , the pickers may find the item of the urgent sub-order and send the item to the packing area 211 . For example, if the emergency sub-order includes a toothbrush and a pair of socks, a picker within or near the oral hygiene section may find a toothbrush and a picker within or near the clothing section may find a pair of socks; As a result, the pickup density is improved. When the container or tote is full the items may be transported to the packing area 211 . This method can increase pickup efficiency by picking up items based on the location of pickers rather than based on customer orders, thereby shortening cycle times and improving overall delivery efficiency.

In some embodiments, system 100 sends, to a user-device (eg, smart phone 119B, or computer 119C), instructions that the device instructs the picker to print order identifier 305 . can In some embodiments, the user-device may include a portable device, such as a PDA, configured to print a label. 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 a label, instruction, note, or the like. The instructions may further include requesting the picker to associate the printed order identifier 305 with an item in the customer order, for example by attaching the printed order identifier 305 to the picked up 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.

The living worker 301 may receive the picked up item 208 at the packing area 211 . In some embodiments, live operator 301 may use user-interface device 302 (eg, smart phone 119B) to receive information from system 100 related to customer orders. User-interface device 302 may include a portable display device (eg, tablet 119A), a smart phone (eg, mobile device/PDA 119B), a computer (eg, computer 119C), body-mounted displays, head-mounted displays, and the like. User-interface device 302 may be substantially similar to a mobile device, such as computer 119C of FIG. 1A , for example. User-interface device 302 may communicate and exchange information with WMS 119 , for example.

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 include information including information related to the customer order, such as the number of items ordered, the urgency of delivery for the items ordered, the destination location of the item to be shipped, and the like. In some embodiments, the user-interface display may be a visual display or an audiovisual display. For example, if the order is “urgent,” the user-interface device 302 may receive an audiovisual message indicating a request for expedited fulfillment of the order. 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, user-interface device 302 may provide an audible, visual, or tactile notification to the user and indicate a request to acknowledge receipt of the notification via one or more interactive elements of the user-interface display. . In some embodiments, the user-interface device 302 may include data recording functionality, such as barcode scanning, optical character reader, etc., to record information in the order identifier 305 . 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 may automatically upload the recorded information to a database.

In some embodiments, the user-interface device 302 may receive instructions to review the order identifier 305 associated with the picked up item 208 , displayed via an interactive element of the user-interface display. For example, one of the computer implemented systems of system 100 (eg, WMS 119 , SCM 117 , or SAT 101 ) begins examining the order identifier 305 associated with the item 208 . may generate a command for the user-interface device 302 to display an indication to the user to do so. Reviewing the order identifier 305 may include determining the final destination of the item 208 by, for example, scanning or reading the order identifier 305 . For example, scanning an order identifier (eg, a barcode) using a barcode scanning device can reveal information related to 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, and the like. can be displayed. In some embodiments, customer orders may include multiple sub-orders and each sub-order may further include multiple items. It may be appreciated that item 208 may comprise a package comprising one or more items of a customer order.

Once the final destination for delivery of the item 208 is determined, the living worker 301 may place the item 208 in the first storage location 320 based on the determined final destination. The first storage location 320 may include a storage cell 324 . Each storage cell 324 of the first storage location 320 may be associated with a sort location. In some embodiments, the first storage location 320 may include living walls, storage units, storage racks or cabinets having cells. Other structured storage means may also be used.

In some embodiments, items 208 may be sorted into storage cells 324 in the first storage location based on their destination regardless of the status of the order or other items in the order with which the item is associated. In a system that currently exists, a living operator could wait for all items in an order to be picked up before the order is sorted for delivery. In contrast, in the disclosed embodiment, each item may be treated as a separate order and sorted based on destination regardless of the status of other items in that order. This can reduce the idle time of the living worker, thereby increasing the packing efficiency. In some embodiments, as disclosed herein, packing efficiency may be expressed as the number of items packed in a particular time period. For example, package efficiency may be expressed in units per hour (UPH). Other efficiency metrics may also be used. Personalization of items may also reduce the display time of an item, defined herein as the period of time the item is on a shelf before being picked up, packed, sorted, or shipped, thereby reducing costs associated with inventory management, thereby It can reduce the risk of negligence or misplacement of items.

In some embodiments, each storage cell 324 may be associated with a camp-site 340 . In some embodiments, camp-site 340 may be an on-site storage or sorting facility on the premises of FC 200 . In some embodiments, camp-site 340 may be an off-site storage or sorting facility at a remote location. An association of each storage cell 324 (eg, 324_1 or 324_2 ) with a corresponding camp-site may be identified using the camp-site identifier. A camp-site identifier may include, but is not limited to, a label, barcode, number or tag. Although only a limited number of storage cells 324 are shown, it will be appreciated that the first storage location 320 may include any number of storage cells 324 .

In some embodiments, the user-interface device 302 places the item 208 into the corresponding storage cell 324 based on determining the destination location of the item 208, via presentation to the living operator 301 . 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 ) may determine which item 208 is destined for the camp-site. can be decided The living worker 301 may place the item 208 in the corresponding storage cell 324 .

In some embodiments, the living operator 301 may receive, via the user-interface device 302 , an indication to associate the item 208 with the corresponding storage cell 324 in which the item 208 is placed. For example, the living worker 301 may be asked to scan the order identifier 305 and the camp-site identifier to establish an association between the camp-site and the item 208 for sorting. Information relating to the order identifier of the placed item and the camp-site identifier of the storage cell in which the item is placed may be automatically updated in a database containing information relating to customer orders and delivery schedules of customer orders.

In some embodiments, if camp-site 340 is an on-site facility, items may be transported using a transportation means such as, for example, a conveyor belt, forklift, pallet, trolley, or tote. In the case of an off-site facility, the items may be transported using a delivery truck or the like.

In some embodiments, storage cell 324 may contain one or more items that must be transported to a corresponding camp-site. In some embodiments, a camp-site may be represented as a storage location. For example, camp-site 340 may be associated with storage cell 324_1 , indicating that items placed in storage cell 324_1 (eg, item 208 ) may be directed to camp-site 340 . indicates.

In some embodiments, camp-site 340 may include one or more storage spaces 342 . The storage space 342 may include, but is not limited to, a wall having storage cells, a storage unit, a storage rack having cells, or a cabinet. Other structured storage means may also be used. For example, storage space 342 may include a wall with storage cells 344 . Each storage cell 344 may be associated with a sub-route for delivery of an item 208 .

An operator at the camp-site 340 may receive one or more items 208 from the storage location 320 . An operator (eg, a classifier) may review the order identifier 305 associated with the picked up item 208 . In some embodiments, the operator may receive a notification on the user-interface device 302 to review the order identifier 305 . For example, one of the computer implemented systems of system 100 (eg, WMS 119 , SCM 117 or SAT 101 ) to be displayed on user-interface device 302 for a user; An indication may be generated to begin reviewing the order identifier 305 associated with the item 208 . Reviewing the order identifier 305 may include determining the final destination of the item 208 .

Once the final destination for delivery of the item 208 is determined, the operator stores the items (eg, item 208 ) in the storage cell 344 based on the determined sub-route for the final destination of the item 208 . put on Each storage cell 344 of the camp-site 340 may be associated with a sub-root.

In some embodiments, the user-interface device 302 may, via an indication, inform the operator to place the item 208 in the corresponding storage cell 344 based on the determined final destination of the item 208 . For example, based on a customer order, one of the computer-implemented systems of system 100 (eg, WMS 119 , SCM 117 or SAT 101 ) may store the item 208 toward which it may be directed. Cell 344 may be determined. The operator may place the item 208 in the corresponding storage cell 324 based on the indication from the user-interface device 302 .

The association of each storage cell 344 with the corresponding sub-root may be identified using the sub-root identifier. A sub-route identifier may include, but is not limited to, a label, barcode, number or tag. Although only a limited number of storage cells 344 are shown, it will be appreciated that camp-site 340 may include any number of storage cells 344 .

In some embodiments, items may be sorted into storage cell 344 based on a determined sub-route for a final destination of delivery, regardless of the status of an order or other item in the order to which the item may be associated. In currently existing delivery systems, the classifier may wait for all items in an order to be received before the order is ready to be delivered. In contrast, in the disclosed embodiment, each item may be treated as a separate order and sorted based on the determined sub-routes for delivery regardless of the status of other items in the order. This reduces the idle time of sorters in the camp area, increasing sorting efficiency and overall package delivery efficiency.

In some embodiments, user-interface device 302 may be configured to display an indication to associate an item with a corresponding storage cell 344 in which the item is placed. For example, the indication may include a request to scan the order identifier 305 and the sub-route identifier to establish an association between the item 208 and a sub-route for delivery. The information associated with the order identifier 305 of the placed item and the sub-root identifier of the storage cell 344 in which the item is placed may be automatically updated in a database containing information related to the customer order and the delivery schedule of the customer order. .

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a tote). All items in storage cell 344 (eg, item 208 ) may be contained in container 350 . In some embodiments, container 350 may be identified using container identifier 355 . The container identifier 355 may include information associated with a sub-route including the sub-route identifier. In some embodiments, container identifier 355 may include information related to camp-sites and sub-roots. For example, the container identifier may include the label CS3_SR1, where CS indicates the origin camp-site and SR indicates the sub-route designated for delivery of items contained in the container. Container identifier 355 may include, but is not limited to, a label, barcode, number, or tag.

In some embodiments, the user-interface device 302 may be configured to display a notification or indication to place the item 208 in the corresponding container 350 based on the determined final destination of the item 208 . For example, based on a customer order, one of the computer-implemented systems of system 100 (eg, WMS 119 , SCM 117 , or SAT 101 ) is a container in which item 208 may be contained. (350) can be determined. The operator may place the item 208 into the corresponding container 350 based on the indication from the user-interface device 302 .

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

In some embodiments, one or more containers 350 may be loaded onto a delivery vehicle (eg, delivery truck 201 ) for delivery to a customer. Container 350 may be placed within delivery truck 201 based on sub-route. For example, a package or item (e.g., item 208) that is to be delivered to a destination close to the starting point of the sub-route may be located closer to the access door, thereby giving the delivery person direct access to the package. have. In some embodiments, the container 350 containing the urgent order may be positioned closer to the access door to allow quick access of the packages. In some embodiments, sub-routes may be adjusted based on the type and urgency of the order or PDD. In some embodiments, both sub-route and placement of containers within delivery truck 201 may be adjusted based on customer orders and PDD.

The container 350 may be loaded into the container carrier 360 before being loaded onto the delivery truck 201 . The container carrier 360 may include a cart, a trolley, a cage, a basket, and the like. In some embodiments, container carrier 360 may include an identifier such as a barcode, label or tag. In some embodiments, the user-interface device 302 may inform the delivery man or truck loader via an indication to place the container 350 on the delivery truck 201 based on a predetermined placement. For example, based on the PDD, one of the computer-implemented systems of the system 100 (eg, the transportation system 107 ) may place or deliver the container 350 on the container carrier 360 on the truck 201 . The placement of one or more container carriers 360 may be determined. The delivery man or truck loader transfers the container 350 or container carrier 360 to the delivery truck 201 based on a determination made by one of the computer-implemented systems of the system 100 (eg, the transportation system 107 ). can be placed in The user-interface device 302 may display to a delivery person or truck loader a representation of the placement of the container 350 in the container carrier 360 and/or the placement of the container carrier 360 in the delivery truck 201 . can

In some embodiments, the user-interface device 302 may be configured to display a depiction of the one or more container carriers 360 and the deployed container 350 within the delivery truck 201 . The format of the depiction may include one of visual, graphical, auditory, audiovisual, or a combination thereof. In some embodiments, the user-interface display may include a depiction of the container 350 and container carrier 360 deployed within the delivery truck 201 for the delivery person.

In some embodiments, the delivery man, after loading into the delivery truck 201 , generated by one of the computer-implemented systems of the system 100 (eg, the transportation system 107 ), navigates to the sub-route. You may receive an indication to start. The delivery man may receive the indication via a user-interface display on the user interface device 302 .

Reference is now made to FIG. 4 , which illustrates an exemplary flow diagram of a process 400 for personalized package delivery, in accordance with disclosed embodiments. The process receives a customer order, generates an order identifier based on the customer order, determines an intended final destination for the items in the customer order, picks up at least a portion of the items in the customer order, and based on a two-step sorting process sorting the picked up items, loading the picked up items of the customer order into a delivery truck without waiting for the remainder of the items in the customer order, and delivering the picked up items to the customer.

The overall package delivery efficiency is a metric that depends on the efficiency of each step in the process of package delivery. Shipping a package from an FC to a customer to fulfill an order generally involves several steps, most of which must be performed in successive subsequent orders. For example, picking up may be preceded by receiving an order and generating an order identifier, sorting may precede picking up, packing may precede sorting, and placing the item on a delivery truck. The loading may be preceded by packing or the like. In other words, each step of the process is initiated by the completion of the previous step. In this process flow, the overall efficiency of the process is determined by the efficiency at each step. The 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 the other step. As discussed above, "individualization" herein refers to the individual shipping of items of a customer order comprising multiple items without waiting for the customer order to be fully fulfilled prior to shipping, which reduces cycle time and reduces the process and By reducing the idle time of the staff involved, the efficiency of package delivery can be improved. In some embodiments, one or more steps of process 400 may be executed by one or more user-interface devices (eg, each operated by a user in a different region 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 a plurality of items. In some embodiments, a customer order may include a plurality of sub-orders and each sub-order may include a plurality of items. One or more computer-implemented systems of system 100 may be configured to review customer orders and identify information such as the total number of items ordered, a description of each item ordered, a requested delivery time, the final destination of the item, and the like. In some embodiments, one or more computer-implemented systems of system 100 may determine an promised delivery date or promised delivery time for a customer order based at least on the requested delivery time. For example, for an expedited order request from a customer, the system may determine an promised delivery time of several hours or a delivery within 24 hours to an intended final destination. In some embodiments, the system may be configured to individually determine an 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 regular 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 ) may receive multiple customer orders. Each customer order may include a plurality of 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 an indication for a common item, requesting input from the user, for example, of receipt confirmation. This indication may include information related to the description of the item, the quantity of the item 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, eg, a bottle of water. An operator (eg, a picker) may receive, via a user-interface device, an indication that 50 bottles of water should be picked up. Implementation of this approach can improve the pickup efficiency and 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. The order identifier may include a barcode, label, tag, alphanumeric code, QR code, and the like. The order identifier may be a machine-readable optical label that contains information regarding the customer order. The information contained in the order identifier may include, but is not limited to, the final destination of the order, the total number of items in the customer's order, the type of shipment requested, customer information, the promised delivery date and the promised delivery time, and the like. In some embodiments, the system for generating an order identifier is a storage location (eg, camp area 215 , hub area 213 ) and a delivery route to which items in the customer order belong based on the final destination information of the customer order. can be decided For example, based on the zip code of the final destination, the system may determine a storage location for items in the customer's order, and based on the identified street or region in the final destination, the system may A delivery route may be determined for items in an order.

For example, upon scanning or reading the order identifier using a user-interface device (eg, user-interface device 302 ) having a barcode scanning function, the user-interface device sends information associated with the order identifier. can be displayed. For example, upon scanning or reading the order identifier, the user-interface device may display the number of items picked up, the number of items remaining to be picked up, 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 an indication to associate each item in a customer order with an order identifier. The user-interface device may be configured to display, for a received customer order, an indication or warning from the user, for example, requesting input of an acknowledgment of receipt. Upon receiving input from the user, the user-interface device may display some or all of the customer's order and information associated with the customer order. An operator (eg, a picker) picks up one or more items of a customer order and associates each picked up item with an order identifier received from one or more computer-implemented systems, eg, by scanning an order identifier and a barcode on the item. can do it In some embodiments, associating an item of a customer order with an order identifier may include physical printing of the order identifier using a label printer or barcode printer. A printed label or barcode may be affixed or affixed to, for example, an item in order to provide all staff with easy access to information related to ordering and delivery schedules. For example, an operator who has not received or does not have access to the original order identifier may scan a printed and affixed order identifier on the item.

At step 440 , one or more computer systems of system 100 may determine an intended final shipping address for each of the items in the customer order. As an example, the system could order a bouquet of flowers to be delivered to a friend's house before 8pm 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 distinct order identifiers representing the two orders. Each item can be sent to a storage location and sorted by delivery route at the storage location, each based on its intended final destination.

In some embodiments, one or more computer-implemented systems of system 100 may be configured to store the intended delivery location, a storage space associated with the intended delivery location (eg, storage cells 324/344 ), and items of a customer order to the intended delivery location. can determine a delivery route for delivery to

In some embodiments, the classification process may be a two-step classification process. A first step may include sorting the picked up item based on a camp-site to which the item may be directed. The camp-site may be determined, for example, based on the zip code of the intended final destination for the item in the customer order. The second step may include sorting the selected item at the camp-site based on a delivery route through which the item may be sent for delivery. The delivery route may be determined, for example, based on an area or distance within the area indicated by the zip code.

At step 450 , the one or more computer-implemented systems of the system 100 configure the pre-allocated storage space determined by the one or more computer-implemented systems of the system 100 (eg, the storage cells 324 of the storage location 320 ). ))), send a command to the user interface device to display an indication or warning to sort the picked up items of the customer order. The pre-allocated storage space may represent a camp-site to which items may be directed for further sorting. In some embodiments, one or more storage space may be allocated to a camp-site. For example, storage space 1-12 is allocated for camp-site 1, represented by storage cell 324-1, and storage space 13-23 is allocated for camp, represented by storage cell 324-2. - allocated for site 2 , and storage space 24 may be allocated for camp-site 3 represented by storage cell 324 .

Each classified item may be shipped to a corresponding camp-site. In some embodiments, the camp-site may be an on-site storage facility (eg, camp area 215 ) within the premises of the FC 200 . The sorted items may be transported to camp area 215 using, for example, a transport device such as a conveyor belt, forklift, hand truck, trolley, cart. In some embodiments, the camp-site may be an off-site storage facility, such as a warehouse or a storage unit separate from FC 200 . The sorted items may be transported to an off-site storage facility using, for example, a delivery truck. Sorted items belonging to a customer order can be shipped to the camp-site without waiting for the remaining items in the customer order to reduce idle time.

At step 460 , one or more computer-implemented systems of system 100 may send an instruction to the user-interface device to display an indication or warning to sort items picked up at the camp-site based on the delivery route. The delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final destination in the customer order. An operator may sort items picked up at the camp-site by placing the items in a storage cell (eg, storage cell 344 ) based on the delivery route. An operator may obtain delivery route information, for example, by scanning an order identifier on an item. Each of the storage cells 344 may be identified by a route identifier or a sub-root identifier.

At step 470 , the one or more computer-implemented systems of system 100 send a user-instruction to display an indication or warning to place the sorted items in storage cell 344 into a container (eg, container 350 ). can be transmitted to the interface 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 comprising information identifying the camp-site and storage cell. Pickup items belonging to a customer order can be placed in a container without waiting for the rest of the items in the same customer order to reduce idle time.

Container 350 or container carrier 360 may be loaded onto a delivery vehicle (eg, delivery truck 201 ) configured to receive containers, totes, wheel cages, carts, trolleys, and the like. Containers may be loaded according to batches, for example based on delivery routes, in a manner to reduce unloading time during delivery of items. The placement of a container in a delivery truck may also be based on factors including, but not limited to, the urgency of delivery, the promised delivery time, whether the item is a perishable food item, and the like. . In some embodiments, the storage compartment of the delivery truck may include a built-in storage space such as a cabinet, cell, shelf, rack, cage, or wheel cage. Each container carrier in the delivery truck may be identified by a container carrier identifier (eg, a barcode). The container carrier identifier may include information associated with the location of the container carrier within the storage compartment of the delivery truck. For example, four container carriers 360 may be placed against the back wall of the storage compartment, labeled 360_1-360_4 from left to right. Accordingly, the container carrier located at the rear left corner of the storage compartment of the delivery truck may be identified as container carrier 360_1, and the container carrier located at the rear right corner of the storage compartment of the delivery truck may be identified as container carrier 360_4. The visual or graphical depiction of the placement of the container carrier 360 may be generated by one or more computer-implemented systems of the system 100 , such as, for example, the transportation system 107 .

In some embodiments, the loading arrangement of containers on the container carrier 360 may be recorded to create a depiction of the delivery truck loading arrangement. For example, the transportation system 107 scans the container identifiers (eg, barcodes) of all containers contained in a container carrier and sends a command to the user-interface device to display an indication to scan the corresponding container carrier identifiers. can The system may generate a depiction of the loading batch based on the scanned information. In some embodiments, the loading arrangement may be presented to the user in a graphical or visual format. The loading arrangement may be printed on a sheet of paper, displayed on a user-interface device, or presented to the user prior to commencing their delivery operation.

At step 480 , one or more computer-implemented systems of system 100 (eg, transportation system 107 ) may, for example, send instructions to the user to display an indication to deliver items stored in containers loaded on delivery trucks. - can transmit to an interface device (eg, one of mobile devices 107A-107C). The user-interface device may display an indication requesting input from a user (eg, a delivery person or loader) to verify completion of the loading process prior to commencing delivery of the items. The user-interface device may 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 may send an instruction to the user-interface device to display an indication to record information associated with the order identifier, such as by scanning the order identifier. The user-interface device sorts the picked up item based on the storage location in the first step of the sorting process after the item is picked up, before the sorted item is shipped to the camp-site, after it arrives at the camp-site, After sorting the picked up item based on the delivery route in the second step of the sorting process, after putting the sorted item into a container, after loading the container into the delivery truck, an instruction to record the order identifier information may be displayed. . Information recorded at all stages of this 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, system 100 may generate a status update notification message in response to an inquiry from a customer about the status of an order, based on updated information stored in a database. In some embodiments, system 100 may preferentially generate a status update notification message for a customer based on updated information stored in a database.

Reference is now made to FIG. 5 , which illustrates an exemplary flow diagram of a process 500 for generating a visual depiction of a loading arrangement of a delivery vehicle, in accordance with disclosed embodiments. The flowchart is an exemplary sequence of steps in a process, and it will be appreciated that the steps may also be performed in other sequences. Also, 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 the 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 type, or other data. For example, the transportation system 107 may identify a small delivery vehicle for a narrow road delivery route, and a delivery truck operator on duty (eg, a truck driver) has only a valid driver's license for the small transportation vehicle. there may be In some embodiments, transportation system 107 may identify the delivery vehicle based on storage space requirements. For example, if there are 20 containers full of items to be delivered to one delivery route or sub-route, the system 100 may recommend a large delivery vehicle with more storage space.

At step 520 , one or more computer-implemented systems, such as transportation system 107 of system 100 , may send an instruction to the user-interface device to display an indication to determine a placement of the storage space within the delivery truck. In some embodiments, the delivery truck may include built-in storage space within the storage compartment, for example, cabinets, racks, shelves, cages, and the like. The delivery truck may include a storage compartment for receiving a removable storage unit such as, for example, a wheel cage.

In some embodiments, each storage space within the delivery truck may be identified using a storage space identifier or container carrier identifier. The container carrier identifier may include a barcode, label, tag or QR code. The container carrier identifier may include information associated with the location of the container carrier 360 within the storage compartment of the delivery truck. For example, four container carriers 360 may be placed from left to right against the rear wall of the storage compartment labeled 360_1 - 360_4 (not shown in FIG. 3 ). Accordingly, the container carrier located at the rear left corner of the storage compartment of the delivery truck may be identified as container carrier 360_1, and the container carrier located at the rear right corner of the storage compartment of the delivery truck may be identified as container carrier 360_4. 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, a driver or loader) may record the placement of the built-in storage space within the delivery truck, eg, by scanning the storage space identifier. In some embodiments, the database of system 100 may include information related to the placement of storage space in delivery trucks. For example, the database may include information related to the placement of 24 storage spaces within the 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. The container identifier may include a barcode, label, tag or QR code. The container identifier may include information associated with at least a camp-site and a delivery route for the items contained in the container. In some embodiments, one or more containers may be assigned a delivery route based on the number of items to be delivered along that route. The container identifier can be used as a QR or an indication of the final intended shipping address for the items in the container.

At step 540 , one or more computer-implemented systems, such as transportation system 107 of system 100 , may send a command to the user-interface device to display an indication to load containers into the storage space of the delivery truck. Containers can be loaded onto delivery trucks in a way that allows quick access to items that need to be unloaded during shipping.

At step 550 , one or more computer-implemented systems, such as transportation system 107 of system 100 , may send a command to the user-interface device to display an indication to associate each container with the storage space in which it resides. For example, the transportation system 107 scans the container identifiers (eg, barcodes) of all containers placed in the storage space and sends a command to the user-interface device to display an indication to scan the corresponding storage space identifiers. can In some embodiments, the instructions may include step-by-step instructions to associate the container with the storage space and upload the information to a database of the system 100 .

At step 560 , one or more computer-implemented systems, such as transportation system 107 of system 100 , may generate a visual depiction of the loading arrangement of containers and storage space based on the association established at step 550 . In some embodiments, the loading arrangement may be presented to a user (eg, a delivery truck driver) in a graphical or visual format. The loading arrangement may be printed on paper, displayed on a user-interface device, or presented to the user prior to commencing their delivery operation.

In some embodiments, the loading arrangement of the delivery truck may be displayed on a user-interface display of the delivery vehicle (eg, a graphical user-interface display screen of the delivery truck). In some embodiments, the visual depiction of the loading arrangement may be updated when delivery is complete. For example, when a delivery truck driver delivers an item to a customer and the container is empty, the display of the loading batch may indicate that the item in the container placed in storage has been delivered. This information is updated in the database to enable transportation system 107 and/or system 100 to determine whether an promised delivery date and time has been met.

Reference is now made to FIG. 6 , which is an alternative embodiment of a process 400 as described above, and illustrates a further step performed during the second step of the classification process. For example, during a second phase of the sorting process, items may be picked up at a camp-site and sorted based on a sub-route determined to a final destination for delivery regardless of order, where a particular item may be It may be associated with other items in the spell or the status of other items.

In some embodiments, the classification process may be a two-step classification process. A first step may include sorting the picked up item based on a camp-site to which the item may be directed. The camp-site may be determined, for example, based on the zip code of the intended final destination for items in the customer order. The second step may include sorting the selected item at the camp-site based on a delivery route through which the item may be sent for delivery. The delivery route may be determined, for example, based on an area or distance within an area indicated by a zip code.

In some embodiments, the miss-sort reduction procedure is to be implemented during the second step of the sorting process, ie, when the picked up item is sorted based on the delivery route/sub-route in the second step of the sorting process. can For example, when an item is picked up at a camp-site and placed in a container to be sorted based on a delivery route or sub-route, there may be a possibility that the item was placed in the wrong container and eventually in the wrong delivery vehicle. This can make it difficult for delivery truck drivers to scrutinize the whole and find the exact item that is going to the correct destination. One or more computer-implemented systems of system 100 may be configured to provide real-time alerts or alarms to operators (eg, classifiers) 301 when misclassifications occur, which may assist in detecting and reducing misclassifications. It is advantageous. Reducing misclassification can help drivers easily map items and deliver orders more efficiently.

In some embodiments, one or more computer-implemented systems, such as transportation system 107 of system 100 , may perform comparisons of destinations with existing routes and/or sub-routes, the amount of workload for each route and/or sub-routes. The route and/or sub-route item 208 that should be associated may be determined based on calculations, time of day, shipping method, shipping cost, and the like. In some embodiments, the operator 301 or machine may scan the item 208 or package 220 (eg, using the user-interface device 302 ) to determine its final destination. Once the final destination for delivery of the item 208 is determined, the operator will place the item (eg, item 208 ) into the container 350 based on the determined sub-route for the final destination of the item 208 . can In some embodiments, items may be classified based on a sub-route determined to a final destination for delivery, regardless of the order in question, and the item may be associated with another item in the order or the status of another item in the order. For example, upon receipt of an item at a camp-site (eg, camp area 215 ) from a packing area, the item is placed in a sub-route without waiting for other items of that order to arrive at that camp-site. Or it may be classified based on the delivery route. Because items are sorted based on sub-roots rather than based on the customer order to which they belong, it can reduce the dependency of waiting for all items in a customer order, thereby reducing the sorting rate. improve For example, a t-shirt that is not labor intensive on a customer order and requires less space in a delivery vehicle may be included. Customer orders can also be labor intensive, require longer times to be delivered to the camp-site for sorting, and include table sets that larger delivery vehicles may require. As items are sorted at the camp site, the t-shirt may be sorted based on its destination and loaded into a delivery vehicle based on the determined delivery area and/or delivery route. In this case, the t-shirts can be loaded onto the delivery vehicle before the table set, without waiting for the table set, which reduces the length of time the t-shirt is on the shelf waiting for the table set to be picked up, packed, sorted or shipped. In this case, the t-shirt may be delivered to the customer prior to the dining table set. This can increase space utilization, shorten display time, improve efficiency, shorten cycle time, and improve customer experience.

In some embodiments, one or more computer-implemented systems of system 100 are configured to: an operator assigned to sort item 208 , order identifier 305 , container 350 , container identifier 355 , item 208 . An association may be established between the identity of 301 , the user interface device 302 assigned to the operator 301 and the sub-route for delivery. In some embodiments, an operator (eg, operator 301 ) performs a barcode (eg, order identifier 305 ) and/or location associated with a package (eg, package 208 ) prior to initiating a process. identifier) can be scanned. The operator 301 may scan the barcode using the user interface device 302 . Upon receiving the barcode from the user interface device 302 , the system 100 configures a container 350 , a container identifier 355 , an operator 301 assigned to sort the item 208 , and an operator assigned to the operator 301 . User interface device 302 , a sub-route for delivery associated with item 208 , and order identifier 305 may be identified. System 100 may store the identified information. The system 100 may, for example, assign an item 208 to an order identifier 305 , a container 350 , a container identifier 355 , an identity of an operator 301 assigned to sort the item 208 , and the operator It may maintain a mapping table in tabular form, capable of storing all identified information, associated with the user interface device 302 assigned to 301 . The mapping table may be stored in a database including information related to customer orders and delivery schedules of customer orders.

In some embodiments, item 208 may arrive at a camp-site to be sorted into a delivery vehicle. The operator 301 may scan the barcode of the item 208 and the order identifier 305 of the customer order. Upon scanning, system 100 may retrieve information related to item 208 from a mapping table, which may be transmitted to operator 301 . This information may include the container 350 in which the item 208 is to be classified and contained. The operator 301 may receive an indication from the system 100 specifying the container 350 in which the item 208 should be classified and contained. The operator 301 can then place the item 208 into the container 350 and scan the container identifier 355 using the user interface device 302 . For example, information recorded by scanning may be stored in a database of system 100, which allows for tracking of packages as they are processed. A barcode on the container (eg, container identifier 355 ) or tote may also be scanned, which provides information associated with the location of the item contained in the container during the process of pickup, sorting, packing, shipping, etc. In some embodiments, the system 100 may, for example, assign an item 208 to an order identifier 305 , a container 350 , a container identifier 355 , a worker 301 assigned to sort the item 208 . may maintain a mapping table in tabular form, which may store all scanned information, associating it with the user interface device 302 assigned to the operator 301 . The mapping table may be automatically updated in real time when the operator 301 scans the container 305 containing the order identifier and the item being sorted using the user interface device 302 . In some embodiments, one or more computer-implemented systems of system 100 may analyze the stored data when starting a process with data scanned from operator 301 to determine whether an exception event has occurred. In some embodiments, the exception event is associated with stored information and one or more of an item 208 , an order identifier 305 , a container 350 , a container identifier 355 , and a worker 301 assigned for sorting the item. This can occur when there is a mismatch between the scanned information and the scanned input from the operator 301 . In some embodiments, the association between the item 208 , the order identifier 305 , the container 350 , the container identifier 355 and the identity of the worker 301 assigned to sort the item 208 is ) may be accessed, stored, updated, or modified in one or more databases connected to

In some embodiments, worker 301 may oversee that item 208 is classified into container 305 associated with container identifier 355 . In some embodiments, an operator 301 using the user interface device 302 may receive an indication to scan the item 208 and the container identifier 355 containing the item 208 . The operator 301 can use the user interface device 302 to scan the item 208 and the container identifier 355 . In some embodiments, the exception event includes stored information and one or more of an item 208 , an order identifier 305 , a container 350 , a container identifier 355 , and a worker 301 assigned for sorting the item; This can occur when there is a mismatch between the relevant scanned information, and the scanned input from the operator 301 . In an example embodiment, system 100 may compare scanned information (eg, order identifier 305 and container identifier 355 ) to stored information to determine whether an exception event has occurred. An exception event may occur when item 208 is misclassified and placed in a container that should not contain item 208 . When an exception event occurs, the operator 301 overseeing the classification of the item 208 may be notified in real time that a misclassification error has occurred. This notification or alarm may be provided by system 100 to operator 301 via user interface device 302 . Alternatively, the exception event notification may be displayed on a large display screen viewable by the operator 301 or the site 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 a plurality of items. In some embodiments, a customer order may include a plurality of sub-orders and each sub-order may include a plurality of items. One or more computer-implemented systems of system 100 may be configured to review a customer order and identify information such as a total number of items ordered, a description for each item ordered, a requested delivery time, the final destination of the item, and the like. .

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. The order identifier 305 may include a barcode, label, tag, alphanumeric code, OR code, and the like. The order identifier 305 may be a machine-readable optical label containing information about a customer order. The information contained in the order identifier 305 may include, but is not limited to, the final destination of the order, the total number of items in the customer order, the type of delivery requested, customer information, the promised delivery date and the promised delivery time, and the like. doesn't happen

In some embodiments, the system 100 for generating an order identifier may determine which storage location (eg, camp area 215 , hub area 213 ) and items in the customer order belong to based on the final destination of the customer order. A possible delivery route and/or sub-route may be determined. For example, based on the zip code of the final destination, the system may determine a storage location for the items in the customer order, and based on the identified distance or region at the final destination, the system may determine the storage location for the items in the customer order. You can decide the delivery route.

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

At step 630 , one or more computer-implemented systems of system 100 may associate an order identifier 305 with each item of a customer order. User interface device 302 may be configured to display an indication or alarm for a received customer order, requesting input (eg, confirmation of receipt from a user (eg, operator 301 )). Upon receiving input from a user, user interface device 302 may display a customer order and some or all of information associated with the customer order. An operator 301 (eg, a picker) picks up one or more items of a customer order, for example by scanning a barcode and an order identifier on the item, with an order identifier 305 received from one or more computer-implemented systems; Each picked up item can be associated. In some embodiments, associating an item of a customer order with an order identifier may include physically printing the order identifier using a label printer or barcode printer. A printed label or barcode may be affixed or affixed to the item, for example, to provide all employees with easy access to information related to ordering and delivery schedules. For example, an operator who has not received or does not have access to the original order identifier can scan the order identifier printed and pasted onto the item.

In some embodiments, an operator 301 (eg, a classifier) assigned to sort an item will receive the item 208 and determine the corresponding customer order. For example, operator 301 may use a device such as user interface device 302 to scan a barcode on item 208 . When worker 301 scans item 208, one or more computer-implemented systems of system 100, for every item in the customer order, to sort based on the determined final destination of the item, container 350 , determine the container identifier 355 and the route or sub-route. Items 208 may be classified based on delivery routes or sub-routes. The delivery route or sub-route may be predetermined by one or more computer implemented systems of system 100 . In some embodiments, one or more systems of computer-implemented system 100 (eg, SAT 101 , WMS 119 , SCM 117 ) interact with user interface device 302 to indicate the classification of an item. may be configured to communicate.

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

As an example, a customer may order a bouquet of flowers that should be delivered to a friend's house before 8 PM, and a battery pack that should 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 to indicate that there are two orders. Each item may be transported to a storage location (eg, storage cell 344 ) and sorted by a delivery route at the storage location based on its intended final destination. Each storage cell 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 comprising information identifying the camp-site and storage cell.

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a tote). All items in storage cell 344 (eg, item 208 ) may be contained in container 350 . In some embodiments, container 350 may be identified using container identifier 355 . The container identifier 355 may include information associated with a sub-route including the sub-route identifier. In some embodiments, container identifier 355 may include information related to camp-site and sub-root. For example, the container identifier may include the label CS3_SR1, where CS indicates the origin camp-site and SR indicates the sub-route designated for delivery of items contained in the container. Container identifier 355 may include, but is not limited to, a label, barcode, number, or tag.

At step 650 , process 600 may include a further step wherein one or more computer-implemented systems of system 100 may store information associated with a customer order in a mapping table based on the order identifier 305 . This information may include a container 350 associated with the item 208 , a container identifier 355 associated with each container 350 , and a delivery route or sub-route. In some embodiments, an operator (eg, operator 301 ) may scan a barcode (eg, order identifier 305 and/or location identifier) associated with a package (eg, package 208 ). can The operator 301 may scan the barcode using the user interface device 302 . Upon receiving the barcode from the user interface device 302 , the system 100 configures a container 350 , a container identifier 355 , an operator 301 assigned to sort the item 208 , and an operator assigned to the operator 301 . The user interface device 302 may determine a route or sub-route for delivery associated with the order identifier 305 . System 100 may, for example, assign item 208 to order identifier 305 , container 350 , container identifier 355 , worker 301 assigned to sort item 208 , route for delivery Alternatively, it may maintain a mapping table in tabular form, which may store all determined information associated with the sub-root and user interface device 302 assigned to the operator 301 .

At step 660 , the one or more computer-implemented systems of the system 100 configure the pre-allocated storage space determined by the one or more computer-implemented systems of the system 100 (eg, the storage cells 324 of the storage location 320 ). )) may send a command to the user interface device to display an indication or alarm to sort the picked up items of the customer order based on the The pre-allocated storage space may represent a camp-site to which items may be directed for further sorting. In some embodiments, one or more storage space may be allocated to a camp-site. For example, storage spaces 1-12 are allocated for camp-site 1, represented by storage cell 324-1, storage spaces 13-23 are allocated for camp-site 2, represented by storage cell 324-2, Storage space 24 may be allocated for camp-site 3 represented by storage cell 324 .

Each classified item may be shipped to a corresponding camp-site. In some implementations, the camp-site may be an on-site storage facility (eg, camp area 215 ) on the premises of the FC 200 . The sorted items may be transported to camp area 215 using, for example, a transport device such as a conveyor belt, forklift, hand truck, trolley, or cart. In some embodiments, the camp site may be an off-site storage facility, such as, for example, a warehouse or a storage unit separate from FC 200 . The sorted items may be transported to an off-site storage facility using, for example, a delivery truck. Sorted items belonging to a customer order may be shipped to the camp-site without waiting for the remaining items in the customer order to reduce idle time.

At step 670 , one or more computer-implemented systems of system 100 sort items picked up at the camp-site based on the delivery route and place the sorted items from storage cell 344 into containers (eg, containers 350))), or send a command to display an alarm to the user-interface device. The delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final destination in the customer order. The operator may sort the picked up items at the camp-site by placing the items in a storage cell (eg, storage cell 344 ) based on the delivery route. An operator may obtain delivery route information, for example, by scanning an order identifier on an item. Each of the storage cells 344 may be identified by a route identifier or a sub-root 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 (eg, a scanned order identifier) from a user, user-interface device 302 may display some or all of the customer order and information associated with the customer order. An operator 301 (eg, a classifier) places an order based on a container identifier 355 received from one or more computer-implemented systems, eg, by scanning a barcode and an order identifier 305 on the item 208 . Container 350 associated with identifier 305 may classify one or more items of a customer order. Items/items can be placed in a container without waiting for the rest of the items in the same customer order to reduce idle time.

In some embodiments, worker 301 may receive a single customer order with multiple items that should be delivered to the same delivery address. It may be desirable for items in an order to be delivered separately, as certain items may arrive before others. In some embodiments, the indication to sort may include certain additional details, such as sort order and delivery requirements, in order to most efficiently place all items in designated containers. In some embodiments, if one or more items in an order are not immediately available, the remaining items in the order may be delivered to the customer first, and missing items may be delivered later as they become available. For example, in a situation where one or more items in an order may be perishable, system 100 may determine that such items must be delivered within a few hours to their intended final destination, and missing items may be delivered later. In this situation, the system 100 may direct this to the operator 301 along with information related to the customer order including the container identifier. Operator 301 (eg, a classifier) may then sort one or more perishable items of the customer order into the indicated container 350 . Items/items can be placed in containers for loading on delivery trucks without waiting for other items in the customer order. In some embodiments, system 100 may be configured to determine an individually promised delivery date and time for each item in a customer order. For example, a customer order may include some items that are urgently subject to delivery and others that are subject to general delivery. The system may be configured to determine the promised delivery time based on the requested delivery type. In this situation, the system 100 may show the listed items to the operator 301 for faster delivery. Operator 301 (eg, a classifier) may then sort one or more of the items of the customer order from container 350 . Items/items can be placed in containers for loading on delivery trucks without waiting for other items in the customer order. Implementation of a method of individually shipping items of a customer order including multiple items without waiting for the customer order to be fully fulfilled before delivery may improve the sorting efficiency and overall efficiency of the process. Implementation of this approach can also improve package delivery efficiency by reducing cycle times and reducing the idle time of staff involved in the process.

At step 680, one or more computer-implemented systems of system 100 determine whether an exception event has occurred, such as the scanned order identifier 305 and container identifier 355 of the container 350 containing the item. You can compare information stored in mapping tables for orders. In some embodiments, as described above, the exception event includes stored information and an operator assigned to classify the item 208 , the order identifier 305 , the container 350 , the container identifier 355 , and the item 208 . This may occur when there is a mismatch between the scanned information associated with one or more of 301 , and the scanned input from the operator 301 . For example, worker 301 may classify item 208 as the wrong container, that is, a container not intended for that item 208 , in which case there is a mismatch between the order identifier 350 and the container identifier 355 . An exception event may be raised when a match is detected.

In some embodiments, worker 301 has placed an item in a designated container, but instead of scanning the container identifier in which the item is contained, it may scan the next order identifier. In this case, a mismatch between the order identifier 305 and the container identifier 355 may be detected. In some embodiments, operator 301 may identify items associated with other order identifiers and classify those items into containers 350 associated with order identifiers 305 . In this case, a mismatch between the order identifier 305 and the container identifier 355 may be detected. In some embodiments, the operator 301 may scan the order identifier 305 multiple times instead of scanning the container identifier 355 . In this case, a mismatch between the order identifier 305 and the container identifier 355 may be detected. In some embodiments, the operator 301 may scan the container identifier 355 multiple times instead of first scanning the order identifier 305 before scanning the container identifier 355 . In this case, a mismatch between the order identifier 305 and the container identifier 355 may be detected. In some embodiments, the operator 301 may scan the item 208 associated with the previous order identifier instead of the order identifier 305 . In this case, a mismatch between the order identifier 305 and the 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 a screen of the user interface device 302 . The displayed notification may include a miss-scan criterion of why the exception event occurred. In some embodiments, notifications may be sent to and displayed on the user interface device 302 in real time. In some embodiments, user interface device 302 may generate an alarm or warning message when a notification for an exception event is received. In some embodiments, notifications may be displayed on a large monitoring screen within a camp area, camp site, or any other area within a fulfillment center. This notifies the site manager/supervisor when an exception event occurs, allowing the respective classifier/operator to be notified of the error.

In some embodiments, the operator 301 may receive the report on the 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 may display a notification on the dashboard via a large monitoring screen in one or more of the pickup area, packing area, hub area, camp area, or any other area within the fulfillment center. can The system 100 may send a notification to the user interface device 302 that an exception event has occurred. In some embodiments, system 100 may provide a plurality of channels for delivering notifications or alarms to user interface device 302, including, but not limited to, text messages, SMS, phone calls, and in-app notifications. doesn't happen Notifications may appear on the user interface device 302 in the form of an icon, a badge on the icon of an application, in status bar format, in a report or tabular format, or as a more detailed message on the user interface device 302 .

7 is a schematic diagram of an exemplary notification dashboard in accordance with disclosed embodiments. The alert dashboard may be displayed to the operator 301 (eg, a classifier) and the site supervisor or manager via a user interface device 302 or a large display screen within the camp area. In an exemplary embodiment, the dashboard displays a notification with miss-scan criteria of why the exception event occurred. In some embodiments, the mapping table may include an association between the order identifier 305a , the container identifier CS3_SR1_a and the worker 301a based on the route or sub-route for the item 208 . When worker 301a scans the item associated with order identifier 305a, user interface device 302 will instruct worker 301a to place item 208 in a container (or tote) associated with container ID CS3_SR1_a. can This information may be stored in a mapping table. In the case of an exception event, there may be a mismatch between these identifiers, as shown in FIG. 7 . For example, in some embodiments, worker 301a may place item 208 in a container associated with container identifier CS3_SR1_b. The worker 301 may scan the container identifier CS3_SR1_b containing the item 208 . When the system 100 receives the scanned data, the system 100 compares the information stored in the mapping table with the scanned data received from the worker 301a, and when an exception event occurs, there may be a mismatch between the two. It can be determined that there is

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

In some embodiments, an exception event may occur when operator 301a uses the wrong device to scan an order. For example, the operator 301a may use the interface device 302 assigned to the operator 301b. The worker 301 may put the item 208 in a container associated with the container identifier CS3_SR1_a, and scan another container, that is, the container associated with the container identifier CS3_SR1_b. In this case, the system 100 may detect a mismatch between the container identifier, the order identifier, and the operator identifier. The system 100 may notify the site manager/supervisor by displaying a notification on a large display screen that an exceptional event may have occurred.

In some embodiments, an exception event may occur when operator 301a misses to scan the container after scanning the order identifier. For example, worker 301a may place item 208 into a container associated with container identifier CS3_SR1_a and scan another order identifier 305b or scan a previous order identifier eg order identifier 305a again. . In this case, the system 100 may determine that there may be an exception event due to a missing container (or tote) scan.

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

Although the present disclosure has been shown and described with reference to specific embodiments thereof, it will be understood that the present disclosure may be practiced in other environments, without modification. The foregoing description has been presented for purposes of illustration. It is not intended to be exhaustive or to be exhaustive of the precise forms or embodiments disclosed. Changes and adjustments will be apparent to those skilled in the art from consideration of the description and practice of the disclosed embodiments. Additionally, although forms of the disclosed embodiments have been described as being stored in memory, those of ordinary skill in the art will recognize that these forms are stored in secondary storage devices, such as hard disks or CD ROMs, or other forms of RAM or ROM, USB media, DVDs. , Blu-ray, or other optical drive media, it will be understood that the storage may be stored in other forms of computer-readable media.

A computer program based on the foregoing description and disclosed method is within the skill of the skilled developer. Several programs or program modules may be created using any technique known to those of ordinary skill in the art, or may be designed in connection with existing software. For example, a program section or program module may include .NET Framework, .NET Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective C, HTML, HTML/AJAX combination, XML, or Java Applet. can be designed within or by embedded HTML.

Moreover, although exemplary embodiments have been described herein, the scope of some or all of the embodiments is to be understood by those of ordinary skill in the art based on the present disclosure, with equivalent elements, modifications, omissions, and combinations (eg, spanning multiple embodiments). combinations of forms), adjustments and/or modifications. The limitations in the claims are intended to be broadly understood based on the language applied within the claims, and are not limited to the examples set forth herein or during the performance of the application. The examples are intended to be construed as non-exclusive. Additionally, the steps of the disclosed methods may be altered in any other way, including rearranging steps and/or inserting or deleting steps. Therefore, the descriptions and examples are to be considered exemplary only, and the true scope and spirit is intended to be indicated by the following claims and their full equivalents.

Claims (20)

memory storage for storing computer-executable instructions; and one or more processors configured to execute the stored instructions;
The commands are
generate an order identifier based on the received customer order, the order comprising a plurality of items;
associate each item in the customer order with the 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;
store, 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;
send a first indication to the at least one user-device to initiate a first sorting process to classify one or more items of the plurality of items based on the mapping;
classify the one or more items of the plurality of items based on the first indication;
receive, from at least one user-device, a first input related to a state of the first classification process;
a second indication to at least one user-device for display associated with a classifier to classify each classified item based on the delivery route using a second sorting process, regardless of the state of the first sorting process send;
receive, from at least one user-device, a second input related to a state of the second classification process;
compare the order identifier with the container identifier after the second sorting process;
detect that an exception event has occurred in the second classification process based on the comparison;
and send, to the at least one user-device associated with the classifier, a notification that the exception event has occurred. The method according to claim 1,
the processor is
determine an order identifier;
determine a container identifier;
use the mapping table to correlate the order identifier to the container identifier, wherein the mapping table lists each item of the plurality of items in the customer order mapped to the container identifier based on the order identifier. including-;
and determine that there is a mismatch between the order identifier and the container identifier. 3. The method according to claim 2,
the processor is further configured to send an indication to the at least one user-device to reclassify one or more of the plurality of items based on the detected mismatch between the order identifier and the container identifier. for computer implemented systems. 3. The method according to claim 2,
and the processor is further configured to send information associated with the detected exception event to a display device separate from the at least one user-device for display. 5. The method according to claim 4,
and the information associated with the detected exception event includes the real-time cause of the exception event. The method according to claim 1,
wherein the processor is further configured to detect successful completion of the second sorting process and generate a status update. 7. The method of claim 6,
and the processor is further configured to transmit information associated with the updated status to a display device separate from the at least one user-device for display. 7. The method of claim 6,
wherein the processor is further configured to delete the mapping between the container identifier and each item of the plurality of items of the customer order based on the order identifier upon successful completion of the second sorting process. system. The method according to claim 1,
and the processor is further configured to receive, from at least one user-device, an input comprising information associated with at least one of the order identifier or the container identifier. The method according to claim 1,
receiving a scan event comprising an invoice identifier and a scan event comprising an unrelated container identifier;
receiving a first scan event comprising a first order identifier from a first user-device, followed by receiving a second scan event comprising a second order identifier from the first user-device;
receiving a scan event comprising the first invoice identifier and subsequently receiving a second scan event comprising the second invoice identifier;
receiving a scan event comprising the first container identifier and subsequently receiving a second scan event comprising the second container identifier;
receiving a first scan event comprising a first order identifier from a first user-device, followed by receiving a second scan event comprising the first order identifier from the first user-device;
wherein the detection of one or more of the exception events is triggered. using the computer implemented system, generate an order identifier based on the received customer order, wherein the order includes a plurality of items;
associate each item in the customer order with the 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;
store, 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;
send a first indication to the at least one user-device to initiate a first sorting process to classify one or more items of the plurality of items based on the mapping;
classify the one or more items of the plurality of items based on the first indication;
receive a first input related to a state of the first classification process from at least one user-device;
a second indication to at least one user-device for display associated with a classifier to classify each classified item based on the delivery route using a second sorting process, regardless of the state of the first sorting process send;
receive, from at least one user-device, a second input related to a state of the second classification process;
compare the order identifier with the container identifier after the second sorting process;
detect that an exception event has occurred in the second classification process based on the comparison;
and sending, to the at least one user-device associated with the classifier, a notification that the exceptional event has occurred. 12. The method of claim 11,
Detecting the exception event includes:
determine an order identifier;
determine a container identifier;
correlate the order identifier to the container identifier using the mapping table, wherein the mapping table includes a list of each item of the plurality of items in the customer order mapped to the container identifier based on the order identifier —;
and determining that there is a mismatch between the order identifier and the container identifier. 13. The method of claim 12,
and sending an indication to at least one user-device to reclassify one or more of the plurality of items based on the detected mismatch between the order identifier and the container identifier. A computer implemented method. 12. The method of claim 11,
and sending information associated with the detected exception event to a display device separate from the at least one user-device for display. 15. The method of claim 14,
wherein the information associated with the detected exception event includes the real-time cause of the exception event. 12. The method of claim 11,
and detecting successful completion of the second sorting process and generating a status update. 17. The method of claim 16,
and transmitting information associated with the updated status to a display device separate from the at least one user-device for display. 17. The method of claim 16,
and deleting the mapping between each item of the plurality of items in the customer order and the container identifier based on the order identifier upon successful completion of the second sorting process. . 12. The method of claim 11,
and receiving, from at least one user-device, an input comprising information associated with at least one of the order identifier or the container identifier. 12. The method of claim 11,
receiving a scan event comprising an invoice identifier and a scan event comprising an unrelated container identifier;
receiving a first scan event comprising a first order identifier from a first user-device, followed by receiving a second scan event comprising a second order identifier from the first user-device;
receiving a scan event comprising the first invoice identifier and subsequently receiving a second scan event comprising the second invoice identifier;
receiving a scan event comprising the first container identifier and subsequently receiving a second scan event comprising the second container identifier;
receiving a first scan event comprising a first order identifier from a first user-device, followed by receiving a second scan event comprising the first order identifier from the first user-device;
wherein the detection of one or more of the exception events is triggered.

Images