TWI860950B - Computerized system and computer-implemented method for package management - Google Patents

Abstract

The present disclosure provides a computerized method for package management, including: receiving an item identifier corresponding to an item in response to the item being shipped; receiving a container identifier corresponding to a container comprising the item; converting the item identifier and container identifier into a standardized entry; storing the standardized entry in a data structure, the data structure correlating the item identifier with the container identifier; generating a message comprising at least one of the container identifier or a location in response to a query comprising the item identifier; and transmitting the message to a user responsible for the query.

Description

Computerized system and computer-implemented method for package management

The present disclosure generally relates to computerized systems and methods for improving package tracking efficiency. Specifically, embodiments of the present disclosure relate to innovative and non-traditional systems and methods for providing tracking information updates for groups of items and applying the updates to subordinate groups and individual items.

Modern shipping methods provide customers with tracking updates that enable them to view the shipping status of items in transit. This increases customer satisfaction by allowing customers to more clearly see packages in transit and providing increased predictability of when a package may arrive.

However, providing high-fidelity tracking updates for large numbers of packages often requires shippers to manually collect large amounts of data. For example, a shipper may need to individually scan each item arriving and departing from a midpoint (such as a transshipment hub) to ensure that customers have access to tracking information and provide a location log to help locate lost items. In addition to requiring cumbersome data collection methods, individual scans also add delays and increase the number of personnel required to load, unload, and transfer items during the transshipment process.

Additionally, some shippers group packages into larger collections of items for faster loading and unloading (e.g., by forklifts in warehouses). Furthermore, shippers may have "nested" groupings of items. For example, a shipper may group items into packages, packages into pallets, pallets into trucks, and trucks into warehouses.

While nested groupings of packages enable faster transfers and loading, this approach inhibits tracking individual items with the fidelity that modern consumers expect. Gathering status updates for the many items held within nested groupings is often cumbersome, time-consuming, and error-prone because warehouse operators and delivery personnel may have to account for each item hidden within multiple layers of nested groupings, thus adding additional unloading and loading steps to verify the presence of each item within the larger grouping. For example, when a truck carrying a pallet containing packages with items arrives at a location, an employee may need to confirm the pallet, packages, and items on the truck and update the location of each entity at each nested grouping layer. Without these updates, tracking fidelity may be reduced and if an item is lost, personnel may not be sure where to find it.

To further illustrate, in some traditional approaches, items may be recorded when entering a shipping stream at a point of origin and when exiting a shipping stream at a destination. However, if an item is lost after entering a transit stream, the shipper may not be able to determine where the item was lost without having high-fidelity tracking information for each item throughout the shipment. Locating the lost item may be even more difficult if the item is grouped with other items or transferred between warehouses and trucks. In addition, the shipper may not be able to determine the responsible party (e.g., a worker who misplaced or stole the item) and is also unable to identify and prevent loss trends.

Therefore, there is a need for improved methods and systems that enable low-cost, efficient shipping through nested grouping of items while also providing high-fidelity tracking of individual items.

One aspect of the present disclosure relates to a computerized system for package management, the computerized system comprising: at least one processor; and at least one non-transitory storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform steps. The steps include: receiving an item identifier corresponding to the item in response to the item being shipped; receiving a container identifier corresponding to the container including the item; converting the item identifier and the container identifier into a standardized table; storing the standardized table in a data structure that associates the item identifier with the container identifier; generating a message including at least one of the container identifier or the location in response to a query including the item identifier; and transmitting the message to a user responsible for the query.

Another aspect of the present disclosure is a computer-implemented method for package management, the computer-implemented method comprising: receiving an item identifier corresponding to an item in response to the item being shipped; receiving a container identifier corresponding to a container including the item; converting the item identifier and the container identifier into a standardized table; storing the standardized table in a data structure that associates the item identifier with the container identifier; generating a message including at least one of the container identifier or a location in response to a query including the item identifier; and transmitting the message to a user responsible for the query.

Another aspect of the present disclosure is related to a computer-implemented method for package management, the computer-implemented method comprising: receiving an item identifier corresponding to the item in response to the item being shipped; receiving a container identifier corresponding to a container including the item; converting the item identifier and the container identifier into a standardized table; storing the standardized table in a data structure, the data structure associating the item identifier with the container identifier; in response to the container being loaded into a transport container, The invention relates to a method for detecting a vehicle identifier corresponding to a container on a vehicle; updating the standardized entry in the data structure to associate the vehicle identifier with the container; receiving an indication of the location of the vehicle; updating the standardized entry in the data structure to include the location; generating a message including at least one of the vehicle identifier, the container identifier, or the location in response to a query including the item identifier; and transmitting the message to a user responsible for the query.

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

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

Embodiments of the present disclosure relate to systems and methods configured for efficiently grouping ordered items into packages.

Referring to FIG. 1A , a schematic block diagram 100 is shown that illustrates an exemplary embodiment of a system including a computerized system for shipping, transportation, and logistics operations capable of communication. As shown in FIG. 1A , the system 100 may include various systems, each of which may be connected to each other via one or more networks. The systems may also be connected to each other via direct connections (e.g., using cables). 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 (WMS) 119, mobile devices 119A, 119B, and 119C (shown as being located within a fulfillment center (FC) 200), and a 3rd party fulfillment (3 ^rd party fulfillment, 3PL) systems 121A, 121B and 121C, fulfillment center authorization system (FC Auth) 123 and labor management system (LMS) 125.

