TWI837449B - Computerized systems and computer-implemented methods for package delivery - 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

Computerized system and computer-implemented method for package delivery

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-known computerized systems, methods, and user interfaces for efficiently fulfilling customer orders and delivering packages with reduced cycle times while maintaining high worker efficiency in multiple areas within a fulfillment center.

A fulfillment center (FC) enables e-commerce merchants to outsource warehousing and shipping. Inventory management in a FC is an essential component of fostering an optimal customer experience for online shoppers. Inventory management may include several steps ranging from receiving merchandise from sellers, stowing received merchandise for picking visits, packaging items, verifying orders, and package delivery. Although currently existing FCs and systems for inventory management in FCs are configured to handle large volumes of incoming and outgoing merchandise, the efficiency and timeliness of fulfillment of customer orders may be limited, in part due to inefficient practices in obtaining items to fulfill orders. Delays in package delivery may result in customer dissatisfaction and, in some cases, may impact the cost and profitability of a business.

With the development and widespread acceptance of e-commerce, Internet shopping has provided a one-stop shop for all shopping needs including food, furniture, electronics, clothing, books, etc. Each online order typically includes a combination of items from widely varying categories. Although in currently existing order fulfillment practices, systems can be employed 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 sections of the FC based on category, and a packer may have to wait for a picker to pick up all the items of an order before they can pack the items. This can cause delays in subsequent steps in the process of packaging and delivering the package to the customer, which slows down 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 the items are picked individually, they are packed into a container at the same time before being loaded as packages on the delivery truck. If the storage space where the picked items are stored is not accessible, expected or unexpected delays in packaging may affect the picking efficiency. The process of storing packages and shipping packages out of the FC includes several steps, such as receiving, stacking, picking, sorting, packaging, loading, delivery, and verifying order accuracy at each of the steps. In order to be efficient overall, the efficiency of the individual steps must also be high. For example, if the process includes 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 operations. One of the technical challenges in the warehouse may be to quickly communicate information to workers on the ground, such as urgent customer orders, priority shipments, etc. Currently existing logistics and inventory management systems lack the ability to efficiently consider expected or unexpected urgency in customer orders, which may lead to customer dissatisfaction and higher associated inventory costs.

Therefore, there is a need for improved methods and systems for efficient package delivery through unification to reduce cycle time and promised delivery time while maintaining high overall throughput and efficient utilization of resources.

One aspect of the present disclosure is a computer-implemented method for 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 in the customer order with the order identifier; and determining an expected delivery destination, a storage space associated with the expected delivery destination, and a delivery route for each item based on the order identifier. The method may further include: sending a first instruction to a user device for display to sort each of the plurality of objects using a first sorting process based on the storage space associated with the expected delivery destination; receiving a first input related to a state of the first sorting process from at least one user device; and sending a second instruction to at least one user device to sort each sorted object using a second sorting process based on the delivery route configured to include the expected delivery destination without considering the state of the first sorting process. device for display; receiving a second input related to the status of the second sorting process from at least one user device; sending a third instruction to place each of the sorted objects in a container associated with the delivery route to at least one user device for display, regardless of the status of the second sorting process; and sending a fourth instruction to deliver the placed objects of the plurality of objects to the intended delivery destination to at least one user device for display, regardless of the status of other objects of the plurality of objects in the customer order.

Another aspect of the present disclosure is a computer-implemented method for 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 in the customer order with the order identifier; and determining an expected delivery destination, a storage space associated with the expected delivery destination, and a delivery route for each item based on the order identifier. The method may further include: sending a first instruction to a user device for display to sort each of the plurality of objects using a first sorting process based on the storage space associated with the expected delivery destination; receiving a first input related to the status of the first sorting process from at least one user device; sending a second instruction to at least one user device for display to sort each sorted object using a second sorting process based on the delivery route configured to include the expected delivery destination without considering the status of the first sorting process; receiving a second input related to the status of the second sorting process from at least one user device; placing each of the sorted objects in a container associated with the delivery route; A third instruction is sent to at least one user device for display without regard to the state of the second sorting process; a third input including information associated with the container identifier of the container is received from at least one user device; a fourth instruction to deliver the placed object of the plurality of objects to the intended delivery destination is sent to at least one user device for display without regard to the state of other objects of the plurality of objects in the customer order; a fourth input including information associated with a delivery schedule of the placed object of the plurality of objects is received from at least one user device; and the first input, the second input, the third input, and the fourth input are stored in a database associated with a computer implementation system.

Another aspect of the present disclosure is directed to a computer-implemented system for package delivery. The system may include: a 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; associate each of a plurality of items in the customer order with the order identifier; and determine an expected delivery destination, a storage space associated with the expected delivery destination, and a delivery route for each item. The processor may execute the instructions to: send a first instruction to a user device for display to sort each of the plurality of objects using a first sorting process based on the storage space associated with the expected delivery destination; receive a first input related to a status of the first sorting process from at least one user device; send a second instruction to at least one user device for display to sort each sorted object using a second sorting process based on the delivery route configured to include the expected delivery destination without considering the first sorting process; receiving a second input related to the status of the second sorting process from at least one user device; sending a third instruction to place each of the sorted objects in a container associated with the delivery route to at least one user device for display without considering the status of the second sorting process; and sending a fourth instruction to deliver the placed objects of the plurality of objects to the intended delivery destination to at least one user device for display without considering the status of other objects of the plurality of objects in the customer order.

Another aspect of the present disclosure is directed to a computer-implemented method for package delivery, the method comprising: receiving a customer order by a computer-implemented system; generating an order identifier based on the customer order using the computer-implemented system; associating multiple items of the customer order with the order identifier; determining an expected delivery destination and an expected delivery time of each item based on the order identifier; determining a delivery node and a delivery wave of each item, a first container associated with the delivery node, and one or more second containers associated with the delivery node and the delivery wave based on the expected destination and the expected delivery time of each item; sending a first instruction to a first user device to sort each of the multiple items based on the associated delivery node using a first sorting process at a first location; receiving a first instruction from the first user device to sort each of the multiple items based on the associated delivery node; sending a first input related to the status of the first sorting process; sending a second instruction to the first user device to place the first sorted object in the first container associated with the delivery node at the first location without considering the status of other objects in the plurality of objects in the customer order; receiving a second input related to the placement status of each object in the first container from the first user device; sending a third instruction to the second user device to sort each object in the first container using a second sorting process at a second location; and sending a fourth instruction to the second user device to deliver the second sorted object in the second container to the intended delivery destination at a time associated with the delivery wave without considering the status of other objects in the plurality of objects in the customer order.

Another aspect of the present disclosure is directed to a computerized system for package delivery, comprising: a memory storage for storing computer executable instructions; and one or more processors configured to execute the stored instructions to perform the following operations: receiving a customer order; generating an order identifier based on the customer order; associating each of a plurality of items in the customer order with the order identifier; determining the identity of each item based on the order identifier; An expected delivery destination and an expected delivery time; based on the expected destination and the expected delivery time of each object, determine the delivery node and the delivery wave of each object, a first container associated with the delivery node, and one or more second containers associated with the delivery node and the delivery wave; send a first instruction to a first user to sort each of the plurality of objects based on the delivery node using a first sorting process at a first location; a first user device without considering the status of other items in the plurality of items in the customer order; receiving a first input related to the status of the first sorting process from the first user device; sending a second instruction to place the first sorted items in the first container at the first location to the first user device; receiving a second input related to the placement status of each item in the first container from the first user device; sending a third instruction to sort each item in the first container associated with the delivery wave using a second sorting process at a second location to the second user device; and sending a fourth instruction to deliver the second sorted items in the second container to the intended delivery destination at a time associated with the delivery wave to the second user device without considering the status of other items in the plurality of items in the customer order.

Another aspect of the present disclosure is directed to a computerized system for package delivery, comprising: a memory storage for storing computer executable instructions; and one or more processors configured to execute the stored instructions to perform the following operations: receiving a customer order; generating an order identifier based on the customer order; associating each of a plurality of items in the customer order with the order identifier; determining an expected delivery destination and an expected delivery time of each item based on the order identifier; The method comprises: determining a distribution node and a distribution wave of each object, a first container associated with the distribution node, and one or more second containers associated with the distribution node and the distribution wave based on the expected destination and the expected delivery time of each object; sending a first instruction to a first user device to sort each of the plurality of objects based on the distribution node using a first sorting process at a first location; receiving from the first user device an instruction related to the first sorting process; ; sending a second instruction to the first user device to place the first sorted object into the first container at the first location; receiving a second input related to the placement status of each object in the first container from the first user device; causing the first container to be transferred from the first location to the second location; sending a third instruction to the second user device to sort each object associated with the delivery wave in the first container using a second sorting process at the second location; sending a fourth instruction to the second user device to place the second sorted object into the second container based on the second sorting process; and sending a fifth instruction to the second user device to deliver the second sorted object in the second container to the intended delivery destination at a time associated with the delivery wave, without considering the status of other objects in the plurality of objects of the customer order.

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

100, 300: System

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: Implementation of optimization system

115: Implement communication gateway

117: Supply Chain Management System

119:Warehouse management system

121A, 121B, 121C: Third-party fulfillment system

