TWI773055B - Computerized systems for package delivery - Google Patents

Abstract

Embodiments of the present disclosure include computer-implemented systems and methods for dynamic package priority. The system may include at least one processor configured to receive, via a network, a first electronic customer order for a first item, the first order comprising an identifier of the first item and assign a first shipping metric to the first customer order. The system may be configured to transmit an instruction to a mobile device to acquire the first item for the first order, and to receive, via the network, a second electronic customer order for the first item, the second order comprising the identifier of the first item. The system may be configured to assign a second shipping metric to the second customer order. The system may be configured to compare the first shipping metric to the second shipping metric to determine priority for the first customer order and the second customer order. The system may be configured to send an instruction to an order tracking system to reassign the acquired first item to the second order, based on determining that the second shipping metric should have a higher priority than the first shipping metric. The system may be configured to transmit an indication of the reassignment to an output device.

Description

Computerized system for package delivery

This application is a continuation-in-part of US Application No. 16/416,909, filed May 20, 2019, the contents of which are incorporated herein by reference in their entirety.

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

Fulfillment centers (FCs) enable e-commerce merchants to outsource warehousing and shipping. Inventory management in FC is a necessary part of fostering the best customer experience for online shoppers. Inventory management may include several steps within the scope of receiving merchandise from sellers, stowage of received merchandise for easy picking access, packing items, validating 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 shoe Inefficient practice when placing orders. Delays in package delivery can lead to unhappy customers and, in some cases, can impact a business's costs and profitability.

With the development and widespread acceptance of e-commerce, Internet shopping provides a one-stop shop for all shopping needs including food, furniture, electronics, clothes, books, and more. Each online order typically includes a combination of items of widely varying categories. Although in current 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 parts of the FC based on category, and packers may have to wait for a picker to pick all items of an order before they can be packed. This can result in delays in subsequent steps in the packaging and delivery of packages to customers, which delays the throughput of the system and the efficiency of the computerized systems that control the shipping process.

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

Additionally, the current existing FC employs a team of workers to ensure smooth 24 hour operation. One of the technical challenges in a warehouse may be quickly communicating information to workers on the ground, such as urgent customer orders, priority shipping, and the like. current logistics And inventory management systems lack the ability to efficiently account for expected or unexpected urgency in customer orders, potentially resulting in customer dissatisfaction and higher associated inventory costs.

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

One aspect of the present disclosure relates to a computer-implemented system for package delivery. The system can include at least one processor configured to receive, via a network, a first electronic customer order for an item, the first electronic customer order including an identifier for the item. At least one processor can be configured to assign a first shipping metric to the first electronic customer order. The at least one processor may be configured to transmit to the mobile device an instruction to obtain an item of the first electronic customer order. The at least one processor may be configured to receive a scan indicating a product identifier of an item for which the first item has been acquired. The at least one processor can be configured to identify a second electronic customer order for the item. The at least one processor may be configured to compare the first shipping metric with the shipping metric of the second electronic customer order for the item to determine a prioritization of the first electronic customer order and the second electronic customer order. At least one processor may be configured to transmit an indication of the determined priority order to the output device.

Another aspect of the present disclosure relates to a computer-implemented system for package delivery. The system can include at least one processor configured to: receive, via a network, a first electronic customer order for a first item, the first order including an identifier for the first item; and assign a first shipping metric to the first customer order. The at least one processor can be configured to: transmit to the mobile device an instruction to obtain the first item of the first order; and A second electronic customer order for the first item is received via the network, the second order including an identifier for the first item. The at least one processor may be configured to assign a second shipping metric to the second customer order. At least one processor may be configured to compare the first shipping metric with the second shipping metric to determine a priority order for the first customer order and the second customer order. The at least one processor may be configured to send an instruction to the order tracking system to reassign the acquired first item to the second order based on a determination that the second shipping metric should have a higher priority than the first shipping metric. At least one processor can be configured to transmit the reassigned indication to the output device.

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

100: Internet

101: Shipping Authorization Technical System

102A, 107A, 107B, 107C, 119A, 119B, 119C: Mobile Devices

102B: Computer

103: External Front-End Systems

105: Internal Front-End Systems

107: Transportation Systems

109: Seller Portal

111: Shipping and Order Tracking System

113: Execution optimization system

115: Fulfill the communication gateway

117: Supply Chain Management Systems

119: Warehouse Management System

121A, 121B, 121C: 3rd Party Fulfillment Systems

123: Fulfillment Center Authorization System

125: Labor Management System

200: Fulfillment Center

201, 222: Truck

202A, 202B, 208: Objects

203: Inbound area

205: Buffer

206: Forklift

207: Unloading area

209: Picking area

210: Storage Unit

211: Packaging area

213: Hub Area

214: Transport Agency

215: Camp Area

216: Wall

218, 220: Package

224A, 224B: Delivery workers

226: Car

300: Computer Implementation System

301: Confluence Worker

302: User Interface Device

305: Order Identifier

305A, 305B, 305C: Sub-order identifiers

320: first storage location

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

340: Camp

342: Storage space

350: Container

355: container identifier

360, 360_1~360_4: container carrier

400: Process

410, 420, 430, 440, 450, 460, 480, 505, 510, 515, 520, 525, 530, 535, 540, 545, 550, 555, 560, 565, 650, 810, 820, 830, 840, 850, 860: Steps

500, 800: method

600: Operation

610: First Electronic Customer Order

615:Identifier associated object

620: Second Electronic Customer Order

630: Third Electronic Customer Order

640: Fourth Electronic Customer Order

660: Packaged articles

705, 710, 715, 720, 725: line

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

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

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

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

FIG. 1E depicts objects including items from a virtual shopping cart, consistent with disclosed embodiments Items and information about purchasing and shipping, as well as a sample order page with interactive user interface elements.

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

3 is an illustration of an exemplary computerized singulated package delivery system configured to utilize the disclosed computerized system, consistent with disclosed embodiments.

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

5 is a schematic diagram of an exemplary process flow for dynamic packaging prioritization, consistent with disclosed embodiments.

FIG. 6 illustrates exemplary dynamic wrapping prioritization operations consistent with disclosed embodiments.

FIG. 7 illustrates an example of dynamic packing prioritization and corresponding tasks performed, consistent with disclosed embodiments.

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

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference 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 implementations are possible. For example, components and steps shown in the figures may be replaced, added, or modified, and the description described herein may be modified by substituting, reordering, removing steps, or adding steps to the disclosed methods Illustrative method. Therefore, the following detailed description The description is not limited to the disclosed embodiments and examples. Rather, the proper scope of the invention is defined by the appended claims.

Embodiments of the present disclosure relate to devices configured to reduce cycle time and increase the 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. system and method.

Referring to FIG. 1A, depicted is a schematic block diagram 100 illustrating an exemplary embodiment of a network including a computerized system for implementing communications for shipping, transportation, and logistics operations. As shown in FIG. 1A, system 100 may include various systems, each of which may be connected to each other via one or more networks. The depicted system includes shipping authority technology (SAT) system 101, external front end system 103, internal front end system 105, shipping system 107, mobile device 107A, mobile device 107B, and mobile device 107C, seller portal 109, shipping and Order tracking (shipment and order tracking; SOT) system 111, fulfillment optimization (fulfillment optimization; FO) system 113, fulfillment messaging gateway (fulfillment messaging gateway; FMG) 115, supply chain management (supply chain management; SCM) system 117, warehouse management system 119, mobile device 119A, mobile device 119B, and mobile device 119C (depicted as inside fulfillment center (FC) 200), 3rd party fulfillment system 121A, 3rd party fulfillment system 121B, and 3rd party fulfillment System 121C, fulfillment center authorization (FC Auth) 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 can determine if the order is past its Promised Delivery Date (PDD) and can take appropriate action, including initiating New orders, reshipment of items in undelivered orders, cancellation of undelivered orders, initiation of contact with ordering customers, or the like. The SAT system 101 may also monitor other data, including outputs (such as the number of packages shipped during a particular time period) and inputs (such as the number of empty cartons received for shipment). SAT system 101 may also act as a gateway between different devices in system 100, enabling communication between devices such as external front-end system 103 and FO system 113 (eg, using store-and-forward or other techniques).

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

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