In some embodiments, the SAT system 101 may be implemented as a computer system that monitors order status and delivery status. For example, the SAT system 101 may determine whether an order has exceeded its Promised Delivery Date (PDD), and may take appropriate actions including placing a new order, reshipping items in an undelivered order, canceling an undelivered order, initiating contact with the ordering customer, etc. The SAT system 101 may also monitor other data including output (e.g., the number of packages shipped during a specific time period) and input (e.g., the number of empty cartons received for shipping). The SAT system 101 may also act as a gateway between different devices in the system 100, enabling communication between devices such as the external front-end system 103 and the FO system 113 (e.g., using store-and-forward or other techniques).

In some embodiments, the external front-end system 103 may be implemented as a computer system that enables external users to interact with one or more systems in the system 100. For example, in an embodiment in which the system 100 is capable of presenting a system so that a user can place an order for an item, the external front-end system 103 may be implemented as a website server that receives search requests, presents an item page, and solicits payment information. For example, the external front-end system 103 may be implemented as one or more computers running software such as Apache Hypertext Transfer Protocol (HTTP) server, Microsoft Internet Information Services (IIS), NGINX, etc. In other embodiments, the external front-end system 103 may run customized website server software that is designed to receive and process requests from external devices (e.g., mobile device 102A or computer 102B), obtain information from databases and other data stores based on those requests, and provide responses to the received requests based on the obtained information.

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

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

The external front-end system 103 may prepare an SRP based on the information (e.g., FIG. 1B ). The SRP may include information that satisfies the search request. For example, this may include pictures of products that satisfy the search request. The SRP may also include the corresponding price of each product, or information related to enhanced delivery options, PDD, weight, size, offers, discounts, etc. for each product. The external front-end system 103 may send the SRP to the user device that issued the request (e.g., via a network).

The user device may then select a product from the SRP, for example, by clicking or tapping on the user interface (or using another input device) to select a product presented on the SRP. The user device may 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 may request information related to the selected product. For example, the information may include additional information in addition to the information presented for the product on the corresponding SRP. This additional information may include, for example, shelf life, country of origin, weight, size, number of items in a package, handling instructions, or other information about the product. The information may also include suggestions for similar products (e.g., based on big data and/or machine learning analysis of customers who purchased the product and at least one other product), answers to frequently asked questions, reviews from customers, manufacturer information, pictures, etc.

The external front-end system 103 may prepare a single detail page (SDP) (e.g., FIG. 1C ) based on the received product information. The SDP may also include other interactive elements such as a “Buy Now” button, an “Add to Cart” button, a quantity field, an item picture, and the like. The SDP may further include a list of sellers that provide the product. The list may be sorted based on the price offered by each seller, so that the seller offering the product at the lowest price may be listed at the top. The list may also be sorted based on seller rankings, so that the highest-ranked seller may be listed at the top. Seller rankings may be determined based on a variety of factors, including, for example, a seller's past tracking record of meeting the promised PDD. The external headend system 103 may deliver the SDP to the requesting user device (eg, via a network).

The requesting user device may receive an SDP listing product information. After receiving the SDP, the user device may then interact with the SDP. For example, a user of the requesting user device may click on or otherwise interact with an "add to cart" button on the SDP. This will add the product to a shopping cart associated with the user. The user device may transmit such a request to add a product to a shopping cart to an external front-end system 103.

The external front-end system 103 may generate a shopping cart page (e.g., FIG. 1D ). In some embodiments, the shopping cart page lists products that have been added to a virtual “shopping cart” by the user. The user device may request the shopping cart page by clicking on an icon on the SRP, SDP, or other page or otherwise interacting with an icon on the SRP, SDP, or other page. In some embodiments, the shopping cart page may list all products that have been added to the shopping cart by the user, as well as information about the products in the shopping cart, such as the quantity of each product, the unit price of each product, the price of each product based on the associated 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 additional products or setting up recurring delivery of products, options for setting interest payments, user interface elements for continuing purchases, etc. A user at a user device may click on or otherwise interact with a user interface element (e.g., a button that reads "Buy Now") to initiate a purchase of the products in the shopping cart. In doing so, the user device may transmit such a request to initiate a purchase to the external front-end system 103.

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

The user device may enter information on the order page and click on or otherwise interact with user interface elements that send the information to the external front end system 103. The external front end system 103 may send information from the user interface elements to different systems in the system 100 to enable a new order to be created and processed with the products in the shopping cart.

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

