TWI798613B - Computer-implemented system and method for sorting package - Google Patents

Abstract

Embodiments of the present disclosure include computer-implemented systems and methods for package delivery. The method may comprise receiving a customer order, generating an order identifier, associating each item of the customer order with the order identifier, and determining an intended delivery destination for each item. The method may further comprise causing the user-device to display a first indication to sort each item based on the storage space associated with the intended delivery destination, display a second indication to sort the sorted each item based on the delivery route, display a third indication to place the sorted each item into a container, without regard to a status of the other items of the customer order, and display a fourth indication to deliver the placed items of the plurality of items to the intended delivery destination, without regard to the status of the other items of the customer order.

Description

Computer implementation system and method for sorting parcels

The present disclosure generally relates to computerized systems and methods for package delivery to fulfill customer orders. In particular, embodiments of the present disclosure relate to inventive and non-conventional computerized systems, methods, and user interfaces for efficiently fulfilling customer Orders and deliver packages while maintaining high worker productivity at multiple zones within the fulfillment center.

[Cross Reference to Related Applications]

This application is a continuation-in-part of now-pending US Patent Application Serial No. 16/416,909, filed May 20, 2019, which is hereby incorporated by reference in its entirety.

A fulfillment center (FC) enables e-commerce merchants to outsource warehousing and shipping. Inventory management in FC is an essential part of fostering the best customer experience for online shoppers. Inventory management may encompass several steps ranging from receiving merchandise from sellers, stacking received merchandise for pick access, packing items, validating orders, and package delivery. Although current existing FCs and systems for inventory management in FCs are configured to handle large volumes of incoming and outgoing merchandise, the fulfillment of customer orders The efficiency and timeliness of the company may be limited, due in part to inefficient practices in obtaining items to fulfill orders. Delays in package delivery can lead to customer dissatisfaction and, in some cases, can affect a business' costs and profitability.

With the development and widespread acceptance of e-commerce, Internet shopping provides a one-stop shop for all shopping needs including food, furniture, electronics, clothes, books, etc. Each online order typically includes a combination of widely varying categories of items. While currently existing order fulfillment practices employ systems to obtain each individual item in an order in an efficient manner, the overall efficiency of order delivery is limited by the ability to obtain each individual item. For example, items are often stored in various parts of the FC based on category, and a packer may have to wait for a picker to pick up all the items for an order before they can be packaged. This can cause delays in subsequent steps in the packaging and delivery of packages to customers, which delays the throughput of the system and the efficiency of the computerized system that controls the shipping process.

In addition, the overall efficiency and throughput of the FC may be affected because although items are picked individually, they are packed simultaneously into one container before being loaded as a package on a delivery truck. Anticipated or unexpected delays in packaging can affect picking efficiency if the storage space in which the picked items are stored is inaccessible. The process of storing and shipping packages out of the FC includes several steps such as receiving, stacking, picking, sorting, packing, loading, delivering, and verifying order accuracy at each of the steps. For overall efficiency to be high, the efficiency of individual steps must also be high. For example, if the process consists of 10 steps and the efficiency of each step is higher than 90%, the overall efficiency is only 83.9%.

Additionally, currently existing FCs employ a team of workers to ensure smooth 24-hour operation. One of the technical challenges in the warehouse may be providing rapid Quickly communicate information such as urgent customer orders, priority shipping, and more. Current existing logistics and inventory management systems lack the ability to efficiently account for anticipated or unexpected urgency in customer orders, potentially resulting in customer dissatisfaction and associated higher inventory costs.

Accordingly, there is a need for improved methods and systems for efficient package delivery through simplification to reduce cycle times and committed delivery times while maintaining high overall throughput and efficient utilization of resources.

One aspect of the disclosure is directed to a computer-implemented method of package delivery. The method may include: receiving a customer order; generating an order identifier based on the customer order; associating each of a plurality of items of the customer order with the order identifier; and identifying an order identifier based on the order symbols to determine an intended delivery destination for each item, a storage space associated with the intended delivery destination, and a delivery route. The method may further include sending to a user a first indication to sort each item of the plurality of items using a first sorting process based on the storage space associated with the intended delivery destination. device for display; receiving a first input related to the status of said first sorting process from at least one user device; regardless of said status of said first sorting process, a second a second indication that the sorting process sorts each sorted item based on the delivery route configured to include the intended delivery destination is sent to at least one user device for display; from at least one user means receiving a second input relating to a state of said second sorting process; regardless of said state of said second sorting process, each item of said sorting will be placed in a a third indication of the container associated with the delivery route is sent to at least one user device for display; and sending a fourth instruction to deliver a placed item of the plurality of items to the intended delivery destination to at least one user or device for display.

Another aspect of the present disclosure is directed to a computer-implemented method of package delivery. The method may include: receiving a customer order; generating an order identifier based on the customer order; associating each of a plurality of items of the customer order with the order identifier; and identifying an order identifier based on the order symbols to determine an intended delivery destination for each item, a storage space associated with the intended delivery destination, and a delivery route. The method may further include sending to a user a first indication to sort each item of the plurality of items using a first sorting process based on the storage space associated with the intended delivery destination. device for display; receiving a first input related to the status of said first sorting process from at least one user device; regardless of said status of said first sorting process, a second a second indication that the sorting process sorts each sorted item based on the delivery route configured to include the intended delivery destination is sent to at least one user device for display; from at least one user means receiving a second input relating to a state of said second sorting process; regardless of said state of said second sorting process, each item of said sorting will be placed in a sending to at least one user device for display a third indication in a container associated with the delivery route; receiving a third input from at least one user device comprising information associated with a container identifier for the container; at sending a fourth instruction to deliver a placed item of the plurality of items to the intended delivery destination to at least one user device for display; receiving from at least one user device the placed a fourth input of information associated with an item's delivery schedule; and storing said first input, said second input, said third input, and said fourth input in a database associated with a computer-implemented system middle.

Another aspect of the present disclosure is directed to a computer-implemented system for package delivery. The system may include: memory storing instructions; and at least one processor configured to execute the instructions to: receive a customer order; generate an order identifier based on the customer order; Each of the items is associated with the order identifier; and an intended delivery destination, a storage space associated with the intended delivery destination, and a delivery route are determined for each item. The instructions executable by the processor to: sort a first indication of each item of the plurality of items using a first sorting process based on the storage space associated with the intended delivery destination sending to a user device for display; receiving a first input from at least one user device relating to a state of said first sorting process; irrespective of said state of said first sorting process, sending to at least one user device for display a second indication that each sorted item is sorted using a second sorting process based on the delivery route configured to include the intended delivery destination; at least one user device receives a second input related to the state of the second sorting process; regardless of the state of the second sorting process, each item in the sorted a third indication to be placed in a container associated with the delivery route is sent to at least one user device for display; and regardless of the status of other items of the plurality of items of the customer order Next, a fourth indication to deliver the placed item of the plurality of items to the intended delivery destination is sent to at least one user device for display.

Another aspect of this disclosure is directed at a computer for sorting parcels system. The system may include: memory storing instructions; and at least one processor configured to execute the instructions to: generate an order identifier based on a received customer order, the order including a plurality of items; causing the Each item of the customer order is associated with the order identifier; determining a storage container associated with each item, a container identifier associated with each container, and a delivery route based on the order identifier; based on the order identifier storing an association between each of said plurality of items of said customer order and said container identifier in a mapping table by said order identifier; a first sorting process will be initiated to sort based on said mapping sending to at least one user device a first indication of one or more of the plurality of items; sorting the one or more of the plurality of items based on the first indication; Receiving a first input from at least one user device relating to a state of said first sorting process; irrespective of said state of said first sorting process, a second sorting process will be used based on said A second indication is sent to at least one user device for display associated with the sorter to sort each sorted item according to the delivery route; receiving from at least one user device associated with the second sorting process A second input related to the status of the second sorting process; comparing the order identifier with the container identifier after the second sorting process; detecting that an exceptional event has occurred during the second sorting process based on the comparison ; sending a notification that the exceptional event has occurred to the at least one user device associated with the sorter.

Yet another aspect of the present disclosure is directed to a computer-implemented method of sorting packages, the method comprising: using a computer-implemented system to generate an order identifier based on a received customer order, the order including a plurality of items; each item of the customer order is associated with the order identifier; determining, based on the order identifier, the storage container associated with each item, the container identifier associated with each container, and a delivery route; storing an association between each of said plurality of items of said customer order and said container identifier in a mapping table based on said order identifier; a first sorting process will be initiated to Sent to at least one user device a first indication of sorting one or more of the plurality of objects based on the mapping; sorting the one of the plurality of objects based on the first indication one or more of: receiving a first input from at least one user device relating to a state of said first sorting process; regardless of said state of said first sorting process, to use a second a second indication that the sorting process sorts each sorted item based on the delivery route is sent to at least one user device for display associated with the sorter; A second input related to the status of a second sorting process; comparing said order identifier with said container identifier after said second sorting process; detecting a change in said second sorting process based on said comparison an exceptional event has occurred in the system; sending a notification that the exceptional event has occurred to the at least one user device associated with the sorter.

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

201, 222: Trucks

100: System/Network

101: Shipping Authorization Technology System

102A, 107A, 107B, 107C, 119A, 119B, 119C: mobile devices

102B: Computer

103:External front-end system

105:Internal front-end system

107: Transportation system

109:Seller Portal

111: Shipping and Order Tracking System

113: Fulfillment Optimization System

115: Fulfillment communication report gateway

117: Supply chain management system

119: Warehouse management system

121A, 121B, 121C: 3rd party fulfillment systems

123: Fulfillment Center Authorization System

125: Labor management system

200: Fulfillment Center

202A, 202B, 208: objects

203: Inbound area

205: buffer

206: forklift

207: unloading area

209: Picking area

210: storage unit

211: Packing area

213: Hub area

214: Transport agency

215: Camp area

216: wall

218, 220: Parcel

224A, 224B: delivery workers

226: car

300:Computer execution system/simplified package delivery system

301:Confluent Worker/Worker

301a, 301b: workers

302: User interface device

305, 305a, 305b: order identifier/sub-order identifier

320: the first storage location

324, 324_1, 324_2, 344: storage cells

340: Second storage location/camp

342: storage space

350: container

355, CS3_SR1_a, CS3_SR1_b: container identifier

360, 360_1, 360_2, 360_3, 360_4: container carrier

400, 500, 600: process

410, 420, 430, 440, 450, 460, 470, 480, 510, 520, 530, 540, 550, 560, 610, 620, 630, 640, 650, 660, 670, 680, 690: step

700: Notification Dashboard

FIG. 1A is a schematic block diagram illustrating an exemplary embodiment of a network including a computerized system of communications for enabling shipping, transportation, and logistics operations, consistent with disclosed embodiments.

FIG. 1B depicts a sample Search Result Page (SRP) including one or more search results and interactive user interface elements satisfying a search request, consistent with disclosed embodiments.

FIG. 1C depicts a sample Single Display Page (SDP) including a product and information about the product, as well as interactive user interface elements, consistent with disclosed embodiments.

Figure ID depicts a sample shopping cart page including items in a virtual shopping cart and interactive user interface elements consistent with disclosed embodiments.

FIG. 1E depicts a sample order page including items from a virtual shopping cart along with information about purchase and shipping and interactive user interface elements consistent with disclosed embodiments.

2 is a diagrammatic illustration of an exemplary fulfillment center configured to utilize the disclosed computerized system, consistent with disclosed embodiments.