With the exemplary steps shown in Figure 1B, Figure 1C, Figure 1D, and Figure 1E This set of steps will help describe some of the operations of the external front-end system 103. External front-end systems 103 may receive information from systems or devices in network 100 for presentation and/or display. For example, the external front-end system 103 may host or provide one or more web pages, including a search results page (SRP) (eg, FIG. 1B ), a single detail page (Single Detail Page; SDP) (eg, FIG. 1C ), A shopping cart page (eg, FIG. 1D ), or an order page (eg, FIG. 1E ). A user device (eg, using mobile device 102A or computer 102B) can navigate to external front-end system 103 and request a search by entering information into the search box. External front-end systems 103 may request information from one or more systems in network 100 . For example, the external front end system 103 may request the FO system 113 for results that satisfy the search request. The external front end system 103 may also request and receive (from the FO system 113) a Promised Delivery Date or "PDD" for each product returned in the search results. In some embodiments, the PDD represents an estimate of when the package will arrive at the user's desired location if ordered within a certain time period (eg, before the end of the day (11:59 PM)). (PDD is discussed further below with respect to the FO system 113.)

The external front-end system 103 may prepare the SRP based on the information (eg, FIG. 1B ). The SRP may contain information to satisfy the search request. For example, this may include images of products that satisfy the search request. The SRP may also contain 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 (eg, via a network) to the requesting user device.

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

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

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 a "put in cart" button on the SDP. This adds the product to the shopping cart associated with the user. The user device may transmit this request to add a product to the shopping cart to the external front end system 103 .

The external front end system 103 may generate a shopping cart page (eg, Figure ID). In some embodiments, the shopping cart page lists products that the user has added to a virtual "shopping cart." A user device may request a shopping cart page by clicking on or otherwise interacting with an icon on an SRP, SDP, or other page. In some embodiments, the shopping cart page may list all the products that the user has added to the shopping cart, along with information about the products in the shopping cart (such as quantity of each product, item price, price per product based on the associated quantity), information about the PDD, delivery method, shipping cost, user interface elements for modifying products in the cart (e.g., delete or modify quantity), for Options to order additional products or set up recurring delivery of products, options to set up interest payments, user interface elements to advance to purchase, or the like. A user at the user device may click on or otherwise interact with a user interface element (eg, a button that says "Buy Now") to initiate a purchase of the products in the shopping cart. Buy. After doing so, the user device may transmit this request to initiate a purchase to the external front end system 103 .

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

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

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

In some embodiments, internal front end system 105 may be implemented as a computer system that enables internal users (eg, employees of an organization that owns, operates, or leases network 100 ) to interact with one or more systems in 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 internal front end system 105 may be implemented to enable the user to view diagnostic and statistical information about the order, modify item information, or review Web server for order-related statistics. For example, the internal front end system 105 may be implemented as a computer or computer running software such as an Apache HTTP server, Microsoft Internet Information Services (IIS), NGINX, or the like. In other embodiments, the internal front end system 105 may operate designed to receive and process requests from the devices depicted in the network 100 (as well as other devices not depicted), from databases and other data repositories based on their requests Customized web server software that obtains information and provides responses to 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 analytics system, an order monitoring system, or the like. In one aspect, internal front-end system 105 may include one or more of these systems, while in another aspect, internal front-end system 105 may include an interface to one or more of these systems (eg, , server-to-server, database-to-database, or other network connection).

In some embodiments, the transportation system 107 may be implemented as a computer system that enables communication between the devices in the network 100 and the mobile devices 107A to 107C. In some embodiments, the transportation system 107 may be from one or more mobile devices 107A to mobile devices 107C (eg, mobile phones, smartphones, PDAs, or the like) ) to receive information. For example, in some embodiments, mobile devices 107A-107C may comprise devices operated by delivery workers. Delivery workers, who may be permanent, temporary, or shift employees, may utilize mobile devices 107A-107C to effect 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 (eg, in the back of a truck or in the package's crate), scan or otherwise capture an identifier (eg, a barcode) on the package using a mobile device , image, text string, RFID tag, or the like) and deliver the package (eg, by leaving it at the front door, leaving it to a guard, giving it to the recipient, or the like) . In some embodiments, the delivery worker may capture a photo of the package and/or may obtain a signature. The mobile device may send communications to the transportation system 107 including information about the delivery including, for example, time, date, GPS location, photo, identifier associated with the delivery worker, identifier associated with the mobile device, or similar. Transportation system 107 may store this data in a database (not depicted) for access by other systems in network 100 . In some embodiments, the shipping system 107 may use this information to prepare and send tracking data to other systems, indicating the location of a particular package.

In some embodiments, some users may use one type of mobile device (eg, permanent workers may use specialized PDAs with customized hardware such as barcode scanners, styluses, and other devices), while others use Alternatively, other types of mobile devices may be used (eg, off-the-shelf mobile phones and/or smart phones may be utilized by temporary workers or shift workers).

In some embodiments, the transport system 107 may allow the user to communicate with each device Associated. For example, the transportation system 107 may store users (represented by, for example, user identifiers, employee identifiers, or telephone numbers) and mobile devices (represented by, for example, International Mobile Equipment Identity (IMEI), International Mobile Equipment Identifier (International Mobile Subscription Identifier; IMSI), phone number, Universal Unique Identifier (UUID) or Globally Unique Identifier (Globally Unique Identifier; GUID) representation). The transportation system 107 may use this relationship in conjunction with the data received at the time of delivery to analyze the data stored in the database to determine, among other things, the location of the worker, the efficiency of the worker, or the speed of the worker.

In some embodiments, the seller portal 109 may be implemented as a computer system that enables sellers or other external entities to electronically communicate with other aspects of order-related information. 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 the seller wishes to sell via system 100 .

In some embodiments, shipping and order tracking system 111 may be implemented as a computerized system that receives, stores, and forwards information about the location of packages ordered by customers (eg, by users 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 the shipping company that delivers the package ordered by the customer.

In some embodiments, shipping and order tracking system 111 may request and store information from the systems depicted in network 100 . For example, shipping and order tracking system 111 may request information from shipping system 107 . As discussed above, the transportation system 107 may travel from one or more mobile devices 107A associated with one or more of the users (eg, delivery workers) or vehicles (eg, delivery trucks) to the line A mobile device 107C (eg, a mobile phone, smart phone, PDA, or the like) receives the information. In some embodiments, shipping and order tracking system 111 may also request information from warehouse management system (WMS) 119 to determine the location of individual packages within a fulfillment center (eg, fulfillment center 200 ). Shipping and order tracking system 111 may request data from one or more of shipping system 107 or WMS 119, process the data upon request, and present the data to devices (eg, user device 102A and user device 102B).

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

The FO system 113 may also calculate the corresponding PDD (Promised Delivery Date) 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 (eg, how many times the product has been ordered over a period of time), expected demand for the product (eg, forecasting upcoming demand for the product) how many customers will order the product during the upcoming period), network-wide past demand indicating how many products have been ordered during the period, network-wide expected demand indicating how many products are expected to be ordered during the upcoming period, one or more counts of products stored in each fulfillment center 200, Which fulfillment center stores each product, anticipated or current orders for a product, or the like.

In some embodiments, the FO system 113 may periodically (eg, hourly) determine the PDD for each product and store it in a database for retrieval or sending to other systems (eg, external front-end system 103 , SAT system 101 ) , Shipping and Order Tracking System 111). In other embodiments, FO system 113 may receive electronic requests from one or more systems (eg, external front-end system 103, SAT system 101, shipping and order tracking system 111) and compute PDDs 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 ), transfers the data in the communications Convert to another format and forward the data in the converted format to other systems, such as WMS 119 or 3rd party fulfillment system 121A, 3rd party fulfillment system 121B or 3rd party fulfillment system 121C, and vice versa.

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

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

In some embodiments, WMS 119 may store data that associates one or more devices (eg, device 107A to device 107C or device 119A to device 119C) with one or more users (the one or more users and the network 100 associated) associated information. For example, in some cases a user (such as a part-time employee or a full-time employee) may be associated with a mobile device because the user owns the mobile device (eg, the mobile device is a smartphone). In other cases, the user may be associated with the mobile device because the user temporarily holds the mobile device (eg, the user gets 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, WMS 119 may maintain a work log for each user associated with network 100 . For example, the WMS 119 may store information associated with each employee, including any specified process (eg, unloading from a truck, picking an item from a pick area, rebin wall work, packing an item), use of person identifier, location (eg, floor or zone in fulfillment center 200), by employee via Number of units moved by the system (eg, number of items picked, number of items packed), identifiers associated with devices (eg, devices 119A to 119C), or the like. In some embodiments, WMS 119 may receive registration 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 through 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 not be otherwise available for storage in fulfillment center 200 . 3PL systems 121A-3PL systems 121C may be configured to receive orders from FO system 113 (eg, via FMG 115 ) and may provide products and/or services (eg, delivery or installation) directly to customers.

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

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

The particular configuration depicted in Figure 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 particular configuration. Indeed, 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 intranet, a Wide-Area Network; WAN), Metropolitan-Area Network (MAN), IEEE 802.11a/b/g/n compliant wireless network, leased line, 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 fulfillment center 200 . Fulfillment center 200 is an example of a physical location that stores items for shipping to customers at the time of ordering. Fulfillment center (FC) 200 may be divided into multiple zones, each of which is depicted in FIG. 2 . In some embodiments, these "zones" can be thought of as virtual divisions between the different stages of the process of receiving, storing, retrieving, and shipping items. Thus, although "zones" are depicted in Figure 2, other zone divisions are possible, and in some embodiments zones in Figure 2 may be omitted, duplicated, or modified.

