TWI830614B - Computer-implemented system and computer-implemented method for generating visual representation of loading arrangement for delivery vehicle on delivery route - Google Patents

Abstract

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

Description

Used to generate loading configurations for delivery vehicles on delivery routes Computer execution system and computer execution method for visual representation

This disclosure generally relates to computerized systems and methods for package delivery to fulfill customer orders. Specifically, embodiments of the present disclosure relate to inventive and non-conventional computerized systems, methods, and user interfaces for efficiently performing customer tasks with reduced cycle times. orders and delivers packages while maintaining high worker productivity across multiple locations within the fulfillment center.

[Cross-reference to related applications]

This application is a continuation in part of currently pending U.S. Patent Application No. 16/416,909, filed on May 20, 2019, all of which is hereby incorporated by reference in its entirety.

Fulfillment center (FC) enables e-commerce merchants to outsource warehousing and shipping. Inventory management in FC is an essential part of cultivating the best customer experience for online shoppers. Inventory management can include receiving goods from sellers, stacking Several steps within the scope of receiving merchandise for picking access, packing items, verifying orders, and parcel delivery. Although currently existing FCs and the systems used 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 the time required to obtain items before they are obtained. Inefficient practices in fulfilling orders. Delays in package delivery can lead to customer dissatisfaction 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, electronic products, clothes, books, etc. Each online order typically includes a combination of items from a wide variety of categories. Although in currently existing order fulfillment practices systems can be employed to obtain each individual item in an order in an efficient manner, the overall efficiency of order delivery is limited by the ability to obtain each individual item. For example, items are often stored in various sections of the FC based on categories, and a packer may have to wait for a picker to pick all items for an order before they can be packed. This can cause delays in subsequent steps in the process of packaging and delivering 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 FC may be affected because although items are picked individually, they are packed simultaneously into a container before being loaded as a package on a delivery truck. If the storage space in which picked items are stored is inaccessible, expected or unexpected delays in packaging can impact picking efficiency. The process of storing and shipping packages out of a FC involves several steps, such as receiving, stowing, picking, sorting, packaging, loading, delivering, and verifying order accuracy at each of the steps. For overall efficiency to be high, individual step efficiencies must also be high. For example, if a process consists of 10 steps and the efficiency of each step is greater than 90%, the overall efficiency is only 83.9%.

In addition, currently existing FC uses a team of workers to ensure smooth 24-hour operation. One of the technical challenges in the warehouse may be communicating information quickly to workers on the ground, such as urgent customer orders, priority shipping, etc. Current existing logistics and inventory management systems lack the ability to efficiently account for expected or unexpected urgency in customer orders, which can lead to customer dissatisfaction and higher associated inventory costs.

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

One aspect of the present disclosure is directed to a computer-implemented method for generating a visual representation of a delivery vehicle's loading configuration on a delivery route, including: identifying a delivery vehicle that includes at least one storage space; determining a storage space for each storage space identifier; generating a container identifier for at least one container; sending a load instruction displayed on a user device, wherein the load instruction displays an indication to be associated with the at least one container identifier based on the determined storage space identifier loading at least one container into the storage space; associating each container with the storage space in which it is placed based on the loading instruction; and generating a loading configuration of the container and the storage space based on the association. Visual representation.

Another aspect of the present disclosure is directed to a computer-implemented system for generating a visual representation of a loading configuration of a delivery vehicle, the system including: a memory storage for storing computer-executable instructions; and one or more processes A processor configured to execute the instructions to perform one or more of the methods described above.

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

201, 222: Truck

100:System/Network

101: Shipping Authorization Technology Systems

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

102B:Computer

103:External front-end system

105: Internal front-end system

107:Transportation system

109:Seller Portal

111: Shipping and order tracking system

113: Fulfillment Optimization System

115: Execute communication reporting channel

117:Supply chain management system

119:Warehouse Management System

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

123: Fulfillment Center Authorization System

125:Labor management system

200: Fulfillment Center

202A, 202B, 208: Object

203: Inbound area

205:Buffer

206:Forklift

207:Unloading area

209: Picking area

210:Storage unit

211:Packaging area

213:hub area

214:Transportation agencies

215: Camp area

216:Wall

218, 220:Package

224A, 224B: Delivery workers

226:Car

300: Computer execution system/single package delivery system

301: Convergence worker/worker

301a, 301b: workers

302:User interface device

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

320: First storage location

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

340: Second storage location/camp

342:Storage space

350: Container

355. CS3_SR1_a, CS3_SR1_b: Container identifier

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

400, 500, 600: process

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

700: Notification Dashboard

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

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

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

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

Figure IE depicts a sample order page including items from a virtual shopping cart as well as information about purchasing and shipping and interactive user interface elements consistent with the disclosed embodiments.

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

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

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

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

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

7 is a schematic diagram of an exemplary notification dashboard consistent with the 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 illustrated in the drawings may be substituted, added, or modified, and the methods described herein may be modified by replacing, reordering, removing, or adding steps to the disclosed methods. Indicative method. Accordingly, the following detailed description is not limited to the disclosed embodiments and examples. Rather, the true scope of the invention is defined by the appended claims.

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

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

In some embodiments, SAT system 101 may be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 may determine whether an order has exceeded its Promised Delivery Date (PDD) and may take appropriate actions, including initiating a new order, reshipping items in undelivered orders, canceling undelivered orders, initiating and ordering Customer contact, or similar. 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 cardboard boxes received for shipping). SAT system 101 may also act as a gateway between different devices in system 100, thereby enabling communications 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, the network 100 allows the system to be presented to allow users to place orders for items. In a single embodiment, the external front-end system 103 may be implemented as a web server that receives search requests, renders object pages, and requests payment information. For example, the external front-end system 103 may be implemented as a computer or computer running 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 be configured to receive and process requests from external devices (not depicted), obtain information from databases and other data repositories based on those requests, and store information based on the obtained information. Custom web server software that responds to requests received.

In some embodiments, the external front-end system 103 may include one or more of a web cache system, a database, a search system, or a payment system. In one 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 (e.g., , server to server, database to database, or other network connection).