3 is a diagrammatic illustration of an exemplary computerized unitized package delivery system configured to utilize the disclosed computerized system consistent with disclosed embodiments.

4 is a schematic diagram of an exemplary process flow for singularized package delivery consistent with disclosed embodiments.

5 is a schematic diagram of an exemplary process flow for generating a representation of a stowage configuration for a delivery vehicle, consistent with disclosed embodiments.

6 is a schematic diagram of an exemplary process flow for singularized package delivery consistent with disclosed embodiments.

7 is a schematic diagram of an exemplary notification dashboard consistent with disclosed embodiments.

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers will be used in the drawings and the following description to refer to the same or like parts. While several illustrative embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, substitutions, additions or modifications may be made to components and steps shown in the drawings, and the methods described herein may be modified by substituting, reordering, removing or adding steps to the disclosed methods illustrative method. Accordingly, the following detailed description is not limited to the disclosed embodiments and examples. Rather, the true scope of the invention is defined by the appended patent claims.

Embodiments of the present disclosure are directed to reducing cycle time and increasing the efficiency of package delivery by individually shipping items of the same order without waiting for remaining items, thereby avoiding slowing down computerized systems and processes systems and methods.

Referring to FIG. 1A , there is depicted a schematic block diagram 100 illustrating an exemplary embodiment of a network comprising computerized systems for enabling communications for shipping, transportation, and logistics operations. As shown in FIG. 1A , system 100 may include various systems, each of which may be connected to each other via one or more networks. The depicted system includes a shipment authority technology (SAT) system 101, an external front-end system 103, an internal front-end system 105, a shipping system 107, a mobile device 107A, a mobile device 107B, and a mobile device 107C, a vendor portal 109, shipping and Order tracking (shipment and order tracking; SOT) system 111, fulfillment optimization (fulfillment optimization; FO) system 113, fulfillment messaging gateway (fulfillment messaging gateway; FMG) 115, supply chain management (supply chain management; SCM) System 117, warehouse management system 119, mobile device 119A, mobile device 119B, and mobile device 119C (depicted as located within fulfillment center (FC) 200), 3rd party fulfillment system 121A, 3rd party fulfillment system 121B, and 3rd party fulfillment system 121A. 3-Party Fulfillment System 121C, Fulfillment Center Authorization (FC Auth) 123 and Labor Management System (labor management system; LMS)125.

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 can determine if an order is past its promised delivery date (PDD) and can take appropriate action, including initiating a new order, re-shipping items in an undelivered order, canceling an undelivered order, initiating and ordering Client's Contact, or the like. The SAT system 101 may also monitor other data, including outputs (such as the number of packages shipped during a particular time period) and inputs (such as the number of empty cartons received for shipping). SAT system 101 may also act as a gateway between different devices in system 100, enabling communication between devices such as external front-end system 103 and FO system 113 (eg, using store-and-forward or other techniques).

In some embodiments, the external front-end system 103 may be implemented as a computer system that enables external users to interact with one or more systems in the network 100 . For example, in embodiments where network 100 enables the presentation of the system to allow users to place orders for items, external front-end system 103 may be implemented as a web server that receives search requests, presents item pages, and solicits payment information. For example, the external front-end system 103 can be implemented as a computer or computer running software, such as Apache HTTP server, Microsoft Internet Information Service (IIS), NGINX, or the like. In other embodiments, the external front-end system 103 may operate and be designed to receive and process requests from external devices (not depicted), obtain information from databases and other data repositories based on those requests, and Custom web server software that responds to requests received.

In some embodiments, the external front-end system 103 may include one or more of a web cache system, a database, a search system, or a payment system. In one form, External front-end system 103 may include one or more of these systems, and in another aspect, external front-end system 103 may include an interface to one or more of these systems (e.g., server-to-server , database-to-database, or other network connection).

The exemplary set of steps illustrated by FIGS. 1B , 1C, 1D and 1E will help describe some operations of the external front-end system 103 . The external front-end system 103 can receive information from systems or devices in the network 100 for presentation and/or display. For example, the external front-end system 103 can host or provide one or more webpages, including a search result page (SRP) (for example, FIG. 1B ), a single detail page (Single Detail Page; SDP) (for example, FIG. 1C ), A shopping cart page (eg, FIG. 1D ), or an order page (eg, FIG. 1E ). A user device (eg, using mobile device 102A or computer 102B) can navigate to external front-end system 103 and request a search by entering information into a search box. The external front-end system 103 can request information from one or more systems in the network 100 . For example, external front-end system 103 may request results from FO system 113 that satisfy a search request. 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 represents an estimate of when the package will arrive at the user's desired location if ordered within a certain time period (eg, by end of day (11:59 pm)). (PDD is discussed further below with respect to FO system 113.)

The external front-end system 103 can prepare the SRP based on the information (eg, FIG. 1B ). The SRP may contain information that satisfies the search request. For example, this could include images of products that satisfy a search request. The SRP may also contain individual prices for each product, or information related to each product's enhanced delivery options, PDD, weight, size, offers, discounts, or the like. The external front-end system 103 may deliver the SRP (e.g., via a network) sent to the requesting user device.

The user device may then select a product represented on the SRP, such as by clicking or tapping a user interface or selecting a product from the SRP using another input device. The user device may formulate and send a request for information about the selected product to the external front-end system 103 . In response, the external front-end system 103 may request information related to the selected product. For example, the information may include additional information beyond that presented for the products on the respective SRP. This may include, for example, shelf life, country of origin, weight, size, number of items in the package, disposal instructions, or other information about the product. Information may also include recommendations of similar products (based on, for example, extensive data and/or machine learning analysis of customers who purchased this product and at least one other product), answers to frequently asked questions, reviews from customers, manufacturer information, image, or similar.

The external front-end system 103 can prepare an SDP (Single Detail Page) (eg, FIG. 1C ) based on the received product information. The SDP may also contain other interactive elements, such as a "Buy Now" button, an "Add to Cart" button, a quantity column, an image of an item, or the like. The external front-end system 103 may deliver the SDP (eg, via a network) to the requesting user device.

Requests that the user's device can receive an SDP listing product information. After receiving the SDP, the user device can then interact with the SDP. For example, a user requesting a user device may click or otherwise interact with a "Put in Cart" button on the SDP. This adds the product to the cart associated with the user. The user device may transmit this request to add the product to the shopping cart to the external front-end system 103 .

The external front-end system 103 can generate 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." The user device can click on the icon on the SRP, SDP or other pages or Interact with the icon in other ways to request a shopping cart page. In some embodiments, the shopping cart page may list all products that the user has added to the shopping cart, as well as information about the products in the shopping cart (such as the quantity of each product, the price per item of each product, the Product price based on associated quantity), information about PDD, delivery method, shipping cost, user interface elements for modifying products in the shopping cart (for example, deleting or modifying quantity), for ordering other products or setting products Options for recurring deliveries, options for setting interest payments, user interface elements for advancing to purchases, or the like. A user at the user device may tap on or otherwise interact with a user interface element (e.g., a button that says "Buy Now") to initiate a purchase of the products in the shopping cart. Buy. After doing so, the user device may transmit this request to initiate a purchase to the external front-end system 103 .

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 relists items from the shopping cart and requests entry of payment and shipping information. For example, an order page may include a request for information about the buyer (e.g., name, address, email address, phone number), information about the recipient (e.g., name, address, phone number, delivery information), shipping information (e.g., speed/method of delivery and/or picking), payment information (e.g., credit card, bank transfer, check, stored points), request for cash receipt (e.g., for tax purposes) UI elements, or similar. The external front-end system 103 can send the order page to the user device.

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

In some embodiments, the external front-end system 103 may be further configured to enable sellers to transmit and receive order-related information.

In some embodiments, internal front-end system 105 may be implemented as a computer system that enables internal users (eg, employees of the organization that owns, operates, or leases network 100 ) to interact with one or more systems in network 100 . For example, in embodiments where the network 101 enables the presentation of the system to allow users to place orders for items, the internal front-end system 105 may be implemented to enable internal users to view diagnostic and statistical information about orders, modify item information, or A web server that reviews order-related statistics. For example, the internal front-end system 105 may be implemented as a computer or computer-running software, such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, internal front-end system 105 may operate and be designed to receive and process requests from the systems or devices depicted in network 100 (and other devices not depicted), based on those requests from databases and other data The repository retrieves the information, and based on the retrieved information provides a response to the custom web server software for the received request.

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 analysis system, an order monitoring system, or 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 may include an interface to one or more of these systems (e.g. , server-to-server, database-to-database, or other network connections).