Inbound zone 203 represents the FC 200's self-desired use of the network from Figure 1A 100 The area where the item is received by the seller who sold the product. For example, a seller may use truck 201 to deliver item 202A and item 202B. Item 202A may represent a single item large enough to occupy its own shipping pallet, while item 202B may represent a collection of items stacked together on the same pallet to save space.

Workers will receive the item in the inbound area 203 and can use a computer system (not depicted) to check the item for damage and correctness as appropriate. For example, a worker may use a computer system to compare the quantity of items 202A and 202B with the ordered quantity of items. If the quantities do not match, the worker may reject one or more of item 202A or item 202B. If the quantities do match, the worker can move those items to the buffer zone 205 (using, for example, a trolley, walker, forklift, or manually). Buffer 205 may be a temporary storage area for items that currently do not need to be in the pick area (eg, due to the presence of a high enough number of items in the pick area to meet forecast demand). In some embodiments, forklift 206 operates to move items around buffer zone 205 and between inbound area 203 and unload area 207 . If item 202A or item 202B in the pick area is required (eg, due to forecast demand), a forklift may move item 202A or item 202B to unload area 207 .

The unloading area 207 may be an area of the FC 200 where items are stored prior to being moved to the picking area 209 . Workers assigned to picking tasks ("pickers") can approach items 202A and 202B in the unloading area, use a mobile device (eg, device 119B) to scan the barcodes in the picking area, and scan the barcodes associated with items 202A and 202B. The barcode associated with item 202B. The picker may then take the item to the picking area 209 (eg, by placing the item on a cart or carrying the item).

Picking area 209 may be an area of FC 200 where items 208 are stored on storage unit 210 . In some embodiments, the storage unit 210 may include physical shelves, books one or more of a shelf, box, handbag, refrigerator, freezer, cold storage area, or the like. In some embodiments, the picking area 209 may be organized into multiple floors. In some embodiments, workers or machines can move items into the picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyors, carts, walkers, carts, automated robots or devices, or manually . For example, a picker may place items 202A and 202B on a trolley or cart in unloading area 207 and walk items 202A and 202B to picking area 209 .

Pickers may receive instructions to place (or "stow") items at specific points in pick area 209 , such as specific spaces on storage unit 210 . For example, a picker may use a mobile device (eg, device 119B) to scan item 202A. The device may indicate to the picker where the item 202A should be stowed, eg, using a system of indicating aisles, racks, and locations. The device may then prompt the picker to scan the barcode at the location prior to stowage of the item 202A at that location. The device may send data (eg, via a wireless network) to a computer system such as WMS 119 in Figure 1A, indicating that item 202A has been stowed at that 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 items 208 from storage unit 210 . The picker may retrieve the item 208 , scan the barcode on the item 208 , and place the item 208 on the transport mechanism 214 . Although the transport mechanism 214 is shown as a slide, in some embodiments, the transport mechanism may be implemented as one or more of a conveyor belt, elevator, cart, forklift, walker, dolly, or the like. Object 208 may then arrive at packing area 211 .

The packing area 211 may be the area of the FC 200 that receives items from the picking area 209 and packs the items into boxes or bags for eventual shipping to customers. in packaging In zone 211, the worker assigned to receive the item ("confluent worker") will receive the item 208 from the picking zone 209 and determine which order the item 208 corresponds to. For example, a confluence worker may use a device such as computer 119C to scan the barcode on item 208. Computer 119C can visually indicate to which order item 208 is associated. This may include, for example, spaces or "cells" on the wall 216 that correspond to orders. Once the order is complete (eg, since the cell contains all of the items for that order), the confluence worker can instruct the packer (or "packer") that the order is complete. A packer can retrieve items from the cell and place the items in boxes or bags for shipping. The packer may then send the box or package to the hub zone 213, eg, via a forklift, cart, dolly, cart, conveyor, manually or otherwise.

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

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

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

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

3 shows an exemplary unitary package delivery system. As used herein, the term "singularization" refers to a single shipment of items of a customer order that includes multiple items without waiting for the customer order to be fully fulfilled before shipping. Delivery by a single package can have numerous advantages over existing systems for package delivery. Delivery by a single package may have some or all of the advantages discussed herein, as well as other advantages.

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

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

iii. Improved Traceability - As shown in FIG. 3, in a unitary package delivery system 300, a worker (eg, worker 301 ) can scan and 208) the associated barcode (eg, order identifier 305 and/or location identifier). Additionally, the barcode can be scanned periodically during the process or upon receipt of a prompt. Information recorded, eg, by scanning, may be stored in the database of the system 100, allowing the package to be tracked as it undergoes processing. The barcode of the container or tote can also be scanned to provide information associated with the location of the items contained in the container during the process of picking, sorting, packing, shipping, etc., allowing container and package traceability.

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

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

vi. Reduction of "load-ready" time - In existing package delivery and delivery systems, employees such as workers, drivers, loaders, janitors, floor inspectors, etc. may spend a significant amount of their time at the beginning of a shift or work period For example, make sure to load all the items that belong to the order. Such a system may be inefficient in utilizing resources such as manpower and time, both of which may increase operating costs and affect throughput. The singulation of items can reduce load preparation time as employees load containers or container carriers, such as handbags, 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 as items are placed in large standardized totes or containers based on the delivery route. Additionally, items remain in standardized containers until delivery, minimizing damage or misplacement due to disposal. A large standardized tote or container allows the loader to follow easy instructions to load the truck, and allows the driver to easily understand what is on the map and deliver the order more efficiently.

In some embodiments, the system 100 may be configured to receive customer orders. A customer order can include multiple items. In some embodiments, each customer order may include multiple sub-orders, each of which may include multiple items. For example, a customer order may include three sub-orders. The first sub-order may be a rush order for toothpaste, toothbrush, and mouthwash, the second sub-order may include regular deliveries of cheese, crackers, and potato chips, and the third sub-order may include delayed deliveries of beverages. System 100 can receive customer orders and generate order identifiers 305 associated with each of the ordered items. In some embodiments, the system 100 may generate a unique A child order identifier (eg, child order identifier 305A for the first child order, child order identifier 305B for the second child order, and child order identifier 305C for the third child order).