In some embodiments, the internal front-end system 105 may be implemented as a computer system that enables internal users (e.g., employees of an organization that owns, operates, or leases the system 100) to interact with one or more systems in the system 100. For example, in an embodiment in which the system 101 is capable of presenting a system so that a user can place an order for an item, the internal front-end system 105 may be implemented as a website server that enables an internal user to view diagnostic and statistical information about an order, modify item information, or check statistics related to an order. For example, the internal front-end system 105 may 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 may run custom website server software that is designed to receive and process requests from systems or devices shown in the system 100 (as well as other 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.

In some embodiments, the internal front-end system 105 may include one or more of a website cache 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 may include one or more of these systems, and in another aspect, the internal front-end system 105 may include an interface (e.g., server-to-server, database-to-database, or other network connection) connected to one or more of these systems.

In some embodiments, the transport system 107 may be implemented as a computer system that enables communication between systems or devices in the system 100 and mobile devices 107A to 107C. In some embodiments, the transport system 107 may receive information from one or more mobile devices 107A to 107C (e.g., mobile phones, smart phones, personal digital assistants (PDAs), etc.). For example, in some embodiments, the mobile devices 107A to 107C may include devices operated by delivery workers. Delivery workers (who may be permanent, temporary, or shift employees) may utilize mobile devices 107A to 107C to effectuate the delivery of packages containing products ordered by users. For example, to deliver a package, a delivery worker may receive a notification on a mobile device indicating which package to deliver and where to deliver the package. Upon arriving at the delivery location, the delivery worker may use the mobile device to locate the package (e.g., in the back of a truck or in a crate of packages), scan or otherwise capture data associated with an identifier on the package (e.g., a barcode, image, text string, radio frequency identification (RFID) tag, etc.), and deliver the package (e.g., by leaving the package at the front door, leaving it with security guards, handing it to the recipient, etc.). In some embodiments, the delivery worker may use the mobile device to capture a photo of the package and/or may use the mobile device to obtain a signature. The mobile device may send information to the transport system 107 including information about the delivery, such as the time, date, Global Positioning System (GPS) location, photos, an identifier associated with the delivery worker, an identifier associated with the mobile device, etc. The transport system 107 may store this information in a database (not shown) for access by other systems in the system 100. In some embodiments, the transport system 107 may use this information to prepare and send tracking data to other systems indicating the location of a particular package.

In some embodiments, certain users may use one type of mobile device (e.g., a permanent worker may use a dedicated PDA with customized hardware such as a bar code scanner, stylus, and other devices) while other users may use other types of mobile devices (e.g., temporary or shift workers may utilize off-the-shelf cell phones and/or smartphones).

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

In some embodiments, the seller portal 109 may be implemented as a computer system that enables a seller or other external entity to electronically communicate with one or more systems in the system 100. For example, a seller may utilize 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 using the seller portal 109.

In some embodiments, the shipping and order tracking system 111 may be implemented as a computer system that receives, stores, and transmits information about the location of packages containing products ordered by customers (e.g., by users using devices 102A-102B). In some embodiments, the shipping and order tracking system 111 may request or store information from a website server (not shown) operated by a shipping company that delivers packages containing products ordered by customers.

In some embodiments, the shipping and order tracking system 111 can request and store information from the systems depicted in the system 100. For example, the shipping and order tracking system 111 can request information from the transportation system 107. As discussed above, the transportation system 107 can receive information from one or more mobile devices 107A-107C (e.g., mobile phones, smart phones, PDAs, etc.) that are in communication with one or more of a user (e.g., a delivery worker) or a vehicle (e.g., a delivery truck). In some embodiments, the shipping and order tracking system 111 can also request information from a warehouse management system (WMS) 119 to determine the location of individual products 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 the WMS 119, process it, and present it to a device (e.g., user devices 102A and 102B) based on the request.

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

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

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

In some embodiments, the fulfillment messaging gateway (FMG) 115 may be implemented as a computer system that receives requests or responses in one format or protocol from one or more systems in the system 100 (e.g., the FO system 113), converts them into another format or protocol, and transmits them in the converted format or protocol to other systems such as the WMS 119 or third-party fulfillment systems 121A, 121B, or 121C, and vice versa.

In some embodiments, the supply chain management (SCM) system 117 may be implemented as a computer system that performs forecasting functions. For example, the SCM system 117 may forecast the demand level for a specific product based on, for example, past demand for the product, expected demand for the product, past demand for the entire network, expected demand for the entire network, product counts stored in each fulfillment center 200, expected orders or current orders for each product, etc. Based on such forecast levels and the quantity of each product in all fulfillment centers, the SCM system 117 may generate one or more purchase orders to purchase and store sufficient quantities to meet the forecast demand for the specific product.

In some embodiments, a warehouse management system (WMS) 119 may be implemented as a computer system that monitors workflow. For example, the WMS 119 may receive event data from individual devices (e.g., devices 107A-107C or 119A-119C) indicating discrete events. For example, the WMS 119 may receive event data indicating that a package was scanned using one of the devices. As discussed below with reference to fulfillment center 200 and FIG. 2 , during the fulfillment process, a package identifier (e.g., barcode or RFID tag data) may be scanned or read by a machine (e.g., an automated or handheld barcode scanner, an RFID reader, a high-speed camera, a device such as tablet 119A, a mobile device/PDA 119B, a computer 119C, or the like) at certain stages. WMS 119 may store each event indicating a scan or read 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., shipping and order tracking system 111).

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

In some embodiments, WMS 119 may maintain a work log for each user associated with system 100. For example, WMS 119 may store information associated with each employee, including any assigned processes (e.g., unloading a truck, picking items at a pick-up area, rebining wall work, packaging items), user identifiers, locations (e.g., floors or areas in fulfillment center 200), the number of units the employee moved through the system (e.g., number of items picked, number of items packaged), identifiers associated with devices (e.g., devices 119A-119C), and the like. In some embodiments, WMS 119 may receive check-in information and check-out information from a timing system, such as a timing system operating on devices 119A-119C.

In some embodiments, third-party fulfillment (3PL) systems 121A-121C represent computer systems that communicate with third-party providers of logistics and products. For example, while some products are stored in fulfillment center 200 (as discussed below with respect to FIG. 2 ), other products may be stored off-site, may be produced on demand, or may not otherwise be stored in fulfillment center 200. 3PL systems 121A-121C may be configured to receive orders from FO system 113 (e.g., via FMG 115 ) and may provide products and/or services (e.g., delivery or installation) directly to customers. In some embodiments, one or more of the 3PL systems 121A-121C may be part of the system 100, while in other embodiments, one or more of the 3PL systems 121A-121C may be external to the system 100 (e.g., owned or operated by a third-party provider).

In some embodiments, fulfillment center authorization system (FC Auth) 123 may be implemented as a computer system having various functions. For example, in some embodiments, FC Auth 123 may act as a single-sign on (SSO) service for one or more other systems in system 100. For example, FC Auth 123 may enable a user to log in via internal front-end system 105, determine that the user has similar privileges to access resources at shipping and order tracking system 111, and enable the user to access those privileges without requiring a second login process. In other embodiments, FC Auth 123 may enable a user (e.g., an employee) to associate themselves with a specific task. For example, some employees may not have electronic devices (e.g., devices 119A-119C), but may instead move between tasks and between zones during the course of a day within fulfillment center 200. FC Auth 123 may be configured to enable these employees to indicate what tasks they are performing and what zone they are in at different times of the day.

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