It will be helpful to describe some of the operations of the external front-end system 103 through the exemplary set of steps shown in FIGS. 1B, 1C, 1D, and 1E. External front-end system 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, Figure 1D), or an order page (eg, Figure 1E). A user device (eg, using mobile device 102A or computer 102B) can navigate to external front-end system 103 and request a search by entering information into a search box. External front-end system 103 may request information from one or more systems in network 100 . For example, the external front-end system 103 may request results from the FO system 113 that satisfy the search request. External front-end system 103 is also available (from FO system 113) Request and receive the 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 specific time period (eg, by the end of the day (11:59 PM)). (PDD is discussed further below with respect to FO system 113.)

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

The user device may then select a product represented on the SRP, such as by clicking or tapping the user interface or using another input device to select a product from the SRP. The user device can formulate and send a request for information about the selected product to the external front-end system 103 . In response, the external front-end system 103 may request information related to the selected product. For example, the information may include additional information in addition to the information presented for the products on the respective SRP. This can 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 for similar products (based on, for example, large amounts of 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, Figure 1C). SDP can also contain other interactive elements, such as "Buy Now" buttons, "Add to Cart" buttons, quantity columns, and images of objects. Like, or similar. The external front-end system 103 may deliver the SDP to the requesting user device (eg, via a network).

Requests that the user device can receive an SDP listing product information. After receiving the SDP, the user device can then interact with the SDP. For example, a user of the requesting user device may click or otherwise interact with an "Add to 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 the product to the shopping cart to the external front-end system 103.

The external front-end system 103 may generate a shopping cart page (eg, Figure ID). In some embodiments, the shopping cart page lists products that the user has added to the 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 products that the user has added to the shopping cart, as well as information about the products in the shopping cart (such as the quantity of each product, the price of each item of each product, and the price of each item in the shopping cart). product price based on associated quantity), information about the PDD, delivery method, shipping cost, user interface elements for modifying products in the shopping cart (e.g., deleting or modifying quantities), for ordering additional products or setting up products options for recurring delivery, an option to set up interest payments, a user interface element to advance to a purchase, or the like. The user at the user device may click on or otherwise interact with a user interface element (e.g., a button that says "Buy Now") to initiate a purchase of the products in the shopping cart. Purchase. After doing so, the user device may transmit the request to initiate a purchase to the external front-end system 103.

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

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

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

In some embodiments, 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 embodiments where the network 101 enables a presentation of the system to allow users to place orders for items, the internal front-end system 105 may perform actions to enable internal users to view diagnostic and statistical information about orders, modify item information, or Web servers that review 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, internal front-end system 105 may be configured to receive and process requests from systems or devices depicted in network 100 (and other devices not depicted), retrieve data from databases, and other data based on those requests. The repository obtains information and provides a response to the receiving Requested custom web server software.

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

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

In some embodiments, some users may use one type of mobile device (e.g., a permanent worker may use a dedicated PDA with customized hardware such as a barcode scanner, stylus, and other devices), while others may use Workers may use other types of mobile devices (e.g. temporary workers or shift workers may use readily available mobile phones and/or smartphones).

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

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

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

In some embodiments, shipping and order tracking system 111 may request and store information from 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 be from one or more mobile devices 107A associated with one or more of a user (e.g., a delivery worker) or a vehicle (e.g., a delivery truck) to a mobile device 107C (e.g., a delivery truck) , mobile phone, smart phone, PDA or similar) to receive information. In some embodiments, the shipping and order tracking system 111 may also request information from a warehouse management system (WMS) 119 to determine the location of individual packages within a fulfillment center (eg, fulfillment center 200). Shipping and order tracking system 111 may request data from one or more of shipping system 107 or WMS 119, process the data upon request, and present the data to devices (e.g., user device 102A and user device 102A). 102B).

In some embodiments, fulfillment optimization (FO) system 113 may be implemented as a computer system that stores information about 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 specific 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 only Store a specific collection of items (for example, fresh produce or frozen products). The FO system 113 stores this information and associated information (eg, quantity, size, receipt date, expiration date, etc.).

The FO system 113 may also calculate the corresponding PDD (Promised Delivery Date) for each product. In some embodiments, PDD may be based on one or more factors. For example, the FO system 113 may calculate the PDD for a product based on past demand for the product (e.g., how many times the product has been ordered over a period of time), expected demand for the product (e.g., forecasts for the product in the near future). how many customers will order the product during an upcoming period), network-wide past demand indicating how many products have been ordered during a 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, expected or current orders for the product, or the like.

In some embodiments, the FO system 113 can determine the PDD of each product periodically (eg, every hour) 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 calculate PDD on demand.

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

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

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

In some embodiments, WMS 119 may store a link between one or more devices (e.g., device 107A through device 107C or device 119A through device 119C) and one or more users (the one or more users are associated with the network). 100 related) related information News. For example, in some situations, a user (such as a part-time or full-time employee) may be associated with a mobile device because the user owns the mobile device (eg, the mobile device is a smartphone). In other situations, a user may be associated with a mobile device because the user has custody of the mobile device temporarily (e.g., the user gets the mobile device at the beginning of the day, will use the mobile device during the day, and will use the mobile device during the day). The mobile device is returned at the end of the day).

In some embodiments, WMS 119 may maintain a log of work for each user associated with network 100. For example, WMS 119 can store information associated with each employee, including any specified process (e.g., unloading from truck, picking items from picking area, rebin wall work, packing items), usage The user identifier, location (e.g., floor or zone in fulfillment center 200), number of units moved by the employee through the system (e.g., number of items picked, number of items packed), and device (e.g., device 119A to 119C) associated identifiers, or the like. In some embodiments, WMS 119 may receive check-in and log-out information from a timekeeping system, such as a timekeeping system operating on device 119A through device 119C.

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

In some embodiments, 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 requiring a second login process. obtain their privileges under the circumstances. In other embodiments, FC Auth 123 may enable users (eg, employees) to associate themselves with specific tasks. For example, some employees may not have electronic devices (such as device 119A-119C) and may actually move within fulfillment center 200 from task to task and zone to zone during the course of a day. FC Auth 123 can be configured to enable employees to indicate what tasks they are working on and where they are located at different times of the day.

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

The specific configuration depicted in Figure 1A is an example only. For example, although FIG. 1A depicts FC Auth system 123 connected to FO system 113 via FMG 115, not all embodiments require this specific configuration. Indeed, in some embodiments, 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, Network; WAN), Metropolitan-Area Network; MAN), wireless network compliant with IEEE 802.11a/b/g/n standards, leased lines, or similar. 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.