In some embodiments, the order identifier 305 and sub-order identifier (eg, 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 item to be delivered, the destination of the item to be delivered. In some embodiments, the order identifier 305 may also contain information about several sub-orders within a single order. System 100 may send an indication to user interface device 302 to indicate that the order includes a number of sub-orders, and the urgency associated with each sub-order. Pickers can fulfill orders or sub-orders accordingly.

In some embodiments, one or more pickers may receive indications related to the urgency of sub-orders when retrieving items from other customer orders. The picker may retrieve items of the urgent sub-order based on their current location within the picking area 209 and forward the items to the packing 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 can retrieve the toothbrush and a picker in or near the apparel section A clerk can retrieve the pair of socks, resulting in improved pick density. Once the container or tote is full, the item can be transported to the packing 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, system 100 may send an instruction to a user device (eg, smartphone 119B, or computer 119C) such that the device instructs the picker to print order identifier 305 . In some embodiments, the user device may include a configured Handheld devices such as PDAs marked with print. Alternatively, system 100 may include a printing device (not depicted) such as an indicia printer, ink jet printer, or laser printer. The printing device may be configured to receive instructions to print indicia, instructions, memos, or the like from one of the computer-implemented systems of system 100 . The instructions may further include requesting the picker to associate the printed order identifier 305 with the item of the customer order, such as by affixing the printed order identifier 305 to the picked item 208 . In some embodiments, the system 100 may be configured to electronically associate the order identifier 305 with the items of the customer order. For example, the system 100 can update a database that includes information related to all incoming customer orders.

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

In some embodiments, 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 the customer order, such as the number of items ordered, the urgency of delivery of the ordered items, the destination location of the items to be delivered, and the like. In some embodiments, the user interface display may be a visual display or an audiovisual display. For example, if the order is "urgent", the user interface device 302 can receive an audiovisual 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 acknowledge receipt of the notification. In some embodiments, user interface device 302 may include data recording capabilities (such as barcode scanning, optical character readers, etc.) to record order identifier 305 information. User interface device 302 may be configured to temporarily store recorded information and later upload to a database of one of the computer-implemented systems of system 100 . In some embodiments, the user interface device 302 may automatically upload the logged 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 item 208 via an interactive element of the user interface display. For example, one of the computer-implemented systems of system 100 (eg, WMS 119 , SCM 117 , or SAT 101 ) may generate a display to user interface device 302 indicating to the user to begin reviewing the order identifier associated with object 208 305 instructions. Reviewing the order identifier 305 may include determining the final destination of the delivery of the item 208 by, for example, scanning or reading the order identifier 305 . For example, scanning an order identifier (eg, a barcode) using a barcode scanning device can 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 Wait. In some embodiments, a customer order may include several sub-orders and each sub-order may further include several items. It should be appreciated that item 208 may include a package containing one or more items of a customer order.

After determining the final destination for the delivery of the item 208, the merge worker 301 may place the item 208 in the first storage location 320 based on the determined final destination. 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 merging wall, a storage unit, a storage rack with cells, or a cabinet. Other tissue storage means may also be used.

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

In some embodiments, each storage cell 324 may be associated with a camp 340 . In some embodiments, camp 340 may be an on-site storage or sorting facility within the premises of FC 200 . In some embodiments, camp 340 may be an off-site storage or sorting facility at a remote location. Each storage cell can be identified using a camp identifier 324 (eg, storage cell 324_1 or storage cell 324_2) is associated with the corresponding camp. Camp identifiers may include, but are not limited to, markings, barcodes, numbers, or labels. Although only a limited number of storage cells 324 are shown, it should be appreciated 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 via an instruction to place the object 208 in the corresponding storage cell 324 based on determining the destination location of the object 208 . For example, based on the customer order, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may determine the camp to which item 208 is likely to be directed. Confluence worker 301 may place object 208 in corresponding storage cell 324 .

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

In some embodiments, if camp 340 is an on-site facility, the items may be transported using transportation means such as, for example, conveyor belts, forklifts, pallets, dollies, or in handbags. For off-site facilities, delivery trucks or similar may be used to transport items.

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

In some embodiments, campsite 340 may include one or more storage spaces 342 . Storage space 342 may include, but is not limited to, walls with storage cells, storage cells, storage shelves with cells, or cabinets. Other tissue 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 the item 208 .

Workers at camp 340 may receive one or more items 208 from storage location 320 . A worker (eg, a sorter) may review the order identifier 305 associated with the picked item 208 . In some embodiments, the worker may receive a notification on the user interface device 302 to review the order identifier 305 . For example, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may generate a start review order associated with object 208 to the worker to be displayed on user interface device 302 An indication of the identifier 305 . Reviewing the order identifier 305 may include determining the final destination of the item 208 .

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

In some embodiments, the user interface device 302 may notify the worker via 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 the customer order, one of the computer-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may determine storage cell 344 to which object 208 may lead. Workers can use The instruction of the user interface device 302 places the object 208 in the corresponding storage cell 324 .

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

In some embodiments, items may be sorted into storage cells 344 based on the determined sub-route of the final destination for delivery without regard to the status of the order or other items of the order that may be associated with the item middle. In current existing delivery systems, a sorter may wait to receive all items of an order before preparing the order for delivery. In contrast, in the disclosed embodiments, each item may be treated as an individual order and sorted based on the determined sub-route for delivery without regard to the status of the other items of the order . This may reduce the idle time of the sorters in the camp area, thereby increasing 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 and the corresponding storage cell 344 in which the object 208 is placed. For example, the instruction may include a request to scan the order identifier 305 and the sub-route identifier to establish an association between the item 208 and the sub-route for delivery. The information related to the order identifier 305 of the placed item and the sub-route identifier of the storage cell 344 in which the item was placed may be automatically updated to data including information related to the customer order and the delivery schedule of the customer order library.

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a handbag). All items of storage cell 344 (eg, item 208 ) may be placed in container 350 . In some embodiments, container identification may be used symbol 355 to identify container 350. The container identifier 355 may include information associated with the sub-route that includes the sub-route identifier. In some embodiments, the container identifier 355 may contain information related to camps and sub-routes. For example, the container identifier may include the indicia CS3_SR1, where CS indicates the starting camp and SR indicates the designated sub-route for delivering the items in the container. The container identifier 355 may include, but is not limited to, a mark, barcode, number, or label.

In some embodiments, the user interface device 302 may be configured to display a notification or indication 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-implemented systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may determine a container 350 in which item 208 may be placed. The worker may place the object 208 in the corresponding container 350 based on the instructions from the user interface device 302 .

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

In some embodiments, one or more containers 350 may be loaded on a delivery vehicle (eg, delivery truck 201 ) for delivery to a customer. Containers 350 may be deployed in delivery truck 201 based on sub-routes. For example, a package or item (eg, item 208 ) to be delivered at a destination closer to the start of the sub-route may be placed closer to the entry and exit Doors are placed so delivery workers have direct access to packages. In some embodiments, the container 350 containing the rush order may be placed closer to the access door to enable quick access to the package. In some embodiments, sub-routes may be adjusted based on the type and urgency or PDD of the order. In some embodiments, both the sub-route and the configuration of the containers in the delivery truck 201 may be adjusted based on customer orders and PDDs.

The container 350 may be placed on the container carrier 360 prior to being loaded into the delivery truck 201 . The container carrier 360 may include a cart, dolly, cage, basket, or the like. In some embodiments, the container carrier 360 may include an identifier, such as a barcode, label, or label. In some embodiments, the user interface device 302 may notify the delivery worker or truck loader via instructions to place the container 350 on the delivery truck 201 based on a predetermined configuration. For example, based on the PDD, one of the computer-implemented systems of system 100 (eg, transportation system 107 ) may determine the configuration of container 350 on container carrier 360 or the configuration of one or more container carriers 360 on delivery truck 201 . A 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 (eg, the transport 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 presentation 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 load the delivery truck 201 An instruction to begin driving on the sub-route is then received, generated by one of the computer-implemented systems of system 100, such as transportation system 107. Delivery workers may receive instructions via a user interface display on user interface device 302 .

Referring now to FIG. 4, an illustrative flow diagram of a process 400 for unitary package delivery is shown, consistent with disclosed embodiments. The process may include: receiving a customer order; generating an order identifier based on the customer order; determining an expected final destination of items of the customer order; picking at least some of the items of the customer order; sorting the picked items based on a two-step sorting process pick up the item; load the picked item of the customer order onto a delivery truck without waiting for the remaining items of the customer order; and deliver the picked item to the customer.

Overall package delivery efficiency is a measure that depends on the efficiency of each step in the process of package delivery. Shipping a package from an FC to a customer to fulfill an order typically involves multiple steps, and most of these steps must be performed in a linear sequential order. For example, picking may be prior to receiving an order and generating an order identifier, sorting may be prior to picking, packaging may be prior to sorting, loading items onto a delivery truck may be prior to packaging, and the like. In other words, each step of the process is initiated by the completion of the previous step. In such a process flow, the overall efficiency of the process is determined by the efficiency at each step. The overall efficiency can be improved by increasing the efficiency of each step or by increasing the efficiency of at least one step while maintaining the efficiency of the other steps. As discussed above, "singularization" herein refers to a single shipment of an item of a customer order that includes multiple items without waiting for the customer order to be fully fulfilled prior to shipment, which can be achieved by reducing cycle time and reducing in-process The spare time of the employees involved in improving the efficiency of package delivery. In some embodiments, one or more steps of process 400 may be used by one or more user interface devices (eg, each user interface device may be used by a different area of FC 200 ) operator operation) is executed.

In step 410, one or more computer-implemented systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) may receive customer orders. A customer order can include multiple items. In some embodiments, a customer order may include multiple sub-orders and each sub-order may include multiple items. One or more computer-implemented systems of system 100 may be configured to review customer orders and identifying information, such as the total number of items ordered, a description of each of the items ordered, the time of delivery requested, the final destination etc. In some embodiments, one or more computer-implemented systems of system 100 may determine a promised delivery date or promised delivery time for a customer order based at least on the requested delivery time. For example, for a rush order request from a customer, the system can determine a 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 the promised delivery date and time for each of the items of the customer order. For example, a customer order may include some items for urgent delivery and 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 (eg, WMS 119, SCM 117, SAT system 101) may receive multiple customer orders. Each of the customer orders may include multiple items. One or more computer-implemented systems of system 100 may be configured to review and identify common items between multiple customer orders. The user interface device may be configured to display an indication of the common object, thereby requesting input from the user, such as receipt of confirmation. The instruction may include information related to a description of the item, the quantity of the item ordered, and the like. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders include a common item, such as a bottle of water. Workers (eg, pickers) can load Set to receive instructions to pick up 50 bottles of water. The implementation of this approach can improve picking efficiency and the overall efficiency of the process.