In some embodiments, the transport system 107 can be implemented as a computer system that implements communication between the devices in the network 100 and the mobile devices 107A to 107C. In some embodiments, the transport system 107 can be accessed from one or more mobile devices 107A To mobile device 107C (eg, mobile phone, smart phone, PDA, or the like) to receive information. For example, in some embodiments, nomadic device 107A-107C may comprise a device operated by a delivery worker. Delivery workers, who may be permanent employees, temporary employees, or shift employees, may utilize mobile devices 107A-107C to effectuate the delivery of packages ordered by users. For example, to deliver a package, a delivery worker may receive a notification on a mobile device indicating which package to deliver and where to deliver the package. Upon arrival at the delivery location, the delivery worker can locate the package (e.g., in the back of a truck or in the package's crate), use a mobile device to scan, or otherwise capture an identifier (e.g., a barcode) associated with the package. , image, text string, RFID tag, or the like), and deliver the package (e.g., by leaving it at the front door, leaving it with a guard, handing it over to the recipient, or the like) . In some embodiments, the delivery worker can capture a photo of the package and/or can obtain a signature. The mobile device may send communications to the transportation system 107, the information including information about the delivery including, for example, time, date, GPS location, photo, identifier associated with the delivery worker, identifier associated with the mobile device, or similar. Transport system 107 may store this data in a database (not depicted) for access by other systems in network 100 . In some embodiments, shipping system 107 may use this information to prepare and send tracking data to other systems, indicating the location of a particular package.

In some embodiments, certain users may use one type of mobile device (for example, a permanent worker may use a dedicated PDA with custom hardware such as barcode scanners, stylus, and other devices), while others use workers may use other types of mobile devices (e.g. casual or shift workers may utilize off-the-shelf mobile phones and/or smartphones).

In some embodiments, the transport system 107 can associate a user with each device. For example, the transport system 107 may store a user (represented by, for example, a user ID, an employee ID, or a phone number) and a mobile device (represented by, for example, an International Mobile Equipment Identity (IMEI), an International Mobile Subscription Identifier (International Mobile Subscription Identifier; IMSI), telephone number, Universal Unique Identifier (Universal Unique Identifier; UUID) or Globally Unique Identifier (Globally Unique Identifier; GUID) representation). Transportation system 107 may use this relationship in conjunction with data received at the time of delivery to analyze data stored in a database to determine, inter alia, a worker's location, worker's efficiency, or worker's speed.

In some embodiments, seller portal 109 may be implemented as a computer system that enables sellers or other external entities to electronically communicate with other aspects of information related to an order. For example, a seller may utilize a computer system (not depicted) to upload or provide product information, order information, contact information, or the like for products that the seller wishes to sell via the system 100 .

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

In some embodiments, shipping and order tracking system 111 may request and store information from the systems depicted in network 100 . For example, shipping and order tracking system 111 may request information from shipping system 107 . As discussed above, the transportation system 107 can be self-contained with a user (e.g., a delivery worker) or a vehicle (e.g., One or more mobile devices 107A-107C (eg, mobile phones, smartphones, PDAs, or the like) associated with one or more of the delivery trucks) receive the information. In some embodiments, shipping and order tracking system 111 may also request information from warehouse management system (WMS) 119 to determine the location of individual packages within a fulfillment center (eg, fulfillment center 200 ). Shipping and order tracking system 111 may request data from one or more of shipping system 107 or WMS 119, process the data upon request, and present the data to devices (e.g., user device 102A and user device 102B).

In some embodiments, fulfillment optimization (FO) system 113 may be implemented as a computer system that stores information on customer orders from other systems (eg, external front-end system 103 and/or shipping and order tracking system 111 ). The FO system 113 may also store information describing where a particular object is kept or stored. For example, some items ordered by a customer may be stored in only one fulfillment center, while other items may be stored in multiple fulfillment centers. In still other embodiments, certain fulfillment centers may be designed to stock only certain sets of items (eg, fresh produce or frozen products). The FO system 113 stores this information as well as associated information (eg, quantity, size, date received, date of expiration, etc.).

The FO system 113 can also calculate the 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 calculate the PDD for a product based on past demand for the product (e.g., how many times the product was ordered over a period of time), expected demand for the product (e.g., predicted how many customers will order the product in the upcoming period), network-wide past demand indicating how much the product has been ordered during the period, network-wide expectations indicating how much the product is expected to be ordered in the upcoming period demand, one or more counts of the products stored in each fulfillment center 200, which fulfillment center stores each product, prospective or current orders for the products, or the like.

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

In some embodiments, Fulfillment Communication Gateway (FMG) 115 may be implemented to receive communications from one or more systems in network 100, such as FO system 113, convert data in the communications to another format And a computer system that forwards the data in a converted format or protocol to other systems such as WMS 119 or 3rd party fulfillment system 121A, 3rd party fulfillment system 121B or 3rd party fulfillment system 121C and vice versa.

In some embodiments, supply chain management (SCM) system 117 may be implemented as a computer system that performs forecasting functions. For example, the SCM system 117 may determine the level of demand for a particular product based on, for example, past demand for the product, expected demand for the product, network-wide past demand, network-wide expected demand, stored in each A count of products in the fulfillment center 200, expected or current orders for each product, or the like. In response to this determined forecast level and the volume of each product in all fulfillment centers, the SCM system 117 may generate one or more purchase orders to satisfy the forecasted demand for the particular product.

In some embodiments, warehouse management system (WMS) 119 may be implemented as a computer system that monitors workflow. For example, WMS 119 can be downloaded from individual devices such as For example, devices 107A-107C or devices 119A-119C) receive event data indicative of discrete events. For example, WMS 119 may receive event data indicative of the use of one of these devices to scan a package. As discussed below with respect to fulfillment center 200 and FIG. 2 , during the fulfillment process, certain stages may be accessed by machines (e.g., automated or hand-held barcode scanners, RFID readers, high-speed cameras, such as tablet computers 119A). , mobile device/PDA 119B, computer 119C or the like) scans or reads the package identifier (eg, barcode or RFID tag data). WMS 119 may store each event indicative of a scan or read of a package identifier along with the package identifier, time, date, location, user identifier, or other information in a corresponding database (not depicted), and may store this Information is provided to other systems (eg, shipping and order tracking system 111).

In some embodiments, WMS 119 may store information that enables one or more devices (e.g., device 107A-device 107C or device 119A-device 119C) and one or more users (the one or more users and the network 100 associated) associated information. For example, in some cases, a user (such as a part-time or full-time employee) may be associated with a mobile device because the user owns the mobile device (eg, the mobile device is a smartphone). In other cases, a user may be associated with a mobile device due to the user taking temporary custody of the mobile device (e.g., the user gets the mobile device at the beginning of the day, will use the mobile device during the day, and will return said mobile device at the end of the day).

In some embodiments, WMS 119 may maintain a work log for each user associated with network 100 . For example, WMS 119 may store information associated with each employee, including any specified process (e.g., unload from truck, pick item from pick area, rebin wall work, pack item), use identification character, location (e.g., floor or zone in fulfillment center 200), number of units moved through the system by employees (e.g., number of items picked, number of items packed), and devices (e.g., devices 119A to device 119C), an associated identifier, or the like. In some embodiments, WMS 119 may receive log-in and log-out information from a timekeeping system, such as a timekeeping system operating on devices 119A-119C.

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

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

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

The particular configuration depicted in Figure 1A is an example only. For example, although FIG. 1A depicts FC Auth system 123 connected to FO system 113 via FMG 115, not all embodiments require this particular configuration. In fact, in some embodiments, the systems in network 100 may be connected to each other via one or more public or private networks, including the Internet, intranets, wide-area networks (Wide-Area Networks) Network; WAN), Metropolitan-Area Network (MAN), wireless network conforming to IEEE 802.11a/b/g/n standards, leased lines, or the like. In some embodiments, one or more of the systems in network 100 may be implemented as one or more virtual servers implemented at a data center, server farm, or the like.

FIG. 2 depicts a fulfillment center 200 . Fulfillment center 200 is an example of a physical location that stores items for shipment to customers when ordered. Fulfillment center (FC) 200 may be divided into zones, each of which is depicted in FIG. 2 . In some embodiments, these "zones" can be thought of as virtual divisions between the different stages of the process of receiving, storing, retrieving, and shipping items. Thus, although "regions" are depicted in FIG. 2, other divisions are possible, and regions in FIG. 2 may be omitted, duplicated, or modified in some embodiments.

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

Workers will receive items in the inbound area 203 and may use a computer system (not pictured) to check the items for damage and correctness as appropriate. For example, a worker may use a computer system to compare the quantities of items 202A and 202B with the ordered quantities of the items. If the quantities do not match, the worker may reject one or more of item 202A or item 202B. If the quantities do match, a worker can move the items to the buffer zone 205 (using, for example, a dolly, dolly, forklift, or manually). The buffer zone 205 may be a temporary storage area for items that do not currently need to be in the picking area (eg, due to the presence of a sufficiently high number of items in the picking area to meet forecasted demand). In some embodiments, forklifts 206 operate to move items around buffer zone 205 and between inbound area 203 and unloading area 207 . If item 202A or item 202B in the pick area is needed (eg, due to forecasted demand), a forklift may move item 202A or item 202B to unload area 207 .

The unloading area 207 may be an area of the FC 200 where items are stored prior to moving them to the picking area 209 . A worker ("picker") assigned to a picking task may approach item 202A and item 202B in the picking area, use a mobile device (e.g., device 119B) to scan the barcode of the picking area, and scan the barcode associated with item 202A. and the barcode associated with item 202B. The picker may then fetch the item to the picking area 209 (eg, by placing the item on a cart or carrying the item).

Picking area 209 may store items 208 in a storage unit of FC 200 210 on the area. In some embodiments, storage units 210 may include one or more of physical shelves, bookshelves, boxes, totes, refrigerators, freezers, cold storage areas, or the like. In some embodiments, picking area 209 may be organized into multiple floors. In some embodiments, workers or machines can move items into the picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyor belts, carts, dollies, dollies, automated robots or devices, or manually . For example, the picker can place the items 202A and 202B on a trolley or cart in the unloading area 207 and walk the items 202A and 202B to the picking area 209 .

Pickers may receive instructions to place (or “stack”) items at specific points in picking area 209 , such as specific spaces on storage units 210 . For example, a picker may use a mobile device (eg, device 119B) to scan item 202A. The device may indicate where the picker should stack the item 202A, for example using a system of indicating aisles, shelves, and locations. The device may then prompt the picker to scan the barcode at the location before stacking the item 202A at the location. In some embodiments, the device may send data (eg, via a wireless network) to a computer system, such as WMS 119 in FIG. 1A , indicating that object 202A has been stowed at that location by a user using device 119B. place.

Once a user places an order, a picker may receive an instruction on device 119B to retrieve one or more items 208 from storage unit 210 . A picker may retrieve an item 208 , scan a barcode on the item 208 , and place the item 208 on the transport mechanism 214 . Although the transport mechanism 214 is shown as a slide, in some embodiments the transport mechanism may be implemented as one or more of a conveyor belt, elevator, cart, forklift, dolly, trolley, or the like. Items 208 may then arrive at packing area 211 .

Packing area 211 may receive items from picking area 209 of FC 200 and place The items are packaged into boxes or bags for eventual shipment to the customer's area. In packing area 211, workers assigned to receive items ("merge workers") will receive items 208 from picking area 209 and determine which order the items 208 correspond to. For example, a merge worker may use a device such as computer 119C to scan a barcode on item 208 . Computer 119C may visually indicate which order item 208 is associated with. This may include, for example, a space or "cell" on wall 216 that corresponds to an order. Once an order is complete (eg, because a cell contains all the items for said order), the merge worker can instruct a pack worker (or "packer") that the order is complete. A packer can retrieve items from a cell and place the items in a box or bag for shipping. The packer may then send the box or pack to hub zone 213, eg, via forklift, cart, dolly, dolly, conveyor belt, manually, or otherwise.

Hub area 213 may be the area of FC 200 that receives all boxes or packages ("packages") from packing area 211. Workers and/or machines in hub zone 213 can retrieve packages 218 and determine which part of the delivery zone each package is intended to go to, and deliver the packages to the appropriate camp zone 215 . For example, if a delivery area has two smaller sub-areas, the package will go to one of the two camp areas 215 . In some embodiments, a worker or machine may scan the package (eg, using one of devices 119A-119C) to determine its final destination. Dropping the package to a camp area 215 may include determining a portion of a geographic area to which the package is going, for example (eg, based on a postal code), and determining a camp area 215 associated with that portion of the geographic area.

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

Workers and/or machines in camp area 215 may determine which route and/or sub-route a package 220 should be associated with, for example, based on a comparison of the destination to existing routes and/or sub-routes, for each Calculation of workload for routes and/or sub-routes, time of day, shipping method, cost of shipping package 220, PDD associated with items in package 220, or the like. In some embodiments, a worker or machine may scan the package (eg, using one of devices 119A-119C) to determine its final destination. Once a package 220 is assigned to a particular route and/or sub-route, workers and/or machines may move the package 220 for delivery. In exemplary FIG. 2 , camp area 215 includes trucks 222 , cars 226 , and delivery workers 224A and 224B. In some embodiments, truck 222 may be driven by delivery worker 224A, where delivery worker 224A is a full-time employee delivering packages for FC 200, and truck 222 is owned, leased, or operated by the same company that owns, leases, or operates FC 200. In some embodiments, car 226 may be driven by delivery worker 224B, where delivery worker 224B is a "flexible" or temporary worker who delivers on an as-needed basis (eg, seasonally). Car 226 may be owned, leased or operated by delivery worker 224B.

FIG. 3 shows an illustrative schematic diagram of a computer-implemented system 300 for unitized package delivery. In some embodiments, the system 300 may include a merge worker 301, a picked item 208 with an order identifier 305 (e.g., barcode, tag, label), a user interface device 302 (e.g., mobile device/PDA 119B) . The system 300 may further include: a first storage location 320 (eg, packaging area 211 ) including storage cells 324 (eg, storage cells 324_1 , storage cells 324_2 ), a second storage location 340 ( referred to herein as the camp), and the delivery truck 201. The first storage location 320 and the campsite 340 (e.g., campsite area 215) may be based on Sort objects based on different information related to the final destination. As one example, at first storage location 320, items (e.g., item 208) may be sorted (e.g., based on postal code) based on the geographic area the package is going to, and at campsite 340, items may be sorted (e.g., based on route) number) to sort items based on delivery routes or sub-routes. (Other sorting methods are also possible.) Delivery routes or sub-routes may be predetermined by one or more computer-implemented systems of system 100 . In some embodiments, one or more systems of computer-implemented system 100 (eg, SAT 101 , WMS 119 , SCM 117 ) may be configured to communicate with user interface device 302 to indicate sorting of objects.