Figure 2 depicts a fulfillment center 200. Fulfillment center 200 is an example of a physical location that stores items for shipment to customers upon 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 different stages of the process of receiving an object, storing an object, retrieving an object, and shipping an object. Thus, although "zones" are depicted in Figure 2, other zone divisions are possible, and in some embodiments the zones in Figure 2 may be omitted, duplicated, or modified.

Inbound area 203 represents the area of FC 200 that receives items from sellers wishing to sell products using network 100 from Figure 1A. For example, the 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.

The worker will receive the object in the inbound area 203 and may optionally check the object for damage and correctness using a computer system (not depicted). For example, a worker may use a computer system to compare the quantities of items 202A and 202B to the ordered quantities of the items. If the quantities do not match, the worker may reject one or more of item 202A or item 202B. If the quantities do match, workers can move the items to buffer 205 (using, for example, a dolly, a trolley, a forklift, or manually). Buffer 205 may be a temporary storage area for items that do not currently need to be in the picking area (eg, because there is a high enough number of items in the picking area to meet forecast demand). In some embodiments, the forklift 206 operates to unload cargo around the buffer zone 205 and in the inbound zone 203 Move objects between areas 207. If item 202A or item 202B is needed in the picking area (eg, due to forecasted demand), a forklift may move item 202A or item 202B to unloading area 207 .

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

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

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

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

Packaging area 211 may be the area where items are received by the pick-to-pick area 209 of FC 200 and packed into boxes or bags for final shipment to the customer. In the packing area 211, the worker assigned to receive the items (the "merging worker") will receive the items 208 from the picking area 209 and determine which order the item 208 corresponds to. For example, the convergence worker may use a device such as computer 119C to scan a barcode on item 208. Computer 119C can visually indicate which order item 208 is associated with. This may include, for example, the spaces or "cells" on wall 216 that correspond to the order. Once the order is complete (for example, because the cell contains all items for the order), the merging worker can instruct the packaging worker (or "packer") that the order is complete. Packers can obtain items from cells and place the items in boxes or bags for shipping. The packer may then send the boxes or packages to hub zone 213, such as via forklift, cart, dolly, hand truck, conveyor belt, manually, or otherwise.

Hub area 213 may be the area of FC 200 that receives all boxes or packages ("packages") from packaging area 211 . Workers and/or machines in hub area 213 can obtain packages 218 and determine which part of the delivery area each package is intended to go to, and deliver the package 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 a package (eg, using one of devices 119A through 119C) to determine its final destination. Delivering the package to the camp area 215 may include, for example, determining a portion of the geographic area to which the package is destined (eg, based on a zip code) 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 where 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 a package 220 should be associated with, for example based on comparison of the destination to existing routes and/or sub-routes, a comparison of each route and/or sub-route, Calculations of workload for routes and/or sub-routes, timings, shipping methods, costs of shipping package 220, PDDs associated with items in package 220, or the like. In some embodiments, a worker or machine may scan a package (eg, using one of devices 119A through 119C) to determine its final destination. Once a package 220 is assigned to a specific route and/or sub-route, workers and/or machines can move the package 220 for delivery. In illustrative Figure 2, camp area 215 includes trucks 222, cars 226, and delivery workers 224A and 224B. In some embodiments, truck 222 may be driven by a delivery worker 224A, who is a full-time employee delivering packages for FC 200, and truck 222 is owned, leased, or operated by the same company that owns, leases, or operates FC 200. In some embodiments, car 226 may be driven by delivery worker 224B, where the delivery worker Person 224B is a "flexible" or temporary worker who delivers on an as-needed basis (e.g., seasonally). Car 226 may be owned, rented, or operated by delivery worker 224B.

Figure 3 shows an exemplary schematic diagram of a computer implementation system 300 for unitized package delivery. In some embodiments, system 300 may include a consolidation worker 301 , a picked item 208 having an order identifier 305 (eg, barcode, tag, label), a user interface device 302 (eg, mobile device/PDA 119B) . The system 300 may further include: a first storage location 320 (eg, packaging area 211) including storage cells 324 (eg, storage cell 324_1, storage cell 324_2), a second storage location 340 (eg, storage cell 344). Referred to herein as the campground), and the delivery truck 201. The first storage location 320 and camp 340 (eg, camp area 215) may sort items based on different information related to the final destination. As an example, at first storage location 320, items (eg, items 208) may be sorted based on the geographic area to which the package is destined (eg, based on zip code), and at campground 340, items may be sorted (eg, based on route ) to sort items based on delivery routes or sub-routes. (Other sorting methods are also possible.) Delivery routes or sub-routes may be system scheduled by one or more computers of system 100 . In some embodiments, one or more systems of computer execution system 100 (eg, SAT 101, WMS 119, SCM 117) may be configured to communicate with user interface device 302 to direct the sorting of objects.

Figure 3 illustrates an exemplary unitized package delivery system. As used herein, the term "singleization" refers to a single shipment of an item from a customer order that includes multiple items without waiting for the customer order to be fully fulfilled prior to shipment. By unifying package delivery there can be numerous advantages over existing systems for package delivery. Delivery via unitized packages may have some or all of the advantages discussed herein, as well as other advantages.

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

ii. Increase picking density - In the current existing package delivery system, pickers can pick items in order to fulfill customer orders. For example, a picker can pick all items in order 1 before picking items in order 2. This sequential path of picking results in time and efficiency losses as the picker spends more time transitioning than picking items. In contrast, the unified package delivery system 300 may allow for increased picking density because pickers may be tasked with picking items based on their location and not based on customer orders. For example, a picker can 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 increases picking density by reducing the time spent by pickers on transitions.

iii. Improved traceability - As shown in Figure 3, in a unified package delivery system 300, a worker (e.g., worker 301) can scan and package (e.g., package 208) Associated barcode (eg, order identifier 305 and/or location identifier). Additionally, barcodes can be scanned periodically during the process or after receiving a prompt. Information recorded, such as by scanning, may be stored in a database of the system 100, allowing tracking of packages as they undergo processing. Barcodes on containers or totes can also be scanned to provide information associated with the location of items contained in the container during the picking, sorting, packaging, shipping, etc. processes, allowing container and package traceability.

iv. Faster sorting - After receiving items at a camp (e.g., camp area 215) from the packing area, the 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 the items belong, the storage period of the items can be reduced, thus improving the sorting speed. This also enables better space utilization, improved worker efficiency, reduced cycle times and an enriched customer experience.