In step 420, one or more computer-implemented systems of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifiers may include barcodes, labels, labels, alphanumeric codes, quick response (QR) codes, or the like. The order identifier may be a machine-readable optical indicia containing information about the customer's order. The information contained in the order identifier may include, but is not limited to, the final destination of the order, the total number of items in the customer's order, the type of delivery requested, customer information, promised delivery date and promised delivery time, and the like. In some embodiments, the system that generates the order identifier may determine storage locations (eg, camp area 215, hub area 213) and delivery routes to which 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 may determine the storage location of the item in the customer order, and based on the street or district identified in the final destination, the system may determine for delivery of the item in the customer order route.

After scanning or reading the order identifier, eg, using a user interface device (eg, user interface device 302) 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 time remaining to fulfill the order.

In step 430, one or more computer-implemented systems of system 100 may instruct the user interface device to display instructions for associating each item of the customer order with an order identifier. The user interface device may be configured to display indications or alerts regarding received customer orders, requesting input from the user, such as confirmation of receipt. 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 (eg, a picker) may pick one or more items of a customer order and have each picked item be compared with one or more computers by scanning the order identifier and barcode on the item, for example. associated with the order identifier received by the system. In some embodiments, associating the items of the customer order with the order identifier may include using an indicia printer or a barcode printer to physically print the order identifier. A printed indicia or barcode may be attached or affixed to the item, for example, to allow all employees to easily access information associated with the order and delivery schedule. For example, a worker who did not receive or have no access to the original order identifier may be able to scan the printed and affixed order identifier on the item.

In step 440, one or more computer-implemented systems of system 100 may determine the intended final delivery destination for each of the items of the customer order. As an example, a customer might order a bouquet of flowers to be delivered to a friend's house by 8 pm and a pack of batteries to be delivered to their parents' house within 24 hours. One or more computer-implemented systems of system 100 may generate two separate order identifiers representing the two orders. Each of the items 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 the intended delivery destination, the storage space associated with the intended delivery destination (eg, in storage cell 324/storage cell 344), and A delivery route for an item of a customer order to be delivered 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 item based on the camp to which the item may be directed. Marketing can be determined based on, for example, the postal code of the intended final delivery destination for the item in the customer order. land. The second step may include sorting the picked items in the camp based on the delivery routes to which the items can be sent for delivery. Delivery routes may be determined based on, for example, districts or streets within an area represented by zip codes.

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

Each of the sorted items can be transported to the corresponding camp. In some embodiments, the camp may be an on-site storage facility within the premises of FC 200 (eg, camp area 215). The sorted items may be transported to the camp area 215 using transport means such as, for example, conveyor belts, forklifts, carts, carts, carts. In some embodiments, the camp may be an off-site storage facility, such as a warehouse or a storage unit separate from the FC 200 . The sorted items may be transported to an off-site storage facility using, for example, a delivery truck. Sorted items belonging to customer orders can be transported to camp to reduce idle time without waiting for the rest of the customer order.

In step 460, one or more computer-implemented systems of system 100 may send instructions to the user interface device displaying instructions or alerts to sort the picked items in the camp based on the delivery route. The delivery route may be provided by one or more electrical devices of system 100. The brain fulfillment system pre-orders based on the final delivery destination in the customer order. Workers may sort picked items in a camp by placing the items in a storage cell (eg, storage cell 344 ) based on the delivery route. Workers can obtain delivery route information by, for example, scanning an order identifier on an item. 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-implemented systems of system 100 may send instructions to the user that display instructions or alerts to place the sorted objects from storage cell 344 into a container (eg, container 350). interface device. Each storage cell 344 may be associated with a container that is configured to hold the items stored in the corresponding storage cell. In some embodiments, each container may be identified with a container identifier that includes information identifying camps and storage cells. Picked items belonging to a customer order can be placed in the container without waiting for the rest of the same customer order to reduce idle time.

Container 350 or container carrier 360 may be loaded on a delivery vehicle (eg, delivery truck 201 ) configured to accommodate containers, totes, wheeled cages, carts, dollys, and the like. Containers may be loaded in a manner that reduces unloading time during item delivery based on, for example, the configuration of the delivery route. The configuration of 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 item is a perishable food, and the like. In some embodiments, the storage compartment of the delivery truck may contain built-in storage space, such as cabinets, cells, shelves, racks, cages, or wheeled cages. Each container carrier in the delivery truck can be identified by a container carrier identifier (eg, a barcode). The container carrier identifier may contain information associated with the location of the container carrier within the storage compartment of the delivery truck. For example, four container carriers 360 may be arranged against the rear wall of the storage compartment, labeled 360_1 to 360_4 from left to right. therefore, The container carrier located in 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 in 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 container carrier 360 may be generated by one or more computer-implemented systems of system 100, such as transport system 107.

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

In step 480, one or more computer-implemented systems of system 100, such as transportation system 107, may, for example, send instructions to a user interface device (eg, an instruction to deliver an item stored in a container loaded on a delivery truck) , one of mobile device 107A to mobile device 107C). The user interface device may display an indication requesting input from a user (eg, a delivery worker or loader) to verify completion of the loading process prior to setting off to deliver the item. The user interface device may receive input from the user and store the received input in a database associated with the system 100 .

In some embodiments, one or more computer-implemented systems of system 100 may send an instruction to the user interface device to display an instruction to record information associated with the order identifier, for example, by scanning the order identifier. User interface devices can be After picking the item, after sorting the picked item based on the storage location in the first step of the sorting process, before transporting the sorted item to the camp, after arriving at the camp, in the first step based on the sorting process The delivery route in the second step displays an instruction to record the order identifier information after sorting the picked items, after placing the sorted items in the container, and after loading the container on the delivery truck. Information recorded at all steps of the process may be stored and updated in a database associated with system 100 (eg, associated with or connected to WMS 119 or transportation system 107 ).

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

In some embodiments, the system 100 may dynamically change the shipping priority of customer orders. After the order identifier for the customer order is generated in step 420, the shipping priority of the order may be changed during any step in process 400. The order identifier may be updated or modified by the system to reflect the change in shipping priority prior to shipping the order. For example, in step 450, one or more computer-implemented systems of system 100 may display a selection of picked items for a customer order based on a pre-designated storage space (eg, storage cell 324 of storage location 320). Instructions or warnings are sent to the user interface device. The pre-designated storage space may be associated with a customer order that is not the original customer order expected for the picked item.

5 illustrates a computer-implemented method 500 of dynamic package prioritization performed by the system 100 in accordance with some aspects of the present disclosure. The method 500 shown in FIG. 5 may be performed by at least one processor present in the system 100 . For example, method 500 Can be performed by one or more of the systems depicted in Figure 1A. In some embodiments, method 500 may be performed by shipping authorization technology system 101 , shipping and order tracking system 111 , fulfillment optimization system 113 , or warehouse management system 119 alone or in combination with other systems in system 100 . Additionally, the methods may be performed by one or more off-site processors, such as one or more cloud-based devices in communication with the system 100 .

In step 505, a first customer order is received. The first customer order can be for any number of products or items. Orders may be received electronically from anywhere within the system 100 . For example, an order may be received by external front end system 103 from user device 102A, user device 102B, from seller portal 109, or from another input device within system 100. Orders may be received via any wired or wireless communication channel. System 100 may receive a first customer order and generate an order identifier to allow monitoring of order status and tracking of the order. The order identifier can be specific to the order and can be associated with any item or detail of the order. The order identifier may contain elements that associate groups of products such as auto parts, produce, bathroom items, and the like. The order identifier may contain elements associated with other information, such as the intended address for delivery, the customer identifier, the location of the product within the FC, or any other information related to the product, supplier, or customer. The order identifier may comprise a machine readable identifier such as a barcode or RFID tag, or may comprise a unique code, number or symbol. The order identifier may be stored in memory, in one or more databases, and accessible by any part of the system 100 (such as by one or more of devices 107A-107C or devices 119A-119C), or may include printing mark. The system 100 may also generate one or more unique sub-order identifiers. The sub-order identifier may be associated with any one or more items in order or with any details related to the order as discussed above. each object Can contain identifiers or suborder identifiers.

The system 100 can assign a first shipping metric to the first customer order (when received). In some embodiments, shipping metrics may be based on one or more quantifiable or non-quantifiable criteria of a measure used to determine shipping priorities for one or more orders. For example, shipping metrics may be related to internal goals such as the number of items packed in a particular time period, productivity, or the latest possible pack time. The latest possible packing time can include the latest time the item must be packed in the fulfillment center to be ready for shipping. The internal goals of each fulfillment center may vary. For example, the internal goals of each FC may be productivity, financial considerations, the items located in the FC, the geographic location of the FC, the number of customers served by the FC, the number of employees in the FC, or any other consideration specific to each FC drive. Targets can be static, or can change dynamically based on various factors. For example, targets can be associated with global or local market conditions, and can be adjusted in response to market volatility. Additionally, WMS 119 can analyze data related to the workflow and adjust internal goals accordingly.