Figure 3 illustrates an exemplary unitized package delivery system. As used herein, the term "singulation" refers to a single shipment of items for a customer order that includes multiple items without waiting for the customer order to be fully fulfilled prior to shipping. Package delivery by unitization may have numerous advantages over existing systems for package delivery. Delivery by a unitized package may have some or all of the advantages discussed herein, as well as others.

i. Improved packing efficiency - In current existing package delivery systems, a merge worker can wait to pack all items of an order into a single package, and the package can be placed on the merge wall space associated with a particular order for further processing Processing, including sorting or shipping. In contrast, in the unitized package delivery system 300, the packer can sort items individually into storage cells (e.g., storage cells) without waiting for other items of the order to arrive at the packer's station or packing area. 324_1), thereby reducing the idle time of packers. Reducing the idle time of each packer allows for an overall increase in packing efficiency.

ii. Increased picking density - In current existing package delivery systems, pickers pick items sequentially to fulfill customer orders. For example, a picker may pick all items of order 1 before picking items of order 2. This sequential approach to picking results in time and efficiency losses as pickers spend more time transitioning than picking items. In contrast, the singularized package delivery system 300 may allow for increased picking density since pickers may be tasked to pick items based on their location and not based on customer orders. For example, a picker may be tasked with picking items that are near his current physical location but may be associated with other customer orders. This parallel approach to picking can increase picking density by reducing the time spent by pickers in transition.

iii. Improved Traceability - As shown in FIG. 3, in the unitized package delivery system 300, a worker (eg, worker 301) can scan and track a package (eg, package 208) Associated barcode (eg, order identifier 305 and/or location identifier). Additionally, barcodes can be scanned periodically during the process or upon receipt of a prompt. Information recorded, such as by scanning, may be stored in a database of the system 100, allowing packages to be tracked as they undergo processing. Barcodes of containers or totes can also be scanned, providing information associated with the location of the items contained in the container during the process of picking, sorting, packing, shipping, etc., allowing container and package traceability.

iv. Faster sorting - After receiving items at a camp (eg, camp area 215 ) from a packing area, items can be sorted based on sub-routes or delivery routes without waiting for other items of the order to arrive at the camp. Since the items are sorted based on the sub-routes and not based on the customer order to which the items belong, the shelf life of the items can be reduced, thereby improving the sorting rate. This also results in better space utilization, improved worker efficiency, reduced cycle times, and an enhanced customer experience.

v. Reduced storage time - Singulation of items can enable a reduction in the duration of items sitting on shelves waiting to be picked, packed, sorted or shipped, as they can be processed without regard to the status of other items of the order said object. The reduced storage time of items can reduce the associated costs associated with inventory management and reduce the risk of mishandling and misplacement of items.

vi. Reduced "ready to load" time - In existing package delivery and delivery systems, employees such as workers, drivers, loaders, stewards, floor supervisors, etc. may spend a significant amount of their time at the start of a shift or work period For example to ensure that all items that belong to an order are loaded. Such a system may be inefficient in utilizing resources such as manpower and time, both of which may increase operating costs and affect throughput. Singulation of items can reduce load setup time as employees load containers or container carriers such as totes, cages, etc. into delivery trucks based on planned delivery areas and delivery routes.

vii. Improved loading and delivery efficiency - delivery trucks can be loaded more efficiently since items are placed in large standardized totes or containers based on the delivery route. Additionally, items remain in standardized containers until delivery, thereby minimizing damage or misplacement due to handling. Large standardized totes or containers allow loaders to follow easy instructions to load trucks and allow drivers to easily map items and deliver orders more efficiently.

In some embodiments, system 100 can be configured to receive customer orders. A customer order can include multiple items. In some embodiments, each customer order may include multiple sub-orders, each of which may include multiple items. For example, a customer order may include three sub-orders. The first sub-order may be a rush order for toothpaste, toothbrush, and mouthwash, the second sub-order may include normal delivery of cheese, biscuits, and potato chips, and the third sub-order may include delayed delivery of beverages. System 100 can receive customer orders and generate order identifiers 305 associated with each of the items ordered. exist In some embodiments, system 100 may generate a unique sub-order identifier associated with each sub-order (e.g., sub-order identifier 305a for a first sub-order, sub-order identifier 305b for a second sub-order , and the suborder identifier for the third suborder).

In some embodiments, order identifier 305 and sub-order identifiers (e.g., sub-order identifier 305a, sub-order identifier 305b, or sub-order identifier) may include information including, but not limited to, the number of items ordered, pending The urgency of the delivered item, the destination of the item to be delivered. In some embodiments, the order identifier 305 may also contain information about several sub-orders within a single order. The system 100 can send an indication to the user interface device 302 that the order includes a number of sub-orders, and an urgency associated with each sub-order. Pickers can fulfill orders or sub-orders accordingly.

In some embodiments, one or more pickers may receive an indication related to the urgency of the sub-order while retrieving items for other customer orders. A picker may retrieve items for the urgent sub-order based on their current location within the picking area 209 and send the items onward to the packing area 211 . For example, if an urgent sub-order includes a toothbrush and a pair of socks, a picker in or near the oral hygiene section can retrieve the toothbrush, and a picker in or near the apparel section A clerk can retrieve the pair of socks, allowing for improved picking density. Once the container or tote is full, the items can be transported to the packing area 211 . This approach can increase picking efficiency by picking items based on the picker's location and not based on customer orders, thereby reducing cycle time and improving overall delivery efficiency.

In some embodiments, the system 100 may send instructions to a user device (eg, smartphone 119B, or computer 119C) such that the device instructs the picker to print the order identifier 305 . In some embodiments, a user device may include a configured Hand-held devices such as PDAs marked with print. Alternatively, system 100 may include a printing device (not depicted) such as an indicium printer, inkjet printer, or laser printer. The printing device may be configured to receive from one of the computer-implemented systems of system 100 an instruction to print a sign, order, memo, or the like. The instructions may further include requesting the picker to associate the printed order identifier 305 with the items of the customer order, such as by affixing the printed order identifier 305 to the picked items 208 . In some embodiments, the system 100 can be configured such that the order identifier 305 is electronically associated with the items of the customer's order. For example, system 100 may update a database that includes information related to all incoming customer orders.

The merge worker 301 can receive the picked item 208 in the packing area 211 . In some embodiments, amalgamation worker 301 may receive information associated with a customer order from system 100 using user interface device 302 (eg, smartphone 119B). User interface devices 302 may include, but are not limited to, handheld display devices (e.g., tablet computer 119A), smartphones (e.g., mobile device/PDA 119B), computers (e.g., computer 119C), body-mounted displays, head-mounted display etc. User interface device 302 may be substantially similar to a mobile device, such as, for example, computer 119C of FIG. 1A . User interface device 302 may communicate and exchange information with, for example, WMS 119 .

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, delivery urgency of the ordered items, destination location of the items to be delivered, and the like. In some embodiments, the user interface display may be a visual display or an audiovisual display. For example, if the order is "urgent", the user interface device 302 may accept Receive audiovisual messages indicating requests to expedite order fulfillment. In some embodiments, the user interface device 302 may be configured to receive user input and provide feedback to the user via one or more interactive elements of the user interface display. For example, the user interface device 302 may provide an audio, visual, or tactile notification to the user via one or more interactive elements of the user interface display and indicate a request to acknowledge receipt of the notification. In some embodiments, the user interface device 302 may include data recording capabilities (such as barcode scanning, optical character reader, etc.) to record the information of the order identifier 305 . User interface device 302 may be configured to temporarily store recorded information and later upload to a database in one of the computer-implemented systems of system 100 . In some embodiments, the user interface device 302 can automatically upload the recorded information to a database.

In some embodiments, the user interface device 302 may receive an instruction to review the order identifier 305 associated with the picked item 208 via an interactive element of the user interface display. For example, one of the computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, or SAT 101) may generate a display to user interface device 302 indicating to the user to initiate a review of the order identifier associated with item 208 305 instructions. Reviewing order identifier 305 may include determining a final destination for delivery of item 208 by, for example, scanning or reading order identifier 305 . For example, scanning an order identifier (e.g., a barcode) using a barcode scanning device can reveal information associated with the order identifier, such as the final destination of the items in the order, the urgency of delivery, the number and description of the items ordered wait. In some embodiments, a customer order may include several sub-orders and each sub-order may further include several items. It should be appreciated that item 208 may include a package containing one or more items of a customer order.

After determining the final destination for delivery of the item 208, the merge worker 301 may place the item 208 in the first storage location 320 based on the determined final destination. middle. 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 sorting location. In some embodiments, the first storage location 320 may comprise a confluence wall, a storage unit, a storage shelf with cells, or a cabinet. Storage means of other organizations may also be used.

In some embodiments, the item 208 may be sorted into the storage cell 324 of the first storage location 320 based on the destination of the item 208 without regard to the status of the order or other items of the order that may be associated with the item. . In current existing systems, a merge worker may wait to pick all items of an order before sorting the order for delivery. In contrast, in the disclosed embodiments, each item can be considered an individual order and sorted based on destination without regard to the status of other items of the order. This reduces idle time for merge workers, thereby increasing packaging efficiency. In some embodiments, packing efficiency as disclosed herein may be referred to as the number of items packed within a certain period of time. For example, packaging efficiency can be expressed in units per hour (UPH). Other efficiency metrics may also be used. Singulation of items can also reduce the shelf life of an item (defined herein as the duration an item sits on a shelf before it is picked, packed, sorted, or shipped), thereby reducing the associated costs associated with inventory management. cost and reduce the risk of mishandling and misplacement of items.

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

In some embodiments, the user interface device 302 can notify the merge worker 301 to place the object 208 in the corresponding storage cell 324 based on the determined destination location of the object 208 via an instruction. 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 a camp to which item 208 may be directed. The merge worker 301 can place the object 208 in the corresponding storage cell 324 .

In some embodiments, merge worker 301 may receive, via user interface device 302 , an instruction to associate object 208 with a corresponding storage cell 324 in which object 208 is placed. For example, the merge worker 301 may be requested to scan the order identifier 305 and the camp identifier to establish an association between the item 208 and the camp for sorting. Information related to the order identifier of the placed item and the camp identifier of the storage cell in which the item is placed may be automatically updated to the database including information related to the customer order and the delivery schedule of the customer order.

In some embodiments, if campsite 340 is an on-site facility, items may be transported using transportation means such as, for example, a conveyor belt, forklift, pallet, dolly, or in a tote. For off-site facilities, a delivery truck or the like may be used to transport items.

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

In some embodiments, camp 340 may include one or more storage spaces 342 . The storage space 342 may include, but is not limited to, a wall with storage cells, a storage unit, a storage shelf with cells, or a cabinet. Storage means of other organizations 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 item 208 .

Workers at camp 340 may receive one or more items 208 from storage location 320 . A worker (eg, a picker) may review the order identifier 305 associated with the picked item 208 . In some embodiments, the worker 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 (e.g., WMS 119, SCM 117, or SAT 101) can generate a start review order associated with item 208 to the worker to be displayed on user interface device 302 An indication of the identifier 305 . Review order identifier 305 may include determining the final destination of item 208 .