The specific configuration shown in FIG. 1A is only an example. For example, although FIG. 1A shows that the FC Auth system 123 is connected to the FO system 113, not all embodiments require such a specific configuration. In fact, in some embodiments, the systems in the system 100 can be connected to each other through one or more public or private networks including: the Internet, an intranet, a wide area network (WAN), a metropolitan area network (MAN), a wireless network that complies with the Institute of Electrical and Electronic Engineers (IEEE) 802.11a/b/g/n standards, a leased line, etc. In some embodiments, one or more of the systems in system 100 may be implemented as one or more virtual servers implemented at a data center, server farm, or the like.

FIG. 2 illustrates a fulfillment center 200. A fulfillment center 200 is an example of a physical location where items are stored for shipment to customers when ordered. A fulfillment center (FC) 200 may be divided into a plurality of zones, each of which is illustrated in FIG. 2 . In some embodiments, the “zones” may be viewed as virtual divisions between different stages of the process of receiving items, storing items, picking up items, and shipping items. Thus, although “zones” are illustrated in FIG. 2 , other divisions of zones may exist, and in some embodiments, the zones in FIG. 2 may be omitted, duplicated, or modified.

Inbound area 203 represents an area of FC 200 that receives items from sellers who wish to sell products using system 100 from Figure 1A. For example, a seller may deliver items 202A and 202B using truck 201. Item 202A may represent a single item that is large enough to occupy its own shipping pallet, while item 202B may represent a group of items that are stacked together on the same pallet to save space.

The worker will receive the items in the inbound area 203 and can optionally check the items for damage and correctness using a computer system (not shown). For example, the worker can use the computer system to compare the quantities of items 202A and 202B with the quantities of items ordered. If the quantities do not match, the worker can reject one or more of the items 202A or 202B. If the quantities match, the worker can move the items (using, for example, a cart, a hand truck, a forklift, or manually) to a buffer zone 205. The buffer zone 205 can be a temporary storage area for items that are not currently needed in the picking zone (for example, because there is a sufficiently high amount of such items in the picking zone to meet the forecast demand). In some embodiments, the forklift 206 operates to move items around in the buffer zone 205 and between the inbound zone 203 and the unloading zone 207. If the item 202A or 202B is needed in the picking zone (e.g., due to forecasted demand), the forklift can move the item 202A or 202B to the unloading zone 207.

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

The picking area 209 may be an area of the FC 200 where items 208 are stored on storage units 210. In some embodiments, the storage units 210 may include one or more of physical shelving, bookcases, boxes, shipping boxes, refrigerators, freezers, cold storage, etc. In some embodiments, the picking area 209 may be organized into multiple floors. In some embodiments, workers or machines may move items into the picking area 209 in a variety of ways including, for example, forklifts, elevators, conveyor belts, transporters, carts, trolleys, carts, automated robots or devices, or manual methods. For example, the picker may place items 202A and 202B on a cart or transporter in the unloading area 207 and walk the items 202A and 202B to the picking area 209.

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

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

The packaging area 211 may be the area of the FC 200 where the self-picking area 209 receives items and packages them into boxes or bags for final shipment to customers. In the packaging area 211, a worker assigned to receive items (a "rebin worker") receives the item 208 from the self-picking area 209 and determines what order the item 208 corresponds to. For example, the rebin worker may use a device such as a computer 119C to scan a bar code on the item 208. The computer 119C may visually indicate which order the item 208 is associated with. For example, this may include a space or "cell" on the wall 216 that corresponds to the order. Once the order is complete (e.g., because the cell accommodates all of the items for the order), the distribution worker may indicate to the packaging worker (or "packer") that the order is complete. The packer may pick the items from the cell and place them into boxes or bags for shipment. The packer may then send the boxes or bags to a hub zone 213, such as by forklift, truck, dolly, wheelbarrow, conveyor, manual means, or other means.

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

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

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

FIG. 3 is an illustration of item tracking layers according to disclosed embodiments. A package management system according to the present disclosure may provide item tracking at any of a plurality of layers of nested groupings. For example, as shown in FIG. 3 , a plurality of items 208 may be in transit, such as between a warehouse and a customer. The items may be grouped together in one of a plurality of packages 218. The plurality of packages may be further grouped into one of a plurality of pallets 302. Additionally, a plurality of pallets 302 may be grouped into one of a plurality of trucks 222. Still further, a plurality of trucks may be present at a fulfillment center 200 or other transfer area.

To illustrate, a customer may purchase multiple items from an e-commerce site that has a fulfillment center. An employee at the e-commerce site may place the items purchased by the customer into a box. The employee may create a pallet that holds the customer's box and multiple other boxes with a destination similar to the customer's destination, such as the same apartment building. The employee may also group multiple pallets with similar destination areas together and load the multiple pallets onto a truck. For example, pallets that hold boxes for customers in a certain city may be grouped into a truck. The truck may be loaded at the fulfillment center along with multiple other trucks that may have the same or different destinations.

Thus, an item may be associated with a package 218, a pallet 302, a truck 222, and a fulfillment center 200. Similarly, a warehouse may be associated with multiple trucks, pallets, packages, and items; a truck may be associated with multiple pallets, packages, and items; a pallet may be associated with multiple packages and items; and a package may be associated with multiple items. The number of grouping layers discussed above is non-limiting. Thus, for example, in some embodiments, one or more additional grouping layers may also be introduced, such as a collection of fulfillment centers in a region.