123: Fulfillment Center Authorization System

125: Labor management system

200: Fulfillment Center

201, 222: Truck

202A, 202B, 208: Objects

203: Arrival area

205: Buffer Zone

206:Forklift

207: Unloading area

209: Picking area

210: Storage unit

211: Packaging area

213: Hub

214:Transportation Agency

215: Camp area

216: Wall

218, 220: Package

224A, 224B: Delivery workers

226:Car

301: Convergence Worker

302: User interface device

305: Order identifier

320: First storage location

324, 324_1, 324_2, 344, 622-1, 622-2, 622-n, 624-1, 624-2, 624-n: storage cell

340: Campsite location

342: Storage space

350:Container

355:Container identifier

360:Container carrier

400, 500, 700: Process

410, 420, 430, 440, 450, 460, 470, 480, 510, 520, 530, 540, 550, 560, 710, 720, 730, 740, 750, 760, 770, 780, 790: Steps

602, 606: Workers

612, 614: Handbag

612a, 614a: Handbag identifier

616: Order identifier

622: First packaging position

624: Second packaging area

632: Transmission device

FIG. 1A is a schematic block diagram showing an exemplary embodiment of a network including a computerized system for communicating to implement shipping, transportation, and logistics operations consistent with the disclosed embodiments.

FIG. 1B depicts a sample search result page (SRP) including one or more search results satisfying a search request and an interactive user interface element consistent with the disclosed embodiments.

FIG. 1C depicts a sample single display page (SDP) including a product and information about the product and interactive user interface elements consistent with the disclosed embodiments.

FIG. 1D depicts a sample shopping cart page including items in a virtual shopping cart and interactive user interface elements consistent with the disclosed embodiments.

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

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

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

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

FIG5 is a schematic diagram of an exemplary process flow for generating a representation of a loading configuration of a delivery vehicle consistent with the disclosed embodiments.

FIG. 6 is a schematic illustration of an alternative embodiment of a computerized system for a unitized package delivery system consistent with the disclosed embodiments.

FIG. 7 is a flow chart illustrating an alternative process for a computerized system for a unitized package delivery method consistent with the disclosed embodiments.

The following detailed description refers to the accompanying drawings. Whenever possible, the same figure numbers are used in the drawings and the following description to refer to the same or similar parts. Although several illustrative embodiments are described herein, modifications, adaptations, and other embodiments are possible. For example, the components and steps shown in the drawings may be replaced, added, or modified, and the illustrative methods described herein may be modified by replacing, reordering, removing, or adding steps to the disclosed methods. Therefore, the following detailed description is not limited to the disclosed embodiments and examples. Instead, the proper scope of the invention is defined by the scope of the accompanying patent applications.

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

1A, a schematic block diagram 100 is shown illustrating an exemplary embodiment of a network of computerized systems including communications for implementing shipping, transportation, and logistics operations. As shown in FIG1A, system 100 may include various systems, each of which may be connected to each other via one or more networks. The depicted systems include a shipment authority technology (SAT) system 101, an external front-end system 103, an internal front-end system 105, a transportation system 107, mobile devices 107A, 107B, and 107C, a seller portal 109, a shipment and order tracking (SOT) system 111, a fulfillment optimization (FO) system 113, a fulfillment messaging gateway (FMG) 115, a supply chain management (SCM) system 117, a warehouse management system 119, and mobile devices 119A, 119B, and 119C (depicted as being located at a fulfillment center). center; FC) 200), third-party fulfillment system 121A, third-party fulfillment system 121B and third-party fulfillment system 121C, fulfillment center authorization (FC Auth) system 123 and 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 may determine whether an order has exceeded its promised delivery date (PDD) and may take appropriate action, including placing a new order, reshipping items in an undelivered order, canceling an undelivered order, initiating contact with the ordering customer, or the like. The SAT system 101 may also monitor other data, including output (such as the number of packages shipped during a specific time period) and input (such as the number of empty cardboard boxes received for shipping). The SAT system 101 may also act as a gateway between different devices in the system 100, thereby enabling communication between devices such as the external front-end system 103 and the FO system 113 (e.g., 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 an embodiment where the network 100 enables the presentation of a system to allow a user to place an order for an item, the external front-end system 103 may be implemented as a web server that receives search requests, presents an item page, and requests payment information. For example, the external front-end system 103 may be implemented as a computer or a 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 run customized web server software designed to receive and process requests from external devices (not depicted), obtain information from databases and other data repositories based on those requests, and provide responses to the received requests based on the obtained information.

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 embodiment, the external front-end system 103 may include one or more of these systems, and in another embodiment, the external front-end system 103 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

The exemplary set of steps shown in FIG. 1B , FIG. 1C , FIG. 1D , and FIG. 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 web pages, including a search result page (SRP) (e.g., FIG. 1B ), a single detail page (Single Detail Page; SDP) (e.g., FIG. 1C ), a shopping cart page (e.g., FIG. 1D ), or an order page (e.g., FIG. 1E ). A user device (e.g., using a mobile device 102A or a computer 102B) can navigate to the external front-end system 103 and request a search by entering information into a search box. The external front-end system 103 may request information from one or more systems in the network 100. For example, the external front-end system 103 may request results that satisfy a search request from the FO system 113. The external front-end system 103 may also request and receive (from the FO system 113) a promised delivery date or "PDD" for each product returned in the search results. In some embodiments, the PDD represents an estimate of when a package will arrive at a user's desired location if ordered within a specific time period, such as by the end of the day (11:59 p.m.). (PDD will be discussed further below with respect to the FO system 113).

The external front-end system 103 may prepare an SRP based on the information (e.g., FIG. 1B ). The SRP may include information that satisfies the search request. For example, this may include images of products that satisfy the search request. The SRP may also include individual prices for each product, or information related to enhanced delivery options, PDDs, weights, sizes, quotes, discounts, or the like for each product. The external front-end system 103 may deliver the SRP to the requesting user device (e.g., via a network).

The user device may then select a product from the SRP, such as by clicking or tapping on a user interface or using another input device to select a product represented on the SRP. 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 product on the respective SRP. This may include, for example, a shelf life, country of origin, weight, size, number of items in a package, disposal instructions, or other information about the product. The information may also include recommendations of similar products (based on, for example, big data and/or machine learning analysis of customers who purchased the product and at least one other product), answers to frequently asked questions, reviews from customers, manufacturer information, images, or the like.

The external front-end system 103 may prepare an SDP (single detail page) (e.g., FIG. 1C ) based on the received product information. The SDP may also include other interactive elements, such as a “buy now” button, an “add to cart” button, a quantity field, an image of the item, or the like. The external front-end system 103 may deliver the SDP to the requesting user device (e.g., via a network).

The requesting user device may receive an SDP listing product information. After receiving the SDP, the user device may then interact with the SDP. For example, a user of the requesting user device may click or otherwise interact with an "add to cart" button on the SDP. This adds the product to a shopping 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 may generate a shopping cart page (e.g., FIG. 1D ). In some embodiments, the shopping cart page lists products that the user has added to a virtual “shopping cart.” The user device may request the shopping cart page by clicking on or otherwise interacting with an icon on the SRP, SDP, or other 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 (e.g., the quantity of each product, the price per item of each product, the price of each product based on the associated quantity), information about the PDD, the delivery method, the shipping cost, a user interface element for modifying the products in the shopping cart (e.g., deleting or modifying the quantity), an option for ordering additional products or setting up recurring deliveries of products, an option for setting up interest payments, a user interface element for proceeding to purchase, or the like. A user at the user device may click on or otherwise interact with the user interface element (e.g., a button that says "Buy Now") to initiate a purchase of the products in the shopping cart. After doing so, the user device may transmit the request to initiate the purchase to the external front-end system 103.

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

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

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

In some embodiments, the internal front-end system 105 may be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases the network 100) to interact with one or more systems in the network 100. For example, in embodiments where the network 101 enables the presentation of systems to allow users to place orders for items, the internal front-end system 105 may be implemented as a web server that enables users to view diagnostic and statistical information about orders, modify item information, or review statistics related to orders. For example, the internal front-end system 105 may be implemented as a computer or a computer running software such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, the internal front-end system 105 may run customized web server software designed to receive and process requests from the devices depicted in the network 100 (as well as other devices not depicted), obtain information from databases and other data repositories based on those requests, and provide responses to the received requests based on the obtained information.

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

In some embodiments, the transport system 107 may be implemented as a computer system that implements communication between devices in the network 100 and the mobile devices 107A to 107C. In some embodiments, the transport system 107 may receive information from one or more mobile devices 107A to 107C (e.g., mobile phones, smart phones, PDAs, or the like). For example, in some embodiments, the mobile devices 107A to 107C may include devices operated by delivery workers. Delivery workers (who may be permanent employees, temporary employees, or shift employees) may use mobile devices 107A to 107C to implement 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 arriving at the delivery location, the delivery worker may locate the package (e.g., in the back of a truck or in a crate of packages), use the mobile device to scan or otherwise capture data associated with an identifier on the package (e.g., a barcode, 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, giving it to the recipient, or the like). In some embodiments, the delivery worker may take a photo of the package and/or may obtain a signature. The mobile device may send a communication to the transport system 107 that includes information about the delivery, including, for example, the time, date, GPS location, a photo, an identifier associated with the delivery worker, an identifier associated with the mobile device, or the like. The transport system 107 may store this data in a database (not depicted) for access by other systems in the network 100. In some embodiments, the transport 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, some users may use one type of mobile device (e.g., a permanent worker may use a dedicated PDA with customized hardware such as a barcode scanner, stylus, and other devices), while other users may use other types of mobile devices (e.g., temporary or shift workers may utilize off-the-shelf cell phones and/or smartphones).

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