After determining the final destination for delivery of item 208 , the worker may place the item (eg, item 208 ) in storage cell 344 based on the determined sub-route for the final destination of item 208 . Each storage cell 344 of a campsite 340 may be associated with a sub-route.

In some embodiments, the user interface device 302 may notify the worker to place the object 208 in the corresponding storage cell 344 based on the determined final destination of the object 208 via an instruction. 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 a storage location 344 to which item 208 may be directed. The worker can place the object 208 in the corresponding storage cell 324 based on the instruction from the user interface device 302 .

The association of each storage cell 344 with the corresponding sub-way can be identified using the sub-way identifier. Sub-route identifiers may include, but are not limited to, labels, barcodes, numbers, or labels. Although only a limited number of storage cells 344 are shown, it should be understood that camp 340 may include any number of storage cells 344 .

In some embodiments, items may be sorted into storage cells 344 based on determined sub-routes for delivery to the final destination without regard to the status of the order or other items of the order that may be associated with the item. middle. In current existing delivery systems, a sorter may wait to receive all items of an order before preparing the order for delivery. In contrast, in the disclosed embodiments, each item can be treated as an individual order and sorted based on the determined sub-routes for delivery without regard to the status of the other items of the order . This can reduce idle time for sorters in the camp area, thereby increasing sorting efficiency and overall package delivery efficiency.

In some embodiments, the user interface device 302 can be configured to display an indication associating the object 208 with the corresponding storage cell 344 in which the object 208 is placed. For example, an instruction may include a request for a scan order identifier 305 and a sub-route identifier to associate the item 208 with a sub-route for delivery. Information related to the order identifier 305 of the placed item and the sub-route identifier of the storage cell 344 in which the item is placed can be automatically updated to include information related to the customer order and the delivery schedule of the customer order library.

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a handbag). All items of storage cells 344 (eg, items 208 ) may be placed in container 350 . In some embodiments, container identifier 355 may be used to identify container 350 . Container identifier 355 may include information associated with the sub-routes containing the sub-routes identifiers. In some embodiments, the container identifier 355 may include information related to the campsite and sub-route. For example, a container identifier may include the label CS3_SR1, where CS indicates the origin camp and SR indicates the designated sub-route for delivering the items in the container. Container identifier 355 may include, but is not limited to, labels, strips codes, numbers or labels.

In some embodiments, the user interface device 302 may be configured to display a notification or an indication to place the object 208 in a corresponding container 350 based on the determined final destination of the object 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 determine a container 350 in which item 208 may be placed. The worker may place the object 208 into the corresponding container 350 based on the instructions 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 associating the object 208 with the corresponding container 350 in which the object 208 is placed. For example, instructions may include a request to scan order identifier 305 and container identifier 355 to establish an association between item 208 and container 350 for package delivery. Information related to the order identifier 305 of the placed item 208 and the container identifier 355 of the container 350 in which the item is placed may be automatically updated to a database including information related to customer orders and delivery schedules for customer orders .

In some embodiments, one or more containers 350 may be loaded onto a delivery vehicle (eg, delivery truck 201 ) for delivery to customers. Containers 350 may be deployed in delivery trucks 201 on a sub-route basis. For example, a package or item to be delivered at a destination closer to the start of the sub-route (eg, item 208) can be placed closer to the entry and exit gate so that the delivery worker can directly access the package. In some embodiments, the container 350 containing the rush order may be placed closer to the access door to enable quick access to the package. In some embodiments, sub-routes may be adjusted based on the type and urgency or PDD of the order. In some embodiments, both the sub-routes and the configuration of containers in the delivery truck 201 can be adjusted based on the customer order and PDD.

Container 350 may be placed on container carrier 360 prior to loading in delivery truck 201 . Container carrier 360 may include a cart, trolley, cage, basket, or the like. In some embodiments, container carrier 360 may include an identifier, such as a barcode, indicia, or label. In some embodiments, the user interface device 302 may notify the delivery worker or truck loader to place the container 350 on the delivery truck 201 based on a predetermined configuration via instructions. For example, based on PDD, one of the computer-implemented systems of system 100 (e.g., transport system 107) may determine the configuration of containers 350 on container carriers 360 or the configuration of one or more container carriers 360 on delivery truck 201 . A delivery worker or truck loader may place container 350 or container carrier 360 in delivery truck 201 based on a determination made by one of the computer-implemented systems of system 100 (eg, transportation system 107 ). User interface device 302 may indicate to a delivery worker or truck loader a representation of the configuration of containers 350 within container carrier 360 and/or the configuration of container carrier 360 in delivery truck 201 .

In some embodiments, user interface device 302 may be configured to display a representation of deployed containers 350 and one or more container carriers 360 in delivery truck 201 . The format of the presentation may include one of visual, tabular, audio, audio-visual, or a combination thereof. In some embodiments, the user interface display may include a representation of the deployed containers 350 and container carriers 360 in the delivery worker's delivery truck 201 .

In some embodiments, the delivery worker may receive an instruction generated by one of the computer-implemented systems of system 100 , such as transportation system 107 , to begin driving on the sub-route after delivery truck 201 has been loaded. The delivery worker may receive instructions via a user interface display on the user interface device 302 .

Reference is now made to FIG. 4 , which shows an exemplary flowchart of a process 400 for singularized package delivery, consistent with disclosed embodiments. The process may include: receiving customer orders; generating an order identifier based on the customer order; determining an intended final destination of items of the customer order; picking at least some of the items of the customer order; sorting the picked items based on a two-step sorting process; loading the picked items of the customer order on the delivery truck with the remainder of the items; and delivering the picked items to the customer.

Overall package delivery efficiency is a measure that depends on the efficiency of each step in the process of package delivery. There are usually multiple steps involved in moving a package from FC to customer to fulfill an order, and most of these steps must occur in a linear subsequent sequence. For example, picking may precede receiving orders and generating order identifiers, sorting may precede picking, packing may precede sorting, loading items on delivery trucks may precede packaging, etc. In other words, each step of the process is initiated by the completion of the previous step. In such process flows, the overall efficiency of the process is determined by the efficiency at each step. Overall efficiency can be improved by increasing the efficiency of each step or by increasing the efficiency of at least one step while maintaining the efficiency of other steps. As discussed above, "singulation" in this context refers to a single shipment of items for a customer order that includes multiple items without waiting for the customer order to be fully fulfilled prior to shipping, which can be achieved by reducing cycle time and reducing processing time in the process. The free time of the employees involved in the package can be used to improve package delivery efficiency. In some embodiments, one or more steps of process 400 may be performed by one or more user interface devices (eg, each user interface device is operated by a user in a different zone of FC 200).

In 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 can include multiple items. In some embodiments, a customer order may include multiple sub-orders and each sub-order may include multiple items. One or more computers of system 100 implement The system can be configured to review customer orders and identify information such as the total number of items ordered, descriptions for each of the items ordered, requested delivery time, final destination of the items, and the like. In some embodiments, one or more computer-implemented systems of system 100 may determine a promised delivery date or promised delivery time for a customer order based at least on the requested delivery time. For example, for a rush order request from a customer, the system can determine a committed delivery time of several hours or delivery to the intended final destination within 24 hours. In some embodiments, the system can be configured to individually determine the promised delivery date and time for each of the items ordered by the customer. For example, a customer order may include some items for urgent delivery and remaining items for normal delivery. The system can be configured to determine a promised delivery time based on the type of delivery requested.

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 of the customer orders may include multiple items. One or more computer-implemented systems of system 100 can be configured to review and identify common items among multiple customer orders. The user interface device can be configured to display an indication of the common object, thereby requesting input from the user, such as confirmation of receipt. The instructions may include information related to a 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 include a common item, such as a bottle of water. A worker (eg, a picker) may receive an instruction to pick up 50 bottles of water via the user interface device. The implementation of this approach can improve the efficiency of picking and the overall efficiency of the process.

In step 420, one or more computer-implemented systems of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifiers can include barcodes, tags, labels, alphanumeric, quick response (quick response; QR) code or similar. An order identifier can be a machine-readable optical indicia containing information about a customer's 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 delivery requested, customer information, the promised delivery date, and the promised delivery time. In some embodiments, the system that generates the order identifier can determine the storage location (eg, camp area 215, hub area 213) and the likely delivery route for the items in the customer order based on the final destination information of the customer order. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or area identified in the final destination, the system can determine the delivery of the items in the customer order route.

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

In step 430, one or more computer-implemented systems of system 100 may instruct the user interface device to display instructions associating each item of the customer's order with an order identifier. The user interface device may be configured to display instructions or alerts regarding received customer orders, thereby requesting input from the user, such as confirmation of receipt. Upon receiving input from the user, the user interface device may display some or all of the customer order and information associated with the customer order. A worker (e.g., a picker) may pick one or more items of a customer order and associate each picked item with execution from one or more computers, for example, by scanning an order identifier and a barcode on the item. associated with the order identifier received by the system. In some embodiments, items ordered by customers are associated with Associating the order identifier may include physically printing the order identifier using an indicia printer or a barcode printer. Printed indicia or barcodes may, for example, be attached or affixed to the item to allow all employees to easily access information associated with the order and delivery schedule. For example, workers who did not receive or have no access to the original order identifier may be able to scan the printed and affixed order identifier on the item.

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

In some embodiments, one or more computer-implemented systems of system 100 may determine an intended delivery destination, a storage space associated with the intended delivery destination (e.g., in storage cell 324/storage cell 344), and The delivery route used to deliver the items ordered by the customer at the intended delivery destination.

In some embodiments, the sorting process can be a two-step sorting process. The first step may include sorting the picked item based on the camp to which the item may be directed. The camp can be determined based on, for example, the zip code of the intended final delivery destination of the items in the customer order. The second step may include sorting the picked items in the camp based on the delivery route the items may be sent for delivery. Delivery routes may be determined based on, for example, districts or streets represented by zip codes within an area.

In step 450, one or more computer-implemented systems of system 100 may base the display on a pre-designated storage space (e.g., storage cell 324 of storage location 320). Instructions or alerts for sorting the picked items of customer orders are sent to the user interface device, and the pre-designated storage space is determined by one or more computers of the system 100 to implement the system. A pre-designated storage space may represent a camp to which items may be directed for further sorting. In some embodiments, one or more storage spaces may be designated as campsites. For example, storage space 1 to storage space 12 may be designated as camp 1 represented by storage cell 324_1 , storage space 13 to storage space 23 may be designated as camp 2 represented by storage cell 324_2 , and Storage space 24 is designated as Camp 3 represented by storage cell 324 .

Each of the sorted items may be transported to a corresponding camp. In some embodiments, the camp may be an on-site storage facility (eg, camp area 215 ) within the premises of FC 200 . The sorted items may be transported to the camp area 215 using transport devices such as, for example, conveyor belts, forklifts, dollies, dollies, carts. In some embodiments, the camp may be an off-site storage facility, such as a warehouse or a storage unit separate from the 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 transported to camp without waiting for the remaining items of the customer order to reduce idle time.

In step 460, one or more computer-implemented systems of the system 100 may send instructions to the user interface device to display an instruction or alert to sort the picked items in the camp based on the delivery route. A delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer's order. Workers may sort picked items in the campsite by placing the items in storage cells (eg, storage cell 344 ) based on the delivery route. Workers can obtain delivery routing information by, for example, scanning an order identifier on an item. Each of the storage cells 344 can be identified by a route identifier or a sub-route identifier.