4 is a flow chart showing an exemplary embodiment of a package management process 400 according to the disclosed embodiments. For example, the FO system 113 can run the process 400 to provide shipment tracking services to customers and help locate lost items and identify loss trends.

In step 402, the FO system 113 may receive an item identifier corresponding to the item in response to the item being shipped. For example, when a customer places an order from an e-commerce site, the item shipment may be initiated. Additionally, when a person provides the item to a shipping service, the item shipment may be initiated. In some embodiments, the item may be a return item shipped by a purchaser back to a seller. Additionally, at step 402, the shipper may assign an item identifier and provide the item identifier to the FO system 113. The item identifier may also be provided by the customer (e.g., in the case of a return). In some embodiments, the FO system 113 may also assign an item identifier. For example, an item identifier may indicate the item's type, size, weight, stock keeping unit (SKU), Universal Product Code (UPC), price, or return number. An item identifier may also be a free-text description of the item.

In step 404, the FO system 113 may receive a container identifier corresponding to a container including the item. The container may be a package 218 as shown in FIG. 3 and may include a box or a bag. The container may also be a pallet 302 as shown in FIG. 3. The container may also include a shipping container, such as a 20' x 40' Container Express (CONEX) box or other sized shipping container, which may facilitate the shipment of large items. In some embodiments, the container may also be a collection of smaller boxes secured by external straps or wrapping.

In addition, the container identifier may be a code assigned to the container. The code may include container specifications, such as container type, size, stacking restrictions, measured weight, or maximum weight. The code may also indicate storage requirements, such as refrigeration, climate control, or dry storage. In addition, the code may be a unique serial number assigned to the container by the manufacturer, for example. The container identifier may be determined by reading a barcode on the container. For example, when placing an item inside the container, a technician may scan the barcode using a mobile device 107A to 107C. The identifier may also be determined by scanning a Quick Response (QR) code. In some embodiments, the container identifier can be determined by reading an RFID tag placed on or in the container. For example, the RFID tag of the container can be scanned when the container enters the loading area of the warehouse.

In step 406, the FO system 113 may convert the item identifier and the container identifier into standardized entries. For example, a shipper may use multiple container types from different manufacturers, each of which has a different serial number pattern. The FO system 113 may convert the size and weight of the container or item from metric units to standard units. In addition, the FO system 113 may use, for example, regular expressions to extract data portions of the item identifier and the container identifier and use the extracted portions to fill in the fields of the format. The FO system 113 may also perform text manipulation (i.e., character replacement, removal, and addition). In addition, the FO system 113 may execute code to fill in the template based on the information provided by the item identifier or the container identifier. The FO system 113 may also execute code to perform automated structured query language (SQL) queries and obtain the information needed to populate the template. For example, the FO system 113 may query a database based on a received container serial number to determine the manufacturer of the container or may extract an origin or destination based on an item identifier.

In step 408, the FO system 113 may store the standardized table entries in a data structure that associates item identifiers with container identifiers. The data structure may be, for example, a JavaScript Object Notation (JSON) file or other dictionary with keys and corresponding values. The data structure may also be an SQL table. The FO system 113 may store the data structure in memory, or the data structure may be stored in a database accessed by the FO system 113. To further illustrate, in some embodiments, the data structure may be a JSON file. The JSON file may have a key for each container tracked by the FO system 113. Each container key may correspond to a list of item identifiers.

The JSON file may be hierarchical to match the nested grouping layers, as presented in FIG3 . For example, as shown in FIG3 , a pallet with packages may be loaded onto a truck. Thus, the data structure may further include an identifier for a vehicle, the vehicle identifier being stored in association with at least one container identifier. In various embodiments, the vehicle may be any mode of transportation, such as a truck, a box truck, an airplane, a ship, or a train. Additional hierarchical data structure layers are also contemplated, including storage area identifiers, the storage area identifiers being associated with at least one vehicle. The storage area may correspond to the type of vehicle and may include, for example, an airport, a train station, a fulfillment center, a parking lot, or a port.

For example, a JSON file may be keyed by a fulfillment center identifier. Each fulfillment center key may have a corresponding value, which is another JSON file keyed by a vehicle identifier. Each vehicle may also have a corresponding value, which is a JSON file keyed by a pallet identifier. Each pallet identifier may have a corresponding file, which is a JSON file keyed by a package identifier, and each package identifier may have a value that is a list of item identifiers for the items contained in the package. To further illustrate, a data structure may be in the format of {fulfillment center:{vehicle:{pallet:{package:item}}}}. Thus, an item may be identified in the data structure by specifying its fulfillment center, vehicle, pallet, and/or package. The FO system 113 may also index the data structure by item identifier so that a given item identifier returns the corresponding fulfillment center, vehicle, pallet, and package. In some embodiments, the data structure may be partitioned and stored in subsets to enable faster searching of large data sets.

In step 410, the FO system 113 may receive a query including an item identifier. For example, the query may be submitted by a shipment customer requesting the tracking status of an item via a website. Alternatively, a shipment manager may submit a query to an internal shipment tracking system. In some embodiments, the FO system 113 may receive or generate multiple queries, which may enable statistical analysis of item movements. At step 412, the FO system 113 may access the data structure and identify at least one container identifier corresponding to the item identifier of the query and generate a message including the container identifier. In addition, the FO system 113 can capture the location associated with the container identifier and generate a message including the location. For example, in some embodiments, the data structure can have entries for trucks, containers, and items. In addition, the data structure can store the location associated with the truck. The FO system 113 can receive a query for an item identifier, find the item identifier in the data structure, and access higher level groups of item identifiers until the FO system 113 locates, for example, a location record of the vehicle carrying the identifier. In some embodiments, the FO system 113 may receive a query for an identifier (e.g., a container identifier, a warehouse identifier, or a vehicle identifier) at any level of the nested grouping hierarchy represented by the data structure. In addition, at step 414, the FO system 113 may transmit a message to the user responsible for the query, such as via a website, an application, a text message, etc. The FO system 113 may also provide an analysis of the data structure in response to the query, such as counting dependent items (i.e., the number of item identifiers associated with the provided vehicle identifier). The FO system 113 may then return to step 402 to receive additional item identifiers, or in some embodiments, return to step 410 to receive additional queries. In addition, the FO system 113 may simultaneously receive item identifiers while receiving queries.