In some embodiments, the shipping metrics may be associated with the promised delivery date or the promised delivery time of the customer order. The promised delivery date or promised delivery time may be based on the requested delivery time, which may be related to the shipping method selected by the customer. The promised delivery date or promised delivery time can be based on membership in a program that promises expedited shipping. For example, customers participating in this program receive overnight shipping on all orders placed.

In some embodiments, shipping metrics may relate to locations or addresses associated with customer orders. The location or address can be any physical location, such as a home address, business address, post box, or other desired address where the order is intended to be delivered. For example, a customer may be associated with a home address but wish to have the order delivered to another address (eg, when sending a gift to a friend or relative). In this case, shipping metrics may involve The address associated with a friend or relative, because this is the delivery location.

In some embodiments, the shipping metrics may relate to shipping couriers. For example, one courier may require the package to be ready for shipping at a specific time, while another courier may require the package to be ready for shipping at a later time. Additionally, shipping metrics can be related to shipping methods. For example, expedited shipping methods can deliver packages within hours or overnight. Conversely, land shipping methods can take several days to complete the delivery. While several examples of shipping metrics are given here, they are by no means an exhaustive list.

At step 510, an item is acquired for shipping. A display device associated with an employee of the fulfillment center may receive an instruction to collect items associated with the customer order. For example, FO 113, WMS 119, SCM 117, or SAT 101 may generate instructions to send instructions to user interface device 302 or device 107A to device 107C or device 119A to device 119C, alerting the user to collect objects. Indications may include notifications and may be delivered visually, audibly or tactilely. The instructions may be wirelessly transmitted to a picker-owned mobile device via one or more networks or other wireless communication channels. The instructions may instruct an employee, such as a picker, to obtain the item in the desired location of the fulfillment center or warehouse. For example, a picker may receive instructions to physically take an item and bring the item to a second location. The instructions may include a display of the direction of a particular rack in a particular portion of the fulfillment center where a picker can find and remove an item. The picker can confirm the instruction or instruction by responding using the user interface device 302 or the device 107A to the device 107C or the device 119A to the device 119C. For example, a picker can enter a code, obtain an image of the item in the storage location, scan a barcode or other identifier, and upload a response to the system 100 . Additionally, pickers may receive instructions directly from supervisors or other individuals, either verbally or in writing (such as by printing indicia).

In some embodiments, may be obtained by one or more robotic devices for operation sent items (step 520). In response to signals generated by one of the computer-implemented systems of system 100 (eg, FO 113, WMS 119, SCM 117, or SAT 101), such as automated guided vehicles, automated storage and retrieval systems, co-working robots, or articulated robots The robotic device of the arm can collect one or more objects. Once captured, the collected items may then be brought to a desired location within the FC, such as packing area 211, by one or more robotic devices.

In some embodiments, items may be obtained for shipping (as received from third parties or other sources). In this case, customer orders may be placed for out-of-stock shipments. One or more computerized systems in system 100 may query one or more databases associated with items in inventory at each fulfillment center and generate an indication that the item is unavailable or out of stock. In some embodiments, seller portal 109 may generate a request for out-of-stock shipments. Requests may be widely distributed or sent to specific third parties or other sources. Notifications may be generated when the system 100 identifies an item that has been received at the desired FC, such as by scanning a barcode via the internal front end system 105 or manually entering the item's received quantity.

Before receiving the initial first customer order, after receiving the initial first customer order, or at some time concurrently with the first customer order, the system 100 may receive a second customer order that includes a number of items, wherein at least one of the items is The same item as the item in the first customer order (received in step 505). The system 100 may then assign shipping metrics to the second customer order. The shipping metrics for the second customer order may contain the same metrics as the shipping metrics for the first order, or may have different metrics. For example, in one aspect, both the first shipping metric and the second shipping metric may be based on a promised delivery date. In another aspect, the first shipping metric can be based on the promised delivery date and the second shipping metric can be based on the latest possible pack time. Pick Depending on considerations within each of the fulfillment centers, the basis for specifying shipping metrics may be dynamic.

At step 515, the system 100 may search for any outstanding customer orders. Unfulfilled customer orders may be orders that have not been packaged or otherwise marked as completed. The system may search any database or system (such as SAT 101, FO 113, SOT 111 or WMS 119) to identify any outstanding customer orders. Searches can be limited by various parameters. For example, the system 100 may only search for customer orders received within a certain time frame. Additionally, searches may be initiated by events occurring in the system 100 . For example, a search may be initiated where a worker at packaging area 211 scans an item ready to be packaged using user interface device 302 .

At step 520, the system 100 compares the shipping metrics for any unfulfilled customer orders that share a common item. For example, the system 100 may compare the first shipping metric with the second shipping metric to determine the priority of the first customer order and the second customer order. The comparison may include any calculation or manipulation of values, scores or data that allows prioritization of customer orders to be obtained. In some embodiments, SAT 101, FO 113, SOT 111, or WMS 119 may determine priority by directly comparing the first shipping metric with the second shipping metric. In this case, the shipping metric with the higher value (and thus, the priority order) is determined to have the highest priority order. In some embodiments, SAT 101, FO 113, SOT 111, or WMS 119 may determine priorities via statistical analysis or other data analysis used to determine shipping priorities.

As shown in FIG. 5 , when the system 100 determines by comparing the first shipping metric to the second shipping metric that the first customer order is preferred over the second customer order, then at step 525 shipping of the first order continues. Instructions to print the shipping indicia of the first customer order may be sent to the output device. The pointer instructing the packer to pack the article may also be The display is sent to one or more of user interface device 302 or device 107A to device 107C or device 119A to device 119C. The item is packaged and shipped to the delivery location or address associated with the first customer order. Meanwhile, at step 530, the system generates a notification to fill the second order. Notifications may be sent to one or more of user interface device 302 or device 107A to device 107C or device 119A to device 119C to inform the picker to obtain an item from buffer area 205 , unload area 207 or pick area 209 as needed . Notifications may include audible, visual, or tactile alerts as discussed above, and may be transmitted via any communication channel. In some embodiments, a notification of an item acquisition may be communicated to one or more robotic devices.

At step 535, the items of the second customer order are obtained. The item may be acquired in any manner as discussed above. The item may follow the process described in FIGS. 3 and 4, ending at step 540 with shipping the item to the delivery location or address associated with the second customer order.

When the system 100 determines that the second shipping metric should have a higher priority than the first shipping metric, the item previously acquired for the first customer order at step 510 is reassigned to the second customer order, as shown at step 545 . The instructions may include instructions generated by SAT 101 , FO 113 , SOT 111 or WMS 119 to reassign the acquired first item to the second order. The instructions may include disassociating the order identifier for the first order and associating the order identifier with the second order. In some embodiments, the instructions may include sending a notification to one or more of user interface device 302 or device 107A-device 107C or device 119A-device 119C. Instructions may include instructions to reassign orders that may be sent from SAT 101 , FO 113 , SOT 111 , or WMS 119 to a portion of system 100 via a wired or wireless communication channel. For example, instructions may be sent by the SAT 101 to the Shipping and Order Tracking (SOT) system 111 to notify the second customer Customer orders re-designate common objects. This can include updating the file or database to reflect changes in the designation of common objects. In response, shipping and order tracking (SOT) system 111 may transmit the reassigned instructions to an output device, such as user interface device 302 or device 107A to device 107C or device 119A to device 119C.

In some embodiments, the output device may comprise a handheld device, such as a PDA, configured to print indicia or barcodes. The packer in the packing area 211 may receive instructions from the SOT 111 on this PDA including instructions to print a new label or barcode, reflecting the reassignment of the common items of the second customer order. In other embodiments, the set of printers may print new shipping marks to be affixed to packages containing items. The re-assignment instruction may include any means of notifying a portion of the system 100 , the fulfillment center, personnel at the fulfillment center, or any other user of the system 100 . The indication may comprise a visual signal, an audible signal, or a tactile indication.

In some embodiments, in response to reassigning the item to the second customer order in step 545, the WMS 119 may determine the location within the FC of the item or package associated with the first customer order. WMS 119 may then generate instructions depending on which zone the item or package is located in (eg, pick zone 209, pack zone 211, hub zone 213, or camp zone 215). For example, if the item or package is in the packaging area 211, the instructions may include printing a new barcode or label affixed to the package using the output device. However, if the item or package is within the pick area, the instructions may include displaying to the user interface device 302 or devices 107A to 107C or devices 119A to 119C the particular cell 324 to place the item or package in the storage location 320 notice in . The instructions may include receiving a response from the employee to confirm receipt of the notification, as well as verifying the new location of the item or package. Responses can be submitted using devices 107A to 107C or devices 119A to 119C and can include scanning barcodes or labels, capturing images, entering codes, numbers or symbols No. WMS 119 may update one or more databases with information related to the new location.