In step 470, one or more computer-implemented systems of system 100 may send instructions to the user displaying an instruction or alert to place the sorted items from storage cell 344 into a container (e.g., container 350). interface device. Each storage cell 344 may be associated with a container configured to hold the items stored in the corresponding storage cell. In some embodiments, each container can be identified with a container identifier that includes information identifying the campsite and the storage cell. Picked items belonging to a customer order can be placed in containers without waiting for the remaining items of 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 accommodate containers, totes, wheeled cages, carts, dollies, and the like. Containers may be loaded in a manner that reduces unloading time during item delivery based on, for example, the configuration of the delivery route. The configuration of containers on a delivery truck may also be based on factors including, but not limited to, urgency of delivery, 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 comprise built-in storage spaces, such as cabinets, cells, shelves, racks, cages, or wheeled cages. Each container carrier in the delivery truck can 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 arranged against the rear wall of the storage compartment, labeled 360_1 to 360_4 from left to right. Thus, the container carrier located in the rear left corner of the storage compartment of the delivery truck can be identified as container carrier 360_1 and the container carrier located in the rear right corner of the storage compartment of the delivery truck can be identified as container carrier 360_4. For example, a visual or tabular representation of the configuration of container carriers 360 may be generated by one or more computer-implemented systems of system 100 , such as transport system 107 .

In some embodiments, the loading of containers on container carrier 360 may be recorded Configure to produce a representation of the delivery truck load configuration. For example, the transport system 107 may send an instruction to the user interface device displaying an instruction to scan container identifiers (eg, barcodes) of all containers placed in the container carrier and scan the corresponding container carrier identifiers. The system can generate a representation of the loading configuration based on the scanned information. In some embodiments, the loading configuration may be presented to the user in a tabular or visual format. The loading configuration can be printed on a piece of paper, displayed on a user interface device, or presented to the user before starting its delivery round.

In step 480, one or more computer-implemented systems of the system 100 (such as the transportation system 107), for example, may send instructions to a user interface device (such as , one of the mobile devices 107A to 107C). The user interface device may display an indication requesting input from a user (eg, a delivery worker or loader) to verify that the loading process is complete before proceeding to deliver the item. 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 instructions to the user interface device to display an instruction to record information associated with the order identifier, such as by scanning the order identifier. The user interface device may be after the items have been picked, after sorting the picked items based on the storage location in the first step of the sorting process, before transporting the sorted items to the camp, after arriving at the camp, Displaying recorded order identifier information after sorting the picked items based on the delivery route in the second step of the sorting process, after placing the sorted items in containers, after loading the containers on a delivery truck instructions. Information recorded at all steps of the process may be stored in a database associated with the system 100 (e.g., associated with or connected to the WMS 119 or the transportation system 107) save and update.

In some embodiments, the system 100 may generate a status update notification message based on updated information stored in a database in response to an inquiry from a customer regarding an order status. In some embodiments, the system 100 can pre-emptively generate status update notification messages for customers based on the updated information stored in the database.

Reference is now made to FIG. 5 , which shows an exemplary flowchart of a process 500 for generating a visual representation of a delivery vehicle's stowage configuration, consistent with disclosed embodiments. It should be understood that the flowcharts are an exemplary order of steps of a process and that the steps may be performed in other orders. Additionally, steps may be added, omitted, skipped, repeated or modified based on application and user needs.

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

In step 520, one or more computer-implemented systems of system 100, such as transportation system 107, may send instructions to the user interface device to display instructions determining the configuration of storage spaces within the delivery truck. In some embodiments, the delivery truck may include built-in storage spaces, such as cabinets, racks, shelves, cages, etc., in storage compartments. example For example, delivery trucks may include storage compartments to accommodate removable storage units such as wheeled cages.

In some embodiments, each storage space in a delivery truck may be identified using a storage space identifier or a container carrier identifier. Container carrier identifiers may include barcodes, labels, labels or QR codes. 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, labeled 360_1 to 360_4 from left to right (not shown in FIG. 3 ), can be arranged against the rear wall of the storage compartment. Thus, the container carrier located in the rear left corner of the storage compartment of the delivery truck can be identified as container carrier 360_1 and the container carrier located in the rear right corner of the storage compartment of the delivery truck can 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, driver or loader) may record the configuration of the built-in storage space in the delivery truck, eg, by scanning the storage space identifier. In some embodiments, the database of system 100 may include information associated with the configuration of storage spaces in delivery trucks. For example, the database may include information associated with the configuration of 24 storage spaces in a delivery truck.

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

In step 540, one or more computer-implemented systems of system 100, such as transport system 107, may send instructions to the user interface device displaying instructions to load the container into the storage space of the delivery truck. The container may be loaded onto the delivery truck in a manner that enables quick access to the item for unloading during delivery.

In step 550, one or more computer-implemented systems of system 100, such as transport system 107, may send instructions to the user interface device to display an indication associating each container with the storage space in which it is placed. For example, the transportation system 107 may send an instruction to the user interface device showing an instruction to scan container identifiers (eg, barcodes) of all containers placed in the storage space and scan the corresponding storage space identifiers. In some embodiments, the instructions may include step-to-step instructions for associating a container with a storage space and uploading the information to a database of the system 100 .

In step 560 , one or more computer-implemented systems of system 100 , such as transport system 107 , may generate a visual representation of the stowage configuration of the containers and storage spaces based on the associations established in step 550 . In some embodiments, the loading configuration may be presented to a user (eg, a delivery truck driver) in a tabular or visual format. The loading configuration can be printed on paper, displayed on a user interface device, or presented to the user before commencing its delivery round.

In some embodiments, the loading configuration of the delivery truck may be displayed on a user interface display of the delivery vehicle, such as a graphical user interface display screen of the delivery truck. In some embodiments, the visual representation of the loading configuration 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 configuration may indicate that the item placed in the container in the storage space has been delivered. This information can be updated in the database, allowing transportation system 107 and/or system 100 to determine whether the promised delivery date and time was met.

Reference is now made to FIG. 6, which is an alternative embodiment of process 400 as discussed above and illustrates an additional step performed during the second step of the sorting process. For example, during the second step of the sorting process, items may be picked on their own initiative and based on the ultimate purpose for delivery without regard to the status of the order or other items of the order that may be associated with the item The determined sub-route of the ground is used to sort the object.

In some embodiments, the sorting process can be a two-step sorting process. The first step may include sorting the picked item based on the camp to which the item may be directed. The camp can be determined based on, for example, the zip code of the intended final delivery destination of the items in the customer order. The second step may include sorting the picked items in the camp based on the delivery route the items may be sent for delivery. Delivery routes may be determined based on, for example, districts or streets represented by zip codes within an area.

In some embodiments, the mis-sort reduction procedure may be implemented during the second step of the sorting process (i.e. when sorting picked items based on the delivery route/sub-route in the second step of the sorting process) . For example, when items are picked up on site and placed in containers to be sorted based on a delivery route or sub-route, there may be a risk of an item being placed in the wrong container and then placed on the wrong delivery vehicle possibility. This can make it difficult for delivery truck drivers to search and try to find the correct item to the correct destination. One or more computer-implemented systems of system 100 can be configured to provide immediate notification or alerts to workers (eg, sorters) 301 when missorts occur, which facilitates detection and reduction of missorts. Fewer mis-picks help drivers easily understand items on the map and deliver orders more efficiently.

In some embodiments, one or more computer-implemented systems of system 100 (such as transportation system 107 ) may, for example, based on a comparison of the destination to existing routes and/or sub-routes, the workload on each route and/or sub-routes calculation, time, shipping method, Shipping costs or the like are used to determine which route and/or sub-route the item 208 should be associated with. In some embodiments, worker 301 or machine may (eg, using user interface device 302 ) scan object 208 or package 220 to determine its final destination. After determining the final destination for delivery of item 208 , the worker may place the item (eg, item 208 ) in container 350 based on the determined sub-route for the final destination of item 208 . In some embodiments, the item may be sorted based on the determined sub-route for the final destination of delivery without regard to the status of the order or other items of the order that may be associated with the item. For example, after receiving items at a camp (eg, camp area 215 ) from a packing area, the items may be sorted based on sub-routes or delivery routes without waiting for other items of the order to arrive at the camp. Since items are sorted based on sub-routes and not based on the customer order to which they belong, the dependencies of all items waiting for a customer order can be reduced, improving the sorting rate. For example, a customer order may contain T-shirts, which may not be labor intensive and may require less space on the delivery vehicle. Customer orders may also include table sets, which can be labor intensive, may take longer to deliver to camp for sorting, and may also require larger delivery vehicles. When sorting items at a campsite, the T-shirts may be sorted based on their destination and loaded onto a delivery vehicle based on a determined delivery area and/or delivery route. In this case, the t-shirts can be loaded on the delivery vehicle ahead of the table set without waiting for the table set, thereby reducing the duration of the t-shirts sitting on the shelf waiting to be picked, packed, sorted or shipped the table set . In this case, the T-shirts may be delivered to the customer prior to the table setting. This results in better space utilization, reduced shelf life, improved efficiency, reduced cycle times, and a better customer experience.

In some embodiments, one or more computer-implemented systems of system 100 may specify An association is established between the identification of the worker 301 for sorting the item 208, the user interface device 302 assigned to the worker 301, and the sub-route for delivery. In some embodiments, a worker (eg, worker 301 ) may scan a barcode (eg, order identifier 305 and/or location identifier) associated with a package (eg, package 208 ) prior to initiating the process. The worker 301 can use the user interface device 302 to scan the barcode. After receiving the barcode from the user interface device 302, the system 100 can identify the container 350, the container identifier 355, the worker 301 assigned to sort the item 208, the user interface device 302 assigned to the worker 301, and the associated item. 208 and the sub-route for delivery associated with the order identifier 305. The system 100 can store the identified information and the system 100 can maintain a mapping table that can store all the identified information, for example in a tabular format, such that the item 208, the order identifier 305, the container 350, the container identifier 355, The identifier of the worker 301 assigned to sort the object 208 is associated with the user interface device 302 assigned to the worker 301 . The mapping table may be stored in a database including information related to customer orders and delivery schedules for customer orders.

In some embodiments, items 208 may arrive at a camp to be sorted into a delivery vehicle. The worker 301 can scan the barcode of the item 208 and the order identifier 305 of the customer order. After scanning, the system 100 can retrieve information related to the object 208 from the mapping table that can be sent to the worker 301 . This information may include the container 350 into which the object 208 needs to be sorted. Worker 301 may receive an indication from system 100 specifying a container 350 into which item 208 needs to be sorted. Worker 301 may then place object 208 into container 350 and scan container identifier 355 using user interface device 302 . Information recorded, such as by scanning, may be stored in a database of the system 100, allowing packages to be tracked as they undergo processing. Can also scan the barcode of the container (e.g. container identifier 355) or the barcode of the tote, thereby providing information associated with the location of the items contained in the container during the process of picking, sorting, packing, shipping, etc. In some embodiments, system 100 may maintain a mapping table that may record all scanned information, such as in a tabular format, such that item 208, order identifier 305, container 350, container identifier 355, and The identifier of the worker 301 of the selection object 208 is associated with the user interface device 302 assigned to the worker 301 . As workers 301 use user interface device 302 to scan order identifiers and containers 305 into which items are sorted, the mapping table can be automatically updated in real time. In some embodiments, one or more computer-implemented systems of system 100 may analyze the data stored at the beginning of the process with the data from the worker's 301 scan to determine whether an exceptional event has occurred. In some embodiments, when the stored information and the scanned information (the scanned information and the object 208, the order identifier 305, the container 350, the container identifier 355 and the worker 301 designated for sorting the object 208 and from Exceptions may occur when there is a mismatch between one or more of the scanned inputs of worker 301 . In some embodiments, items 208, order identifiers 305, containers 350, container identifiers 355, and items assigned to sorting items 208 may be accessed, stored, updated, or modified in one or more databases connected to system 100. The association between the identities of the workers 301.