Additionally, as previously described, the key to each object in the nested grouping layers of the data structure may be obtained by scanning a barcode, QR code, or RFID tag. In some embodiments, the data structure may also store the location of each object, such as provided by a GPS tracking device located on each entity. For example, each container on a truck may have a GPS tracking device. When a container is scanned, the GPS tracking device may report the location of the container, or an automatic report may be sent to the FO system 113. The FO system 113 may also receive container location reports and access the data structure to determine other containers corresponding to the same vehicle. If a container has a different location report than any of the other containers, the FO system 113 may mark the container as misplaced and provide a message to the shipment supervisor.

The above data structure can enable faster updating of item status. For example, the FO system 113 can receive the status of any of the grouping layers of the data structure, such as location and timestamp. For example, a truck can arrive at a warehouse location. When the truck arrives, a worker can scan the QR code on the truck to determine the truck identifier and send the truck identifier to the FO system 113. The FO system 113 can in turn access the data structure to locate the entry corresponding to the scanned truck identifier and update the fields in the data structure with the truck location. The FO system 113 can also update the fields at each level of the data structure so that every pallet, package, and item on the truck is updated with the latest truck location. In this way, the FO system 113 may enable high-fidelity tracking of every item on a vehicle without requiring a worker to individually record each item on the vehicle.

In addition, the above data structure can facilitate rapid loading and unloading of containers from a vehicle without losing item tracking fidelity. For example, a warehouse operator using a mobile device (e.g., mobile devices 119A-119C) can scan a container such as pallet 302 and send a loading instruction for the container to be loaded onto a vehicle (e.g., truck 222). The operator can also scan the vehicle and additional containers at the same location or at different locations, and the operator's mobile device can send additional loading instructions corresponding to the additional containers on the vehicle. The FO system 113 can then associate the initial container and the additional containers with the vehicle identifier of the vehicle in the data structure.

The FO system 113 may then receive an unloading indication, such as from a warehouse operator, that a container is being removed from a vehicle. For example, a warehouse operator may be working at a shipping hub and may need to transfer a container from one truck arriving at the hub to another truck leaving the hub. The FO system 113 may disassociate the container from the vehicle in the data structure in response to the unloading indication. The FO system 113 may then associate the container to a retention entry of the data structure that indicates that the container is at the warehouse but has not yet been loaded onto a truck. The new association may also be applied to each item corresponding to the container. In other words, the FO system 113 may apply a state change recorded at a higher level in the hierarchy in the data structure to each subordinate level in the data structure. Thus, packages in unloaded containers and items in packages may have the same position and state in the data structure as the container. In addition, the FO system 113 may receive a message, such as from a warehouse operator or warehouse manager, that the vehicle should be emptied, and in response to the message, disassociate at least one additional container from the vehicle.

Still further, the operator may transfer a container from a first vehicle to a second vehicle. For example, the operator may transfer items from a small delivery truck (i.e., a local delivery truck suitable for city streets and alleys) to a large delivery truck (i.e., a regional delivery truck that carries items across highways from multiple local delivery trucks) or other conveyance. The large regional delivery truck may transfer items from a first transfer hub to a second transfer hub, such that the first transfer hub receives packages from multiple nearby origins and the second transfer hub delivers the packages to destinations close to the second transfer hub. For example, a first transfer hub may collect items from an origin within 30 miles of the first transfer hub (e.g., a return shipment from a customer), and a second transfer hub may deliver items to a destination within 30 miles of the second transfer hub, and the first transfer hub and the second transfer hub may be 300 miles apart. Thus, to enable faster transfers between vehicles at, for example, transfer hubs, the FO system 113 may associate the container and the at least one additional container to the second vehicle in a data structure in response to the container and the additional container being transferred to the second vehicle while also providing status tracking updates for each item being transferred.

For example, after the operator scans the vehicle identifier, the operator's mobile device may ask the operator if all containers on the vehicle will be unloaded. If the operator indicates yes, the mobile device may also ask the operator if the containers will be loaded onto a second vehicle. If the operator indicates yes again, the mobile device may send a message to the FO system 113, and in response, the FO system 113 may disassociate all containers from the old vehicle and reassociate all containers with the new vehicle. In addition, the mobile device may request the operator to indicate a destination hub identifier, and the FO system 113 may automatically receive the destination and store it in a data structure associated with the new vehicle.

Furthermore, in addition to unloading operations, the FO system 113 may also enable fast tracking of loading operations. For example, the FO system 113 may receive a loading indication that a container is being loaded onto a new vehicle along with a new vehicle identifier, and the FO system 113 may associate the container and its dependent entries in the data structure with the new vehicle.

The FO system 113 can also ensure full utilization of the transport vehicle. For example, the FO system 113 can receive a completion message indicating that the vehicle is loaded and retrieve the vehicle container capacity. For example, the vehicle container capacity can be stored in a database and the FO system 113 can construct a query to access the database and determine the number of containers that can be assembled on the vehicle. In some embodiments, the FO system 113 can capture the vehicle volume and determine the number of containers based on the container size, such as when containers of various sizes are loaded onto the vehicle. In addition, the FO system 113 can capture the vehicle weight capacity and the container weight.