v. Reduce storage time - Singularization of items allows for a reduction in the duration of time 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 in the order said object. Reduced storage time for items reduces the associated costs associated with inventory management and reduces the risk of mishandling and misplacement of items.

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

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

In some embodiments, system 100 may be configured to receive customer orders. Customer orders 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, toothbrushes and mouthwash, the second sub-order may include regular delivery of cheese, biscuits and chips, and the third sub-order may include delayed delivery of beverages. System 100 may receive customer orders and generate an order identifier 305 associated with each of the items ordered. In some embodiments, the system 100 may generate a unique sub-order identifier associated with each sub-order (e.g., sub-order identifier 305a for a first sub-order, sub-order identifier 305a for a second sub-order 305b, and the sub-order identifier for the third sub-order).

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

In some embodiments, one or more pickers may receive an indication regarding the urgency of a sub-order when retrieving items from other customer orders. The picker can retrieve the items for the emergency sub-order based on his or her current location within the picking area 209 and place the items in the order. The pieces are sent forward to packaging area 211. For example, if the emergency sub-order includes a toothbrush and a pair of socks, a picker in or near the oral hygiene section can get the toothbrush, and a picker in or near the apparel section can pick up the toothbrush. The clerk can obtain the pair of socks, thereby improving picking density. Once the container or tote is full, the items can be transported to the packaging area 211. This approach improves picking efficiency by picking items based on the picker's location and not based on customer orders, thereby reducing cycle times and improving overall delivery efficiency.

In some embodiments, the system 100 may send instructions to the user device (eg, smartphone 119B, or computer 119C) such that the device instructs the picker to print the order identifier 305 . In some embodiments, the user device may include a handheld device, such as a PDA, configured to print indicia. Alternatively, system 100 may include a printing device (not depicted) such as a mark printer, an inkjet printer, or a laser printer. The printing device may be configured to receive instructions to print tags, instructions, memos, or the like from one of the computer execution systems of system 100 . The instructions may further include requesting the picker to associate the printed order identifier 305 with an item of the customer order, such as by affixing the printed order identifier 305 to the picked item 208 . In some embodiments, system 100 may be configured to electronically associate order identifier 305 with items of a customer order. For example, system 100 may update a database that includes information related to all incoming customer orders.

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

In some embodiments, user interface device 302 may be configured to display information on a user interface display (not shown in Figure 3). The user interface display may include information including information related to the customer's order, such as the number of items ordered, the urgency of delivery of the items ordered, the destination location of the items to be delivered, etc. In some embodiments, the user interface display may be a visual display or an audiovisual display. For example, if the order is "urgent," user interface device 302 may receive an audio-visual message indicating a request to expedite fulfillment of the order. In some embodiments, user interface device 302 may be configured to receive user input and provide feedback to the user via one or more interactive elements of the user interface display. For example, user interface device 302 may provide audio, visual, or tactile notifications to the user via one or more interactive elements of the user interface display and indicate a request to confirm receipt of the notification. In some embodiments, 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 the logged information and later upload it to a database in one of the computer execution systems of system 100 . In some embodiments, the user interface device 302 can automatically upload the recorded information to the database.

In some embodiments, the user interface device 302 may receive instructions instructing 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 execution systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may interface to the user The device 302 generates a display instructing the user to begin reviewing the order identifier 305 associated with the item 208 . Reviewing the order identifier 305 may include determining the final destination of the 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 may display information associated with the order identifier, such as the final destination of the items in the order, the urgency of delivery, the number and description of the items ordered wait. In some embodiments, a customer order may include several sub-orders and each sub-order may further include several items. It should be understood that items 208 may include a package containing one or more items of the customer's order.

After determining the final destination for delivery of item 208, merge worker 301 may place item 208 in first storage location 320 based on the determined final destination. First storage location 320 may include storage cells 324 . Each storage cell 324 of first storage location 320 may be associated with a sorting location. In some embodiments, first storage location 320 may include a confluence wall, a storage unit, a storage rack with cells, or a cabinet. Storage means from other organizations may also be used.

In some embodiments, items 208 may be sorted into storage cells 324 of first storage location 320 based on the destination of items 208 without regard to the status of the order or other items of the order that may be associated with the items. . In the current existing system, a merge 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 other items in the order. This reduces idle time for merging workers, thereby increasing packaging efficiency. In some embodiments, packaging efficiency as disclosed herein may be referred to as the number of items packaged in a specific time period. For example, packaging efficiency can be expressed in units per hour (UPH). Other efficiency measures can also be used. list of objects Unification also reduces the shelf life of an item (defined here as the duration an item remains on a shelf before it is picked, packed, sorted or shipped), thereby reducing the associated costs associated with inventory management and Reduce the risk of mishandling and misplacement of items.

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

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

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

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

In some embodiments, storage cells 324 may contain one or more items to be transported to the corresponding campsite. In some embodiments, a campsite may be referred to as a storage location. For example, camp 340 may be associated with storage cell 324_1, indicating that objects (eg, object 208) placed in storage cell 324_1 may be 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, a wall with storage cells, a storage unit, a storage shelf with cells, or a cabinet. Storage means from other organizations may also be used. For example, storage space 342 may include a wall with storage cells 344 . Each storage cell 344 may be associated with a sub-route for delivery of items 208 .

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

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

In some embodiments, the user interface device 302 may instruct the worker 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 execution systems of system 100 (eg, WMS 119, SCM 117, or SAT 101) may determine the storage cell 344 to which the object 208 may be directed. The worker may place the object 208 in the corresponding storage cell 324 based on instructions from the user interface device 302 .

The sub-route identifier may 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, markers, barcodes, numbers, or labels. Although only a limited number of storage cells 344 are shown, it should be understood that campground 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 for the final destination of delivery without regard to the status of the order or other items of the order that may be associated with the item. middle. In currently 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 other items of the order. . This reduces the idle time of sorters in the camp area, thereby increasing sorting efficiency and overall package delivery efficiency.

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

In some embodiments, each storage cell 344 may be associated with a container 350 (eg, a handbag). All items of storage cell 344 (eg, items 208) may be placed in container 350. In some embodiments, container 350 may be identified using container identifier 355. Container identifier 355 may include information associated with the sub-route including the sub-route identifier. In some embodiments, container identifier 355 may include information related to campsites and sub-routes. For example, the container identifier may include tag CS3_SR1, where CS indicates a starting camp and SR indicates a designated sub-route for delivering the items in the container. 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 that the object 208 is placed in the corresponding container 350 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 the container 350 in which the item 208 may be placed. The worker may place the object 208 in the corresponding container 350 based on instructions from the user interface device 302 .