In some embodiments, worker 301 may oversee sorting of items 208 into containers 305 associated with container identifiers 355 . In some embodiments, worker 301 using user interface device 302 may receive an indication of scanned object 208 and a container identifier 355 in which object 208 is placed. Worker 301 may use user interface device 302 to scan object 208 and container identifier 355 . In some embodiments, when the stored information and the scanned information (the scanned information and the object 208, order A mismatch may occur when there is a mismatch between one or more of the single identifier 305, the container 350, the container identifier 355, and the worker 301 designated for sorting the object 208 and the input from the scan by the worker 301) exceptional event. In an exemplary embodiment, system 100 may compare scanned information (eg, order identifier 305 and container identifier 355 ) to stored information and determine whether an exceptional event has occurred. This may occur when an item 208 is incorrectly sorted and placed in a container that was not intended for the item 208 . When an exception event occurs, the worker 301 who supervises the sorting of the objects 208 can be notified immediately that a wrong sorting error has occurred. This notification or alert may be provided by system 100 to worker 301 on user interface device 302 . Alternatively, exception event notifications can be displayed on a large display screen that can be viewed by workers 301 or floor managers/supervisors.

In 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 can include multiple items. In some embodiments, a customer order may include multiple sub-orders and each sub-order may include multiple items. One or more computer-implemented systems of system 100 can be configured to review customer orders and identify information, such as the total number of items ordered, a description of each of the items ordered, the requested delivery time, the final date of the item. destination etc.

In step 620, one or more computer-implemented systems of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifier 305 may include a barcode, tag, label, alphanumeric, quick response (QR) code, or the like. Order identifier 305 may be a machine-readable optical indicia containing information about a customer's 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's order, the delivery requested Delivery type, customer information, promised delivery date and promised delivery time, etc.

In some embodiments, the order identifier generation system 100 may determine storage locations (e.g., camp areas 215, hub areas 213) and delivery routes to which items in the customer order may belong based on the final destination information of the customer order and/or or sub-routes. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or area identified in the final destination, the system can determine the delivery of the items in the customer order route.

As discussed above with reference to FIG. 4 , upon scanning or reading an order identifier, for example, using a user interface device equipped with barcode scanning capabilities (e.g., user interface device 302 ), the user interface device may display the order identifier associated with the order identifier. Linked information. For example, after scanning or reading the order identifier, the user interface device 302 can display the number of picked items, the number of remaining items to be picked, the promised delivery time, and the remaining time to fulfill the order.

In step 630 , one or more computer-implemented systems of system 100 may associate each item of the customer order with order identifier 305 . User interface device 302 may be configured to display an indication or alert regarding a received customer order, thereby requesting input from a user (eg, worker 301 ), such as confirmation of receipt. Upon receiving input from the user, user interface device 302 may display some or all of the customer order and information associated with the customer order. A worker 301 (e.g., a picker) may pick one or more items of a customer order and associate each picked item with one or more computers, such as by scanning an order identifier and a barcode on the item. The order identifier 305 received by the fulfillment system is associated. In some embodiments, associating items of the customer order with the order identifier may include physically printing the order identifier using an indicia printer or barcode printer. Printed markings or barcodes can be attached to objects, for example or affixed together to allow all employees to easily access information associated with orders and delivery schedules. For example, workers who did not receive or have no access to the original order identifier may be able to scan the printed and affixed order identifier on the item.

In some embodiments, a worker 301 (eg, a sorter) assigned to sorting an item will receive the item 208 and determine which customer order the item 208 corresponds to. For example, worker 301 may use a device such as user interface device 302 to scan a barcode on item 208 . As worker 301 scans item 208, one or more computer-implemented systems of system 100 determine container 350, container identifier 355, and all items in the customer order for sorting based on the determined final destination of the item. Route or sub-route. Items 208 may be sorted based on delivery routes or sub-routes. Delivery routes or sub-routes 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 ) may be configured to communicate with user interface device 302 to indicate sorting of objects.

In step 640, one or more computer-implemented systems of system 100 may determine an intended final delivery destination for each of the items ordered by the customer. In some embodiments, one or more computer-implemented systems of system 100 may determine the intended delivery destination, the storage space container (e.g., storage cell 324/storage cell 344 ) associated with the intended delivery destination, the Containers 350 configured to hold items stored in corresponding storage cells, and delivery routes to deliver the items ordered by the customer at the intended delivery destination.

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

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a handbag). All items of storage cells 344 (eg, items 208 ) may be placed in container 350 . In some embodiments, container identifier 355 may be used to identify container 350 . Container identifier 355 may include information associated with the sub-routes containing the sub-routes identifiers. In some embodiments, the container identifier 355 may include information related to the campsite and sub-route. For example, a container identifier may include the label CS3_SR1, where CS indicates the origin camp and SR indicates the designated sub-route for delivering the items in the container. Container identifier 355 may include, but is not limited to, a label, barcode, number, or label.

In step 650 , process 600 may include an additional step in which one or more computer-implemented systems of system 100 may store information associated with a customer order in a mapping table based on order identifier 305 . The information may include the containers 350 associated with the item 208, a container identifier 355 associated with each container 350, and a delivery route or sub-routes. In some embodiments, a worker (eg, worker 301 ) may scan a barcode (eg, order identifier 305 and/or location identifier) associated with a package (eg, package 208 ). The worker 301 can use the user interface device 302 to scan the barcode. After receiving the barcode from the user interface device 302, the system 100 can determine the container 350, the container identifier 355, the worker 301 assigned to sort the item 208, the user interface device 302 assigned to the worker 301, and the order Identifier 305 The associated route or sub-route for delivery. The system 100 may maintain a mapping table that may store all determined information, such as in a tabular format, such that an item 208 is associated to an order identifier 305, a container 350, a container identifier 355, a job assigned to sort the item 208 The operator 301, the route or sub-route for delivery, and the user interface device 302 assigned to the worker 301.

In step 660, one or more computer-implemented systems of system 100 may display an instruction or alert to sort the picked items of the customer order based on a pre-designated storage space (e.g., storage cell 324 of storage location 320). The command is sent to the user interface device, and the pre-designated storage space is determined by one or more computers of the system 100 to implement the system. A pre-designated storage space may represent a camp to which items may be directed for further sorting. In some embodiments, one or more storage spaces may be designated as campsites. For example, storage space 1 to storage space 12 may be designated as camp 1 represented by storage cell 324_1 , storage space 13 to storage space 23 may be designated as camp 2 represented by storage cell 324_2 , and Storage space 24 is designated as Camp 3 represented by storage cell 324 .

Each of the sorted items may be transported to a corresponding camp. In some embodiments, the camp may be an on-site storage facility (eg, camp area 215 ) within the premises of FC 200 . The sorted items may be transported to the camp area 215 using transport devices such as, for example, conveyor belts, forklifts, dollies, dollies, carts. In some embodiments, the camp may be an off-site storage facility, such as a warehouse or a storage unit separate from the 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 transported to camp without waiting for the remaining items of the customer order to reduce idle time.

In step 670, one or more computer-implemented systems of system 100 may convert Instructions are sent to the user interface device to display instructions or alerts to sort the picked items in the camp based on the delivery route and to place the sorted items from storage cells 344 into containers (eg, container 350 ). A delivery route may be predetermined by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer's order. Workers may sort picked items in the campsite by placing the items in storage cells (eg, storage cell 344 ) based on the delivery route. Workers can obtain delivery routing information by, for example, scanning an order identifier on an item. Each of the storage cells 344 can be identified by a route identifier or a sub-route identifier. Each storage cell 344 may be associated with a container configured to hold the items stored in the corresponding storage cell. In some embodiments, upon receiving input from the user (eg, a scanned order identifier), user interface device 302 may display some or all of the customer order and information associated with the customer order. A worker 301 (e.g., a sorter) may sort the order identifier 305 associated with the order identifier 305 based on the container identifier 355 received from one or more computer-implemented systems, for example, by scanning the order identifier 305 and a barcode on the item 208. One or more items of the customer order in the associated container 350. Items/items can be placed in containers without waiting for the rest of the same customer order to reduce idle time.

In some embodiments, worker 301 may receive a single customer order with multiple items to be delivered to the same delivery address. It may be desirable for items within an order to be delivered individually such that some items may arrive before others. In some embodiments, the sorting instructions may contain additional details, such as the desired sorting and delivery order in order to most efficiently place all items in designated containers. In some embodiments, where one or more items in the order may not be immediately available, the remaining items in the order may be delivered to the customer first, and once the one or more items become available, may be exist Missing items are then delivered. For example, where one or more items in an order may be perishable, the system 100 may determine that the items need to be delivered to the intended final destination within a few hours, and the missing items may be delivered thereafter . In this case, the system 100 may indicate this to the worker 301, along with information related to the customer's order, including the container identifier. A worker 301 (eg, a sorter) may then sort one or more of the perishable items ordered by the customer into the indicated container 350 . Items/items can be placed in containers for loading delivery trucks without waiting for other items in the customer's order. In some embodiments, the system 100 can be configured to individually determine a promised delivery date and time for each of the items of a customer order. For example, a customer order may include some items for urgent delivery and remaining items for normal delivery. The system can be configured to determine a promised delivery time based on the type of delivery requested. In this case, system 100 may indicate to worker 301 the items listed for earlier delivery. Worker 301 (eg, a sorter) may then sort one or more of the items ordered by the customer into container 350 . Items/items can be placed in containers for loading delivery trucks without waiting for other items in the customer's order. Implementation of this approach to a single shipment of items for a customer order that includes multiple items without waiting for the customer order to be fully fulfilled prior to shipping can increase sorting efficiency and the overall efficiency of the process. Implementation of this approach can also improve package delivery efficiency by reducing cycle time and reducing idle time of employees involved in the process.