The FO system 113 may also determine the number of containers associated with the vehicle by accessing the data structure and send a vehicle underloaded message to the user device for display when the number of containers is less than the vehicle container capacity. Similarly, the FO system 113 may send a vehicle underloaded message when the weight of the containers is less than the vehicle weight capacity or the total volume of the containers is less than the vehicle volume capacity. In this way, the FO system 113 may utilize the characteristics of the data structure to quickly determine whether vehicle utilization is being optimized, thereby reducing inefficiencies during shipping operations.

The high speed, high fidelity tracking update method disclosed herein can also enable shipping organizations to quickly detect loss patterns. FIG5 is a flow chart showing an exemplary embodiment of an employee error detection process 500 according to the disclosed embodiment. The employee error detection process 500 can also be modified to detect container, warehouse or vehicle failures.

At step 502, the FO system 113 may record an employee identifier corresponding to the employee who indicated that the container was present on the vehicle. The employee identifier may be provided by a mobile device used by the employee when scanning an indicator code on the container when loading the container onto the vehicle. The employee identifier may be stored in a data structure associated with the container, thereby providing a record of which employee was most recently responsible for the container.

At step 504, the FO system 113 may receive a lost item notification. A lost item notification may be triggered by a customer who has not received an expected shipment, or by a follow-up employee who discovers that a container is not present on a vehicle when unloading the vehicle. In addition, the FO system 113 may run an automatic check of the data structure to locate containers that have not been recorded as moved within a set time period and identify such containers and corresponding items as lost. For example, if a container has not been scanned for more than one day, this may indicate that the container has not been in transit, and the FO system 113 may generate a lost item notification for the items associated with the container.

At step 506, the FO system 113 may determine the lost item identifier based on the lost item notification by accessing the data structure. At step 508, the FO system 113 may determine the nearest vehicle identifier corresponding to the lost item identifier by accessing the data structure. The nearest vehicle identifier may correspond to the last vehicle that was specified to carry the container with the lost item. Additionally, at step 510, the FO system 113 may determine the responsible employee corresponding to the nearest vehicle identifier by accessing the data structure. In other words, the responsible employee may be the employee who indicated that the container was on the vehicle even though the container was not on the vehicle.

At step 512, the FO system 113 may increment a missing item count associated with the responsible employee. For example, the missing item count may be stored in a separate data structure associated with the employee identifier.

In some cases, the missing items that the employee last loaded may be lost due to additional actions by others. For example, the employee may properly load and secure the container on the truck. However, while the truck is in transit, a thief may steal the container or the items inside the container. Therefore, the missing items may not be the employee's fault. However, if many items associated with the employee are missing, the trend may indicate that the employee is responsible and the shipper may investigate the employee.

Therefore, at step 514, the FO system 113 may compare the lost item count to a threshold value. If the lost item count is less than the threshold value, step 514 is no and the FO system 113 may return to step 502. Alternatively, if the lost item count is greater than the threshold value, step 514 is yes and the FO system 113 may proceed to step 516 to provide a message to the user device for display, the message including identification information of the responsible employee, such as the employee number or name. The message may be provided on the supervisor's user device so that the supervisor can further investigate the employee's lost item trends.

As an exemplary embodiment of the present disclosure, a computer-implemented method for package management may include a plurality of steps. The steps may include: receiving an item identifier corresponding to the item in response to the item being shipped; receiving a container identifier corresponding to the container including the item; converting the item identifier and the container identifier into a standardized table; storing the standardized table in a data structure, the data structure associating the item identifier with the container identifier; receiving a container identifier corresponding to the container in response to the container being loaded onto a vehicle transporting the container; a vehicle identifier corresponding to the vehicle; updating a standardized entry in a data structure to associate the vehicle identifier with a container; receiving an indication of a location of the vehicle; updating the standardized entry in the data structure to include the location; generating a message including at least one of the vehicle identifier, the container identifier, or the location in response to a query including an item identifier; and transmitting the message to a user responsible for the query.

Although the present disclosure has been shown and described with reference to specific embodiments of the present disclosure, it should be understood that the present disclosure may be practiced in other environments without modification. The above description is presented for illustrative purposes. The above description is not exhaustive and is not limited to the precise forms or embodiments disclosed. Various modifications and adaptations will be apparent to those skilled in the art by considering the description 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 appreciate that the aspects may also be stored on other types of computer-readable media, such as secondary storage devices (e.g., hard disks or compact disk read-only memory (CD ROM)) or other forms of random access memory (RAM) or read-only memory (ROM), universal serial bus (USB) media, digital versatile discs (DVD), Blu-ray or other optical drive media.

Computer programs based on the written description and disclosed methods are within the skill of experienced developers. Various programs or program modules can be created using any technology known to those skilled in the art, or can be designed in conjunction with existing software. For example, program sections or program modules can be designed using or with the aid of .Net Framework, .Net Compact Framework (and related languages such as Visual Basic, C, etc.), Java, C++, Objective-C, Hypertext Markup Language (HTML), HTML/AJAX combination, Extensible Markup Language (XML), or HTML including Java applets.

In addition, although exemplary embodiments have been described herein, those skilled in the art will contemplate the scope of any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., combinations of aspects between various embodiments), adaptations and/or changes based on this disclosure. For example, in some embodiments, steps may be substituted, replaced, added, or reordered in the process without departing from the present disclosure. In addition, in some embodiments, some steps may be performed simultaneously. The limitations in the claims should be interpreted broadly based on the language used in the claims, and are not limited to the examples described in this specification or during the course of the application. The examples should be considered non-exclusive. Furthermore, the steps of the disclosed methods may be modified in any manner, including by reordering the steps and/or inserting or deleting steps. Therefore, the specification and examples are intended to be considered as illustrative only, with the true scope and spirit being indicated by the following claims and the full scope of their equivalents.