In some embodiments, the seller portal 109 may be implemented as a computer system that enables a seller or other external entity to electronically communicate 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, the shipping and order tracking system 111 may be implemented as a computer system that receives, stores, and forwards information about the location of packages ordered by customers (e.g., by a user using device 102A to device 102B). In some embodiments, the shipping and order tracking system 111 may request or store information from a web server (not depicted) operated by a shipping company that delivers the packages ordered by the customers.

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

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

The FO system 113 may also calculate a promised delivery date (PDD) for each product. In some embodiments, the PDD may be based on one or more factors. For example, the FO system 113 may calculate the PDD for a product based on past demand for the product (e.g., how many times the product was ordered during a period of time), expected demand for the product (e.g., how many customers are predicted to order the product during an upcoming period of time), network-wide past demand indicating how much of the product was ordered during a period of time, network-wide expected demand indicating how much of the product is expected to be ordered during an upcoming period of time, one or more counts of the product stored in each fulfillment center 200, which fulfillment center stores each product, expected or current orders for the product, or the like.

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

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

In some embodiments, the 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 forecast demand level for a particular product based on, for example, past demand for the product, expected demand for the product, past demand across the network, expected demand across the network, a count of products stored in each fulfillment center 200, expected or current orders for each product, or the like. In response to the forecast level determined and the volume of each product across all fulfillment centers, the SCM system 117 may generate one or more purchase orders to meet the expected demand for the particular product.

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

In some embodiments, WMS 119 may store information associating one or more devices (e.g., devices 107A to 107C or devices 119A to 119C) with one or more users (the one or more users are associated with network 100). For example, in some cases, a user (such as a part-time employee or a full-time employee) may be associated with a mobile device because the user owns the mobile device (e.g., the mobile device is a smartphone). In other cases, a user may be associated with a mobile device because the user temporarily keeps the mobile device (e.g., the user picks up the mobile device at the beginning of the day, will use the mobile device during the day, and will return the mobile device at the end of the day).

In some embodiments, the WMS 119 may maintain a work log for each user associated with the network 100. For example, the WMS 119 may store information associated with each employee, including any specified process (e.g., unloading from a truck, picking items from a pick-up area, rebin wall work, packaging items), a user identifier, a location (e.g., a floor or zone in a fulfillment center 200), a number of units moved through the system by the employee (e.g., number of items picked, number of items packaged), identifiers associated with devices (e.g., devices 119A through 119C), or the like. In some embodiments, WMS 119 may receive login and logout information from a timing system, such as a timing 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 (e.g., via FMG 115), and may provide products and/or services (e.g., delivery or installation) directly to customers.

In some embodiments, the fulfillment center Auth system (FC Auth) 123 may be implemented as a computer system having various functions. For example, in some embodiments, FC Auth 123 may act as a single-sign on (SSO) service for one or more other systems in the 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 obtain those privileges without requiring a second login process. In other embodiments, FC Auth 123 may enable a user (e.g., an employee) to associate himself with a specific task. For example, some employees may not have electronic devices (such as devices 119A-119C) and may actually move from task to task and zone to zone within fulfillment center 200 during the course of a day. FC Auth 123 may be configured to enable such employees to indicate what task they are working on and what zone they are in at different times of the day.

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

The specific configuration depicted in FIG. 1A is merely an example. For example, although FIG. 1A depicts FC Auth system 123 connected to FO system 113 via FMG 115, not all embodiments require this specific configuration. In practice, 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, an enterprise intranet, a wide area network (WAN), a metropolitan area network (MAN), a wireless network compliant with 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. A fulfillment center 200 is an example of a physical location where items are stored for shipment to customers upon ordering. A fulfillment center (FC) 200 may be divided into a plurality of zones, each of which is depicted in FIG. 2. In some embodiments, these "zones" may be thought of as virtual divisions between different stages of the process of receiving items, storing items, retrieving items, and shipping items. Thus, while "zones" are depicted in FIG. 2, other divisions are possible, and the zones in FIG. 2 may be omitted, duplicated, or modified in some embodiments.

Inbound area 203 represents an area of FC 200 where items are received from sellers who wish to sell products using network 100 of FIG. 1 . 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 that are stacked together on the same pallet to save space.

The worker will receive the objects in the inbound area 203, and may use a computer system (not depicted) to check the objects for damage and correctness as appropriate. For example, the worker may use a computer system to compare the quantity of object 202A and object 202B with the ordered quantity of the objects. If the quantity does not match, the worker may reject one or more of object 202A or object 202B. If the quantity does match, the worker may move those objects to the buffer area 205 (using, for example, a dolly, a hand truck, a forklift, or manually). The buffer area 205 may be a temporary storage area for the objects that do not need to be in the picking area at present (e.g., because there is a sufficiently high quantity of objects in the picking area to meet the predicted demand). In some embodiments, forklift 206 operates to move objects around buffer area 205 and between inbound area 203 and unloading area 207. If object 202A or object 202B in the picking area is needed (e.g., due to predicted demand), the forklift can move object 202A or object 202B to unloading area 207.

Unloading area 207 may be an area of FC 200 where objects are stored before being moved to picking area 209. A worker assigned to the picking task ("picker") may approach object 202A and object 202B in the picking area, use a mobile device (e.g., device 119B) to scan a barcode of the picking area, and scan the barcode associated with object 202A and object 202B. The picker may then take the object to picking area 209 (e.g., by placing the object on a cart or carrying the object).

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

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

Once the user places an order, the picker may receive instructions on device 119B to retrieve one or more objects 208 from storage unit 210. The picker may retrieve object 208, scan a barcode on object 208, and place the object 208 on transport mechanism 214. Although 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, an elevator, a cart, a forklift, a hand truck, a dolly, or the like. Object 208 may then arrive at packaging area 211.

The packing area 211 may be an area of the FC 200 where the pick-up area 209 receives items and packages them into boxes or bags for final shipment to customers. In the packing area 211, a worker assigned to receive items (a "merge worker") receives the item 208 from the pick-up area 209 and determines which order the item 208 corresponds to. For example, the merge worker may use a device such as a computer 119C to scan a barcode on the item 208. The computer 119C may visually indicate which order the item 208 is associated with. This may include, for example, a space or "cell" on a wall 216 that corresponds to the order. Once the order is complete (e.g., because the cell contains all the items for the order), the merge worker may indicate to the packing worker (or "packer") that the order is complete. The packer may retrieve items from the cell and place them in boxes or packages for shipping. The packer may then send the boxes or packages to a hub zone 213, such as via a forklift, cart, trolley, hand truck, conveyor belt, manually, or otherwise.

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

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

Workers and/or machines in the 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 with existing routes and/or sub-routes, a calculation of the workload for each route and/or sub-route, the time of day, the method of transportation, the cost of transporting the package 220, the PDD associated with the items in the package 220, or the like. In some embodiments, a worker or machine may scan a package (e.g., using one of the devices 119A-119C) to determine its final destination. Once a package 220 is assigned to a particular route and/or sub-route, the worker and/or machine may move the package 220 to be transported. In exemplary FIG. 2 , the camp area 215 includes a truck 222, a car 226, and a delivery worker 224A and a delivery worker 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, rented, or operated by the same company that owns, rents, 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 (e.g., seasonally). Car 226 may be owned, rented, or operated by delivery worker 224B.

