Computerized system and method for delivering decision-based large order consolidation
The package delivery system implemented by computers improves the parcel delivery efficiency of the fulfillment center using order identifiers and sorting processes, solves the problem of inefficiency of the existing system, and achieves faster delivery and higher customer satisfaction.
Patent Information
- Application Number
- CN202011624610.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-07-10
- Filing Date
- 2020-12-31
- Publication Date
- 2025-06-03
- Estimated Expiration
- 2040-12-31
AI Technical Summary
The existing fulfillment centers’ parcel delivery systems are inefficient, resulting in customer dissatisfaction, increased costs and reduced throughput, especially when handling orders for multi-category items.
A computer-implemented package delivery system is used to associate multiple items in a customer's order with the order identifier and determine the expected delivery destination, storage space, delivery route and package count for each item based on the identifier. The system sorts and loads items into containers through the sorting process and delivers items to the final destination according to the delivery route.
Improves efficiency and throughput for package delivery, reduces packaging and delivery time, reduces costs, and improves customer experience.
Smart Images

Figure CN113919766B_ABST
Abstract
Description
[0001] Cross - reference to related patent applications
[0002] This application is a partial continuation of U.S. Patent Application No. 16 / 416,909, filed on May 20, 2019, the entire content of which is incorporated herein by reference. Technical Field
[0003] The present disclosure generally relates to computerized parcel delivery systems and methods for fulfilling customer orders. In particular, embodiments of the present disclosure relate to creative and unconventional computerized systems, methods, and user interfaces for efficiently fulfilling customer orders and delivering parcels with reduced cycle times, reduced packaging costs, and improved customer experiences, while maintaining high worker efficiency in multiple areas within a fulfillment center. Background Art
[0004] Fulfillment centers (FCs) enable e - commerce merchants to outsource warehousing and shipping. Inventory management in fulfillment centers (FCs) is an important part of cultivating the best customer experience for online shoppers. Inventory management can include many steps, which include receiving goods from sellers, storing the received goods for easy picking, packing items, verifying orders, and parcel delivery. Although current existing fulfillment centers (FCs) and the systems used for inventory management in fulfillment centers (FCs) are configured to handle a large volume of incoming and outgoing goods, the efficiency and timeliness of customer order fulfillment may be limited, in part due to inefficiencies in procuring items to fulfill orders. Packaging and delivery delays can lead to customer dissatisfaction and, in some cases, can affect the cost and profitability of the business.
[0005] With the development and widespread acceptance of e - commerce, Internet shopping provides a one - stop shop for all shopping needs, including food, furniture, electronics, clothing, books, etc. Each online order typically contains a large number of different types of items. Although in current existing order fulfillment practices, systems can be employed to obtain each individual item in an order in an efficient manner, the overall efficiency of order delivery is limited by the ability to procure each individual item. For example, items are typically stored in various parts of a fulfillment center (FC) according to category, and packers may need to wait for pickers to pick all the items in an order before packing the items. This can lead to delays in packing and subsequent steps in the process of delivering the parcel to the customer, thereby delaying the system throughput and the efficiency of the computerized system controlling the shipping process.
[0006] In addition, the overall efficiency and throughput of the fulfillment center (FC) may be affected because, although items are picked individually, they are simultaneously packed into a container before being loaded onto a delivery truck as a package. If there is no access to the storage space where the picked items are stored, expected or unexpected packaging delays may affect the picking efficiency. The process of storing and shipping packages from the fulfillment center (FC) involves many steps, such as, at each step, receiving, storing, picking, sorting, packing, loading, delivering, and verifying order accuracy. To achieve high overall efficiency, the efficiency of individual steps must also be high. For example, if the process consists of 10 steps and the efficiency of each step is above 90%, the overall efficiency is only 83.9%.
[0007] In addition, currently existing fulfillment centers (FCs) employ a team of workers to ensure smooth operation around the clock. One of the technical challenges in the warehouse may be the timely communication of information to frontline workers, such as urgent customer orders, priority shipments, etc. The currently existing logistics and inventory management systems lack the ability to effectively address expected or unexpected emergencies in customer orders, which may lead to customer dissatisfaction and increased associated inventory costs.
[0008] Therefore, there is a need to implement improved methods and systems for effective package delivery through singulation to reduce cycle time and committed delivery time while maintaining high overall throughput and utilization of effective resources without negatively impacting the customer experience. Summary of the Invention
[0009] One aspect of the present disclosure relates to a computer-implemented parcel delivery system. The system may include: a memory storing instructions; and at least one processor configured to execute the instructions to: receive, by the computer-implemented system, a customer order; generate, by the computer-implemented system, an order identifier based on the customer order; associate each of a plurality of items of the customer order with the order identifier; determine, based on the order identifier, an expected delivery destination for each item, a storage space associated with the expected delivery destination, a delivery route, and a parcel count; determine whether the order identifier meets a condition; based on a determination that the condition is not met; send a first indication to at least one user device for display to sort each of the plurality of items using a first sorting process based on the storage space associated with the expected delivery destination; receive a first input related to a state of the first sorting process from the at least one user device; send a second indication to at least one user device for display to sort each sorted item using a second sorting process based on a delivery route configured to include the expected delivery destination, regardless of the state of the first sorting process; receive a second input related to a state of the second sorting process from the at least one user device; send a third indication to at least one user device for display to place each sorted item into a container associated with the delivery route, regardless of the state of the second sorting process; and send a fourth indication to at least one user device for display to deliver the placed items of the plurality of items to the expected delivery destination, regardless of the state of other items of the customer order.
[0010] Another aspect of the present disclosure relates to a computer-implemented parcel delivery method. The method may include: receiving, by a computer-implemented system, a customer order; generating, using the computer-implemented system, an order identifier based on the customer order; associating each of a plurality of items of the customer order with the order identifier; determining, based on the order identifier, an expected delivery destination for each item, a storage space associated with the expected delivery destination, a delivery route, and a parcel count; determining whether the order identifier meets a condition; based on a determination that the condition is not met; sending a first indication to at least one user device for display to sort each of the plurality of items using a first sorting process based on the storage space associated with the expected delivery destination; receiving, from the at least one user device, a first input related to the state of the first sorting process; sending a second indication to at least one user device for display to sort each sorted item using a second sorting process based on a delivery route configured to include the expected delivery destination, regardless of the state of the first sorting process; receiving, from the at least one user device, a second input related to the state of the second sorting process; sending a third indication to at least one user device for display to place each sorted item into a container associated with the delivery route, regardless of the state of the second sorting process; and sending a fourth indication to at least one user device for display to deliver the placed items of the plurality of items to the expected delivery destination, regardless of the state of other items of the customer order.
[0011] Another aspect of the present disclosure relates to a computer-implemented parcel delivery system. The system may include: a memory storing instructions; and at least one processor configured to execute the instructions to: receive a customer order by the computer-implemented system; generate an order identifier based on the customer order using the computer-implemented system; associate each of a plurality of items of the customer order with the order identifier; determine an expected delivery destination, a storage space associated with the expected delivery destination, a delivery route, and a parcel count for each item based on the order identifier; determine whether the parcel count has reached or exceeded a threshold amount; based on the determination that the parcel count has not reached or exceeded the threshold amount, send a first indication to at least one user device for display to sort each of the plurality of items using a first sorting process based on the storage space associated with the expected delivery destination; receive a first input related to the status of the first sorting process from at least one user device; send a second indication to at least one user device for display to sort each sorted item using a second sorting process based on a delivery route configured to include the expected delivery destination, regardless of the status of the first sorting process; receive a second input related to the status of the second sorting process from at least one user device; send a third indication to at least one user device for display to place each sorted item into a container associated with the delivery route, regardless of the status of the second sorting process; send a fourth indication to at least one user device for display to deliver the placed items of the plurality of items to the expected delivery destination, regardless of the status of other items of the customer order; and based on the determination that the parcel count has reached or exceeded the threshold amount, send a fifth indication to at least one user device for display to place the plurality of items in at least one storage unit and package each placed item in at least one common parcel.
[0012] Other systems, methods, and computer-readable media are also discussed herein. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Figure 1A is a schematic block diagram illustrating an exemplary embodiment of a network consistent with the disclosed embodiments, the network including a computerized communication system for implementing shipping, transportation, and logistics operations.
[0014] Figure 1B depicts an example search result page (SRP) consistent with the disclosed embodiments, including one or more search results satisfying a search request and interactive user interface elements.
[0015] Figure 1CDepicts an example Single Display Page (SDP) consistent with the disclosed embodiments, including a product, information about the product, and interactive user interface elements.
[0016] Figure 1D Depicts an example Cart page consistent with the disclosed embodiments, including items in a virtual shopping cart and interactive user interface elements.
[0017] Figure 1E Depicts an example Order page consistent with the disclosed embodiments, including items from a virtual shopping cart, information about purchase and shipping, and interactive user interface elements.
[0018] Figure 2 Is a schematic diagram of an exemplary fulfillment center consistent with the disclosed embodiments, configured to utilize the disclosed computerized system.
[0019] Figure 3 Is a schematic diagram of an exemplary computerized single-piece parcel delivery system consistent with the disclosed embodiments, configured to utilize the disclosed computerized system.
[0020] Figure 4 Is a schematic diagram of an exemplary processing flow for single-piece parcel delivery consistent with the disclosed embodiments.
[0021] Figure 5 Is a schematic diagram of an exemplary processing flow for generating a representation of a loading arrangement for a delivery vehicle consistent with the disclosed embodiments. Detailed Description
[0022] The following detailed description refers to the accompanying drawings. In the drawings and the following description, wherever possible, the same reference numerals are used to refer to the same or similar components. Although several illustrative embodiments are described herein, modifications, adaptations, and other implementations are possible. For example, components and steps shown in the drawings may be replaced, added, or modified, and the illustrative methods described herein may be modified by replacing, reordering, removing, or adding steps to the disclosed methods. Accordingly, the following detailed description is not limited to the disclosed embodiments and examples. Instead, the proper scope of the invention is defined by the appended claims.
[0023] Embodiments of the present disclosure are directed to systems and methods configured to reduce cycle time and improve parcel delivery efficiency by separately shipping items of the same order without waiting for the remaining items, thereby avoiding slowing down computerized systems and processes.
[0024] Refer to Figure 1A, which shows a schematic block diagram 100 that illustrates an exemplary embodiment of a network that includes a computerized communication system for implementing shipping, transportation, and logistics operations. As Figure 1A shown, network 100 may include various systems, each of which may be connected to each other via one or more networks. The systems depicted include a Shipment Authority Technology (SAT) system 101, an external front-end system 103, an internal front-end system 105, a transportation system 107, mobile devices 107A, 107B, and 107C, a seller portal 109, a Shipment and Order Tracking (SOT) system 111, a Fulfillment Optimization (FO) system 113, a Fulfillment Messaging Gateway (FMG) 115, a Supply Chain Management (SCM) system 117, a warehouse management system 119, mobile devices 119A, 119B, and 119C (depicted as being inside a fulfillment center (FC) 200), third-party fulfillment systems 121A, 121B, and 121C, a Fulfillment Center Authorization System (FC Auth) 123, and a Labor Management System (LMS) 125.
[0025] In some embodiments, the SAT system 101 may be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 may determine whether an order has exceeded its Promised Delivery Date (PDD) and may take appropriate actions, including initiating a new order, re-shipping items in an undelivered order, canceling an undelivered order, initiating contact with the ordering customer, and so on. The SAT system 101 may also monitor other data, including outputs (such as the number of packages shipped within a specific time period) and inputs (such as the number of empty cardboard boxes received in shipment). The SAT system 101 may also act as a gateway between different devices in system 100, enabling communication (e.g., using store-and-forward or other techniques) between devices such as the external front-end system 103 and the FO system 113.
[0026] In some embodiments, the external front-end system 103 may be implemented as a computer system that enables external users to interact with one or more systems in the network 100. For example, in embodiments where the network 100 is capable of presenting systems to a user to enable the user to order items, the external front-end system 103 may be implemented as a web server that receives search requests, presents item pages, and requests payment information. For example, the external front-end system 103 may be implemented as one or more computers running software such as the Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc. In other embodiments, the external front-end system 103 may run custom web server software that is designed to receive and process requests from external devices (not shown), obtain information from databases and other data stores based on those requests, and provide responses to the received requests based on the obtained information.
[0027] In some embodiments, the external front-end system 103 may include one or more of a web caching system, a database, a search system, or a payment system. In one aspect, the external front-end system 103 may include one or more of these systems, and in another aspect, the external front-end system 103 may include interfaces (e.g., server-to-server, database-to-database, or other network connections) that connect to one or more of these systems.
[0028] Figure 1B , 1C A set of illustrative steps shown in FIGS. 1D and 1E will help to describe some operations of the external front-end system 103. The external front-end system 103 may receive information from systems or devices in the 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 result page (SRP) (e.g., Figure 1B ), a single item detail page (SDP) (e.g., Figure 1C ), a shopping cart page (e.g., Figure 1D ), or an order page (e.g., Figure 1E)。A user device (e.g., using mobile device 102A or computer 102B) can navigate to the external front-end system 103 and request a search by entering information in the search box. The external front-end system 103 can request information from one or more systems in the network 100. For example, the external front-end system 103 can request results that satisfy the search request from the FO system 113. The external front-end system 103 can also request and receive (from the FO system 113) the Promised Delivery Date or "PDD" for each product returned in the search results. In some embodiments, the PDD represents an estimate of when a package will arrive at the user's desired location if ordered within a specific time period (e.g., before the end of the day (11:59 PM)). (The PDD will be further discussed with respect to the FO system 113 below.)
[0029] The external front-end system 103 can prepare an SRP based on this information (e.g., Figure 1B ). The SRP can include information that satisfies the search request. For example, this can include pictures of the products that satisfy the search request. The SRP can also include the corresponding price for each product, or information related to enhanced delivery options, PDD, weight, size, quotes, discounts, etc. for each product. The external front-end system 103 can deliver the SRP to the requesting user device (e.g., via the network).
[0030] Then, the user device can select a product from the SRP, for example, by clicking or tapping on the user interface or using another input device to select the product represented on the SRP. The user device can formulate a request for information about the selected product and send it to the external front-end system 103. In response, the external front-end system 103 can request information related to the selected product. For example, this information can include additional information other than the information provided for the product on the corresponding SRP. For example, this may include shelf life, country of origin, weight, size, number of items in the package, handling instructions, or other information about the product. The information can also include recommendations for similar products (e.g., based on big data and / or machine learning analysis of customers who have purchased this product and at least one other product), frequently asked questions, customer reviews, manufacturer information, pictures, etc.
[0031] The external front-end system 103 can prepare a Single Detail Page (SDP) based on the received product information (e.g., Figure 1C ). The SDP can also include other interactive elements, such as "Buy Now" button, "Add to Cart" button, quantity field, item pictures, etc. The external front-end system 103 can deliver the SDP to the requesting user device (e.g., via the network).
[0032] The requesting user device can receive an SDP that lists product information. After receiving the SDP, the user device can then interact with the SDP. For example, a user of the requesting user device can click the "Place in Cart" button on the SDP or interact with it in other ways. This adds the product to the shopping cart associated with the user. The user device can send a request to add the product to the shopping cart to the external front-end system 103.
[0033] The external front-end system 103 can generate a shopping cart page (e.g., Figure 1D ). In some embodiments, the shopping cart page lists the products that the user has added to the virtual "shopping cart". The user device can request the shopping cart page by clicking an icon on the SRP, SDP, or other page or interacting with it in other ways. In some embodiments, the shopping cart page can list all the products that the user has added to the shopping cart, as well as information about the products in the shopping cart, such as the quantity of each product, the price per item, the price of each product based on the relevant quantity, information about the PDD, the delivery method, the shipping cost, user interface elements for modifying the products in the shopping cart (e.g., deleting or modifying the quantity), options for ordering other products or setting up recurring delivery of products, options for setting up interest payments, user interface elements for proceeding to purchase, etc. A user on the user device can click a user interface element (e.g., a button labeled "Buy Now") or interact with it in other ways to initiate a purchase of the products in the shopping cart. Once this is done, the user device can send a request to initiate the purchase to the external front-end system 103.
[0034] The external front-end system 103 can generate an order page (e.g., Figure 1E ) in response to receiving a request to initiate a purchase. In some embodiments, the order page lists the items in the shopping cart again and requests input of payment and shipping information. For example, the order page can include a section for requesting information about the purchaser of the goods in the shopping cart (e.g., name, address, email address, phone number), information about the recipient (e.g., name, address, phone number, delivery information), shipping information (e.g., speed / method of delivery and / or pickup), payment information (e.g., credit card, bank transfer, check, stored credit), user interface elements to request a cash receipt (e.g., for tax purposes), etc. The external front-end system 103 can send the order page to the user device.
[0035] The user device can input information on the order page and then click on the user interface element that sends the information to the external front-end system 103 or interact with it in other ways. Subsequently, the external front-end system 103 can send the information to different systems in the network 100 to enable the creation and processing of a new order using the products in the shopping cart.
[0036] In some embodiments, the external front-end system 103 can also be configured to enable a seller to send and receive information related to an order.
[0037] In some embodiments, the internal front-end system 105 can be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases the network 100) to interact with one or more systems in the network 100. For example, in embodiments where the network 100 enables the presentation of systems that allow users to place orders for items, the internal front-end system 105 can be implemented as a web server that enables users to view diagnostic and statistical information about orders, modify item information, or review statistical information related to orders. For example, the internal front-end system 105 can be implemented as one or more computers running software (such as Apache HTTP Server, Microsoft Internet Information Services (IIS), NGINX, etc.). In other embodiments, the internal front-end system 105 can run custom web server software that is designed to receive and process requests from the devices described in the network 100 (and other devices not described), obtain information from databases and other data stores based on those requests, and provide responses to the received requests based on the obtained information.
[0038] In some embodiments, the internal front-end system 105 can include one or more of a web caching system, a database, a search system, a payment system, an analysis system, an order monitoring system, etc. In one aspect, the internal front-end system 105 can include one or more of these systems, and in another aspect, the internal front-end system 105 can include interfaces (e.g., server-to-server, database-to-database, or other network connections) that connect to one or more of these systems.
[0039] In some embodiments, the transportation system 107 may be implemented as a computer system that enables communication between devices in the network 100 and the mobile devices 107A - 107C. In some embodiments, the transportation system 107 may receive information from one or more mobile devices 107A - 107C (e.g., mobile phones, smartphones, personal digital assistants (PDAs), etc.). For example, in some embodiments, the mobile devices 107A - 107C may include devices operated by delivery workers. The delivery workers (who may be permanent employees, temporary employees, or shift employees) may use the mobile devices 107A - 107C to effect the delivery of packages ordered by users. For example, to deliver a package, the delivery worker may receive on the mobile device a notification indicating which package to deliver and where to deliver it. After arriving at the delivery location, the delivery worker may locate the package (e.g., in the back of a truck or in the crate of the package), scan or otherwise capture data associated with an identifier on the package (e.g., barcode, image, text string, RFID tag, etc.) using the mobile device, and then deliver the package (e.g., by placing it at the front door, handing it to security, handing it to the recipient, etc.). In some embodiments, the delivery worker may capture a photo of the package and / or may obtain a signature. The mobile device may send information to the transportation system 107 that includes information about the delivery, including, for example, time, date, GPS location, photo, identifier associated with the delivery worker, identifier associated with the mobile device, etc. The transportation system 107 may store this data in a database (not shown) for access by other systems in the network 100. In some embodiments, the transportation system 107 may use this information to prepare tracking data and send it to other systems indicating the location of a particular package.
[0040] In some embodiments, certain users may use one type of mobile device (e.g., permanent workers may use a dedicated PDA with customized hardware, such as a barcode scanner, stylus, and other devices), while other users may use other types of mobile devices (e.g., temporary or shift workers may use off - the - shelf mobile phones and / or smartphones).
[0041] In some embodiments, the transportation system 107 can associate a user with each device. For example, the transportation system 107 can store the relationship between a user (e.g., represented by a user identifier, employee identifier, or phone number) and a mobile device (e.g., represented by an International Mobile Equipment Identity (IMEI), International Mobile Subscription Identifier (IMSI), phone number, Universal Unique Identifier (UUID), or Globally Unique Identifier (GUID)). The transportation system 107 can use this relationship in combination with data received at the time of delivery to analyze the data stored in the database in order to determine, among other things, the location of a worker, the efficiency of a worker, or the speed of a worker.
[0042] In some embodiments, the seller portal 109 can be implemented as a computer system that enables a seller or other external entity to electronically communicate with other aspects of information related to an order. For example, a seller can use a computer system (not shown) to upload or provide product information, order information, contact information, etc. for products that the seller wishes to sell through the system 100.
[0043] In some embodiments, the shipping and order tracking system 111 can be implemented as a computer system that receives, stores, and forwards information about the location of a package ordered by a customer (e.g., a user using devices 102A - 102B). In some embodiments, the shipping and order tracking system 111 can request or store information from a web server (not shown) operated by a shipping company that delivers the package ordered by the customer.
[0044] In some embodiments, the shipping and order tracking system 111 may request and store information from the systems depicted in network 100. For example, the shipping and order tracking system 111 may request information from the transportation system 107. As described above, the transportation system 107 may receive information from one or more mobile devices 107A - 107C (e.g., mobile phones, smart phones, PDAs, etc.) associated with one or more users (e.g., delivery workers) or vehicles (e.g., delivery trucks). In some embodiments, the shipping and order tracking system 111 may also request information from the Warehouse Management System (WMS) 119 to determine the location of individual packages within a fulfillment center (e.g., fulfillment center 200). The shipping and order tracking system 111 may request data from one or more of the transportation system 107 or WMS 119, process the data, and present the data to devices (e.g., user devices 102A and 102B) upon request.
[0045] In some embodiments, the Fulfillment Optimization (FO) system 113 may be implemented as a computer system that stores customer order information from other systems (e.g., external front - end system 103 and / or shipping and order tracking system 111). The FO system 113 may also store information describing where a particular item is held 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 other embodiments, certain fulfillment centers may be designed to store only a particular set of items (e.g., fresh produce or frozen products). The FO system 113 stores this information along with associated information (e.g., quantity, size, receipt date, expiration date, etc.).
[0046] The FO system 113 may also calculate a corresponding PDD (Promised Delivery Date) for each product. In some embodiments, the PDD may be based on one or more factors. For example, the FO system 113 may calculate the PDD of a product based on past demand for the product (e.g., the number of times the product has been ordered over a period of time), expected demand for the product (e.g., how many customers are expected to order the product in a future period of time), past demand across the network indicating how many products have been ordered over a period of time, expected demand across the network indicating how many products are expected to be ordered in an upcoming period of time, one or more counts of the product stored in each fulfillment center 200 that stores each product, and the expected or current orders for the product.
[0047] In some embodiments, the FO system 113 may periodically (e.g., hourly) determine the PDD for each product and store the PDD in a database for retrieval or send it to other systems (e.g., the external front-end system 103, the SAT system 101, the shipping and order tracking system 111). In other embodiments, the FO system 113 may receive an electronic request from one or more systems (e.g., the external front-end system 103, the SAT system 101, the shipping and order tracking system 111) and calculate the PDD on demand.
[0048] In some embodiments, the fulfillment messaging gateway (FMG) 115 may be implemented as a computer system that receives information from one or more systems in the network 100 (e.g., the FO system 113), converts the data in the information to another format, and forwards the data in the converted format to other systems, such as the WMS 119 or third-party fulfillment systems 121A, 121B, or 121C, and vice versa.
[0049] In some embodiments, the supply chain management (SCM) system 117 may be implemented as a computer system that performs a forecasting function. For example, the SCM system 117 may determine a predicted demand level for a particular product based on, for example, historical demand for the product, expected demand for the product, historical demand across the network, expected demand across the network, the count of the product stored in each fulfillment center 200, the expected orders or current orders for each product, etc. In response to the determined forecast level and the quantity of each product across all fulfillment centers, the SCM system 117 may generate one or more purchase orders to meet the expected demand for the particular product.
[0050] In some embodiments, the warehouse management system (WMS) 119 may be implemented as a computer system that monitors the workflow. For example, the WMS 119 may receive event data indicating discrete events from various devices (e.g., devices 107A - 107C or 119A - 119C). For example, the WMS 119 may receive event data indicating the use of one of these devices to scan a package. As discussed below with respect to the fulfillment center 200 and Figure 2 during the fulfillment process, a package identifier (e.g., barcode or RFID tag data) may be scanned or read by a machine at a particular stage (e.g., an automated or handheld barcode scanner, an RFID reader, a high-speed camera, such as a tablet computer 119A, a mobile device / PDA 119B, a computer 119C, etc.). The WMS 119 may store each event indicating the scanning or reading of a package identifier in a corresponding database (not shown) along with the package identifier, time, date, location, user identifier, or other information, and may provide this information to other systems (e.g., the shipping and order tracking system 111).
[0051] In some embodiments, WMS 119 may store information associating one or more devices (e.g., devices 107A-107C or 119A-119C) with one or more users of network 100. For example, in some cases, a user (such as a part-time or full-time employee) may be associated with a mobile device because the user owns the mobile device (e.g., the mobile device is a smartphone). In other cases, a user may be associated with a mobile device because the user is temporarily under the custody of the mobile device (e.g., the user signs the mobile device out at the beginning of the day, will use the mobile device during the day, and will return the mobile device at the end of the day).
[0052] In some embodiments, WMS 119 may maintain a work log for each user associated with network 100. For example, WMS 119 may store information associated with each employee, including any assigned processes (e.g., unloading a truck, picking items from a pick area, rebin wall work, packaging items), user identifiers, locations (e.g., floors or zones in fulfillment center 200), the number of units moved through the system by the employee (e.g., number of items picked, number of items packaged), identifiers associated with equipment (e.g., equipment 119A-119C), etc. In some embodiments, WMS 119 may receive check-in and check-out information from a timekeeping system (such as a timekeeping system running on equipment 119A-119C).
[0053] In some embodiments, the third party fulfills (3 rd Third-party fulfillment (3PL) systems 121A-121C represent computer systems associated with third-party suppliers of logistics and products. For example, although some products are stored in fulfillment center 200 (as described below with reference to Figure 2 ), but other products may be stored off-site, may be produced on demand, or may not be stored in fulfillment center 200 for other reasons. 3PL systems 121A-121C may be configured to receive orders from FO system 113 (e.g., via FMG 115) and may provide products and / or services (e.g., delivery or installation) directly to customers.
[0054] In some embodiments, the Fulfillment Center Auth system (FCAuth) 123 can be implemented as a computer system with various functions. For example, in some embodiments, FC Auth 123 can act as a single-sign on (SSO) service for one or more other systems in the network 100. For example, FCAuth 123 can enable a user to log in via the internal front-end system 105, determine that the user has similar privileges to access resources at the shipping and order tracking system 111, and enable the user to access those privileges without a second login process. In other embodiments, FC Auth 123 can enable users (e.g., employees) to associate themselves with specific tasks. For example, some employees may not have electronic devices (e.g., devices 119A - 119C), but instead may move from task to task and from area to area within the fulfillment center 200 during the course of a day. FC Auth 123 can be configured to enable these employees to indicate the tasks they are performing and the areas they are in at different times of the day.
[0055] In some embodiments, the labor management system (LMS) 125 can be implemented as a computer system that stores attendance and overtime information for employees (including full-time and part-time employees). For example, LMS 125 can receive information from FC Auth 123, WMA 119, devices 119A - 119C, the transportation system 107, and / or devices 107A - 107C.
[0056] Figure 1A The specific configurations depicted are merely examples. For example, although Figure 1A the FC Auth system 123 is depicted as connected to the FO system 113 via the FMG 115, not all embodiments require this specific configuration. In fact, in some embodiments, the systems in the network 100 can be connected to each other via one or more public or private networks, including the Internet, intranet, Wide-Area Network (WAN), Metropolitan-Area Network (MAN), wireless networks compliant with the IEEE802.11a / b / g / n standards, leased lines, etc. In some embodiments, one or more systems in the network 100 can be implemented as one or more virtual servers implemented in a data center, server farm, etc.
[0057] Figure 2Depicts fulfillment center 200. The fulfillment center 200 is an example of a physical location that stores items to be shipped to customers after an order. The fulfillment center (FC) 200 can be divided into multiple zones, each zone shown in Figure 2 In some embodiments, these "zones" can be considered a virtual division between different stages of the process of receiving items, storing items, retrieving items, and shipping items. Thus, although "zones" are depicted in Figure 2 other partitions are possible, and in some embodiments, the zones in Figure 2 can be omitted, repeated, or modified.
[0058] The inbound zone 203 represents the area in the FC 200 where items are received from sellers who wish to sell products using the network 100 in FIG. 1. For example, a seller can use a truck 201 to deliver items 202A and 202B. Item 202A can represent a single item large enough to occupy its own shipping pallet, while item 202B can represent a group of items stacked together on the same pallet to save space.
[0059] Workers will receive items in the inbound zone 203 and can optionally use a computer system (not shown) to check if the items are damaged and correct. For example, a worker can use a computer system to compare the quantity of items 202A and 202B with the quantity of items ordered. If the quantities do not match, the worker can reject one or more of items 202A or 202B. If the quantities do match, the worker can move these items (e.g., using a cart, a hand truck, a forklift, or manually) to the buffer zone 205. The buffer zone 205 can be, for example, a temporary storage area for items that are not currently needed in the picking zone because there are a sufficient quantity of items in the picking zone to meet the predicted demand. In some embodiments, a forklift 206 operates to move items around the buffer zone 205 and between the inbound zone 203 and the offloading zone 207. If item 202A or 202B is needed in the picking zone (e.g., due to predicted demand), the forklift can move item 202A or 202B to the offloading zone 207.
[0060] The offloading zone 207 can be the area in the FC 200 where items are stored before being moved to the picking zone 209. Workers assigned to picking tasks ("pickers") can access items 202A and 202B in the picking zone and use a mobile device (e.g., device 119B) to scan barcodes associated with items 202A and 202B to scan the barcodes of the picking area. Then, the picker can bring the items to the picking zone 209 (e.g., by placing the items on a cart or carrying the items).
[0061] The picking area 209 can be the area in the FC200 where the item 208 is stored on the storage unit 210. In some embodiments, the storage unit 210 can include one or more of physical shelves, bookshelves, boxes, totes, refrigerators, freezers, cold storages, etc. In some embodiments, the picking area 209 can be organized into multiple layers. In some embodiments, a worker or a machine can move items into the picking area 209 in a variety of ways, including, for example, forklifts, elevators, conveyor belts, carts, hand trucks, trolleys, automated robots or equipment, or manually. For example, a picker can place the items 202A and 202B on a hand truck or cart in the unloading area 207 and escort the items 202A and 202B to the picking area 209.
[0062] The picker can receive instructions to place (or "stow") an item in a specific location (e.g., a specific space on the storage unit 210) in the picking area 209. For example, the picker can use a mobile device (e.g., device 119B) to scan the item 202A. The device can (e.g., using a system that indicates aisles, shelves, and locations) indicate to the picker where the item 202A should be stowed. Then, the device can prompt the picker to scan a barcode at that location before stowing the item 202A in that location. The device can send data (e.g., via a wireless network) to a computer system (e.g., the WMS119 in FIG. 1), indicating that the item 202A has been stowed in that location by the user using the device 119B.
[0063] Once the user places an order, the picker can receive instructions on the device 119B to retrieve one or more items 208 from the storage unit 210. The picker can retrieve the item 208, scan the barcode on the item 208, and place the item 208 on the transport mechanism 214. In some embodiments, although the transport mechanism 214 is shown as a slider, the transport mechanism can be implemented as one or more of a conveyor belt, an elevator, a cart, a forklift, a hand truck, a trolley, a cart, etc. Then, the item 208 can reach the packaging area 211.
[0064] The packing area 211 can be the area in the FC200 that receives items from the picking area 209 and packs the items into boxes or bags for eventual shipment to customers. In the packing area 211, the worker assigned to receive the items (the "rebin worker") will receive the item 208 from the picking area 209 and determine its corresponding order. For example, the rebin worker can use a device (such as the computer 119C) to scan the barcode on the item 208. The computer 119C can visually indicate the order associated with the item 208. This can include, for example, the space or "cell" on the wall 216 corresponding to the order. Once the order is complete (e.g., because the cell contains all the items for that order), the rebin worker can indicate to the packing worker (or "packer") that the order is complete. The packer can retrieve the items from the cell and place them in a box or bag for shipment. Then, the packer can send the box or bag to the hub area 213 (e.g., via forklift, cart, trolley, hand truck, conveyor belt, manually, or other means).
[0065] The hub area 213 can be the area in the FC200 that receives all the boxes or bags ("parcels") from the packing area 211. The workers and / or machines in the hub area 213 can retrieve the parcels 218 and determine which part of the delivery area each parcel should go to and route the parcels to the appropriate camp area 215 as required. For example, if the delivery area has two smaller sub - areas, the parcel will go to one of the two camp areas 215. In some embodiments, the worker or machine can scan the parcel (e.g., using one of the devices 119A - 119C) to determine its final destination. Routing the parcels to the camp area 215 can include, for example, determining a part of the geographical area specified by the parcel (e.g., based on the zip code) and determining the camp area 215 associated with that part of the geographical area.
[0066] In some embodiments, the camp area 215 can include one or more buildings, one or more physical spaces, or one or more areas where parcels are received from the hub area 213 for sorting into routes and / or sub - routes. In some embodiments, the camp area 215 is physically separated from the FC200, while in other embodiments, the camp area 215 can form part of the FC200.
[0067] Workers and / or machines in the camp area 215 can determine which route and / or sub-route the package 220 should be associated with (e.g., based on a comparison of the destination with existing routes and / or sub-routes, calculation of the workload of each route and / or sub-route, time of day, shipping method, cost of shipping the package 220, PDD associated with the items in the package 220, etc.). In some embodiments, a worker or machine can scan the package (e.g., using one of the devices 119A - 119C) to determine its final destination. Once the package 220 is assigned to a specific route and / or sub-route, the worker and / or machine can move the package 220 to be shipped. In an exemplary Figure 2 embodiment, the camp area 215 includes a truck 222, a car 226, and delivery workers 224A and 224B. In some embodiments, the truck 222 can be driven by the delivery worker 224A, where the delivery worker 224A is a full-time employee who delivers packages for the FC200, and the truck 222 is owned, leased, or operated by the same company that owns, leases, or operates the FC200. In some embodiments, the car 226 can be driven by the delivery worker 224B, where the delivery worker 224B is a "flexible" or temporary worker who delivers as needed (e.g., seasonally). The car 226 can be owned, leased, or operated by the delivery worker 224B.
[0068] Figure 3 An exemplary schematic diagram of a computer-implemented single-piece package delivery system 300 is shown. In some embodiments, the system 300 can include a consolidation worker 301, the picked item 208 with an order identifier 305 (e.g., barcode, marker, label), and a user interface device 302 (e.g., mobile device / PDA 119B). The system 300 can further include: a first storage location 320 (e.g., the packing area 211), which includes storage units 324 (e.g., 324_1, 324_2); a camp 340 (e.g., the camp area 215), which includes storage units 344; and a delivery truck 201. The first storage location 320 and the camp 340 can sort items based on different information related to the final destination. As an example, at the first storage location 320, items (e.g., item 208) can be sorted based on the geographical area specified for the package (e.g., based on the zip code), and at the camp 340, the items can be sorted based on the delivery route or sub-route (e.g., based on the route number). (Other sorting methods are possible.) The delivery route or sub-route can be pre-determined by one or more computer-implemented systems of the system 100. In some embodiments, one or more systems of the computer-implemented system 100 (e.g., SAT101, WMS 119, SCM 117) can be configured to communicate with the user interface device 302 to indicate the sorting of the items.
[0069] Figure 3 An exemplary single-piece parcel delivery system is shown. As used herein, the term "single-piece" refers to shipping the items of a customer order that includes multiple items in a single shipment without waiting to fully fulfill the customer order before shipping. Relative to existing parcel delivery systems, there can be many advantages to single-piece parcel delivery. Delivering parcels in single-piece can have some or all of the advantages discussed herein.
[0070] i. Improved packaging efficiency. In current existing parcel delivery systems, a consolidation worker can wait for all items in an order to be packaged in a single parcel and can place the parcel on the consolidation wall space associated with a particular order for further processing, which further processing includes sorting or shipping. In contrast, in the single-piece parcel delivery system 300, packers can sort items individually in a storage unit (e.g., 324_1) without waiting for other items in the order to arrive at the packer workstation or packaging area, thereby reducing the idle time of the packers. The reduction in the idle time of each packer can generally improve packaging efficiency.
[0071] ii. Enhanced picking density. In current existing parcel delivery systems, pickers can pick items to fulfill customer orders sequentially. For example, a picker can pick all items of order 1 before picking items of order 2. This sequential picking method results in a loss of time and efficiency because pickers spend more time moving than picking items. In contrast, the single-piece parcel delivery system 300 can allow enhanced picking density because pickers can pick items based on the location of the items rather than based on customer orders. For example, a picker may be required to pick items located near their current actual location but which may be associated with other customer orders. This parallel picking method can enhance picking density by reducing the time pickers spend moving.
[0072] iii. Improved traceability. As Figure 3 shown, in the single-piece parcel delivery system 300, a worker (e.g., worker 301) can scan barcodes (e.g., order identifier 305 and / or location identifier) associated with a package (e.g., package 208) before initiating the process and after the process is completed. Additionally, the barcode can be scanned periodically during processing or when prompted. For example, the information recorded by the scan can be stored in the database of system 100, thereby allowing the parcel to be tracked during processing. The barcode of a container or tote can also be scanned to provide information related to the location of the items contained in the container during picking, sorting, packaging, shipping, etc., so that the container and parcel can be tracked.
[0073] iv. Faster sorting. After receiving items at a fulfillment center (e.g., fulfillment zone 215) from a packing area, the items can be sorted based on sub-routes or delivery routes without waiting for other items in the order to arrive at that fulfillment center. Since the items are sorted according to sub-routes rather than according to the customer orders to which the items belong, the shelf time of the items may be reduced, thereby increasing the sorting rate. This can also improve space utilization, increase employee efficiency, reduce cycle time, and enhance the customer experience.
[0074] v. Reduced shelf time. The single sorting of items can shorten the time the items wait on the shelves to be picked, packed, sorted, or shipped because the items can be processed without considering the status of other items in the order. The reduction in the shelf time of items can reduce the associated costs associated with inventory management and reduce the risk of mishandling and misplacement of items.
[0075] vi. Reduced "load preparation" time. In existing parcel delivery and shipping systems, employees (e.g., workers, drivers, loaders, managers, front-line supervisors, etc.) may spend a significant amount of time at the start of a shift or work session, for example, ensuring that all items belonging to an order are loaded. Such systems may be inefficient in utilizing resources such as labor and time, both of which can increase operating costs and affect throughput. The single sorting of items may reduce the load preparation time because employees load containers or container transport racks (e.g., tote bags, cages, etc.) into delivery trucks based on the planned delivery area and delivery route.
[0076] vii. Improved loading and delivery efficiency. Since items are placed in large standardized tote bags or containers according to the shipping route, delivery trucks can be loaded more efficiently. Additionally, the items remain in the standardized containers until delivery, thereby minimizing damage or misalignment due to handling. The large standardized tote bags or containers allow loaders to load the trucks according to simple instructions, and drivers can easily understand the item information and deliver orders more efficiently.
[0077] In some embodiments, system 100 may be configured to receive a customer order. The customer order may include multiple items. In some embodiments, each customer order may include multiple sub-orders, and each sub-order may include multiple items. For example, one customer order may include three sub-orders. The first sub-order may be an emergency order for toothpaste, toothbrush, and mouthwash, the second sub-order may include normal delivery of cheese, crackers, and potato chips, and the third sub-order may include a delayed delivery of beverages. System 100 may receive the customer order and generate an order identifier 305 to be associated with each item ordered. In some embodiments, system 100 may generate a unique sub-order identifier associated with each sub-order (e.g., sub-order identifier 305A for the first sub-order, sub-order identifier 305B for the second sub-order, and sub-order identifier 305C for the third sub-order).
[0078] In some embodiments, the order identifier 305 and the sub-order identifiers (e.g., 305A, 305B, or 305C) may include the following information, which includes but is not limited to the quantity of the items ordered, the urgency of the items to be delivered, and the destination of the items to be delivered. In some embodiments, the order identifier 305 may further include information about the number of sub-orders within a single order. System 100 may send an indication to the user interface device 302 to indicate that the order includes multiple sub-orders and the urgency associated with each sub-order. The picker may fulfill the order or sub-order accordingly.
[0079] In some embodiments, one or more pickers may receive an indication regarding the urgency of a sub-order while retrieving items for other customer orders. Based on their current location in the picking area 209, the pickers may retrieve the items of the emergency sub-order and continue to send the items to the packing 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 department may retrieve the toothbrush, while a picker in or near the clothing department may retrieve a pair of socks, thus increasing the picking density. Once the container or tote is full, the items may be transported to the packing area 211. This method may improve the picking efficiency by picking items based on the picker's location rather than based on the customer order, thereby reducing the cycle time and improving the overall delivery efficiency.
[0080] In some embodiments, system 100 may send instructions to a user device (e.g., smartphone 119B or computer 119C) to cause the device to instruct the picker to print the order identifier 305. In some embodiments, the user device may include a handheld device (e.g., PDA) configured to print labels. Alternatively, system 100 may include a printing device (not shown) (e.g., a label printer, an inkjet printer, or a laser printer). The printing device may be configured to receive instructions from one of the computer-implemented systems of system 100 to print labels, instructions, memos, etc. The instructions may also include a request for the picker to associate the printed order identifier 305 with the items of the customer order (e.g., by pasting the printed order identifier 305 on the picked merchandise 208). In some embodiments, system 100 may be configured to electronically associate the order identifier 305 with the items of the customer order. For example, system 100 may update a database that includes information related to all incoming customer orders.
[0081] The consolidation worker 301 may receive the picked items 208 in the packing area 211. In some embodiments, the consolidation worker 301 may receive information related to the customer order from system 100 using a user interface device 302 (e.g., smartphone 119B). The user interface device 302 may include, but is not limited to, a handheld display device (e.g., tablet computer 119A), a smartphone (e.g., mobile device / PDA 119B), a computer (e.g., computer 119C), an in-vehicle display, a head-mounted display, etc. The user interface device 302 may be substantially similar to a mobile device (e.g., Figure 1A computer 119C in ). The user interface device 302 may communicate and exchange information with, for example, the WMS 119.
[0082] In some embodiments, the user interface device 302 may be configured to be on a user interface display ( Figure 3display information on a display (not shown in the figure). The user interface display may include information, which includes information related to a customer order (e.g., the quantity of items ordered, the delivery urgency of the ordered items, the destination location of the items to be delivered, etc.). In some embodiments, the user interface display may be a visual display or an audiovisual display. For example, if the order is "urgent", the user interface device 302 may receive an audiovisual message to indicate a request to expedite the fulfillment of the order. In some embodiments, the user interface device 302 may be configured to receive user input and provide feedback to the user through one or more interactive elements of the user interface display. For example, the user interface device 302 may provide audio, visual, or tactile notifications to the user and indicate a request to confirm receipt of the notification through one or more interactive elements of the user interface display. In some embodiments, the user interface device 302 may include data recording capabilities (e.g., barcode scanning, optical character reader, etc.) to record information of the order identifier 305. The user interface device 302 may be configured to temporarily store the recorded information and upload it to the database of one of the computer-implemented systems of the system 100 at a later time. In some embodiments, the user interface device 302 may automatically upload the recorded information to the database.
[0083] In some embodiments, the user interface device 302 may receive an instruction to review the order identifier 305 associated with the picked item 208 via an interactive element of the user interface display. For example, one of the computer-implemented systems of the system 100 (e.g., WMS 119, SCM 117, or SAT 101) may generate an instruction to the user interface device 302 to display an indication to the user to start reviewing the order identifier 305 associated with the item 208. Reviewing the order identifier 305 may include determining the final destination of the delivered item 208 by, for example, scanning or reading the order identifier 305. For example, using a barcode scanning device to scan the order identifier (e.g., barcode) may display information associated with the order identifier (e.g., the final destination of the items in the order, the delivery urgency, the quantity and description of the ordered items, etc.). In some embodiments, a customer order may include multiple sub-orders, and each sub-order may further include multiple items. It should be understood that the item 208 may include packaging that includes one or more items of the customer order.
[0084] After determining the final delivery destination of the item 208, the consolidation worker 301 can place the item 208 in the first storage location 320 based on the determined final destination. The first storage location 320 can include storage units 324. Each storage unit 324 of the first storage location 320 can be associated with a sorting location. In some embodiments, the first storage location 320 can include a consolidation wall, storage units, a storage rack or cabinet with units. Other organized storage methods can also be used.
[0085] In some embodiments, items 208 can be sorted in the storage units 324 of the first storage location 320 based on the destination of the item, regardless of the order with which the item can be associated or the status of other items in the order. In currently existing systems, consolidation workers can wait for all items of an order to be picked before sorting the order for delivery. In contrast, in the disclosed embodiments, each item can be treated as a separate order and can be sorted based on the destination, regardless of the status of other items in the order. This can reduce the idle time of the consolidation workers, thereby improving the packing efficiency. In some embodiments, the packing efficiency as disclosed herein can refer to the number of items packed within a specific time period. For example, the packing efficiency can be expressed as units per hour (UPH). Other efficiency metrics can also be used. The single sorting of items can also reduce the shelf time of the items, which is defined herein as the time the items stay on the shelf before being picked, packed, sorted, or shipped, thereby reducing the costs associated with inventory management and reducing the risk of mishandling or misplacement of the items.
[0086] In some embodiments, each storage unit 324 can be associated with a camp 340. In some embodiments, the camp 340 can be an on-site storage or sorting facility within the premises of the FC 200. In some embodiments, the camp 340 can be an off-site storage or sorting facility at a remote location. The association of each storage unit 324 (e.g., 324_1 or 324_2) with the corresponding camp can be identified using a camp identifier. The camp identifier can include, but is not limited to, a marker, barcode, number, or label. Although only a limited number of storage units 324 are shown, it should be understood that the first storage location 320 can include any number of storage units 324.
[0087] In some embodiments, based on determining the destination location of item 208, user interface device 302 may notify the consolidation worker 301 to place item 208 in the corresponding storage unit 324 by an indication. For example, based on a customer order, one of the computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, or SAT 101) may determine the camp to which item 208 may be directed. The consolidation worker 301 may place item 208 in the corresponding storage unit 324.
[0088] In some embodiments, the consolidation worker 301 may receive an indication via user interface device 302 to associate item 208 with the corresponding storage unit 324 in which item 208 is placed. For example, the consolidation worker 301 may be requested to scan the order identifier 305 and the camp identifier to establish an association between item 208 and the camp for sorting. Information related to the order identifier of the placed item and the camp identifier of the storage unit in which the item is placed may be automatically updated to a database including information related to the customer order and the delivery schedule of the customer order.
[0089] In some embodiments, if the camp 340 is an on-site facility, a transportation tool (e.g., a conveyor belt, a forklift, a pallet, a cart, or a tote bag) may be used to transport the item. For an off-site facility, a delivery truck or the like may be used to transport the item.
[0090] In some embodiments, storage unit 324 may include one or more items to be transported to the corresponding camp. In some embodiments, the camp may be referred to as a storage location. For example, camp 340 may be associated with storage unit 324_1, indicating that the item placed in storage unit 324_1 (e.g., item 208) may be directed to camp 340.
[0091] In some embodiments, camp 340 may include one or more storage spaces 342. The storage space 342 may include, but is not limited to, a wall with storage units, storage units, a storage rack or cabinet with units. Other organized storage methods may also be used. For example, the storage space 342 may include a wall with storage units 344. Each storage unit 344 may be associated with a sub-route for delivering item 208.
[0092] Workers at the camp 340 can receive one or more items 208 from the storage location 320. A worker (e.g., a sorter) can review the order identifier 305 associated with the picked item 208. In some embodiments, the worker can receive a notification to review the order identifier 305 on the user interface device 302. For example, one of the computer-implemented systems of the system 100 (e.g., the WMS 119, the SCM 117, or the SAT 101) can generate an indication to be displayed on the user interface device 302 for the worker to start reviewing the order identifier 305 associated with the item 208. Reviewing the order identifier 305 can include determining the final destination of the item 208.
[0093] Once the final delivery destination of the item 208 is determined, the worker can place the item (e.g., the item 208) in the storage unit 344 based on the sub-route of the determined final destination of the item 208. Each storage unit 344 at the camp 340 can be associated with a sub-route.
[0094] In some embodiments, the user interface device 302 can notify the worker to place the item 208 in the corresponding storage unit 344 based on the determined final destination of the item 208 by an indication. For example, based on a customer order, one of the computer-implemented systems of the system 100 (e.g., the WMS 119, the SCM 117, or the SAT 101) can determine the storage unit 344 to which the item 208 can be directed. The worker can place the item 208 in the corresponding storage unit 324 based on the indication from the user interface device 302.
[0095] A sub-route identifier can be used to identify the association of each storage unit 344 with the corresponding sub-route. The sub-route identifier can include, but is not limited to, a marker, a barcode, a number, or a label. Although only a limited number of storage units 344 are shown, it should be understood that the camp 340 can include any number of storage units 344.
[0096] In some embodiments, items can be sorted in the storage unit 344 based on the determined sub-route for the final delivery destination, regardless of the order with which the item can be associated or the status of other items in the order. In currently existing delivery systems, before an order is ready to be delivered, a sorter may have to wait for all items of the order to be received. In contrast, in the disclosed embodiments, each item can be treated as a separate order and sorted based on the determined sub-route to be delivered, regardless of the status of other items in the order. This can reduce the idle time of the sorter in the camp area, thereby improving the sorting efficiency and the overall package delivery efficiency.
[0097] In some embodiments, the user interface device 302 may be configured to display an indication to associate the item 208 with the corresponding storage unit 344 in which the item 208 is placed. For example, the indication may include a request to scan the order identifier 305 and the sub-route identifier to establish an association between the item 208 and the sub-route for delivery. Information related to the order identifier 305 of the placed item and the sub-route identifier of the storage unit 344 in which the item is placed may be automatically updated to a database that includes information related to the customer order and the delivery schedule of the customer order.
[0098] In some embodiments, each storage unit 344 may be associated with a container 350 (e.g., a tote bag). All items (e.g., item 208) of the storage unit 344 may be placed in the container 350. In some embodiments, a container identifier 355 may be used to identify the container 350. The container identifier 355 may include information associated with a sub-route that includes a sub-route identifier. In some embodiments, the container identifier 355 may include information related to the camp and the sub-route. For example, the container identifier may include the label CS3_SR1, where CS represents the origin camp and SR represents the designated sub-route for delivering items in the container. The container identifier 355 may include, but is not limited to, a marker, a barcode, a number, or a label.
[0099] In some embodiments, the user interface device 302 may be configured to display a notification or an indication to place the item 208 in the corresponding container 350 based on the determined final destination of the item 208. For example, based on the customer order, one of the computer-implemented systems of the system 100 (e.g., the WMS 119, the SCM 117, or the SAT 101) may determine the container 350 in which the item 208 may be placed. A worker may place the item 208 in the corresponding container 350 based on the indication from the user interface device 302.
[0100] In some embodiments, the user interface device 302 may be configured to display an indication via one or more interactive elements of the user interface display to associate the item 208 with the corresponding container 350 in which the item 208 is placed. For example, the indication may include a request to scan the order identifier 305 and the container identifier 355 to establish an association between the item 208 and the container 350 for package delivery. Information related to the order identifier 305 of the placed item 208 and the container identifier 355 of the container 350 in which the item is placed may be automatically updated to a database that includes information related to the customer order and the delivery schedule of the customer order.
[0101] In some embodiments, one or more containers 350 can be loaded onto a delivery vehicle (e.g., delivery truck 201) for delivery to a customer. The containers 350 can be arranged in the delivery truck 201 based on sub-routes. For example, packages or items (e.g., item 208) that are to be delivered to a destination closer to the start of a sub-route can be placed in a location closer to the access door so that the delivery worker can have direct access to the package. In some embodiments, a container 350 that includes an emergency order can be placed in a location closer to the service door to enable quick access to the package. In some embodiments, the sub-routes can be adjusted based on the type and urgency of the order or the PDD. In some embodiments, the sub-routes and the arrangement of the containers in the delivery truck 201 can be adjusted based on both the customer order and the PDD.
[0102] The container 350 can be placed on a container transporter 360 before being loaded into the delivery truck 201. The container transporter 360 can include a cart, a trolley, a cage, a basket, etc. In some embodiments, the container transporter 360 can include an identifier (e.g., a barcode, a marker, or a label). In some embodiments, the user interface device 302 can, based on a predetermined arrangement, instruct a delivery worker or a truck loader to place the container 350 on the delivery truck 201 by indicating a notification. For example, based on the PDD, one of the computer-implemented systems of the system 100 (e.g., the transportation system 107) can determine the arrangement of the container 350 on the container transporter 360 or the arrangement of one or more container transporters 360 on the delivery truck 201. The delivery worker or the truck loader can place the container 350 or the container transporter 360 in the delivery truck 201 based on the determination made by one of the computer-implemented systems of the system 100 (e.g., the transportation system 107). The user interface device 302 can indicate to the delivery worker or the truck loader a representation of the arrangement of the container 350 within the container transporter 360 and / or the arrangement of the container transporter 360 within the delivery truck 201.
[0103] In some embodiments, the user interface device 302 can be configured to display a representation of the container 350 and one or more container transporters 360 arranged in the delivery truck 201. The format of the representation can include one of visual, tabular, audio, audiovisual, or a combination thereof. In some embodiments, the user interface display can include a representation of the container 350 and the container transporter 360 arranged for the delivery worker in the delivery truck 201.
[0104] In some embodiments, a delivery worker may receive an indication generated by one of the computer-implemented systems of system 100 (e.g., the transportation system 107) to begin traveling on a sub-route after the delivery truck 201 has been loaded. The delivery worker may receive the indication via a user interface display on the user interface device 302.
[0105] Now refer to Figure 4 , which shows an exemplary flowchart of a single-sort package delivery process 400 consistent with the disclosed embodiments. The process may include receiving a customer order, generating an order identifier based on the customer order, determining an expected final destination for the items of the customer order, picking at least some of the items of the customer order, sorting the picked items based on a two-step sorting process, loading the picked items of the customer order onto a delivery truck without waiting for the remaining items of the customer order, and delivering the picked items to the customer.
[0106] Overall package delivery efficiency is a metric that depends on the efficiency of each step in the package shipping process. Shipping a package from the FC to the customer to fulfill an order typically involves multiple steps, and most of these steps must be performed in a linear order. For example, receiving an order and generating an order identifier may occur before picking, picking may occur before sorting, sorting may occur before packing, packing may occur before loading the items onto a delivery truck, etc. In other words, each step of the process is initiated by the completion of the previous step. In such a processing flow, the overall efficiency of the process depends on the efficiency of each step. The overall efficiency can be increased by increasing the efficiency of each step, or by increasing the efficiency of at least one step while maintaining the efficiency of the other steps. As described above, "single-sort" herein refers to shipping the items in a customer order containing multiple items individually without waiting for the entire customer order to be fulfilled before shipping, and the delivery efficiency of the package can be increased by reducing the cycle time and reducing the idle time of the employees involved in the process. In some embodiments, one or more steps of process 400 may be performed by one or more user interface devices (e.g., each user interface device is operated by a user in a different area of the FC 200).
[0107] In step 410, one or more computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, SAT system 101) may receive a customer order. The customer order may include multiple items. In some embodiments, the customer order may include multiple sub-orders, and each sub-order may include multiple items. One or more computer-implemented systems of system 100 may be configured to review the customer order and identify information (e.g., the total number of items ordered, the description of each item ordered, the requested delivery time, the final destination of the item, etc.). In some embodiments, one or more computer-implemented systems of system 100 may determine a promised delivery date or promised delivery time for the customer order based at least on the requested delivery time. For example, for an urgent order request from a customer, the system may determine a promised delivery time of several hours or delivery to the expected final destination within 24 hours. In some embodiments, the system may be configured to determine the promised delivery date and time separately for each item of the customer order. For example, the customer order may include some items for urgent delivery while the remaining items are for normal delivery. The system may be configured to determine the promised delivery time based on the requested delivery type.
[0108] In some embodiments, one or more computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, SAT system 101) may receive multiple customer orders. Each customer order may include multiple items. One or more computer-implemented systems of system 100 may be configured to review and identify common items among the multiple customer orders. The user interface device may be configured to display an indication regarding the common items to request input from the user (e.g., receive confirmation). The indication may include information related to the description of the item, the quantity of the item ordered, etc. For example, WMS 119 may receive 100 customer orders and determine that 50 of the 100 customer orders include a common item (e.g., a bottle of water). A worker (e.g., a picker) may receive an indication to pick 50 bottles of water through the user interface device. Implementing this method may improve picking efficiency and the overall efficiency of the process.
[0109] In step 420, one or more computer-implemented systems of system 100 may generate an order identifier (e.g., order identifier 305) based on the received customer order. The order identifier may include a barcode, a marker, a label, an alphanumeric code, a quick response (QR) code, etc. The order identifier may be a machine-readable optical marker containing information about the customer order. The information contained in the order identifier may include, but is not limited to, the final destination of the order, the total number of items in the customer order, the requested delivery type, customer information, the promised delivery date, and the promised delivery time, etc. In some embodiments, the system that generates the order identifier may determine the storage location (e.g., camp area 215, hub area 213) and the delivery route to which the items in the customer order may belong based on the final destination information of the customer order. For example, based on the zip code of the final destination, the system may determine the storage location of the items in the customer order, and based on the street or area identified in the final destination, the system may determine the delivery route for the items in the customer order.
[0110] For example, when scanning or reading the order identifier using a user interface device (e.g., user interface device 302) equipped with barcode scanning functionality, the user interface device may display information associated with the order identifier. For example, when scanning or reading the order identifier, the user interface device may display the number of items picked, the number of items remaining to be picked, the promised delivery time, and the remaining time to complete the order.
[0111] In step 430, one or more computer-implemented systems of system 100 may instruct the user interface device to display an indication to associate each item of the customer order with the order identifier. The user interface device may be configured to display an indication or alert regarding the received customer order to request input from the user (e.g., receive confirmation). After receiving input from the user, the user interface device may display the customer order and some or all of the information associated with the customer order. A worker (e.g., a picker) may pick one or more items in the customer order and associate each picked item with the order identifier received from one or more computer-implemented systems (e.g., by scanning the order identifier and the barcode on the item). In some embodiments, associating the items of the customer order with the order identifier may include physically printing the order identifier using a label printer or a barcode printer. The printed label or barcode may be attached or pasted on the item, for example, to allow all employees to easily obtain information related to the order and the delivery schedule. For example, a worker who did not receive or cannot obtain the original order identifier may be able to scan the printed and pasted order identifier on the item.
[0112] In step 440, one or more computer-implemented systems of system 100 can determine an expected final delivery destination for each item of a customer order. For example, a customer can order a bouquet of flowers to be delivered to a friend's house before 8 PM and order a pack of batteries to be delivered to their parents' house within 24 hours. One or more computer-implemented systems of system 100 can generate two separate order identifiers representing the two orders. Each item can be directed to a storage location based on the expected final destination and sorted to a delivery route at that storage location.
[0113] In some embodiments, one or more computer-implemented systems of system 100 can determine an expected delivery destination, a storage space associated with the expected delivery destination (e.g., in storage units 324 / 344), and a delivery route for delivering items in a customer order to the expected delivery destination. In some embodiments, one or more computer-implemented systems of the systems of system 100 can also determine a single-sort parcel count associated with the order identifier. For example, based on the order identifier, one or more systems can determine that, as a result of the single-sort process, the order will be delivered in a specified number of parcels.
[0114] In some embodiments, the sorting process can be a two-step sorting process. The first step can include sorting the picked items based on the camps to which the items can be directed. For example, the camps can be determined based on the zip code of the expected final delivery destination of the items in the customer order. The second step can include sorting the picked items within the camps based on the delivery routes to which the items may be delivered. The delivery routes can be determined based on, for example, the areas or streets within the region represented by the zip code.
[0115] In step 445, in some disclosed embodiments, one or more computer-implemented systems of system 100 (e.g., WMS 119, SCM 117, FO 113, SAT system 101) can be configured to apply logic or a set of rules to improve the efficiency associated with one or more steps in the single-sort delivery process and / or enhance the customer experience. In one example, a customer can order a large number of items in a single order. Throughout the single-sort delivery process, each of these items may be shipped in a separate container, resulting in too many parcels being delivered, which can lead to a negative customer experience. However, to improve the customer experience and reduce packaging costs, system 100 can be configured to consolidate the delivery of items in the single-sort system when a customer order includes a large number of parcels. For example, this can be done by determining that a specified condition is met based on the order identifier and, in response, proceeding with the delivery of the items without using the single-sort process.
[0116] In some embodiments, if the determined parcel count from step 440 reaches or exceeds a threshold amount, the condition of step 445 may be satisfied. The threshold amount may be a fixed value (e.g., 10 parcels), which may be predetermined based on any number of factors, including the level of customer satisfaction based on the number of parcels being delivered. For example, it may be predetermined that there is a certain level of customer dissatisfaction associated with a large number of parcels (e.g., 10 or more parcels), and thus, any order that results in a parcel count equal to or greater than the threshold will satisfy the non-split condition. Additionally, in some embodiments, the determination of satisfying the condition may depend on the determination that the total volume of delivered parcels without splitting will be less than the total volume of delivered parcels with splitting.
[0117] In some embodiments, if the determined volume associated with the parcel count reaches or exceeds a threshold volume, the condition of step 445 may be satisfied. For example, when initially determining the parcel count in step 440, the volume associated with the parcel count may be determined. Similarly, the threshold amount may be a fixed value and may be predetermined based on any number of factors, including the level of customer satisfaction based on the total volume of parcels being delivered. Additionally, in some embodiments, the determination of satisfying the condition may depend on the determination that the total volume of delivered parcels without splitting will be less than the total volume of delivered parcels with splitting.
[0118] System 100 may be configured to determine that an order satisfies the non-split condition based on factors separate from the number of potential parcels resulting from splitting. For example, there may be certain conditions associated with a customer order that make splitting undesirable or incompatible with the delivery of the order. In some embodiments, if system 100 determines that the order is to be shipped by a third-party carrier, the non-split condition may be satisfied. For example, a fulfillment service agency may hire a third-party carrier to deliver certain parcels to certain locations, and the third-party carrier may charge the agency a shipping fee per parcel. Thus, it is desirable to minimize the number of parcels delivered by these carriers by preventing splitting of orders shipped by these carriers. However, generally, system 100 may be configured to dynamically determine whether splitting should be used based on any number of factors and / or conditions associated with the order.
[0119] In some embodiments, if the system 100 determines that the condition is met, the delivery process 400 may proceed to step 490, in which, consistent with other delivery methods described in the present disclosure, the order is delivered without using single-piece separation, so that the customer does not receive a large number of packages generated from the single-piece separation process. For example, at step 490, the system 100 may send at least one indication to be displayed at least on the user device (e.g., devices 119A-C and 302), indicating that single-piece separation should not be used, and / or that a regular or alternative delivery process should be used instead. In some embodiments, for example, the indication may be to place the multiple items associated with the order in at least one storage unit and wait until each of the multiple items is placed in the unit to package each placed item in at least one common package, and / or load the common package ready for delivery onto the delivery vehicle. For example, at least one common package may include a box, a plastic bag, or any other container in which at least a portion of the multiple items may be appropriately packaged together.
[0120] In some embodiments, at step 445, the system 100 may also determine the type of the package (e.g., box or bag), and the type of the non-single-piece separation delivery process at 490 may depend on the type of the package. For example, if the items in the customer order are to be delivered in a box, the system 100 may send an indication to at least one user device showing that the items should be packaged together and directly loaded onto the delivery vehicle. However, if the items in the customer order are to be delivered in the form of a bag, it may be necessary to load the bag onto the delivery vehicle together with other single-piece separation delivered bagged items. In some embodiments, for example, if the items are to be delivered in the form of a bag, the undelivered process at 490 may include sending an indication to continue the delivery process 400 (i.e., to steps 450-480) to at least one user device for display, and these indications include an indication to wait for each item to be picked before proceeding with the sorting process at steps 450 and 460 and / or an indication to place each item in a common package at step 470.
[0121] In some embodiments, the loading arrangement of the delivery truck may be displayed on the user interface display of the delivery vehicle, such as on the graphical user interface display of the device in the delivery truck. In some embodiments, the visual representation of the loading arrangement may be updated while the delivery is in progress. For example, when the delivery truck driver delivers an item to the customer and the container is empty, the display of the loading arrangement may indicate that the items in the container placed in that storage space have been delivered.
[0122] In some embodiments, one or more computer-implemented systems of system 100 may be configured to update a database to reflect the order status during the entire delivery process with or without single-piece. Updating the database may include uploading or modifying information in the database to include the current status or location of each of the plurality of items. For example, system 100 may update the database to reflect the completion of any one or more steps of the delivery process (e.g., process 400 including non-single-piece delivery). In some embodiments, system 100 may also be configured to generate a status update in response to a customer inquiry related to the status of a customer order. The status update may include information related to the status of the delivery process (e.g., whether at least one common package has been delivered) and / or may include information indicating the expected or estimated arrival of the plurality of identical items at the expected delivery destination.
[0123] In step 450, one or more computer-implemented systems of system 100 may send instructions to display an indication or an alert to a user interface device to sort the picked items of a customer order based on a pre-allocated storage space (e.g., storage unit 324 of storage location 320) determined by one or more computer-implemented systems of system 100. The pre-allocated storage space may represent the camp to which the item can be directed for further sorting. In some embodiments, a camp may be assigned to one or more storage spaces. For example, storage spaces 1-12 may be assigned to camp 1 represented by storage unit 324_1, storage spaces 13-23 may be assigned to camp 2 represented by storage unit 324_2, and storage space 24 may be assigned to camp 3 represented by storage unit 324.
[0124] Each sorted item may be transported to a corresponding camp. In some embodiments, the camp may be an on-site storage facility (e.g., camp area 215) within the premises of FC 200. A transportation device (e.g., conveyor belt, forklift, hand pallet truck, trolley, cart) may be used to transport the sorted items to camp area 215. In some embodiments, the camp may be an off-site storage facility (e.g., a warehouse or storage unit separate from FC 200). The sorted items belonging to a customer order may be transported to the off-site storage facility using, for example, a delivery truck. The sorted items belonging to a customer order may be transported to the camp without waiting for the remaining items of the customer order to reduce idle time.
[0125] In step 460, one or more computer-implemented systems of system 100 can send instructions to a user interface device to display an indication or an alert for sorting the picked items in the camp based on the delivery route. The delivery route can be predetermined by one or more computer-implemented systems of system 100 based on the final delivery destination in the customer order. Workers can sort the picked items in the camp by placing the items in storage units (e.g., storage unit 344) based on the delivery route. Workers can obtain delivery route information by, for example, scanning an order identifier on the item. Each storage unit 344 can be identified by a routing identifier or a sub-route identifier.
[0126] In step 470, one or more computer-implemented systems of system 100 can send instructions to a user interface device to display an indication or an alert for placing the sorted items from storage unit 344 into a container (e.g., container 350). Each storage unit 344 can be associated with a container configured to receive the items stored in the corresponding storage unit. In some embodiments, each container can be identified by a container identifier that includes information identifying the camp and the storage unit. The picked items belonging to a customer order can be placed in the container without waiting for the rest of the same customer order to reduce idle time.
[0127] Container 350 or container carrier 360 can be loaded onto a delivery vehicle (e.g., delivery truck 201) configured to receive containers, tote bags, wheeled cages, carts, trolleys, etc. For example, the container can be loaded in a manner that reduces the unloading time of the items during delivery based on, for example, the arrangement of the delivery route. The arrangement of the containers on the delivery truck can also be based on factors including but not limited to the urgency of the delivery, the committed delivery time, whether the items are perishable foods, etc. In some embodiments, the storage compartments of the delivery truck for the items can include built-in storage spaces (e.g., cabinets, units, shelves, racks, cages, or wheeled cages). Each container carrier 360 in the delivery truck can be identified by a container carrier identifier (e.g., a barcode). The container carrier identifier can include information related to the position of the container carrier in the storage compartment of the delivery truck. For example, four container carriers 360 can be arranged against the rear wall of the storage compartment and labeled 360_1 - 360_4 from left to right. Thus, the container carrier located in the left rear corner of the storage compartment of the delivery truck can be identified as container carrier 360_1, and the container carrier located in the right rear corner of the storage compartment of the delivery truck can be identified as container carrier 360_4. For example, a visual or tabular representation of the arrangement of container carriers 360 can be generated by one or more computer-implemented systems of system 100 (such as transportation system 107).
[0128] In some embodiments, the loading arrangement of the containers on the container transport rack 360 can be recorded to generate a representation of the delivery truck loading arrangement. For example, the transportation system 107 can send instructions to a user interface device to display the container identifiers (e.g., barcodes) of all the containers placed in the container transport rack and scan an indication of the corresponding container transport rack identifier. The system can generate a representation of the loading arrangement based on the scanned information. In some embodiments, the loading arrangement can be presented to the user in a tabular or visual format. The loading arrangement can be printed on a piece of paper, displayed on a user interface device, or presented to the user before they start their delivery rounds.
[0129] In step 480, one or more computer-implemented systems of the system 100 (such as the transportation system 107) can, for example, send instructions to a user interface device (such as one of the mobile devices 107A - 107C) to display an indication of delivering the items loaded in the containers on the delivery truck. The user interface device can display an indication requesting input from the user (such as a delivery worker or a loader) to verify the completion of the loading process before departing to deliver the items. The user interface device can receive the input from the user and store the received input in a database associated with the system 100.
[0130] In some embodiments, one or more computer-implemented systems of the system 100 can send instructions to a user interface device to display an indication to record information associated with an order identifier, for example, by scanning the order identifier. The user interface device can display the instruction to record the order identifier information after picking the items, after sorting the picked items based on the storage location in the first step of the sorting process, before transporting the picked items to the camp, after arriving at the camp, 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 onto the delivery truck. The information recorded at all steps of this process can be stored and updated in a database associated with the system 100 (e.g., associated with or connected to the WMS 119 or the transportation system 107).
[0131] In some embodiments, the system 100 can generate a status update notification message in response to an inquiry from a customer about the order status based on the updated information stored in the database. In some embodiments, the system 100 can preemptively generate a status update notification message for the customer based on the updated information stored in the database.
[0132] Now refer to Figure 5, which shows an exemplary flowchart of a process 500 for generating a visual representation of a loading arrangement of a delivery vehicle consistent with the disclosed embodiments. It should be understood that the flowchart is an exemplary order of the steps of the process, and the steps may also be performed in other orders. Additionally, steps may be added, omitted, skipped, repeated, or modified based on the application and user requirements.
[0133] In step 510, one or more computer-implemented systems of system 100 may identify a delivery vehicle (e.g., delivery truck 201) that includes storage space. In some embodiments, the transportation system 107 of system 100 may identify the delivery vehicle based on, for example, storage space requirements, transportation route characteristics, experience of the delivery truck workers, or sorting or other data. For example, the transportation system 107 may identify a small delivery vehicle with a transportation route for narrow roads, and the on-duty delivery truck worker (e.g., the truck driver) may only have a valid driver's license for small transportation vehicles. In some embodiments, the transportation system 107 may identify the delivery vehicle based on storage space requirements. For example, if there are 20 containers filled with items to be delivered on a delivery route or sub-route, system 100 may recommend a larger delivery vehicle with more storage space.
[0134] In step 520, one or more computer-implemented systems of system 100 (e.g., transportation system 107) may send instructions indicating a display to a user interface device to determine the arrangement of the storage space within the delivery truck. In some embodiments, the delivery truck may include built-in storage spaces in the storage room (e.g., cabinets, shelves, racks, cages, etc.). For example, the delivery truck may include a storage room to accommodate removable storage units (e.g., wheeled cages).
[0135] In some embodiments, each storage space in the delivery truck may be identified using a storage space identifier or a container carrier identifier. The container carrier identifier may include a barcode, marker, label, or QR code. The container carrier identifier may include information related to the position of the container carrier 360 in the storage room of the delivery truck. For example, four container carriers 360 may be arranged against the rear wall of the storage room and labeled 360_1 - 360_4 from left to right (not shown in Figure 3 ). Thus, the container carrier located in the left rear corner of the storage room of the delivery truck may be identified as container carrier 360_1, and the container carrier located in the right rear corner of the storage room of the delivery truck may be identified as container carrier 360_4. In some embodiments, the delivery truck may include built-in storage spaces, each having a storage space identifier.
[0136] In some embodiments, a delivery truck worker (e.g., a driver or a loader) may record the layout of the built-in storage space in a delivery truck, for example, by scanning a storage space identifier. In some embodiments, the database of system 100 may include information associated with the layout of the storage space in the delivery truck. For example, the database may include information associated with the layout of 24 storage spaces in delivery truck 14.
[0137] In step 530, one or more computer-implemented systems of system 100 (e.g., transportation system 107) may generate a container identifier for each container. The container identifier may include a barcode, a marker, a label, or a QR code. The container identifier may include at least information associated with the camp and the delivery route of the items contained in the container. In some embodiments, one or more containers may be assigned to the delivery route based on the number of items to be delivered along that route. The container identifier may be used as a quick reference or indication of the final intended delivery destination of the items in the container.
[0138] In step 540, one or more computer-implemented systems of system 100 (e.g., transportation system 107) may send instructions to a user interface device to display an indication to load the container into the storage space of the delivery truck. The container may be loaded onto the delivery truck in a manner that enables quick access to the items to be unloaded during delivery.
[0139] In step 550, one or more computer-implemented systems of system 100 (e.g., transportation system 107) may send instructions to a user interface device to display an indication associating each container with the storage space in which it is placed. For example, transportation system 107 may send instructions to the user interface device to display an indication to scan the container identifier (e.g., barcode) of all the containers placed in the storage space and scan the corresponding storage space identifier. In some embodiments, the instructions may include step-by-step instructions to associate the container with the storage space and upload the information to the database of system 100.
[0140] In step 560, one or more computer-implemented systems of system 100 (e.g., transportation system 107) may generate a visual representation of the loading arrangement of the containers and the storage spaces based on the associations established in step 550. In some embodiments, the loading arrangement may be presented to the user (e.g., the delivery truck driver) in a table or visual format. The loading arrangement may be printed on paper, displayed on a user interface device, or presented to the user before they start their delivery round.
[0141] In some embodiments, the loading arrangement of the delivery truck can be displayed on a user interface display of the delivery vehicle (e.g., on a graphical user interface display screen of the delivery truck). In some embodiments, the visual representation of the loading arrangement can be updated while the delivery is in progress. For example, when the delivery truck driver delivers an item to a customer and the container is empty, the display of the loading arrangement can indicate that the item in the container placed in that 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 dates and numbers have been met.
[0142] Although the present disclosure has been shown and described with reference to particular embodiments thereof, it should be understood that the present disclosure can be implemented in other environments without modification. The foregoing description has been given for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations will be apparent to those skilled in the art in light of the specification and practice of the disclosed embodiments. Additionally, although aspects of the disclosed embodiments are described as being stored in a memory, those skilled in the art will understand that these aspects can also be stored on other types of computer-readable media, such as secondary storage devices, e.g., hard disks or CD ROMs or other forms of RAM or ROM, USB media, DVDs, Blu-ray or other optical disc drive media.
[0143] Computer programs based on the written description and disclosed methods are within the capabilities of experienced developers. Any technology known to those skilled in the art can be used to create various programs or program modules, or various programs or program modules can be designed in combination with existing software. For example, program portions or program modules can be designed using or through.Net Framework,.Net Compact Framework (and related languages such as Visual Basic, C, etc.), Java, C++, Objective-C, HTML, HTML / AJAX combinations, XML, or HTML containing Java applets.
[0144] In addition, although illustrative embodiments have been described herein, the scope of any and all embodiments has equivalent elements, modifications, omissions, combinations (e.g., combinations of aspects in various embodiments), adaptations, and / or alternatives as understood by those skilled in the art based on the present disclosure. The limitations in the claims should be broadly construed based on the language used in the claims and not limited to the examples described in this specification or during the prosecution of this application. These examples should be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering the steps and / or inserting or deleting steps. Accordingly, the present specification and embodiments are considered to be merely exemplary, with the true scope and spirit being indicated by the full scope of the appended claims and their equivalents.
Claims
1. A computer-implemented parcel delivery system, the system comprising: a memory storing instructions; and at least one processor configured to execute the instructions to: receive a customer order by the computer-implemented system; generate an order identifier based on the customer order using the computer-implemented system; associate each of a plurality of items of the customer order with the order identifier; determine, based on the order identifier, an expected delivery destination for each item, a storage space associated with the expected delivery destination, a delivery route, and a parcel count; determine a first location of a first user device configured to send the first location of a user holding the first user device; generate a signal to the first user device based on determining that a first item of the customer order is classified as urgent, wherein the first user device is located at a position closest to the first item determined by the first location; determine whether the order identifier meets a condition; if the condition is met, process each of the plurality of items as a consolidated shipment; if the condition is not met, process each of the plurality of items including the first item as a separate shipment by performing a delivery process, including: send a first instruction to a second user device for display and for each item available for sorting to sort the item into a storage space associated with the expected delivery destination using a first sorting process; for each item sorted into the storage space, receive a first input from the second user device regarding the status of the first sorting process; send a second instruction to the second user device for display and for each item sorted into the storage space to sort the item into a storage unit associated with a delivery route configured to include the expected delivery destination, regardless of the status of the first sorting process, using a second sorting process; for each item sorted into the storage unit, receive a second input from the second user device regarding the status of the second sorting process; send a third instruction to the second user device for display and for each item placed into a container to place the item into a container associated with the delivery route, regardless of the status of the second sorting process; for each item placed into the container, receive a third input from the second user device regarding placing the item into the container; send a fourth instruction to the second user device for display and for each item placed into the container to load the container into a delivery vehicle associated with the expected delivery destination, regardless of the status of other items of the customer order; and track the delivery status of the customer order by updating at least one database in response to receiving the first input, the second input, and the third input.
2. The system according to claim 1, wherein, If the package count reaches or exceeds a threshold amount, the condition is satisfied.
3. The system according to claim 2, wherein, the threshold is fixed.
4. The system according to claim 2, wherein, the processor is further configured to determine a volume associated with the package count, and the threshold includes the volume.
5. The system according to claim 1, wherein, the processor is further configured to determine whether a third-party carrier will deliver the order, and if the third-party carrier will deliver the order, the condition is satisfied.
6. The system according to claim 1, wherein, the processor is further configured to, based on the condition being satisfied, send a fifth indication to the second user device for display to place the plurality of items in at least one storage unit and package each placed item in at least one common package.
7. The system according to claim 6, wherein, the processor is further configured to, if the condition is satisfied, then: send a sixth indication to load the common package for delivery onto a delivery vehicle based on an arrangement determined by a promised delivery date for each of the plurality of items; and display a visual representation of the loading arrangement of a plurality of containers in the delivery vehicle using the second user device.
8. The system according to claim 7, wherein, tracking the delivery status of the customer order further includes updating the at least one database using information related to placing the consolidated shipment in at least one storage unit, packaging the consolidated shipment in the at least one common package, loading the common package for delivery onto a delivery vehicle, and a delivery schedule for the common package for delivery.
9. The system according to claim 1, wherein, tracking the delivery status of the customer order includes updating the at least one database using information related to at least one of the first sorting process, the second sorting process, placing items in the container, and a delivery schedule of the placed items.
10. A computer-implemented package delivery method, wherein, the method includes: receiving a customer order by a computer-implemented system; generating an order identifier based on the customer order using the computer-implemented system; associating each of a plurality of items of the customer order with the order identifier; determining an expected delivery destination for each item, a storage space associated with the expected delivery destination, a delivery route, and a package count based on the order identifier; determining a first location of a first user device configured to send the first location of a user holding the first user device; generating a signal to the first user device based on determining that a first item of the customer order is classified as urgent, wherein the first user device is located at a position closest to the first item determined by the first location; determining whether the order identifier satisfies a condition; If the conditions are met, each of the plurality of items is processed as a consolidated shipment; If the conditions are not met, each of the plurality of items including the first item is processed as a separate shipment by performing a delivery process, including: Sending a first indication to a second user device for display and for each item available for sorting to sort the item into a storage space associated with the intended delivery destination using a first sorting process; For each item sorted into the storage space, receiving a first input related to the status of the first sorting process from the second user device; Sending a second indication to the second user device for display and for each item sorted into the storage space to sort the item into a storage unit associated with a delivery route configured to include the intended delivery destination using a second sorting process, regardless of the status of the first sorting process; For each item sorted into the storage unit, receiving a second input related to the status of the second sorting process from the second user device; Sending a third indication to the second user device for display and for each item placed into a container to place the item into a container associated with the delivery route, regardless of the status of the second sorting process; For each item placed into the container, receiving a third input related to placing the item into the container from the second user device; Sending a fourth indication to the second user device for display and for each item placed into the container to load the container into a delivery vehicle associated with the intended delivery destination, regardless of the status of the other items in the customer order; and In response to receiving the first input, the second input, and the third input, tracking the delivery status of the customer order by updating at least one database.
11. The method according to claim 10, wherein, the conditions are met if the package count reaches or exceeds a threshold amount.
12. The method according to claim 11, wherein, the threshold is fixed.
13. The method according to claim 11, wherein, it further includes determining a volume associated with the package count, and the threshold includes the volume.
14. The method according to claim 10, wherein, it further includes determining whether a third-party carrier will transport the order, and if the third-party carrier will transport the order, the conditions are met.
15. The method according to claim 10, wherein, it further includes, if the conditions are met, sending a fifth indication to the second user device for display to place the consolidated shipment in at least one storage unit and packaging the consolidated shipment in at least one common package.
16. The method according to claim 15, wherein, it further includes, if the conditions are met; Send a sixth instruction to load the common parcel for delivery onto a delivery vehicle based on an arrangement determined by a committed delivery date for each of the plurality of items; and Use the second user device to display a visual representation of the loading arrangement of a plurality of containers in the delivery vehicle.
17. The method according to claim 16, wherein, Tracking the delivery status of the customer order includes updating the at least one database using information related to placing the consolidated shipment in at least one storage unit, packaging the consolidated shipment in the at least one common parcel, loading the common parcel for delivery onto a delivery vehicle, and the delivery schedule of the common parcel for delivery.
18. The method according to claim 10, wherein, Tracking the delivery status of the customer order includes updating the database using information related to at least one of the first sorting process, the second sorting process, placing the items in the container, loading the container into the delivery vehicle, and the delivery schedule of the placed items.
19. A computer-implemented parcel delivery system, wherein, The system includes: A memory storing instructions; and At least one processor configured to execute the instructions to: Receive a customer order by a computer-implemented system; Generate an order identifier based on the customer order using the computer-implemented system; Associate each of the plurality of items of the customer order with the order identifier; Determine an expected delivery destination for each item, a storage space associated with the expected delivery destination, a delivery route, and a parcel count based on the order identifier; Determine a first location of a first user device configured to send the first location of the user holding the first user device; Generate a signal to the first user device based on determining that a first item of the customer order is classified as urgent, wherein the first user device is located at the location closest to the first item determined by the first location; Determine whether the parcel count has reached or exceeded a threshold amount; If the parcel count has not reached or exceeded the threshold amount, process each of the plurality of items including the first item as a separate shipment by performing a delivery process, including: Send a first instruction to a second user device for display and for each item available for sorting to sort the item into a storage space associated with the expected delivery destination using a first sorting process; For each item sorted into the storage space, receive a first input related to the status of the first sorting process from the second user device; Send a second instruction to the second user device for display and for each item sorted into the storage space to sort the item into a storage unit associated with a delivery route configured to include the expected delivery destination using a second sorting process, regardless of the status of the first sorting process; For each item sorted into the storage unit, receive a second input from the second user device related to the status of the second sorting process; Send a third indication to the second user device for display and for each item sorted into the storage unit to place the item into a container associated with the delivery route, regardless of the status of the second sorting process; For each item placed into the container, receive a third input from the second user device related to placing the item into the container; Send a fourth indication to the second user device for display and for each item placed into the container to load the container onto a delivery vehicle associated with the intended delivery destination, regardless of the status of the other items in the plurality of items of the customer order; if the package count reaches or exceeds the threshold amount, process each item of the plurality of items as a consolidated shipment by sending a fifth indication to the second user device for display to place the plurality of items in at least one storage unit and package each placed item in at least one common package; and In response to receiving the first input, the second input, and the third input, track the delivery status of the customer order by updating at least one database.
20. The system according to claim 19, wherein, further comprising, the processor is further configured to, if the order identifier meets a condition, then: Send a sixth indication to load the common package for delivery onto the delivery vehicle based on an arrangement determined by the committed delivery date for each item of the plurality of items; and Use the second user device to display a visual representation of the loading arrangement of the plurality of containers in the delivery vehicle.
Citation Information
Patent Citations
Computerized systems and methods for package delivery
US20200372437A1
Shipment splitting analyzer
US8560461B1