After specifying the item to the second customer order, then at step 550 shipping of the second order continues. The item is packaged and shipped to the delivery location or address associated with the second customer order.

At the same time, at step 555, the system generates a notification to fill the first order. Notifications may be sent to one or more of user interface device 302 or device 107A to device 107C or device 119A to device 119C to inform the picker to obtain an item from buffer area 205 , unload area 207 or pick area 209 as needed . Notifications may include audible, visual, or tactile alerts as discussed above, and may be transmitted via any communication channel. In some embodiments, a notification of an item acquisition may be communicated to one or more robotic devices. At step 560, the items of the second customer order are obtained. The item may be acquired in any manner as discussed above. The item may follow the process described in FIGS. 3 and 4, ending at step 565 with shipping the item to the delivery location or address associated with the first customer order. Although FIG. 5 may depict certain steps in a sequential order, some steps may be performed out of the order shown. For example, in an embodiment where the system 100 generates a notification to fill the order after receiving the order, the notification to fill the second order may occur before comparing the first shipping metric with the second shipping metric.

FIG. 6 shows an exemplary dynamic packing operation 600 for multiple customer orders with common items. In this example, a first electronic customer order 610 is received. Orders may be received electronically from customers from anywhere within the system 100 . For example, an order may be received by external front end system 103 from user device 102A, user device 102B, from seller portal 109, or from another input device within system 100. Orders may be received via any wired or wireless communication channel. The system 100 may include an identifier association object 615 and associate the identifier with the first customer order. for example In other words, the SKU of the object 615 can be stored in the database. The database may also contain other information related to the product 615, such as the location of the item 615 in the fulfillment center. After receiving the order for item 615, system 100 may associate the product number with the first customer order. The system may generate a notification as discussed above to allow acquisition of the item 615 . System 100 assigns shipping metrics as discussed above to first customer order 610 .

A second electronic customer order 620 for item 615 is received in system 100 some time after the first customer order but before the first order has been closed. In some embodiments, an order may be considered closed when it is cancelled by the customer or delivered to the address or location associated with the order. System 100 may associate the identifier of item 615 with the second customer order. At a later time, but before the first and second orders have been closed, a third electronic customer order 630 is received in the system 100 . System 100 may associate the identifier of item 615 with the third customer order. At a later time, but before the first order, the second order, and the third order have been closed, a fourth electronic customer order 640 is received in the system 100 . System 100 may associate the identifier of item 615 with the fourth customer order. In this example, the first customer order 610 , the second customer order 620 , the third customer order 630 , and the fourth customer order contain the identifier of the item 615 .

At 650, the system 100 may compare the shipping metrics for the first customer order, the shipping metrics for the second customer order, the shipping metrics for the third customer order, and the shipping metrics for the fourth customer order to prioritize the orders. As discussed above, a comparison may include any calculation or manipulation of values, scores, or data that allows prioritization of customer orders to be obtained. In some embodiments, the SAT 101, FO 113, SOT 111, or WMS 119 may determine the shipping priority by directly comparing the first shipping metric, the second shipping metric, the third shipping metric, and the fourth shipping metric. In this case, the shipping metric with the higher value (and thus, the priority order) is determined to have the highest priority order. In some embodiments, SAT 101, FO 113, SOT 111, or WMS 119 may determine shipping priorities via statistical analysis or other data analysis used to determine shipping priorities. In this example, the third customer order is considered to have the highest priority. The system 100 may send an instruction to redesignate the acquired item 615 to the third customer order. Reassignment may include updating a database or file with the changes, and transmitting an indication of the reassignment to an output device, such as user interface device 302 or device 107A to device 107C or device 119A to device 119C. The acquired item 615 may then be packaged 660 (if not already packaged) and delivered to the address or location associated with the third order 630 . The remaining orders can then be filled. In some embodiments, the remaining orders may be re-evaluated to determine priorities.

In some embodiments, the method ends once the designation of the common item has been changed from the initial order to a different order and the new indicia or barcode has been printed by the output device. For example, if the output device has printed a new indicia indicating reassignment of the item 615 to the third order 630, no matter how high the shipping metrics of the fourth customer order 640 may be, no shipping of the fourth customer order 640 will occur. reassign. In other embodiments, item 615 may be reassigned until item 615 has been delivered. For example, a mobile device associated with a delivery driver may receive a notification from the system 100 to print a new indicia and affix it to a package.

Referring now to FIG. 7, an example of a dynamic packaging prioritization and corresponding tasks performed by the system 100 and employees of the FC is shown. In FIG. 7 , a timeline is indicated at row 705 . In this example, timeline 705 begins at 10:00 am and proceeds to 10:20 am. Although timeline 705 is shown in units of minutes, it should be understood that tasks or steps may be performed in smaller or larger increments of time. Row 710 shows incoming customer orders. As discussed above, orders may be received by external front end system 103 from user device 102A, user device 102B, from seller portal 109 , or from another input device within system 100 . Row 715 shows the operations performed by system 100 . Operations may be performed by any part of the system, such as SAT 101, FO 113, SOT 111, or WMS 119. Row 720 shows the tasks performed by the picker. Pickers may include any human or robotic device capable of obtaining items from locations within the FC. Row 725 shows the tasks performed by the packer. A packer may include any human or robotic device capable of packing or preparing an item for shipping.

As shown, at 10:01 am time, a first customer order for a unit of item A is received by the system 100 (step 505). The system generates shipping metrics for the first order. At 10:02 am, SAT 101, FO 113, SOT 111, or WMS 119 may generate a notification to acquire one unit of item A. Notifications may be sent to one or more employees, mobile devices, or robotic devices via any wired or wireless communication channel as discussed above. In some embodiments, a notification may be transmitted to a mobile device associated with the picker to instruct the picker to acquire one unit of item A. At 10:05 am, the picker may pick one unit of item A from the picking area 209 (step 510). A second customer order for a unit of Item A is received at 10:10 am when the item is delivered to the packing area 211 . The system 100 generates shipping metrics for the second customer order. At 10:11 am, SAT 101, FO 113, SOT 111 or WMS 119 generates a second notification to acquire one unit of item A associated with the second customer order. At the same time, the packer scans the product identifier associated with item A when received at packing area 211 . In response to receiving the scan of the product identifier, the system 100 performs a search for unfilled orders and identifies all unfilled orders for item A (step 515). In this example, the system 100 identifies a first customer order and a second customer order. The system 100 then The shipping metrics for the first customer order are compared to the shipping metrics for the second customer order to determine which order has priority (step 520). In this example, the second customer order is considered to have a higher priority than the first customer order. The item is then reassigned to the second customer order, and an output device, such as a printer, may print the shipping indicia for the second customer order with the highest shipping priority (step 545). The packer may then pack the second customer order using the item originally picked for the first customer order. At 10:14 am, an additional unit of item A is picked from the picking area 209 in response to the second notification (step 535). At 10:18 am, when item A is received in packing area 211, the packer scans the product identifier associated with item A, which prompts system 100 to search for and identify any unfilled orders for item A (step 515) . In this example, only the first customer order remains, and as such, the first customer order is deemed to have the highest shipping priority. The output device may print out the shipping mark of the first customer order. The packer completes the packing of the first customer order using the items picked as a result of the second picking task associated with the second customer order (step 525).

Referring now to FIG. 8, an illustrative flowchart of a process 800 for generating a visual representation of a loading configuration of a delivery vehicle is shown, consistent with disclosed embodiments. It is understood that the flowcharts are an exemplary order of steps of a process and that steps may be performed in other orders. Additionally, steps may be added, omitted, skipped, repeated or modified based on application and user needs.

In step 810, one or more computer-implemented systems of system 100 may identify a delivery vehicle (eg, delivery truck 201) that includes storage space. In some embodiments, the transportation system 107 of the system 100 may identify delivery vehicles based on, for example, storage space requirements, delivery route characteristics, delivery truck worker experience or classification, or other data. For example, the transportation system 107 may identify a delivery route for use with narrow roads A delivery truck worker on duty (eg, a truck driver) may only have a valid driver's license for the small delivery vehicle. 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 820, one or more computer-implemented systems of the system 100, such as the transportation system 107, may send instructions to the user interface device displaying instructions to determine the configuration of the storage space within the delivery truck. In some embodiments, delivery trucks may include built-in storage spaces in storage compartments, such as cabinets, racks, shelves, cages, and the like. For example, delivery trucks may include storage compartments to accommodate transportable storage units such as wheeled cages.