In some embodiments, user interface device 302 may be configured to display instructions associating object 208 with the corresponding container 350 in which object 208 is placed via one or more interactive elements of the user interface display. For example, the instructions may include a request to scan the order identifier 305 and the container identifier 355 to establish an association between the item 208 and the 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 was placed may be automatically updated to include information related to the customer order and A database of delivery schedules for customer orders.

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

Containers 350 may be placed on container carrier 360 before being loaded into delivery truck 201 . Container carrier 360 may include a cart, trolley, cage, basket, or the like. In some embodiments, container carrier 360 may include an identifier such as a barcode, tag, or label. In some embodiments, user interface device 302 may notify a delivery worker or truck loader via instructions to place container 350 on delivery truck 201 based on a predetermined configuration. For example, based on the PDD, one of the computer implementations of system 100 (eg, transportation system 107) may determine the configuration of containers 350 on container carriers 360 or the configuration of one or more container carriers 360 on delivery trucks 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 implementation systems of the system 100 (eg, the transportation system 107). The user interface device 302 may indicate to a delivery worker or truck loader the configuration of the containers 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, user interface device 302 may be configured to display Representation of configured container 350 and one or more container carriers 360 in delivery truck 201 . The format of the presentation may include 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 worker's delivery truck 201 .

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

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

Overall package delivery efficiency is a measure that relies on the efficiency of each step in the package delivery process. Shipping a package from FC to a customer to fulfill an order typically involves multiple steps, and most of these steps must occur in a linear subsequent order. For example, picking may precede order receipt and order identifier generation, sorting may precede picking, packaging may precede sorting, loading items onto delivery trucks may precede packaging, etc. In other words, each step of the process is initiated by the completion of the previous step. In this type of process flow, the overall efficiency of the process is determined by the efficiency at each step. Overall efficiency can be improved by increasing the efficiency of each step or by increasing the efficiency of at least one step while maintaining the efficiency of other steps. As discussed above, the “single "Packaging" refers to the single shipment of items from a customer order that includes multiple items without waiting for the customer order to be fully fulfilled before shipping. It can improve packaging by reducing cycle time and reducing the idle time of employees involved in the process. Delivery efficiency. In some embodiments, one or more steps of process 400 may be performed by one or more user interface devices (eg, each user interface device is operated by a user in a different zone of FC 200).

In step 410, one or more computer execution systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) may receive the customer order. Customer orders 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 implementations 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 requested delivery time, the final date of the items, Destination etc. In some embodiments, one or more computer implementations 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 an urgent order request from a customer, the system can determine a promised delivery time of a few hours or within 24 hours to the intended final destination. In some embodiments, the system may be configured to individually determine the promised delivery date and time for each of the items of a customer order. For example, a customer order may include some items for emergency delivery and remaining items for regular delivery. The system can be configured to determine the promised delivery time based on the type of delivery requested.

In some embodiments, one or more computer execution systems (eg, WMS 119, SCM 117, SAT system 101) of system 100 may receive multiple customer orders. Each of the customer orders may include multiple items. One or more computer execution systems of system 100 may be configured to review and identify common items among multiple customer orders. The user interface device can be configured to display instructions regarding common objects, thereby requesting input from the user, such as receiving confirmation. Instructions may include information related to a description of the item, the quantity of the item ordered, and the like. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders contain a common item, such as a bottle of water. A worker (eg, a picker) can receive an instruction to pick up 50 bottles of water via the user interface device. The implementation of this approach can improve picking efficiency and the overall efficiency of the process.

In step 420, one or more computer implementations of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. The order identifier may include a barcode, a mark, a label, an alphanumeric code, a quick response (QR) code, or the like. The order identifier may be a machine-readable optical tag 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, etc. In some embodiments, the system that generates the order identifier may determine the storage location (eg, camp area 215, hub area 213) and delivery route to which the items in the customer order may belong based on the final destination information of the customer order. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or district identified in the final destination, the system can determine the delivery location for the items in the customer order. route.

After scanning or reading the order identifier, such as 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 can display the number of items picked, the number of items remaining to be The number of items picked, the promised delivery time, and the time remaining to fulfill the order.

In step 430, one or more computer execution systems of system 100 may instruct the user interface device to display instructions associating each item of the customer order with an order identifier. The user interface device may be configured to display instructions or alerts regarding received customer orders, thereby requesting input from the user, such as confirmation of receipt. 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 (e.g., a picker) can pick one or more items from a customer order and, for example, by scanning an order identifier and a barcode on the item, each picked item can be compared to one or more computers. The order identifier received by the system is associated with it. In some embodiments, associating the items of the customer order with the order identifier may include physically printing the order identifier using a mark printer or barcode printer. Printed tags or barcodes can, for example, be attached or affixed to the item to allow all employees to easily access information associated with the order and delivery schedule. For example, workers who did not receive or have access to the initial order identifier may be able to scan the order identifier printed and attached to the object.

In step 440, one or more computer execution systems of system 100 may determine the expected final delivery destination of 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 8pm and a pack of batteries to be delivered to his parents' house within 24 hours. One or more computer implementations of system 100 may generate two separate order identifiers representing the two orders. Each of the items may be directed to the storage location and sorted into a delivery route at the storage location based on the expected final destination.

In some embodiments, one or more computer execution systems of system 100 may determine the intended delivery destination, the storage space associated with the intended delivery destination (e.g., For example, in storage cell 324/storage cell 344), and a delivery route to deliver the items of the customer order at the intended delivery destination.

In some embodiments, the sorting process may be a two-step sorting process. The first step may include sorting the picked items based on campsites to which they can be directed. The campsite may be determined based on, for example, the postal code of the expected final delivery destination of the item in the customer's order. The second step may include sorting the picked items in the camp based on delivery routes to which the items can be sent for delivery. The delivery route may be determined based on, for example, a district or street represented by a postal code within the area.

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

Each of the sorted objects 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 a transportation device such as, for example, a conveyor belt, forklift, hand truck, trolley, or cart. In some embodiments, the campground may be an off-site storage facility, such as a warehouse or 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. Available at Reduce idle time by transporting sorted items belonging to the customer's order to the camp without waiting for the remaining items of the customer's order.