FIG3 shows an exemplary schematic diagram of a computer-implemented system 300 for unitized package delivery. In some embodiments, the system 300 may include a confluence worker 301, a picked object 208 having an order identifier 305 (e.g., a barcode, a tag), and a user interface device 302 (e.g., a mobile device/PDA 119B). The system 300 may further include: a first storage location 320 (e.g., a packaging area 211) including storage cells 324 (e.g., storage cells 324_1, storage cells 324_2), a camp 340 (e.g., a camp area 215) including storage cells 344, and a delivery truck 201. First storage location 320 and campsite 340 may sort items based on different information related to the final destination. As an example, at first storage location 320, items (e.g., item 208) may be sorted based on the geographic area to which the package is destined (e.g., based on a zip code), and at campsite 340, items may be sorted based on a delivery route or sub-route (e.g., based on a route number). (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 (e.g., SAT 101, WMS 119, SCM 117) may be configured to communicate with user interface device 302 to indicate sorting of items.

FIG. 3 shows an exemplary unitized package delivery system. As used herein, the term "unitized" 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 before shipping. Unitized package delivery may have numerous advantages over existing systems for package delivery. Unitized package delivery may have some or all of the advantages discussed herein, as well as other advantages.

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

ii. Increased picking density - In currently existing parcel delivery systems, pickers may pick items sequentially to fulfill customer orders. For example, a picker may pick all items for Order 1 before picking items for Order 2. This sequential approach to picking results in time and efficiency losses because pickers spend more time in transition than picking items. In contrast, the unified parcel delivery system 300 may allow for increased picking density because pickers may be tasked to pick items based on their location and not based on customer orders. For example, a picker may be tasked to pick 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 transit.

iii. Improved Traceability - As shown in FIG. 3 , in a unified package delivery system 300 , a worker (e.g., worker 301 ) may scan a barcode (e.g., order identifier 305 and/or location identifier) associated with a package (e.g., package 208 ) prior to initiating a process and after completing a process. In addition, the barcode may be scanned periodically during a process or upon receipt of a prompt. Information recorded by the scan may be stored, for example, in a database of the system 100 , thereby allowing the package to be tracked as it passes through processing. Barcodes of containers or totes may also be scanned, thereby providing information associated with the location of items contained in the container during the process of picking, sorting, packaging, shipping, etc., thereby allowing container and package traceability.

iv. Faster sorting - After receiving items at a camp (e.g., camp area 215) from a packaging area, the items can be sorted based on a sub-route or delivery route without waiting for other items of the order to arrive at the camp. Since the items are sorted based on a sub-route and not based on the customer order to which they belong, the storage period of the items can be reduced, thereby improving the sorting rate. This can also achieve better space utilization, improve worker efficiency, reduce cycle time, and enrich customer experience.

v. Reduced storage time - Singulation of items can make it possible to reduce the duration that an item sits on a shelf awaiting picking, packaging, sorting, or shipping, since the item can be processed without regard to the status of other items in the order. Reduced storage time for items can reduce associated costs associated with inventory management and reduce the risk of mishandling and misplacement of items.

vi. Reduced "load preparation" time - In existing package delivery and shipping systems, employees such as workers, drivers, loaders, supervisors, floor monitors, etc. may spend a significant amount of their time at the beginning of a shift or work period, for example, ensuring that all items belonging to an order are loaded. This 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 preparation time as employees load containers or container carriers such as totes, cages, etc. into delivery trucks based on planned delivery areas and delivery routes.

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

In some embodiments, the system 100 may be configured to receive a customer order. The customer order may 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 an emergency order for toothpaste, toothbrush, and mouthwash, the second sub-order may include normal delivery of cheese, crackers, and potato chips, and the third sub-order may include delayed delivery of beverages. The system 100 may receive the customer order and generate an order identifier 305 associated with each of the ordered items. In some embodiments, system 100 may generate a unique sub-order identifier associated with each sub-order (e.g., sub-order identifier 305A for the first sub-order, sub-order identifier 305B for the second sub-order, and sub-order identifier 305C for the third sub-order).

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

In some embodiments, one or more pickers may receive an indication of the urgency of a sub-order while retrieving items for other customer orders. Pickers may retrieve items for urgent sub-orders based on their current location within the picking area 209 and forward the items to the packaging area 211. For example, if the urgent sub-order includes a toothbrush and a pair of socks, a picker in or near the oral hygiene section may retrieve the toothbrush and a picker in or near the apparel section may retrieve the pair of socks, thereby improving the picking density. Once the container or tote is full, the items may be transported to the packaging area 211. This approach can improve 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 (e.g., a smartphone 119B, or a computer 119C) to cause the device to instruct a picker to print the order identifier 305. In some embodiments, the user device may include a handheld device such as a PDA configured to print a label. Alternatively, the system 100 may include a printing device (not depicted) such as a label printer, inkjet printer, or laser printer. The printing device may be configured to receive instructions to print labels, instructions, memos, or the like from one of the computer implementations of the system 100. The instructions may further include requesting the picker to associate the printed order identifier 305 with the object of the customer order, for example by attaching the printed order identifier 305 to the picked object 208. In some embodiments, the system 100 may be configured to electronically associate the order identifier 305 with the object of the customer order. For example, the system 100 may update a database including information related to all incoming customer orders.

The confluence worker 301 may receive the picked object 208 in the packaging area 211. In some embodiments, the confluence worker 301 may use a user interface device 302 (e.g., a smartphone 119B) to receive information associated with a customer order from the system 100. The user interface device 302 may include, but is not limited to, a handheld display device (e.g., a tablet 119A), a smartphone (e.g., a mobile device/PDA 119B), a computer (e.g., a computer 119C), a body mounted display, a head mounted display, etc. The user interface device 302 may be substantially similar to a mobile device, such as (e.g.) the computer 119C of FIG. 1A. The user interface device 302 may communicate and exchange information with, for example, the WMS 119.

In some embodiments, the 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 a customer order, such as the number of items ordered, the urgency of delivery of the ordered items, the destination location of the items to be delivered, etc. In some embodiments, the user interface display may be a visual display or an audio-visual display. For example, if the order is "urgent," the user interface device 302 may receive an audio-visual message indicating a request to expedite fulfillment of the order. 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 confirm 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 information of the order identifier 305. The user interface device 302 may be configured to temporarily store the recorded information and later upload it to a database of one of the computer implementation systems of the system 100. In some embodiments, the user interface device 302 may automatically upload the recorded information to the database.

In some embodiments, the user interface device 302 may receive an instruction to review the order identifier 305 associated with the picked object 208 via an interactive element of the user interface display. For example, one of the computer-implemented systems of the system 100 (e.g., WMS 119, SCM 117, or SAT 101) may generate an instruction to the user interface device 302 to display an instruction to the user to start reviewing the order identifier 305 associated with the object 208. Reviewing the order identifier 305 may include determining a final destination for delivery of the object 208 by, for example, scanning or reading the order identifier 305. For example, scanning an order identifier (e.g., a barcode) using a barcode scanning device may display 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, etc. In some embodiments, a customer order may include a plurality of sub-orders and each sub-order may further include a plurality of items. It should be understood that the object 208 may include a package containing one or more items of a customer order.

After determining the final destination of the delivery of the object 208, the confluence worker 301 may place the object 208 in the first storage location 320 based on the determined final destination. The first storage location 320 may include storage cells 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 include a confluence wall, a storage cell, a storage rack having cells, or a cabinet. Other organizational storage means may also be used.

In some embodiments, objects 208 may be sorted in storage cells 324 of first storage location 320 based on the destination of the objects 208 without regard to the status of orders or other items of the order that may be associated with the objects. In current existing systems, a merge worker may wait to pick up all items of an order before sorting the order for delivery. In contrast, in the disclosed embodiments, each object may be treated as an individual order and sorted based on the destination without regard to the status of other items of the order. This may reduce idle time for merge workers, thereby increasing packaging efficiency. In some embodiments, packaging efficiency as disclosed herein may be referred to as the number of objects packaged in a specific time period. For example, packaging efficiency can be expressed as units per hour (UPH). Other efficiency measures may also be used. Singulation of items can also reduce the shelf life of items (defined in this article 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 and reducing the risk of mishandling and misplacing items.

In some embodiments, each storage cell 324 may be associated with a campsite 340. In some embodiments, the campsite 340 may be an on-site storage or sorting facility within the FC 200's station. In some embodiments, the campsite 340 may be an off-site storage or sorting facility at a remote location. A campsite identifier may be used to identify the association of each storage cell 324 (e.g., storage cell 324_1 or storage cell 324_2) with the corresponding campsite. The campsite identifier may include, but is not limited to, a mark, a barcode, a number, or a label. Although only a limited number of storage cells 324 are shown, it should be understood that the first storage location 320 may include any number of storage cells 324.

In some embodiments, the user interface device 302 may notify the confluence worker 301 through instructions to place the object 208 in the corresponding storage cell 324 based on the determined destination location of the object 208. For example, based on a customer order, one of the computer implementation systems of the system 100 (e.g., WMS 119, SCM 117, or SAT 101) may determine the campsite to which the object 208 may be directed. The confluence worker 301 may place the object 208 in the corresponding storage cell 324.

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

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

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

In some embodiments, camp 340 may include one or more storage spaces 342. Storage spaces 342 may include, but are not limited to, walls with storage cells, storage cells, storage racks with cells, or cabinets. Other organized storage means may also be used. For example, storage space 342 may include a wall with storage cells 344. Each storage cell 344 may be associated with a sub-route for delivery of object 208.

A worker at camp 340 may receive one or more objects 208 from storage location 320. A worker (e.g., a sorter) may review order identifiers 305 associated with the picked objects 208. In some embodiments, a worker may receive a notification to review order identifiers 305 on user interface device 302. For example, one of the computer implementation systems of system 100 (e.g., WMS 119, SCM 117, or SAT 101) may generate an instruction to the worker to start reviewing order identifiers 305 associated with objects 208 to be displayed on user interface device 302. Reviewing order identifiers 305 may include determining a final destination for objects 208.

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

In some embodiments, the user interface device 302 may notify the worker through instructions to place the object 208 in the corresponding storage cell 344 based on the determined final destination of the object 208. For example, based on a customer order, one of the computer implementation systems of the system 100 (e.g., WMS 119, SCM 117, or SAT 101) may determine the storage cell 344 to which the object 208 may be directed. The worker may place the object 208 in the corresponding storage cell 324 based on the instructions from the user interface device 302.

A subroute identifier may be used to identify the association of each storage cell 344 with a corresponding subroute. The subroute identifier may include, but is not limited to, a label, a barcode, a number, or a tag. Although only a limited number of storage cells 344 are shown, it should be understood that the camp 340 may include any number of storage cells 344.

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

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

In some embodiments, each storage cell 344 may be associated with a container 350 (e.g., a handbag). All objects (e.g., object 208) of storage cell 344 may be placed in container 350. In some embodiments, container 350 may be identified using container identifier 355. Container identifier 355 may include information associated with a subroute including a subroute identifier. In some embodiments, container identifier 355 may include information related to a campsite and a subroute. For example, container identifier may include a marker CS3_SR1, where CS indicates a starting campsite and SR indicates a designated subroute for delivering objects in the container. Container identifier 355 may include, but is not limited to, a marker, a barcode, a number, or a label.

In some embodiments, the user interface device 302 may be configured to display a notification or instruction to place the object 208 in the corresponding container 350 based on the determined final destination of the object 208. For example, based on a customer order, one of the computer implementation systems of the system 100 (e.g., WMS 119, SCM 117, or SAT 101) may determine a container 350 in which the object 208 may be placed. The worker may place the object 208 in the corresponding container 350 based on the instruction from the user interface device 302.

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

In some embodiments, one or more containers 350 may be loaded onto a delivery vehicle (e.g., delivery truck 201) for delivery to a customer. Containers 350 may be configured in delivery truck 201 based on sub-routes. For example, packages or objects (e.g., object 208) to be delivered at a destination closer to the start of a sub-route may be placed closer to an entry-exit door so that a delivery worker can directly access the package. In some embodiments, containers 350 including urgent orders may be placed closer to an entry-exit door to enable quick access to the package. In some embodiments, sub-routes may be adjusted based on the type and urgency of the order or PDD. In some embodiments, both the sub-routes and the configuration of containers in delivery truck 201 may be adjusted based on customer orders and PDD.

Containers 350 may be placed on container carriers 360 before being loaded into delivery truck 201. Container carriers 360 may include carts, trolleys, cages, baskets, or the like. In some embodiments, container carriers 360 may include identifiers, such as bar codes, labels, or tags. In some embodiments, user interface device 302 may notify a delivery worker or truck loader via instructions to place containers 350 on delivery truck 201 based on a predetermined configuration. For example, based on the PDD, one of the computer-implemented systems of system 100 (e.g., transportation 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. The delivery worker or truck loader may place the container 350 or container carrier 360 in the delivery truck 201 based on a determination made by one of the computer-implemented systems of the system 100 (e.g., the transportation system 107). The user interface device 302 may indicate to the delivery worker or truck loader the configuration of the container 350 within the container carrier 360 and/or a representation of the configuration of the container carrier 360 in the delivery truck 201.

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

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 a sub-route after the delivery truck 201 has been loaded. The delivery worker may receive the instruction via a user interface display on user interface device 302.

Referring now to FIG. 4 , an exemplary flow chart of a process 400 for singulated package delivery consistent with the disclosed embodiments is shown. The process may include: receiving a customer order; generating an order identifier based on the customer order; determining an expected final destination of items in the customer order; picking at least some of the items in the customer order; sorting the picked items based on a two-step sorting process; loading the picked items in the customer order onto a delivery truck without waiting for the remaining items in the customer order; and delivering the picked items to the customer.

Overall package delivery efficiency is a measure of the efficiency of each step in a process that relies on package delivery. Shipping packages from FCs to customers to fulfill orders typically involves multiple steps, and most of these steps must be performed in a linear sequential order. For example, picking may precede receiving orders and generating order identifiers, sorting may precede picking, packaging may precede sorting, loading items onto delivery trucks may precede packaging, and so on. 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. The overall efficiency can be improved by improving the efficiency of each step or by improving the efficiency of at least one step while maintaining the efficiency of other steps. As discussed above, "singularization" herein 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 before shipping, which can improve package delivery efficiency by reducing cycle time and reducing idle time for employees involved in the process. In some embodiments, one or more steps of process 400 can be performed by one or more user interface devices (e.g., each user interface device is operated by a user in a different zone of FC 200).

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

In some embodiments, one or more computer implementations of system 100 (e.g., 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 implementations of system 100 may be configured to review and identify common objects between multiple customer orders. A user interface device may be configured to display an indication of the common objects, thereby requesting input from the user, such as receiving a confirmation. The indication may include information related to a description of the object, the quantity of the object ordered, etc. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders contain a common object, such as a bottle of water. A worker (e.g., a picker) can receive instructions to pick up 50 bottles of water via a 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 (e.g., order identifier 305) based on the received customer order. The order identifier may include a barcode, a label, a tag, an alphanumeric code, a quick response (QR) code, or the like. The order identifier may be a machine-readable optical label containing information about the customer order. The information contained in the order identifier may include, but is not limited to, the final destination of the order, the total number of items in the customer order, the type of delivery requested, customer information, a promised delivery date, and a promised delivery time, etc. In some embodiments, the system that generates the order identifier can determine the storage location (e.g., campground area 215, hub area 213) and the delivery route to which the items in the customer order may belong based on the final destination information of the customer order. For example, based on the postal 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 district identified in the final destination, the system can determine the delivery route for the items in the customer order.

After scanning or reading the 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 information associated with the order identifier. For example, after scanning or reading the order identifier, the user interface device may 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 a user interface device to display an indication associating each item of the customer order with an order identifier. The user interface device may be configured to display an indication or alert regarding the received customer order, thereby requesting input from the user, such as a receipt confirmation. After receiving the 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 up one or more items of the customer order and associate each picked item with the order identifier received from the one or more computer-implemented systems, such as by scanning the order identifier and a bar code on the item. In some embodiments, associating an item for a customer order with an order identifier may include physically printing the order identifier using a label printer or a barcode printer. The printed label or barcode 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, a worker who does not receive or has access to the initial order identifier may be able to scan the order identifier printed and affixed to the item.

In step 440, one or more computer implementations of system 100 may determine the intended final delivery destination of each of the items ordered by the customer. As an example, the customer may order a bouquet of flowers to be delivered to a friend's house by 8 p.m. and a pack of batteries to be delivered to his or her parents' house within 24 hours. One or more computer implementations of system 100 may generate two separate order identifiers representing the two orders. Each of the items may 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 a delivery route for delivering items of a customer order at the intended delivery destination.

In some embodiments, the sorting process may be a two-step sorting process. The first step may include sorting the picked items based on the campgrounds to which the items may be directed. The campgrounds may be determined based on, for example, the postal 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 campgrounds based on the delivery routes to which the items may be sent for delivery. The delivery routes may be determined based on, for example, the districts or streets represented by the postal code within the area.

In step 450, one or more computer-implemented systems of the system 100 may send instructions to the user interface device to display instructions or alerts to sort the picked items of the customer order based on the pre-designated storage space (e.g., the storage unit 324 of the storage location 320), which is determined by the one or more computer-implemented systems of the system 100. The pre-designated storage space may represent a campsite to which the items can be directed for further sorting. In some embodiments, one or more storage spaces may be designated to a campsite. For example, storage space 1 to storage space 12 may be designated as campsite 1 represented by storage cell 324_1, and storage space 13 to storage space 23 may be designated as campsite 2 represented by storage cell 324_2, and storage space 24 may be designated as campsite 3 represented by storage cell 324.

Each of the sorted objects may be transported to a corresponding campsite. In some embodiments, the campsite may be an on-site storage facility (e.g., campsite area 215) within the FC 200's station. The sorted objects may be transported to the campsite area 215 using a transport device such as, for example, a conveyor belt, a forklift, a hand truck, a dolly, or a cart. In some embodiments, the campsite may be an off-site storage facility such as a warehouse or a storage unit separate from the FC 200. The sorted objects may be transported to the off-site storage facility using, for example, a delivery truck. The sorted objects belonging to the customer order may be transported to the campsite without waiting for the rest of the objects in the customer order to reduce idle time.

In step 460, one or more computer implementations of system 100 may send instructions to the user interface device to display instructions or alerts to sort the picked objects in the camp based on the delivery route. The delivery route may be reserved by one or more computer implementations of system 100 based on the final delivery destination in the customer order. The worker may sort the picked objects in the camp by placing the objects in a storage cell (e.g., storage cell 344) based on the delivery route. The worker may obtain the delivery route information by, for example, scanning an order identifier on the object. Each of the storage cells 344 may be identified by a route identifier or a sub-route identifier.

In step 470, one or more computer implementations of system 100 may send instructions to a user interface device to display instructions or alerts to place the selected objects from storage cells 344 into a container (e.g., container 350). Each storage cell 344 may be associated with a container configured to accommodate the objects stored in the corresponding storage cell. In some embodiments, each container may be identified by a container identifier that includes information identifying the site and the storage cell. The picked objects belonging to the customer order may be placed in the container without waiting for the remaining objects of the same customer order to reduce idle time.

The containers 350 or container carriers 360 may be loaded onto a delivery vehicle (e.g., a delivery truck 201) configured to accommodate containers, totes, wheeled cages, carts, dollies, and the like. The containers may be loaded in a manner that reduces unloading time during delivery of the items based on, for example, the configuration of the delivery route. The configuration of the containers on the delivery truck may also be based on factors including, but not limited to, the urgency of the delivery, the promised delivery time, whether the items are perishable foods, and the like. In some embodiments, the storage compartments of the delivery truck may include built-in storage spaces such as cabinets, cells, shelves, racks, cages, or wheeled cages. Each container carrier in the delivery truck may be identified by a container carrier identifier (e.g., 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 configured against the rear wall of the storage compartment, labeled 360_1 to 360_4 from left to right. Thus, the container carrier located at the rear left corner of the storage compartment of the delivery truck may be identified as container carrier 360_1, and the container carrier located at the rear right corner of the storage compartment of the delivery truck may be identified as container carrier 360_4. For example, a visual or tabular representation of the configuration of the container carriers 360 may be generated by one or more computer implementation systems of the system 100, such as the transport system 107.

In some embodiments, the loading configuration of containers on the container carrier 360 may be recorded to generate a representation of the delivery truck loading configuration. For example, the transportation system 107 may send instructions to the user interface device that display an instruction to scan the container identifiers (e.g., barcodes) of all containers placed in the container carrier and scan the corresponding container carrier identifiers. The system may 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 may 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 system 100 (such as transportation system 107), for example, may send a command to a user interface device (e.g., one of mobile devices 107A to 107C) to display instructions for delivering objects stored in containers loaded on a delivery truck. The user interface device may display an instruction requesting input from a user (e.g., a delivery worker or loader) to verify that the loading process is complete before the object is dispatched for delivery. The user interface device may receive input from the user and store the received input in a database associated with system 100.

In some embodiments, one or more computer-implemented systems of the system 100 may send instructions to the user interface device to display instructions to record information associated with the order identifier, such as by scanning the order identifier. The user interface device may display instructions to record the order identifier information after the object has been picked up, after the picked object is sorted based on the storage location in the first step of the sorting process, before the sorted object is transported to the camp, after arriving at the camp, after the picked object is sorted based on the delivery route in the second step of the sorting process, after the sorted object is placed in the container, and after the container is loaded on the delivery truck. Information recorded at all steps of the process may be stored and updated in a database associated with the system 100 (e.g., associated with or connected to the WMS 119 or the transportation system 107).

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

Referring now to FIG. 5 , an exemplary flow chart of a process 500 for generating a visual representation of a loading configuration of a delivery vehicle consistent with the disclosed embodiments is shown. It should be understood that the flow chart is an exemplary sequence of steps of the process, and the steps may be performed in other sequences. In addition, steps may be added, omitted, skipped, repeated, or modified based on the application and user needs.

In step 510, one or more computer-implemented systems of system 100 may identify a delivery vehicle (e.g., delivery truck 201) that includes storage space. In some embodiments, transportation system 107 of system 100 may identify delivery vehicles based on, for example, storage space requirements, delivery route characteristics, delivery truck operator experience or classification, or other data. For example, transportation system 107 may identify small delivery vehicles used for delivery routes with narrow roads, and the delivery truck operator (e.g., truck driver) on duty may only have a valid driver's license 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 a delivery route or sub-route, the system 100 may recommend a larger delivery vehicle that includes more storage space.

In step 520, one or more computer implementations of system 100 (such as transport system 107) may send instructions to a user interface device that display instructions for determining the configuration of storage space within a delivery truck. In some embodiments, a delivery truck may include built-in storage space in a storage compartment, such as a cabinet, rack, shelf, cage, etc. For example, a delivery truck may include a storage compartment to accommodate a removable storage unit such as a wheeled cage.

In some embodiments, a storage space identifier or a container carrier identifier may be used to identify each storage space in a delivery truck. The container carrier identifier may include a barcode, a label, a tag, or a QR code. The container carrier identifier may include information associated with the location of the container carrier 360 within the storage compartment of the delivery truck. For example, four container carriers 360 may be arranged against the rear wall of the storage compartment, labeled 360_1 to 360_4 from left to right (not shown in FIG. 3 ). Thus, the container carrier located at the left rear corner of the storage compartment of the delivery truck may be identified as container carrier 360_1, and the container carrier located at the right rear corner of the storage compartment of the delivery truck may be identified as container carrier 360_4. In some embodiments, a delivery truck may include built-in storage spaces, each storage space having a storage space identifier.

In some embodiments, a delivery truck operator (e.g., a driver or loader) may record the configuration of built-in storage spaces in a delivery truck, for example, by scanning a storage space identifier. In some embodiments, a database of system 100 may include information associated with the configuration of storage spaces in a delivery truck. For example, the database may include information associated with the configuration of 24 storage spaces in a delivery truck 14.

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. The container identifier may include a barcode, a label, a tag, or a QR code. The container identifier may include information associated with at least a campsite and a delivery route for the items contained in the container. In some embodiments, one or more containers may be assigned to a delivery route based on the number of items 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 implementations of system 100 (such as transport system 107) may send instructions to the user interface device to display instructions for loading the container into the storage space of the delivery truck. This may enable quick access to the object during delivery to load the container onto the delivery truck in an unloaded manner.

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 that display instructions for associating each container with the storage space in which it is placed. For example, transport system 107 may send instructions to the user interface device that display instructions for scanning container identifiers (e.g., bar codes) of all containers placed in the storage space and scanning corresponding storage space identifiers. In some embodiments, the instructions may include step-to-step instructions for associating containers with storage spaces and uploading information to a database of system 100.

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

In some embodiments, the loading configuration of the delivery truck can 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 can be updated when a delivery is completed. For example, when the delivery truck driver delivers an object to a customer and the container is empty, the display of the loading configuration can indicate that the object in the container placed in the storage space has been delivered. This information can be updated in the database, allowing the transportation system 107 and/or the system 100 to determine whether the promised delivery date and time is met.

In some cases, a modified singularized delivery approach may be utilized. For example, in a fulfillment center where sufficient space is permitted, the singularized approach may be further simplified. In some cases, once ordered items arrive at the location, the items may be delivered in waves. A wave may, for example, be a delivery shift. There may be multiple delivery waves from the location, and one or more items in an order may be assigned to one of these waves. It may be desirable to separate items within a single order for delivery in different waves so that certain items with a higher urgency may arrive before items with a lower urgency. In some embodiments, when one or more items in an order may not be immediately available, the remaining items in the order may be delivered in one wave, and the missing items may be delivered in another wave when they become available.

FIG6 illustrates an alternative embodiment of a unitized package delivery system that is based on waves of a campsite rather than delivery routes as discussed above with respect to, for example, FIG3. According to some embodiments, there may be a fulfillment center with sufficient building area to host two or more packaging areas. For example, FC 600 may contain a first packaging area 622 and a second packaging area 624. The first packaging area 622 and the second packaging area 624 may be separated by a distance or may be located close to each other. One of ordinary skill in the art will appreciate that the specific layout and spatial configuration of FC 600 may be modified as dictated by the specific location and building of FC 600 or other considerations. The first packaging area 622 may include a plurality of storage cells 622-n, such as storage cell 622-1, storage cell 622-2... storage cell 622-n. Similarly, the second packaging area 624 may include a plurality of storage cells 624-n, such as storage cell 624-1, storage cell 624-2... storage cell 624-n. One or more workers 602 may be present in both the first packaging area 622 and the second packaging area 624 to perform object sorting and packaging.

Each of the plurality of storage cells 622-n may contain a tote 612. The tote 612 may contain items that a customer has ordered. The worker 602 may sort the order items by a first sorting process, and then pack (i.e., place) the order items in an appropriate tote 612 in one of the storage cells 622-n. After the tote 612 is packed, the tote 612 may be transferred to a second packing area 624. Each of the storage cells 622-n may correspond to one or more camps, so that items going to a specific camp will be sorted to a specific storage cell accordingly.

In some embodiments, the tote 612 may be transported from the first packaging area to the second packaging area by means of a conveyor, such as a conveyor 632. Such conveyors may include conveyor belts, rollers, rails, storage systems, or other suitable systems. In some embodiments, the tote 612 may be transported from the first packaging area 622 to the second packaging area 624 by means of a vehicle, a forklift, an electric cart, a drone, a robot, or any such motorized equipment. In some embodiments, the tote 612 may be transported from the first packaging area 622 to the second packaging area 624 by the worker 602 with or without the aid of tools such as carts, trolleys, and/or pallet transporters.

In some embodiments, when the tote 612 arrives at the second packaging area 624, the items contained in the tote 612 may be re-sorted based on the second sorting. After the second sorting, the items may be packaged (i.e., placed) into the tote 614, which may be stored in one of the storage cells _624n . Each of the storage cells _624n may correspond to a particular wave of a particular camp. For example, wave 1 of camp 1 may correspond to storage cell 624-1, wave 1 of camp 2 may correspond to storage cell 624-2, and so on. The second sorting places each item in the tote 612 into its appropriate camp and wave, and then packs it into the tote 614.

Once packaged, tote 614 may be dispatched for delivery. In some embodiments, tote 614 may have a different design than tote 612. For example, tote 614 may have a smaller size than tote 612. In some embodiments, tote 614 may be transported to a corresponding campsite and no further sorting will be required.

Referring now to FIG. 7 , an alternative flow chart of a unified package delivery process 700 is shown, which is based on waves of campsites as discussed above with respect to, for example, FIG. 4 . In some embodiments, process 700 may correspond to the system disclosed in FIG. 6 .

One of ordinary skill in the art will appreciate that the disclosed embodiments can increase the picking density of worker 602. Picking density can refer to the amount of objects processed for delivery per unit time, per work hour, per shift, or other such suitable time interval used to measure efficiency. For example, if worker 606 only picks objects for a particular camp or a particular order, idle time can be generated while worker 606 waits for the next object to be picked. In addition, one of ordinary skill in the art will appreciate that picking density can be further increased by having at least two sorting processes (such as step 750 and step 780) instead of only one sorting process. For example, if a single worker is responsible for both picking objects for delivery to a camp and sorting the picked objects into waves for a particular camp, picking density can be reduced. Picking density, and therefore efficiency, can be maximized by having a second worker perform a more detailed specific sorting process (such as in step 780), which can be performed at a different location from the first worker's location.

In step 710, one or more computer implementations of system 100 (e.g., WMS 119, SCM 117, SAT system 101) may receive a customer order. The customer order may include multiple items. In some embodiments, the customer order may include multiple sub-orders and each sub-order may include multiple items. The one or more computer implementations of system 100 may be configured to review the customer order and identify information such as the total number of items ordered, a description of each of the items ordered, a requested delivery time, a final destination of the items, etc. In some embodiments, the one or more computer implementations of system 100 may determine a promised delivery date or a promised delivery time for the customer order based at least on the requested delivery time. For example, for an emergency order request from a customer, the system may determine a promised delivery time of several hours or delivery to the intended final destination within 24 hours. In some embodiments, the system may be configured to individually determine a promised delivery date and time for each of the items in a customer order. For example, a customer order may include some items for emergency delivery and the remaining items for normal delivery. The system may be configured to determine the promised delivery time based on the type of delivery requested.

In some embodiments, one or more computer-implemented systems of system 100 (e.g., 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 may be configured to review and identify common objects between the multiple customer orders. The user interface device may be configured to display an indication of the common objects, thereby requesting input from the user, such as receiving a confirmation. The indication may include information related to a description of the object, the quantity of the object ordered, etc. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders contain a common object, such as a bottle of water. A worker (e.g., a picker) can receive instructions to pick up 50 bottles of water via a user interface device. The implementation of this approach can improve the efficiency of picking and the overall efficiency of the process.

At step 720, one or more computer-implemented systems of system 100 may generate an order identifier (e.g., order identifier 616) based on the received customer order. The order identifier may include a barcode, a label, a tag, an alphanumeric code, a quick response (QR) code, or the like. The order identifier may be a machine-readable optical label containing information about the customer order. The information contained in the order identifier may include, but is not limited to, the final destination of the order, the total number of items in the customer order, the type of delivery requested, customer information, a promised delivery date, and a promised delivery time, etc. In some embodiments, the system that generates the order identifier can determine the storage location (e.g., campground area 215, hub area 213) and the delivery route to which the items in the customer order may belong based on the final destination information of the customer order. For example, based on the postal 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 district identified in the final destination, the system can determine the delivery route for the items in the customer order.

After scanning or reading the order identifier, for example using a user interface device 606 equipped with barcode scanning capabilities, 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 may 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 730, one or more computer-implemented systems of system 100 may instruct user interface device 606 to display an indication associating each item of the customer order with an order identifier. The user interface device may be configured to display an indication or alert regarding the received customer order, thereby requesting input from the user, such as receipt confirmation. After 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 602 (e.g., a picker) may pick up one or more items of the customer order and associate each picked item with the order identifier received from the one or more computer-implemented systems, such as by scanning the order identifier and a bar code on the item. In some embodiments, associating an item for a customer order with an order identifier may include physically printing the order identifier using a label printer or a barcode printer. The printed label or barcode 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, a worker who does not receive or has access to the initial order identifier may be able to scan the order identifier printed and affixed to the item.

In step 740, one or more computer implementations of system 100 may determine the expected final delivery destination and time for each of the items in the customer's order. As an example, the customer may order a bouquet of flowers to be delivered to a friend's house by 8 p.m. and a pack of batteries to be delivered to his parents' house within 24 hours. One or more computer implementations of system 100 may generate two separate order identifiers representing the two orders. Based on the expected final destination and time, each of the items may be directed to a storage unit and sorted based on the site and delivery wave.

In some embodiments, the sorting process may be a two-step sorting process. The first step may include sorting the picked items based on one or more sites to which the items may be directed. The sites may be determined based on, for example, the postal code of the expected final delivery destination of the items in the customer order. The second step may include sorting the picked items in the sites based on the waves to which the items may be sent for delivery. The waves may be determined based on, for example, expected delivery times or promised delivery times.

In step 750, one or more computer implementations of system 100 may send instructions to a user interface device to display instructions or alerts to sort the picked items for a customer order based on pre-designated storage spaces (e.g., storage cells 622-n of first packaging location 622) determined by one or more computer implementations of system 100. The pre-designated storage spaces may represent campsites to which the items may go for delivery. In some embodiments, one or more storage spaces may be assigned to a campsite. In some embodiments, a single storage cell may be assigned to multiple campsites. For example, storage cell 622-1 may be assigned to campsites 1 to 3, storage cell 622-2 may be assigned to campsites 4 to 6, and so on. If this first sorting is complete, the worker 602 may provide an indication to the system 100 via the user interface device 606. For example, if the storage cells corresponding to one or more campsites are full, the first sorting may be considered complete.

In step 760, each of the sorted objects may be packaged into a container, such as a tote 612. In some embodiments, the system 100 may send instructions to the user interface device to display instructions or alerts to transfer all objects in the storage cells 622-n to the tote 612. In some embodiments, the instructions for packaging may contain additional details, such as the order of packaging, so as to most efficiently place all objects in the tote 612. The worker 602 may provide instructions for packaging the tote 612 to the system 100 via the user interface device 606. In some embodiments, the tote 612 may include a tote identifier 612a, which may be a barcode, a label, a tag, an alphanumeric code, a quick response (QR) code, or the like. The worker 602 can scan the handbag identifier 612a to associate the handbag identifier 612a with all the items packed in the handbag.

In step 770, the handbag 612 may be transferred from the first packaging area to the second packaging area. The handbag 612 may be transferred by the transfer device 632, by a vehicle, or by a worker. In some embodiments, after the transfer, the transfer device 632 may provide an indication that the handbag 612 has arrived at the second packaging area 624. In some embodiments, the worker 602 in the second packaging area 624 may scan the handbag identifier 612a to provide an indication to the system 100 that the handbag 612 has arrived at the second packaging area.

In step 780, one or more computer implementations of system 100 may send instructions to user interface device 606 to display instructions or alerts to sort the objects in tote 612 in the second sort. For example, worker 602 may receive instructions or alerts to place the objects in tote 612 into one of storage cells 624 _n . Each of 624 _n may represent a particular wave of a particular camp. For example, storage cell 624-2 may be camp 1 wave 1, storage cell 624-2 may be camp 2 wave 1, and so on. In some embodiments, worker 602 may scan each object in tote 612 and receive an indication of which camp/wave the scanned object is assigned to. Worker 602 may provide an indication of the completion of the second sort via user interface device 606. In some embodiments, the second sorting is completed when each item in the handbag 612 has been scanned and sorted. In some other embodiments, the second sorting can be completed when one or more of the storage cells 624-n are full.

In step 790, one or more computer-implemented systems of the system 100 may send instructions to the user interface device to display instructions or alerts to place the selected objects from the cells 622-n into the tote 614, which may be associated with the corresponding storage cells. In some embodiments, the tote 614 container may be identified by a tote identifier 614a, which includes information identifying the campsite and the wave. The tote identifier 614a may be one of a barcode, a label, a tag, an alphanumeric code, a quick response (QR) code, or the like. The packaged items belonging to the customer order may be placed in the tote 614 without waiting for the remaining items of the same customer order to reduce idle time. The worker 602 may provide an indication of the completion of the second sorting via the user interface device 606. In some embodiments, the tote 614 may be dispatched to its corresponding camp for delivery. In some embodiments, the process 700 may proceed to step 560 of the process 500 described previously. In some embodiments, the tote 612 may have the same design as the tote 614. Alternatively, the tote 612 may have a different design than the tote 614.

In some embodiments, at one or more steps of process 700, the status of each of the objects in the order may be updated. The status of the objects may be accessed, stored, updated, or modified in one or more databases connected to system 100. The status of the object may include its location (e.g., the object is located in first packaging area 622, second packaging area 624, tote 612, tote 614, and/or left for delivery) and its history (e.g., a timestamp when the object was picked, sorted, and/or packaged). In some embodiments, worker 602 may update the status of time via user interface device 606.

Although the present disclosure has been illustrated and described with reference to specific embodiments of the present disclosure, it should be understood that the present disclosure may be practiced in other environments without modification. The foregoing description has been presented for illustrative purposes. The foregoing description is not exhaustive and is not limited to the precise form or embodiments disclosed. Modifications and adaptations will be apparent to those of ordinary skill in the art from consideration of this specification and practice of the disclosed embodiments. In addition, although the disclosed embodiments are described as being stored in memory, a person skilled in the art will appreciate that such embodiments may also be stored on other types of computer-readable media, such as secondary storage devices, such as hard disks or CD ROMs, or other forms of RAM or ROM, USB media, DVDs, Blu-rays, or other optical media.

Computer programs based on the written description and disclosed methods are within the skills 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, program sections or program modules can be designed with or by means of .Net Framework, .Net Compact Framework (and related languages, such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML/AJAX combination, XML, or HTML including Java applets.

Furthermore, although illustrative embodiments have been described herein, a person of ordinary skill in the art will understand the scope of any and all embodiments with equivalent elements, modifications, omissions, combinations (e.g., of aspects in various embodiments), adaptations, and/or changes based on this disclosure. Limitations in the claims should be interpreted broadly based on the language employed in the claims and are 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 modifications in any manner by reordering the steps and/or inserting or deleting steps. Therefore, it is intended that this specification and examples be considered illustrative only, with the true scope and spirit indicated by the full scope of the claims below and their equivalents.

700: Process

710, 720, 730, 740, 750, 760, 770, 780, 790: Steps

Claims (20)

A computer-implemented method for package delivery, the method comprising: receiving a customer order by a computer-implemented system; generating an order identifier based on the customer order using the computer-implemented system; scanning the order identifier using a user device; storing the scanned order identifier in a database; associating multiple items of the customer order with the order identifier; updating the database with information associated with the order identifier; determining an expected delivery destination and an expected delivery time for each item based on the order identifier; and determining an expected delivery destination and an expected delivery time for each item based on the expected delivery time of each item. The method comprises the steps of: determining a delivery node and a delivery wave of each object, a first container associated with the delivery node, and one or more second containers associated with the delivery node and the delivery wave based on the delivery destination and the expected delivery time, wherein: the delivery node corresponds to a logistics station associated with the expected delivery destination, the delivery wave corresponds to a time associated with one of a plurality of delivery shifts from the logistics station; the delivery node includes two or more sub-nodes, and each object in the first container is sorted based on the sub-nodes and the delivery wave during the sorting process; sorting; sending a first instruction to a first user device to sort each of the plurality of objects at a first location using a first sorting process based on an associated delivery node; receiving a first input related to the status of the first sorting process from the first user device; sending a second instruction to the first user device to place the first sorted object at the first location into the first container associated with the delivery node without considering the status of other objects in the plurality of objects; receiving a first input related to the status of each object in the first container from the first user device a second input related to the placement status of the first container; sending a third instruction to a second user device to sort each object in the first container using a second sorting process at a second location; sorting each object in the first container based on the subnode and the delivery wave in the second sorting process; and sending a fourth instruction to the second user device to deliver the second sorted objects in the one or more second containers to the intended delivery destination at a time associated with the delivery wave, without considering the status of other objects in the plurality of objects of the customer order. The method of claim 1 further comprises: in response to receiving the customer order, picking up at least one of the multiple objects in the customer order to perform the first sorting process and sending a fifth instruction to the first user device to place the at least one object picked up, without considering the status of other objects in the multiple objects. A method as described in claim 1, wherein the delivery node includes two or more sub-nodes, and in the second sorting process, each object in the first container is sorted based on the two or more sub-nodes and the delivery wave. A method as described in claim 3, wherein the one or more second containers are associated with the two or more child nodes and one of the delivery waves. The method as claimed in claim 1 further includes transferring the first container from the first position to the second position. The method of claim 1 further includes: sending a sixth instruction to the second user device to remove each object from the first container during the second sorting process; and sending a seventh instruction to the second user device to place the second sorted object into the one or more second containers based on the second sorting process. A method as claimed in claim 1, wherein the first user device is associated with the first location and the second user device is associated with the second location. The method of claim 1 further comprises using at least one of the first user device or the second user device to display a visual representation of packaging instructions. The method of claim 1 further includes updating the database of the computer implementation system with a status of each of the plurality of objects associated with one of the following: the first sorting process, the second sorting process, placement in the first container and the one or more second containers, transfer from the first location to the second location, or delivery. The method of claim 1 further includes generating a status update by the computer-implemented system in response to a customer inquiry related to the status of each of the plurality of objects. A computerized system for package delivery includes a memory storage for storing computer executable instructions; and one or more processors configured to execute the stored instructions to perform the following operations: receiving a customer order; generating an order identifier based on the customer order; scanning the order identifier using a user device; storing the scanned order identifier in a database; associating each of a plurality of items in the customer order with the order identifier; updating the database with information associated with the order identifier; determining each item based on the order identifier. The method comprises the steps of: determining an expected delivery destination and an expected delivery time of each object; determining a distribution node and a distribution wave of each object, a first container associated with the distribution node, and one or more second containers associated with the distribution node and the distribution wave based on the expected delivery destination and the expected delivery time of each object, wherein: the distribution node corresponds to a logistics station associated with the expected delivery destination, the distribution wave corresponds to a time associated with one of a plurality of delivery shifts from the logistics station; the distribution node includes two or more sub-nodes, and each object in the first container is distributed in a sub-node. The method further comprises: sorting the plurality of objects based on the subnode and the delivery wave in a sorting process; sending a first instruction to a first user device to sort each of the plurality of objects based on the delivery node using a first sorting process at a first location without considering the status of other objects in the plurality of objects; receiving a first input related to the status of the first sorting process from the first user device; sending a second instruction to the first user device to place the first sorted object into the first container at the first location; receiving a first input related to the status of each object in the first container from the first user device; a second input related to the placement status; sending a third instruction to a second user device to sort each object in the first container associated with the delivery wave using a second sorting process at a second location; sorting each object in the first container based on the subnode and the delivery wave in the second sorting process; and sending a fourth instruction to the second user device to deliver the second sorted objects in the one or more second containers to the intended delivery destination at a time associated with the delivery wave without considering the status of other objects in the plurality of objects of the customer order. In the system of claim 11, the one or more processors are further configured to: in response to receiving the customer order, pick up at least one of the multiple objects in the customer order to perform the first sorting process and send a fifth instruction to the first user device to place the at least one object picked up, without considering the status of other objects in the multiple objects. A system as described in claim 11, wherein the delivery node includes two or more sub-nodes, and in the second sorting process, each object in the first container is sorted based on the two or more sub-nodes and the delivery wave. A system as described in claim 13, wherein the one or more second containers are associated with the two or more child nodes and one of the delivery waves. In the system of claim 11, the one or more processors are further configured to: transfer the first container from the first location to the second location. In the system of claim 11, the one or more processors are further configured to: send a sixth instruction to the second user device to remove each object from the first container during the second sorting process; and send a seventh instruction to the second user device to place the second sorted objects into the one or more second containers based on the second sorting process. A system as described in claim 11, wherein the first user device is associated with the first location and the second user device is associated with the second location. In the system of claim 11, the one or more processors are further configured to: generate a visual representation of the packaged instructions on at least one of the first user device or the second user device. The system of claim 11, wherein the one or more processors are further configured to: update a database of the computerized system with a status of each of the plurality of objects associated with one of: the first sorting process, the second sorting process, placement in the first container and the one or more second containers, transfer from the first location to the second location, and delivery; and generate a status update by the computerized system in response to a customer inquiry associated with the status of the customer order. A computerized system for package delivery includes a memory storage for storing computer executable instructions; and one or more processors configured to execute the stored instructions to perform the following operations: receiving a customer order; generating an order identifier based on the customer order; scanning the order identifier using a user device; storing the scanned order identifier in a database; associating each of a plurality of items in the customer order with the order identifier; updating the database with information associated with the order identifier; determining an expected delivery destination and an expected delivery time for each item based on the order identifier; and determining the expected delivery time for each item based on the order identifier. The method comprises the steps of: determining a distribution node and a distribution wave of each object, a first container associated with the distribution node, and one or more second containers associated with the distribution node and the distribution wave, respectively, based on the expected delivery destination and the expected delivery time of the object, wherein: the distribution node corresponds to a logistics station associated with the expected delivery destination, the distribution wave corresponds to a time associated with one of a plurality of delivery shifts from the logistics station; the distribution node includes two or more sub-nodes, and each object in the first container is sorted based on the sub-nodes and the distribution wave in a sorting process; and the first sorting process is used at a first location based on the first container. A first instruction for sorting each of the plurality of objects at the delivery node is sent to a first user device without considering the status of other objects in the plurality of objects; a first input related to the status of the first sorting process is received from the first user device; a second instruction for placing the first sorted object into the first container at the first location is sent to the first user device; a second input related to the placement status of each object in the first container is received from the first user device; the first container is transported from the first location to a second location; and the first container is sorted using a second sorting process at the second location sending a third instruction of each object associated with the delivery wave in the first container to the second user device; sorting each object in the first container based on the subnode and the delivery wave in the second sorting process; and sending a fourth instruction of placing the second sorted objects into the one or more second containers based on the second sorting process to the second user device; and sending a fifth instruction of delivering the second sorted objects in the one or more second containers to the intended delivery destination at a time associated with the delivery wave to the second user device without considering the status of other objects in the multiple objects of the customer order.