In step 680, one or more computer-implemented systems of the system 100 may compare the scanned order identifier 305 and the container identifier 355 of the container 350 in which the item is placed with information stored in the mapping table for the same customer order to determine Determine whether an exceptional event has occurred. In some embodiments, as explained above, when stored information and scanned information (the scanned information and object 208, order identifier 305, container 350, the container identifier 355, and the worker 301 designated for sorting the object 208 and one or more of the input from the worker's 301 scan, an exception event may occur. For example, worker 301 may sort item 208 into the wrong container (i.e., a container not intended for item 208), in which case, since the difference between order identifier 305 and container identifier 355 can be detected Mismatch between, so exceptional events may occur.

In some embodiments, worker 301 may place item 208 in a designated container, but scan the next order ID instead of the container ID in which item 208 is placed. In this case, a mismatch between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 may scan items associated with different order identifiers and sort the items into container 350 associated with order identifier 305 . In this case, a mismatch between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 may scan order identifier 305 multiple times instead of scanning container identifier 355 . In this case, a mismatch between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 may scan container identifier 355 multiple times without first scanning order identifier 305 before scanning container identifier 355 . In this case, a mismatch between order identifier 305 and container identifier 355 may be detected. In some embodiments, worker 301 may scan item 208 associated with a previous order identifier instead of order identifier 305 . In this case, a mismatch between order identifier 305 and container identifier 355 may be detected.

In 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 . Displayed notifications can Contains the false scan criteria for which the exception occurred. In some embodiments, notifications may be sent to and displayed by user interface device 302 in real time. In some embodiments, the user interface device 302 may trigger an alarm or warning message when a notification for an exceptional event is received. In some embodiments, notifications may be displayed on large monitor screens in the camp area, campsite, or any other area within the fulfillment center. This alerts the floor manager/supervisor to notify the individual sorter/worker in error when an exceptional event occurs.

In some embodiments, worker 301 may receive reports on user interface device 302 . One or more computer implementations of system 100 may execute applications including host application software or native application software. When an exceptional event occurs, the system 100 can display a notification on the dashboard via a large monitoring screen in one or more of the picking area, packing area, hub area, camp area, or any other area within the fulfillment center. The system 100 can send a notification to the user interface device 302 that an exceptional event has occurred. In some embodiments, system 100 may provide worker 301 with multiple channels for delivering notifications or alerts on user interface device 302 , including but not limited to text message, SMS, cell phone call, or in-app notification. Notifications may appear on UI device 302 in the form of icons, badges on icons for applications, status bar format, report or table formats, or as more detailed messages on UI device 302 .

FIG. 7 is a schematic diagram of an exemplary notification dashboard 700 consistent with disclosed embodiments. The notification dashboard can be displayed to workers 301 (eg, sorters) as well as floor supervisors or managers on user interface devices 302 or large display screens within the camp area. In an exemplary embodiment, the dashboard displays notifications with false scan criteria due to which exceptional events occurred. In some embodiments, the mapping table may contain information based on the The relationship between the order identifier 305a, the container identifier CS3_SR1_a, and the worker 301a of the route or sub-route of the item 208. When worker 301a scans the item associated with order identifier 305a, user interface device 302 may instruct worker 301a to place item 208 in the container (or tote) associated with container ID CS3_SR1_a. This information can be stored in a mapping table. In exceptional events, there may be a mismatch between these identifiers, as depicted 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 ID CS3_SR1_b in which the object 208 is placed. When system 100 receives scanned data, system 100 may compare the information stored in the mapping table with the scanned data received from worker 301a and determine that there may be a mismatch between the two, in which case an exception occurs event.

In some embodiments, an exceptional event may occur when a worker 301 scans the wrong container (or tote). For example, the worker 301a may place the object 208 in the container associated with the container ID CS3_SR1_a, but scan an unrelated container, ie, the container associated with the container ID CS3_SR1_b. In this case, the system 100 may compare the scanned data to the data stored in the mapping table and determine that there may be a mismatch. The mapping table may contain profiles with associations between order identifiers 305a and container identifiers CS3_SR1_a that differ from scanned profiles and exceptions may occur.

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

In some embodiments, an exceptional event may occur when the worker 301a may have missed scanning a container after scanning the order identifier. For example, worker 301a may place item 208 in a container associated with container ID CS3_SR1_a, but scan a different order ID 305b or re-scan a previous order ID, such as order ID 305a. In this case, the system 100 may determine that there may be exceptional events due to missed container (or tote) scans.

In some embodiments, exceptions may occur when worker 301 may have missed scanning the next order identifier. For example, worker 301a may scan order identifier 305a and place item 208 in the container associated with container identifier CS3_SR1_a. After this, the worker 301a may scan again the container associated with the container identifier CS3_SR1_a instead of the order identifier 305b. In this case, the system 100 may determine that there may be exceptional events due to missed invoice scans.

Although the disclosure has been illustrated and described with reference to particular embodiments thereof, it should be understood that the disclosure may be practiced in other environments without modification. The foregoing description has been presented for purposes of illustration. The foregoing description is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments. In addition, although aspects of the disclosed embodiments are described as being stored in memory, those skilled in the art should understand that such aspects can also be stored in memory. other types of computer-readable media, such as secondary storage devices such as hard disk or CD ROM, or other forms of RAM or ROM, USB media, DVD, Blu-ray, or other optical drive media.

Computer programs based on the written description and disclosed methods are within the skill of experienced developers. Various programs or program modules can be created using any of the techniques known to those of ordinary skill in the art or can be designed in conjunction with existing software. For example, a program segment or a program module can be implemented or implemented with the help of .Net Framework (.Net Framework), .Net Compact Framework (.Net Compact Framework) (and related languages, such as Visual Basic, C, etc. ), Java (Java), C++, Objective-C (Objective-C), HTML, HTML/AJAX combination, XML, or HTML containing Java applets.

Furthermore, although illustrative embodiments have been described herein, those having ordinary skill in the art will recognize equivalent elements, modifications, omissions, combinations (eg, aspects of various embodiments) based on this disclosure , adaptations and/or alterations within the scope of any and all embodiments. The limitations in the claims should be interpreted broadly based on the language employed in the claims and not limited to the examples described in this specification or during the prosecution of this application. Examples should be considered non-exclusive. In addition, the steps of the disclosed methods may include modification in any manner by reordering the steps and/or inserting or deleting steps. Accordingly, it is intended that the specification and examples be considered illustrative only, with a true scope and spirit being indicated by the following claims and the full range of equivalents thereof.

600: process

610, 620, 630, 640, 650, 660, 670, 680, 690: steps

Claims (20)

A computer-implemented system for sorting parcels, comprising: memory storage for storing computer-executable instructions; and one or more processors configured to execute the stored instructions to: generating an order identifier, the customer order comprising a plurality of items, wherein the plurality of items includes an item for urgent delivery and an item for normal delivery; determining a promised delivery time for an item; associating each item of the customer order with the order identifier; determining the promised delivery time associated with each item based on the order identifier and the promised delivery time for each item storing containers, a container identifier associated with each container, and a delivery route; storing in a mapping table the number of items of the customer order based on the order identifier and the promised delivery time for each item an association between each item and the container identifier; sending to at least one of at least one user device; sorting the one or more objects of the plurality of objects based on the first indication; receiving a first input related to a status of the first sorting process from at least one user device ; regardless of the state of the first sorting process, the second A second indication that the sorting process sorts each sorted item based on the delivery route is sent to at least one user device for display associated with the sorter; A second input related to the status of a second sorting process; comparing said order identifier with said container identifier after said second sorting process; detecting a change in said second sorting process based on said comparison An exceptional event has occurred in , wherein the exceptional event is triggered upon detection of: receiving a scan event including an invoice identifier and a scan event including an extraneous container identifier, wherein the extraneous container identifier is not including an item associated with the invoice identifier; sending a notification that the exception event has occurred to at least one user device associated with the sorter. The system of claim 1, wherein the processor is further configured to: determine the order identifier; determine the container identifier; associate the order identifier to the container using the mapping table identifiers, wherein the mapping table includes a list of each of the plurality of items of the customer order based on the mapping of the order identifier to the container identifier; determining the relationship between the order identifier and the There is a mismatch between the container identifiers described above. The system of claim 2, wherein said processor is further configured to: re-sort said order identifier based on said detected mismatch between said order identifier and said container identifier. An indication of one or more of multiple objects sent to at least one user device. The system of claim 2, wherein the processor is further configured to: send information associated with the detected exception event to a display device separate from at least one user device for display. The system of claim 4, wherein the information associated with the detected exception event includes an immediate cause of the exception event. The system of claim 1, wherein the processor is further configured to: detect successful completion of the second sorting process and generate a status update. The system of claim 6, wherein the processor is further configured to: send information associated with the updated state to a display device separate from at least one user device for display. The system of claim 6, wherein said processor is further configured to: upon successful completion of said second sorting process, delete said plurality of said customer orders based on said order identifier. A mapping between each of the objects and the container identifier. The system of claim 1, wherein the processor is further configured to: receive an input from at least one user device, the input including at least one of the order identifier or the container identifier associated information. The system of claim 1, wherein the exception event is triggered upon detection of one or more of the following: a first scan event including the first order identifier is received from the first user device, A second scan event comprising a second order identifier is subsequently received from said first user device; a scan event comprising a first invoice identifier is received, followed by a scan event comprising A second scan event for a second invoice identifier; a scan event including a first container identifier is received, followed by a second scan event including a second container identifier; received from said first user device The first scan event including the first order identifier, followed by receiving a second scan event including the first order identifier from the first user device. A computer-implemented method of sorting packages, the method comprising: generating an order identifier based on a received customer order, the customer order comprising a plurality of items, wherein the plurality of items includes items for urgent delivery and items for regular delivery item; determining a promised delivery time for each item in the plurality of items based on whether the item is urgent delivery or regular delivery; associating each item of the customer order with the order identifier; based on the order identifier and the promised delivery time for each item to determine the storage container associated with each item, the container identifier associated with each container, and the delivery route; based on the order identifier and all storing an association between each of said plurality of items of said customer order and said container identifier in a mapping table at said promised delivery time; a first sorting process will be initiated to sort based on said mapping table A first indication of selecting one or more of the plurality of objects is sent to at least one user device; sorting the one or more of the plurality of objects based on the first indication; Receiving a first input from at least one user device relating to a state of said first sorting process; irrespective of said state of said first sorting process, a second sorting process will be used based on said A second indication is sent to at least one user device for display associated with the sorter to sort each sorted item according to the delivery route; receiving from at least one user device associated with the second sorting process A second input related to the status of the second sorting process; comparing the order identifier with the container identifier after the second sorting process; detecting that an exceptional event has occurred during the second sorting process based on the comparison , wherein the exceptional event is triggered upon detection of a scan event comprising an invoice identifier and a scan event comprising an extraneous container identifier, wherein the extraneous container identifier does not include an item associated with the manifest identifier; sending a notification that the exception event has occurred to at least one user device associated with the sorter. The method of claim 11, wherein detecting the exceptional event comprises: determining the order identifier; determining the container identifier; associating the order identifier to the container identifier using the mapping table , wherein the mapping table includes a list of each of the plurality of items of the customer order based on mapping the order identifier to the container identifier; determining the relationship between the order identifier and the container There is a mismatch between identifiers. The method of claim 12, further comprising: re-sorting one or more of the plurality of items based on the detected mismatch between the order identifier and the container identifier An indication of objects is sent to at least one user device. The method of claim 11, further comprising: sending information associated with the detected exception event to a display device separate from at least one user device for display. The method of claim 14, wherein the information associated with the detected exception event includes an immediate cause of the exception event. The method of claim 11, further comprising: detecting successful completion of the second sorting process and generating a status update. The method of claim 16, further comprising: sending information associated with the updated state to a display device separate from at least one user device for display. The method of claim 16, further comprising: upon successful completion of the second sorting process, deleting each of the plurality of items of the customer order based on the order identifier and the The mapping between container identifiers described above. The method of claim 11, further comprising: receiving input from at least one user device, the input including information associated with at least one of the order identifier or the container identifier. The method of claim 11, wherein the exception event is triggered upon detection of one or more of the following: a first scan event comprising the first order identifier is received from the first user device, A first order identifier including a second order identifier is subsequently received from the first user device. Two scan events; a scan event including a first invoice identifier is received, followed by a second scan event including a second invoice identifier; a scan event including a first container identifier is received, followed by a second scan event comprising a second container identifier; receiving from said first user device said first scan event comprising said first order identifier, subsequently receiving from said first user device comprising A second scan event for the first order identifier.

Images