In step 460, one or more computer execution systems of system 100 may send instructions to the user interface device to display instructions or alerts for sorting the picked items in the camp based on the delivery route. Delivery routes may be scheduled by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer order. Workers can sort picked items in the camp by placing the items in storage cells (eg, storage cell 344) based on delivery routes. Workers can obtain delivery route information by, for example, scanning order identifiers on items. Each of storage cells 344 may be identified by a route identifier or sub-route identifier.

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

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, dolly, etc. Containers may be loaded in a manner that reduces unloading time during item delivery based on, for example, the configuration of the delivery route. The configuration of containers on a delivery truck may also be based on factors including, but not limited to, the urgency of the delivery, promised delivery time, whether the item is a perishable food item, etc. In some embodiments, the delivery truck's storage compartment may include built-in storage Storage spaces such as cabinets, cells, shelves, racks, cages or wheeled cages. Each container carrier in the delivery truck can be identified by a container carrier identifier (eg, a barcode). The container carrier identifier may include information associated with the location of the container carrier within the storage compartment of the delivery truck. For example, four container carriers 360 may be positioned against the rear wall of the storage compartment, labeled 360_1 to 360_4 from left to right. Thus, a container carrier located in the rear left corner of a storage compartment of a delivery truck may be identified as container carrier 360_1, and a container carrier located in the rear right corner of a storage compartment of a 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 execution systems of system 100, such as transportation system 107.

In some embodiments, the loading configuration of the containers on the container carrier 360 may be recorded to produce a representation of the delivery truck loading configuration. For example, the transportation system 107 may send instructions to the user interface device that display instructions to scan container identifiers (eg, barcodes) of all containers placed in the container carrier and scan corresponding container carrier identifiers. The system can 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 tabular or visual format. The load 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 execution systems of system 100 (such as transportation system 107), for example, may send instructions to display instructions for delivering items stored in containers loaded on delivery trucks to a user interface device (e.g., , one of the mobile devices 107A to 107C). The user interface device may display instructions requesting input from a user (eg, a delivery worker or loader) to verify completion of the loading process before proceeding to deliver the item. The user interface device may receive input from the user and store the received input in a database associated with system 100 .

In some embodiments, one or more computer implementations of system 100 may send instructions to the user interface device that display instructions to record information associated with the order identifier, such as by scanning the order identifier. The user interface device may, after the items have been picked, after the picked items have been sorted based on their storage locations in the first step of the sorting process, before transporting the sorted items to the campsite, after arriving at the campsite, Record order identifier information is displayed after sorting the picked items based on the delivery route in the second step of the sorting process, after placing the sorted items in the container, and after loading the container on the delivery truck. instructions. 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 status update notification messages based on updated information stored in the database in response to inquiries from customers regarding order status. In some embodiments, the system 100 may preemptively generate a status update notification message for the client based on updated information stored in the database.

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

In step 510, one or more computer implementations 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 information. vehicle. For example, the transportation system 107 may identify small delivery vehicles for delivery routes with narrow roads, and the delivery truck worker (eg, truck driver) on duty may only have a valid driving license for small transportation vehicles. In some embodiments, transportation system 107 may identify delivery vehicles based on storage space requirements. For example, if there are 20 containers filled with items to be delivered on one delivery route or sub-route, the system 100 may recommend a larger delivery vehicle 201 that includes more storage space.

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

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

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

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

In step 540, one or more computer execution systems of system 100, such as transportation system 107, may send instructions to the user interface device displaying instructions to load the containers into the storage space of the delivery truck. Quick access to items may be enabled to load containers on delivery trucks in an unloaded manner during delivery.

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

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

In some embodiments, the delivery truck's loading configuration 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 load configuration may be updated when a delivery is completed. For example, when a delivery truck driver delivers an item to a customer and the container is empty, the 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 has been met.

Reference is now made to Figure 6, which is an alternative embodiment of process 400 as discussed above and illustrates additional steps performed during the second step of the sorting process. For example, during the second step of the sorting process, items may be picked on site and based on the final purpose for delivery without regard to the status of the order or other items of the order that may be associated with the item. The object is sorted based on the determined sub-route of the location.

In some embodiments, the sorting process may be a two-step sorting process. The first step may include sorting the picked items based on campsites to which they can be directed. The campsite may be determined based on, for example, the postal code of the expected final delivery destination of the item in the customer's order. The second step may include sorting the picked items in the camp based on delivery routes to which the items can be sent for delivery. The delivery route may be determined based on, for example, a district or street represented by a postal code within the area.

In some embodiments, the missort reduction procedure may be implemented during the second step of the sorting process (ie, when the picked items are sorted based on the delivery route/sub-route in the second step of the sorting process) . For example, when an object is picked up from the camp and placed in When in a container to be sorted based on a delivery route or sub-route, there may be the possibility of items being placed in the wrong container and subsequently on the wrong delivery vehicle. This can make it difficult for delivery truck drivers to search and try to find the right item to the right destination. One or more computer implementations of system 100 may be configured to provide immediate notification or alerts to workers (eg, sorters) 301 when missorts occur, which facilitates detection and reduction of missorts. Reduced missorting helps drivers easily understand items on the map and deliver orders more efficiently.

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

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