100: Schematic block diagram/system 101: Shipping authorization technology (SAT) system/system 102A: Device/user device/mobile device 102B: Device/user device/computer 103: External front-end system 105: Internal front-end system 107: Transportation system 107A, 107B, 107C: Mobile device/device 109: Seller portal 111: Shipping and order tracking (SOT) system 113: Fulfillment optimization (FO) system 115: Fulfillment messaging gateway (FMG) 117: Supply chain management (SCM) system 119: Warehouse management system (WMS) 119A: Mobile device/device/tablet 119B: Mobile device/device/PDA 119C: Mobile device/device/computer 121A, 121B, 121C: Third-party fulfillment (3PL) system 123: Fulfillment Center Authorization System (FC Auth) 125: Labor Management System (LMS) 200: Fulfillment Center (FC) 201, 222: Truck 202A, 202B, 208: Item 203: Inbound area 205: Buffer area 206: Forklift 207: Unloading area 209: Picking area 210: Storage unit 211: Packaging area 213: Central area 214: Transportation agency 215: Camp area 216: Wall 218, 220: Package 224A, 224B: Delivery Worker 226: Car 302: Pallet 400: Package Management Process/Process 402, 404, 406, 408, 410, 412, 414, 502, 504, 506, 508, 510, 512, 514, 516: Steps 500: Employee Error Detection Process

FIG. 1A is a schematic block diagram illustrating an exemplary embodiment of a network according to the disclosed embodiments, the network including a computerized system for shipping, transportation, and logistics operations capable of communication. FIG. 1B illustrates a sample Search Result Page (SRP) according to the disclosed embodiments, including one or more search results satisfying a search request and an interactive user interface element. FIG. 1C illustrates a sample Single Display Page (SDP) according to the disclosed embodiments, including products and information about the products and an interactive user interface element. FIG. 1D illustrates a sample Cart page according to the disclosed embodiments, including items in a virtual shopping cart and an interactive user interface element. FIG. 1E illustrates a sample order page including items from a virtual shopping cart and information about purchasing and shipping and interactive user interface elements according to disclosed embodiments. FIG. 2 is an illustration of an exemplary fulfillment center configured to utilize the disclosed computerized system according to disclosed embodiments. FIG. 3 is an illustration of an item tracking layer according to disclosed embodiments. FIG. 4 is a flow chart illustrating an exemplary embodiment of a package management process according to disclosed embodiments. FIG. 5 is a flow chart illustrating an exemplary embodiment of an employee error detection process according to disclosed embodiments.

200: Fulfillment Center (FC)

208:Items

218: Package

222: Truck

302: Pallet

Claims (10)

A computer-implemented method for package management, comprising: Converting an item identifier and a container identifier into a standardized table entry by at least one processor; Storing the standardized table entry in a data structure by the at least one processor, the data structure associating the item identifier with the container identifier; Receiving a query including the item identifier by the at least one processor; Accessing one or more higher level groupings of the item identifier in multiple grouping layers of the data structure by the at least one processor until a location record is located; Receiving a lost item notification for a lost item by the at least one processor; Determining, by the at least one processor, a nearest vehicle identifier of a nearest vehicle designated as carrying a container having the lost item; Determining, by the at least one processor and by accessing the data structure, a responsible employee corresponding to the nearest vehicle identifier; Incrementing, by the at least one processor, a lost item count associated with the responsible employee; and Providing, by the at least one processor, a message to a user device for display when the lost item count of the responsible employee exceeds a threshold value. A computer-implemented method as described in claim 1, wherein the item is an item returned by a user. A computer-implemented method as described in claim 1, wherein the container identifier is determined by reading a bar code on the container. A computer-implemented method as described in claim 1, wherein the container identifier is determined by reading a radio frequency identification tag provided on the container. A computer-implemented method as described in claim 1, wherein the data structure further includes an identifier of a vehicle transporting the container, and the vehicle identifier is stored in association with at least one container identifier. The computer-implemented method of claim 1 further comprises: Associating, by the at least one processor, a container and at least one additional container other than the container containing the item with a vehicle identifier corresponding to the vehicle in the data structure; Receiving, by the at least one processor, an unloading indication that the container is being removed from the vehicle; Disassociating, by the at least one processor, the container from the vehicle in the data structure; In response to an indication from a warehouse operator or warehouse manager that the vehicle should be emptied, by the at least one processor, disassociating, by the at least one processor, the at least one additional container from the vehicle in the data structure; and After removing the container and the at least one additional container from the vehicle, in response to an indication that the container and the at least one additional container are transferred to a second vehicle, the at least one processor associates the container and the at least one additional container with the second vehicle in the data structure. The computer-implemented method of claim 5 further comprises: receiving a completion message indicating that the vehicle has been loaded by the at least one processor; retrieving the vehicle container capacity by the at least one processor; determining the number of containers associated with the vehicle by the at least one processor; when the number of containers is less than the vehicle container capacity, sending a message to the user device by the at least one processor indicating that the vehicle is not fully loaded for display. The computer-implemented method of claim 5 further comprises: The at least one processor stores in the data structure an employee identifier corresponding to the employee indicating that the container was present on the vehicle. A computer-implemented method as described in claim 1, wherein the data structure further includes a storage area identifier corresponding to a storage area where vehicles are stored, and the storage area identifier is associated with at least one vehicle. A computerized system for package management, comprising: a memory storing instructions; and at least one processor configured to execute the instructions to implement the computer-implemented method of at least one of claim 1 to claim 9.

Images