In some embodiments, each storage space in a delivery truck may be identified using a storage space identifier or a container carrier identifier. Container carrier identifiers may include barcodes, labels, labels or QR codes. The container carrier identifier may contain 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 in 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 in the rear right corner of the storage compartment of the delivery truck may be identified as container carrier 360_4. In some embodiments, the delivery truck may include built-in storage spaces, each storage space having a storage space identifier.

In some embodiments, a delivery truck worker (eg, driver or loader) may record the configuration of the built-in storage space in the delivery truck, eg, by scanning the storage space identifier. In some embodiments, the repository of system 100 may include Information associated with the configuration of the storage space in the delivery truck. For example, the database may include information associated with the configuration of storage space in the delivery truck.

In step 830, one or more computer-implemented systems of system 100, such as shipping system 107, may generate a container identifier for each container. Container identifiers may include barcodes, labels, labels or QR codes. The container identifier may include information associated with at least the camp 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 item in the container.

In step 840, one or more computer-implemented systems of system 100, such as transportation system 107, may send instructions to a user interface device that display instructions to load the container into the storage space of the delivery truck. Containers can be loaded onto a delivery truck in an unloaded manner that enables quick access to the item during delivery.

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

In step 860, one or more computer-implemented systems of system 100, such as transportation system 107, may generate a visual representation of the loading configuration of the container and storage space based on the associations established in step 850. In some embodiments, the loading configuration may be presented to a user (eg, a delivery truck driver) in a tabular or visual format. Load configuration The settings can be printed on paper, displayed on a user interface device, or presented to the user before starting their delivery round.

In some embodiments, the loading configuration of the delivery truck may be displayed on a user interface display of the delivery vehicle, such as a graphical user interface display screen of the delivery truck. In some embodiments, the visual representation of the loading configuration may be updated upon completion of delivery. For example, when a delivery truck driver delivers an item to a customer and the container is empty, a display in the loading configuration may indicate that the item placed in the container in the storage space has been delivered. This information can be updated in the database, allowing the transportation system 107 and/or the system 100 to determine whether the promised delivery date and time are met.

Although the present disclosure has been shown 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 purposes of illustration. The foregoing description is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations will be apparent to those of ordinary skill in the art from consideration of this specification and practice of the disclosed embodiments. Additionally, although aspects of the disclosed embodiments are described as being stored in memory, those of ordinary skill in the art will appreciate that aspects of the disclosed embodiments may also be stored on other types of computer-readable media, such as the following A secondary storage device such as a hard disk or CD ROM, or other forms of RAM or ROM, USB media, DVD, Blu-ray, or other optical drive media.

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

Furthermore, although illustrative embodiments have been described herein, those of ordinary skill in the art will appreciate based on this disclosure having equivalent elements, modifications, omissions, combinations (eg, of aspects in various embodiments), The scope of any and all embodiments for adaptation and/or modification. The limitations in the scope of claims should be construed broadly based on the language employed in the scope of claims, and are not limited to examples described in this specification or during the prosecution of this application. Instances shall be considered non-exclusive. Additionally, the steps of the disclosed methods may include modification in any manner by reordering the steps and/or inserting or deleting steps. Therefore, it is intended that the specification and examples be regarded as illustrative only, with the true scope and spirit being indicated by the following claims and their full scope of equivalents.

500: Method

505, 510, 515, 520, 525, 530, 535, 540, 545, 550, 555, 560, 565: Steps

Claims (20)

A computer-implemented system for package delivery, comprising: at least one processor configured to: receive, via a network, a first electronic customer order for an item, the first electronic customer order including an identifier for the item; the first electronic customer order specifies a first shipping metric; transmits an instruction to acquire the item of the first electronic customer order to a mobile device; receives a scan indicating a product identifier of the item of the first item has been acquired ; identify a second electronic customer order for the item; compare the first shipping metric with the shipping metric for the second electronic customer order for the item to determine the first electronic customer order and the second electronic customer order a priority order of customer orders; and transmitting an indication of the determined priority order to an output device. The computer-implemented system for package delivery of claim 1, wherein the shipping metrics include at least one of latest possible packing time, promised delivery date, promised delivery time, location, address, shipping courier, and shipping method . The computer-implemented system for package delivery of claim 1, wherein the output device comprises a printer configured to print shipping indicia based on the determined priority order. The computer-implemented system for package delivery of claim 1, wherein the at least one processor is further configured to: the shipping metric at the second electronic customer order is higher than the first shipping The item is reassigned to the second electronic customer order without measuring. The computer-implemented system for package delivery of claim 4, wherein the at least one processor is further configured to: transmit to a mobile device an instruction to retrieve the item of the first electronic customer order. The computer-implemented system for package delivery of claim 1, wherein the output device comprises a mobile device. The computer-implemented system for package delivery of claim 1, wherein the at least one processor is further configured to: identify a third electronic customer order for the item; compare the first shipping metric, the Shipping metrics for the second electronic customer order and shipping metrics for the third electronic customer order to prioritize the first electronic customer order, the second electronic customer order, and the third electronic customer order; and An indication of the determined priority order is transmitted to an output device. The computer-implemented system for package delivery of claim 7, wherein the at least one processor is further configured to: transmit, to a mobile device, an instruction to obtain the item of an unprioritized electronic customer order . The computer-implemented system for package delivery of claim 1, wherein the first electronic customer order additionally includes a plurality of items, and wherein the at least one processor is further configured to: generate picking of the items and send the notification to the first mobile device; and A notification to pack the item is generated and sent to the second mobile device regardless of the status of the remaining items of the plurality of items. A computer-implemented system for package delivery, comprising: at least one processor configured to: receive, via a network, a first electronic customer order for a first item, the first electronic customer order including an order for the first item identifier; assigning a first shipping metric to the first electronic customer order; transmitting an instruction to obtain the first item of the first electronic customer order to a mobile device; receiving the first item via the network a second electronic customer order that includes the identifier for the first item; assigning a second shipping metric to the second electronic customer order; comparing the first shipping metric to the a second shipping metric to determine the priority of the first electronic customer order and the second electronic customer order; and based on determining that the second shipping metric should have a higher priority than the first shipping metric: the An instruction to reassign the acquired first item to the second electronic customer order is sent to an order tracking system, and the reassignment instruction is transmitted to an output device. The computer-implemented system for package delivery of claim 10, wherein each of the first shipping metric and the second shipping metric includes latest possible pack time, promised delivery date, promised delivery time, location at least one of , address, shipping courier, and shipping method. A computer-implemented system for package delivery as claimed in claim 10, Wherein the output device includes a printer. The computer-implemented system for package delivery of claim 10, wherein the output device comprises a mobile device. The computer-implemented system for package delivery of claim 10, wherein transmitting the indication of the priority order for shipping includes transmitting the indication wirelessly. The computer-implemented system for package delivery of claim 10, wherein the at least one processor is further configured to: receive a third electronic customer order for the first item via the network, the first item Three electronic customer orders include the identifier of the first item; assign a third shipping metric to the third electronic customer order; compare the first shipping metric, the second shipping metric, and the third shipping a metric to determine a priority order of the first electronic customer order, the second electronic customer order, and the third electronic customer order; and based on determining that the third shipping metric should have a higher priority than the first shipping metric or Higher priority of the second shipping metric: sending an instruction to the order tracking system to reassign the acquired first item to the third electronic customer order, and transmitting the reassignment instruction to the output device. The computer-implemented system for package delivery of claim 15, wherein the at least one processor is further configured to prevent redesignation of the first item if the output device has printed shipping indicia . The computer-implemented system of claim 10, wherein the at least one processor is further configured to: Prevents reassignment of the first object if the output device has printed shipping marks. The computer-implemented system of claim 15, wherein the first electronic customer order additionally includes a plurality of items, and wherein the at least one processor is further configured to: generate a notification to pick the first item; and generating a notification to pack the first item regardless of the status of remaining items in the plurality of items. A computer-implemented system for package delivery, comprising: at least one processor configured to: receive, via a network, a first electronic customer order for a first item, the first electronic customer order including an order for the first item identifier; assigning a first shipping metric to the first electronic customer order; transmitting an instruction to obtain the first item of the first electronic customer order to a mobile device; receiving the first item via the network a second electronic customer order that includes the identifier for the first item; assigning a second shipping metric to the second electronic customer order; a third electronic customer order, the third electronic customer order including the identifier of the first item; comparing the first shipping metric, the second shipping metric, and the third shipping metric to determine the prioritizing the first electronic customer order, the second electronic customer order, and the third electronic customer order; and based on determining that the second shipping metric or the third shipping metric should have higher priority than said first shipping metric: sending an instruction to reassign the acquired first item to the second electronic customer order or the third electronic customer order to an order tracking system, and sending the The reassigned instructions are transmitted to the output device. The computer-implemented system for package delivery of claim 19, wherein the at least one processor is further configured to prevent redesignation if the output device has printed shipping indicia.

Images