In some embodiments, items 208 may arrive at the camp to be sorted into delivery vehicles. The worker 301 may scan the barcode of the item 208 and the order identifier 305 of the customer order. After scanning, the system 100 can obtain information related to the object 208 from the mapping table that can be sent to the worker 301 . This information may include the container 350 into which the object 208 needs to be sorted. The worker 301 may receive instructions from the system 100 specifying the container 350 into which the item 208 needs to be sorted. The worker 301 may then place the object 208 into the container 350 and use the user interface device 302 to scan the container identifier 355 . Information recorded, such as by scanning, may be stored in a database of the system 100, allowing tracking of packages as they undergo processing. A container's barcode (eg, container identifier 355) or a tote's barcode may also be scanned to provide information associated with the location of items contained in the container during the picking, sorting, packaging, shipping, etc. process. In some embodiments, system 100 may maintain a mapping table, which may record all scanned information, such as in a tabular format, such that items 208, order identifiers 305, containers 350, container identifiers 355, and items designated for distribution The identification of the worker 301 selecting the object 208 is associated with the user interface device 302 assigned to the worker 301 . When the worker 301 uses the user interface device 302 to scan the order identifier and sort the container 305 into which the items are sorted, the mapping table can be automatically updated on the fly. In some embodiments, one or more computer execution systems of system 100 may analyze data stored at the beginning of the process using scanned data from worker 301 to determine whether an exception event has occurred. In some embodiments, when the stored information and the scanned information (the scanned information and the item 208, the order identifier 305, the container 350, the container identifier 355, and the worker 301 designated to sort the item 208 and from This may occur when there is a mismatch between one or more of the inputs scanned by worker 301 An exception occurs. In some embodiments, items 208 , order identifiers 305 , containers 350 , container identifiers 355 , and items designated for sorting 208 may be accessed, stored, updated, or modified in one or more databases connected to the system 100 The association between the identity of worker 301.

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

In step 610, one or more computer execution systems of system 100 (eg, WMS 119, SCM 117, SAT system 101) may receive the customer order. Customer orders can include multiple items. In some embodiments, a customer order may include multiple sub-orders. Each sub-order can include multiple items. One or more computer implementations 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 requested delivery time, the final date of the items, Destination etc.

In step 620, one or more computer implementations of system 100 may generate an order identifier (eg, order identifier 305) based on the received customer order. Order identifier 305 may include a barcode, tag, label, alphanumeric code, quick response (QR) code, or the like. Order identifier 305 may be a machine-readable optical mark containing information about the customer's order. The information contained in the order identifier 305 may include, but is not limited to, the final destination of the order, the total number of items in the customer's order, the requested delivery type, customer information, promised delivery date and promised delivery time, etc.

In some embodiments, the system 100 that generates the order identifier can determine the storage location (eg, camp area 215, hub area 213) and delivery route to which the items in the customer order may belong based on the final destination information of the customer order. or sub-route. For example, based on the zip code of the final destination, the system can determine the storage location of the items in the customer order, and based on the street or district identified in the final destination, the system can determine the delivery location for the items in the customer order. route.

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

In step 630, one or more computers of system 100 executing the system may use Each item of a customer order is associated with an order identifier 305. User interface device 302 may be configured to display instructions or alerts regarding received customer orders, thereby requesting input from a user (eg, worker 301), such as confirmation of receipt. After receiving input from the user, user interface device 302 may display some or all of the customer order and information associated with the customer order. A worker 301 (e.g., a picker) may pick one or more items from a customer order and associate each picked item with a link from one or more computers, such as by scanning the order identifier and a barcode on the item. The execution system associates the order identifier 305 received. In some embodiments, associating the items of the customer order with the order identifier may include physically printing the order identifier using a mark printer or barcode printer. Printed tags or barcodes can, for example, be attached or affixed to the item to allow all employees to easily access information associated with the order and delivery schedule. For example, workers who did not receive or have access to the initial order identifier may be able to scan the order identifier printed and attached to the object.

In some embodiments, a worker 301 (eg, a sorter) assigned to sort the items will receive the items 208 and determine which customer order the items 208 correspond to. For example, worker 301 may use a device, such as user interface device 302, to scan a barcode on object 208. As the worker 301 scans the item 208, one or more computer execution systems of the system 100 determine the container 350, the container identifier 355, and the identity of all items in the customer order for sorting based on the determined final destination of the item. Route or sub-route. Items 208 may be sorted based on delivery routes or sub-routes. Delivery routes or sub-routes may be system scheduled by one or more computers of system 100 . In some embodiments, one or more systems of computer execution system 100 (eg, SAT 101, WMS 119, SCM 117) may be configured to communicate with user interface device 302 to direct the sorting of objects.

In step 640, one or more computer execution systems of system 100 may determine the expected final delivery destination of each of the items of the customer order. In some embodiments, one or more computer execution systems of system 100 may determine the intended delivery destination, the storage space container (e.g., storage cell 324/storage cell 344) associated with the intended delivery destination, the grouped Containers 350 are configured to hold items stored in corresponding storage cells, and a delivery route is used to deliver the items of the customer order at the intended delivery destination.

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

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

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

In step 660, one or more computer execution systems of system 100 may display instructions or alerts for sorting the picked items of the customer order based on the pre-designated storage space (e.g., storage cell 324 of storage location 320). Instructions are sent to the user interface device, and the pre-designated storage space is determined by one or more computers of the system 100. Pre-assigned storage spaces can represent campsites to which items can be directed for further sorting. In some embodiments, one or more storage spaces may be designated as campsites. For example, storage space 1 through storage space 12 may be designated as campground 1 represented by storage cell 324_1, and storage space 13 through storage space 23 may be designated as campground 2 represented by storage cell 324_2, and storage space 1 through storage space 23 may be designated as campground 2 represented by storage cell 324_2. Storage space 24 is designated as storage unit by Camp 3 represented by grid 324.

Each of the sorted objects 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 a transportation device such as, for example, a conveyor belt, forklift, hand truck, trolley, or cart. In some embodiments, the campground may be an off-site storage facility, such as a warehouse or 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 the customer order can be transported to the camp to reduce idle time without waiting for the remaining items of the customer order.

In step 670, one or more computer implementations of the system 100 may display the sorting of the picked items in the campsite based on the delivery route and place the sorted items from the storage unit 344 into containers (e.g., The instruction or warning command in the container 350) is sent to the user interface device. Delivery routes may be scheduled by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer order. Workers can sort picked items in the camp by placing the items in storage cells (eg, storage cell 344) based on delivery routes. Workers can obtain delivery route information by, for example, scanning order identifiers on items. Each of storage cells 344 may be identified by a route identifier or sub-route identifier. Each storage cell 344 may be associated with a container configured to accommodate items stored in the corresponding storage cell. In some embodiments, after receiving input from the user (eg, a scanned order identifier), user interface device 302 may display some or all of the customer order and information associated with the customer order. A worker 301 (e.g., a sorter) may sort and order identification based on the container identifier 355 received from one or more computer execution systems, such as by scanning the order identifier 305 and a barcode on the item 208 Identifier 305 is associated with one or more items of the customer order in container 350 . Items/items can be placed in containers to reduce idle time without waiting for remaining items from the same customer order.

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

In step 680, one or more computer implementations of system 100 may compare the scanned order identifier 305 and the container identifier 355 of the container 350 in which the item is placed with information for the same customer order stored in the mapping table. Determine whether an exception event has occurred. In some embodiments, as explained above, when the stored information is combined with the scanned information (said scanned information and the item 208, the order identifier 305, the container 350, the container identifier 355, and the item designated for sorting the item 208 Exceptions may occur when there is a mismatch between worker 301 and one or more of the scanned inputs from worker 301 (relevant). For example, worker 301 may sort item 208 into the wrong container (i.e., a container not intended for item 208), in which case the difference between order identifier 305 and container identifier 355 may be detected. mismatch between them, so exceptions may occur.

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

In step 690, one or more computer execution systems of the system 100 send a notification to the user interface device 302 that the exception event has occurred. In some embodiments, notifications may be displayed on the screen of user interface device 302. The displayed notification can contain the misscan criteria for which the exception event occurred. In some embodiments, notifications may be sent to and displayed by user interface device 302 immediately. In some embodiments, user interface device 302 may trigger an alert or warning message when receiving a notification for an exception event. In some embodiments, notifications may be displayed on large surveillance screens in the camp area, campsite, or any other area within the fulfillment center. This alerts the floor manager/supervisor to notify the individual sorter/worker in error when an exception occurs.

In some embodiments, worker 301 may receive reports on user interface device 302. One or more computer execution systems of system 100 may execute applications including host application software or native application software. When an exception event occurs, the system 100 may display a notification on the dashboard via a large monitoring screen in one or more of the picking area, packing area, hub area, camp area, or any other area within the fulfillment center. System 100 may send a notification to user interface device 302 that an exception event has occurred. In some embodiments, system 100 may provide workers 301 with tools to use Multiple channels for delivering notifications or alerts on the user interface device 302 include, but are not limited to, text messages, SMS, mobile phone calls, or in-app notifications. Notifications may appear on user interface device 302 in the form of an icon, a badge on an application's icon, a status bar format, a report or table format, or as a more detailed message on user interface device 302 .

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

In some embodiments, the exception event may occur when worker 301 scans an incorrect container (or tote). For example, worker 301a may place object 208 Place in the container associated with container identifier CS3_SR1_a, but scan an unrelated container, that is, the container associated with container identifier CS3_SR1_b. In this case, the system 100 may compare the scanned data to the data stored in the mapping table and determine that a false match may exist. The mapping table may contain data having an association between the order identifier 305a and the container identifier CS3_SR1_a that is different from the scanned data and for which exception events may occur.

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

In some embodiments, an exception may occur when worker 301a may miss scanning a container after scanning an order identifier. For example, worker 301a may place item 208 in the container associated with container identifier CS3_SR1_a, but scan a different order identifier 305b or scan again a previous order identifier, such as order identifier 305a. In this case, the system 100 may determine that an exception may exist due to a missed container (or tote) scan.

In some embodiments, exceptions may occur when worker 301 may miss scanning the next order identifier. For example, worker 301a may scan order identifier 305a and place item 208 in the container associated with container identifier CS3_SR1_a. After this, worker 301a may scan again to identify the container. Container associated with identifier CS3_SR1_a instead of scanning order identifier 305b. In this case, the system 100 may determine that an exception may exist due to a missed invoice scan.

Although the present disclosure has been illustrated and described with reference to specific embodiments of the present disclosure, it is to 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 become apparent to those skilled 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 understand that such aspects may also be stored on other types of computer-readable media, such as level storage device, such as a hard drive or CD ROM, or other form of RAM or ROM, USB media, DVD, Blu-ray, or other optical drive media.

Computer programming based on the written description and disclosed methods is within the skill of an experienced developer. 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, program sections or program modules may be implemented using the .Net Framework, the .Net Compact Framework (.Net Compact Framework), and related languages such as Visual Basic, C, etc. ), Java (Java), C++, Objective-C (Objective-C), HTML, HTML/AJAX combination, XML or HTML containing Java applets.

Furthermore, although illustrative embodiments have been described herein, those of ordinary skill in the art will recognize, based on this disclosure, that there are equivalent elements, modifications, omissions, combinations (eg, aspects of the various embodiments) , adaptation and/or change of any and the scope of all embodiments. Limitations in a claim are to be construed broadly based on the language employed in the claim and are not limited to the 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 modifications in any manner by reordering steps and/or inserting or deleting steps. Therefore, it is intended that the specification and examples be considered illustrative only, with the true scope and spirit being indicated by the full scope of the following claims and their equivalents.

600:Process

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

Claims (10)

A computer-implemented method for generating a visual representation of a delivery vehicle's loading configuration on a delivery route, comprising: identifying a delivery vehicle that includes at least one storage space; determining a storage space identifier for each storage space; and generating a container for at least one container. identifier; sending a load instruction displayed on the user device, wherein the load instruction displays an instruction to load at least one container associated with at least one container identifier to the storage based on the determined storage space identifier. space; associating each container with the storage space in which it is placed based on the loading instructions; generating a visual representation of the loading configuration of the container and the storage space based on the association; and based on the association determination Whether an exception event has occurred, and upon determining that the exception event has occurred, an updated visual representation of the load configuration indicating the exception event is generated. The method of claim 1, wherein the method further includes identifying the portion of the delivery route based on at least one of storage space requirements, delivery route characteristics, delivery truck worker experience, or delivery truck worker classification. Delivery vehicle. The method of claim 1, wherein the container identifier includes at least one of a barcode, a mark, a label, or a QR code. The method of claim 1, wherein the storage space further includes a built-in storage space. The method of claim 1, wherein the method further includes: determining whether to recommend a second delivery vehicle that is larger than the delivery vehicle based on the container identifier and the storage space identifier. The method of claim 1, wherein the method further includes: receiving step-to-step instructions to associate a container with the storage space identifier and uploading the instructions to a database. The method of claim 1, further comprising: sending the loading configuration in a tabular or visual format for display on a user device. The method of claim 7, upon delivery of an object associated with the determined storage space identifier, updating the visual representation of the load configuration to indicate association with the determined storage space identifier The associated container is empty. The method of claim 8, wherein the method further includes: uploading the loading configuration to a database; and determining whether the promised delivery date is met based on the empty container identifier. A computer-implemented system for generating a visual representation of a loading configuration of a delivery vehicle, the system comprising: a memory storage for storing computer-executable instructions; and one or more processors configured to execute the instructions To execute one or more of the methods described in claim 1 to claim 9.

Images