Systems and methods for tracking item handling data during logistics operations

Abstract

Systems and methods for tracking item handling data are disclosed herein. The method associates, by a first device of a first user, a first identifier of at least a first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package, and the association indicates a nested relationship. The method generates transaction information associated with the at least one item based on the association and packaging information of the at least one item, and generates a third identifier indicating the transaction information associated with the at least one item applied to the second package. The method tracks at least one attribute of the transaction information associated with the at least one item via the third identifier.

Description

background

[0001] Logistics operations involve the transportation and distribution (e.g., delivery) of items (e.g., packages) to destinations (e.g., homes or businesses) and typically involve a multi-party logistics supply chain (e.g., a manufacturer, a distributor, and at least one carrier or transporter) to transport and distribute the items. Items may be packaged for transportation using multiple levels of packaging. For example, at least one item may be packaged in a carton, the carton may be packaged in a casing comprising a plurality of cartons, and the casing may be packaged in a pallet comprising a plurality of casings that may be packaged for transportation and distribution into a container (e.g., a pallet containing a plurality of boxes)implemented as a storage unit attached to a vehicle or stored in a storage area integrated into at least one section of a vehicle). Thus, it can be challenging to link events (e.g., packaging, shipping, receiving, inspection, scanning, and the like) and / or conditions (e.g., fair, tampered, damaged, environment, and the like) to an item across packaging levels during logistics operations (e.g., loading, shipping, delivery, and / or gathering operations). Additionally, it can also be challenging to link these events and / or conditions to an item that is returned (e.g., via a Return Merchandise Authorization (RMA)). Brief description of the different views of the drawings

[0002] The accompanying figures, in which like reference characters refer to identical or functionally similar elements throughout the several views, are incorporated in and constitute a part of the specification, together with the following detailed description, and serve to further illustrate embodiments of concepts incorporating the claimed invention and to explain various principles and advantages of such embodiments. Fig. 1 is a diagram illustrating one embodiment of a system of the present disclosure for tracking item handling data during logistics operations. Fig. 2 is a flowchart illustrating processing steps performed by an embodiment of the system of the present disclosure of Fig. 1 can be executed. Fig. 3 is a flowchart illustrating step 202 of Fig. 2 illustrates this in more detail. Fig. 4 is a flowchart illustrating step 204 of Fig. 2 illustrates this in more detail. Fig. 5 is a flowchart illustrating step 206 of Fig. 2 illustrates this in more detail. Fig. 6 is a flowchart illustrating step 346 of Fig. 5 illustrates this in more detail. Fig. 7 is a flowchart illustrating step 208 of Fig. 2 illustrates this in more detail. Fig. 8 is a diagram illustrating one embodiment of a system of the present disclosure for tracking item handling data during logistics operations. Fig. 9 is a flowchart illustrating processing steps performed by the embodiment of the system of the present disclosure of Fig. 8 can be executed. Fig. 10 is a flowchart illustrating step 602 of Fig. 9 illustrates this in more detail. Fig. 11 is a flowchart illustrating step 604 of Fig. 9 illustrates this in more detail. Fig. 12 is a flowchart illustrating step 606 of Fig. 9 illustrates this in more detail.

[0003] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and clarity and are not necessarily drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help enhance understanding of embodiments of the present invention.

[0004] The system and method components have been represented, where appropriate, by conventional symbols in the drawings showing only those specific details relevant to an understanding of the embodiments of the present invention, in order not to obscure the disclosure with details that would be apparent to one of ordinary skill in the art having recourse to the present description. Detailed description

[0005] As mentioned above, it can be challenging to link events (e.g., packaging, shipping, receiving, inspection, scanning, and the like) and / or conditions (e.g., fair, tampered, damaged, environment, and the like) to an item during logistics operations across packaging levels, and it can also be challenging to link these events and / or conditions to an item being returned (e.g., via a Return Merchandise Authorization (RMA)). Conventional systems and methods may utilize a variety of information systems associated with respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one carrier or transporter) to track item handling data during logistics operations.However, these information systems often store proprietary and / or confidential information that precludes its access by and / or sharing with other parties, thereby obviating the usefulness of these conventional systems and methods. For example, a manufacturer information system may store proprietary and / or confidential manufacturing information (e.g., raw materials, suppliers, a manufacturing facility, etc.) associated with an item, thereby precluding access to the manufacturer information system by a distributor and / or at least one transportation company. Furthermore, conventional systems and methods do not provide detailed item handling data during logistics operations. For example, conventional systems and methods do not provide graded or nested relationship data across packaging levels of an item.

[0006] Thus, traditional systems suffer from a general lack of versatility because these systems cannot automatically and dynamically identify items and their associated data during various logistics operations (e.g., loading, shipping, delivery, and / or collection). For example, these systems may not automatically and dynamically identify items across packaging levels of an item, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the at least one item, and share detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one carrier).Overall, this lack of versatility causes traditional systems to deliver underwhelming performance and reduces the efficiency, safety, and overall timeliness of executing and completing logistics operations.

[0007] Thus, it is an object of the present disclosure to eliminate these and other problems with conventional systems and methods via systems and methods that can automatically and dynamically identify items and data associated with them during various logistics operations (e.g., loading, shipping, delivery, and / or gathering operations). For example, the systems and methods of the present disclosure alleviate the problems present in conventional systems by automatically and dynamically identifying items across packaging levels of an item, tracking at least one attribute of transaction information (e.g., a purchase agreement) associated with the at least one item, and communicating detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g.,a manufacturer, a dealer and / or at least one transport company or transporter).

[0008] In accordance with the foregoing and with the disclosure herein, the present disclosure includes improvements in computer functionality or improvements in other technologies, at least because the present disclosure describes that, for example, logistics operating systems and their associated various components can be improved or enhanced with the disclosed dynamic system features and methods, providing more efficient working conditions for workers and improved monitoring and management of logistics operations for system administrators. That is, the present disclosure describes improvements in the functionality of an operating system itself or "any other technology or technical field" (e.g., the field of distributed / commercial / industrial logistics information systems).For example, the disclosed dynamic system features and methods enhance and extend the identification of items across packaging levels thereof, the tracking of at least one attribute of transaction information (e.g., a contract or agreement) associated with the at least one item, and the sharing of detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a distributor, and / or at least one carrier or transporter) to mitigate (if not eliminate) worker errors, facilitate logistics supply chain workflows, and eliminate inefficiencies (e.g., tampered with or damaged items) typically experienced over time by systems lacking such features and methods.This improves the state of the art, at least because such prior systems are inefficient because they lack the ability to automatically and dynamically identify items across packaging levels of an item, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the at least one item, and share detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a distributor, and / or at least one transportation company).

[0009] Furthermore, the present disclosure applies various features and functionalities as described herein with or using a particular machine, e.g., a processor, a mobile device, a receiver or transceiver device (e.g., a radio frequency identification (RFID) reader or a Bluetooth Low Energy (BLE) gateway), a scanner, and / or other hardware components as described herein.

[0010] Moreover, the present disclosure includes specific features other than what is well understood, routine, conventional activity in the art, or the addition of non-conventional steps that, in various embodiments, demonstrate certain useful applications, such as using and / or controlling signal processing protocols (e.g., authentication, association, etc.) of a receiver or transceiver device (e.g., an RFID reader or a BLE gateway) in connection with and / or a state of transaction information associated with at least one item.

[0011] Accordingly, it would be highly advantageous to develop a system and method that can automatically and dynamically identify an item across packaging levels of the item, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the item, and share detailed item handling data associated with the transaction information while sharing logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one transportation company). The systems and methods of the present disclosure address these and other needs.

[0012] In one embodiment, the present disclosure is directed to a method for tracking item handling data. The method includes associating, by a first device of a first user, a first identifier of at least a first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package, and the association indicates a nested relationship. The method generates transaction information associated with the at least one item based on the association and packaging information of the at least one item. The method generates and applies a third identifier indicative of the transaction information associated with the at least one item to the second package and tracks at least one attribute of the transaction information associated with the at least one item via the third identifier.

[0013] In one embodiment, the present disclosure is directed to a system for tracking article handling data, comprising a first device, a second device, a third device, one or more processors, and a non-transitory computer-readable memory coupled to the first device, the second device, the third device, and the one or more processors.The memory stores instructions thereon that, when executed by the one or more processors, cause the one or more processors to: associate, by the first device of a first user, a first identifier of at least one first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package and the association indicates a nested relationship; generate transaction information associated with the at least one item based on the association and packaging information of the at least one item; generate a third identifier indicating the transaction information associated with the at least one item to be applied to the second package; and track at least one attribute of the transaction information associated with the at least one item via the third identifier.

[0014] In one embodiment, the present disclosure is directed to an accessible machine-readable medium comprising instructions for tracking item handling data that, when executed, cause a machine to: associate, by a first device of a first user, a first identifier of at least one first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package and the association indicates a nested relationship; generate transaction information associated with the at least one item based on the association and packaging information of the at least one item; generate a third identifier indicating the transaction information associated with the at least one item to be applied to the second package;and tracking at least one attribute of the transaction information associated with the at least one item via the third identifier;

[0015] In one embodiment, the present disclosure is directed to a method for tracking item handling data. The method includes identifying, by an end user via an end user device, order information of at least one item intended for return; receiving return identification information of the at least one item based on the identified order information associated with the at least one item; generating return shipping information in response to the received return identification information of the at least one item; generating return transaction information associated with the at least one item based on the order information, the return identification information, and the return shipping information;Receiving a return identifier indicating the return transaction information associated with the at least one item to be applied by the end user to a return package including the at least one item; and tracking at least one attribute of the return transaction information associated with the at least one item via the return identifier.

[0016] In one embodiment, the present disclosure is directed to a system for tracking item handling data, comprising an end-user device, one or more processors, and a non-transitory computer-readable memory coupled to the end-user device and the one or more processors. The memory stores instructions thereon that, when executed by the one or more processors, cause the one or more processors to: receive, from the end-user device, order information of at least one item intended for return; receive return identification information of the at least one item based on the received order information associated with the at least one item; generate return shipping information in response to the received return identification information of the at least one item;Generating return transaction information associated with the at least one item based on the order information, the return identification information, and the return shipping information; generating a return identifier indicating the return transaction information associated with the at least one item to be applied to a return package including the at least one item; and tracking at least one attribute of the return transaction information associated with the at least one item via the return identifier.

[0017] In one embodiment, the present disclosure is directed to an accessible machine-readable medium comprising instructions for tracking item handling data that, when executed, cause a machine to: receive, from an end-user device, order information of at least one item intended for return; receive return identification information of the at least one item based on the received order information associated with the at least one item; generate return shipping information in response to the received return identification information of the at least one item; generate return transaction information associated with the at least one item based on the order information, the return identification information, and the return shipping information;Generating a return identifier indicating the return transaction information associated with the at least one item to be applied to a return package including the at least one item; and tracking at least one attribute of the return transaction information associated with the at least one item via the return identifier.

[0018] With reference to the drawings, Fig. 1 is a diagram 100 illustrating one embodiment of a system of the present disclosure for tracking item handling data during logistics operations (e.g., packing, loading, shipping, delivery, and / or collection operations). As described in more detail below, the system 100 includes a computing device 144 communicatively coupled to devices 106, 124, and 132. The devices 106, 124, and 132 are each associated with a first user 104 (e.g., a manufacturing facility 102), a second user 122 (e.g., a transportation company or transporter), and a third user 130 (e.g., an item handling facility 126).

[0019] As in Fig. 1, the computing device 144 may exchange data with each of the devices 106, 124, and 132, e.g., via a network 142 implemented as any suitable combination of local and wide area networks and respective communication links 143-1, 143-2, 143-4, and 143-3. The system 100 provides for automatically and dynamically identifying an item 103 across packaging levels of the item 103, tracking at least one attribute of transaction information (e.g., a contract or agreement) associated with the item 103, and sharing detailed item handling data associated with the transaction information via shared first and second databases 152-1 and 152-2 during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a distributor, and / or at least one carrier or transporter).

[0020] A manufacturing facility 102 may produce a plurality of items 103-1, 103-2, 103-3 (collectively referred to as items 103 and generally referred to as an item 103). The system 100 may generate a first identifier 112 (e.g., a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, a radio frequency identification (RFID) tag, a quick response (QR) code, a Bluetooth Low Energy (BLE) beacon, etc.), and a first user 104 (e.g., a manufacturing facility worker) may apply the first identifier 112 to a first package 110 including at least one item 103 based on a detected event (e.g., a workflow trigger). The detected event may be associated with the item 103 and may include, but is not limited to, a purchase order, an inventory reallocation, and a threshold (e.g., a shelf life of the item 103).

[0021] The first user 104 may also apply a second identifier 116 (e.g., a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, an RFID tag, a QR code, a Bluetooth Low Energy (BLE) beacon, etc.) to a second package 114 that includes at least one first package 110. As shown in Fig. 1, the second package 116 (e.g., a pallet) may be comprised of a plurality of first packages 110-1, 110-2, and 110-n (collectively referred to as first packages 110 and generally referred to as a first package 110), wherein each first package 110-1, 110-2, and 110-n is respectively associated with a first identifier 112-1, 112-2, and 112-n (collectively referred to as first identifiers 112 and generally referred to as a first identifier 112).

[0022] The first user 104 may use a device 106, including, but not limited to, a tablet, a receiver or transceiver device (e.g., an RFID reader), a scanner (e.g., a barcode reader), or any suitable combination thereof, for authentication and processing. For example, the first user 104 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a graphical user interface (GUI) of the device 106 for authentication purposes. During authentication, the first user 104 may use the device 106 to associate the first identifier 112 of the first package 110 with the second identifier 116 of the second package 114. Additionally, the system 100 may store transaction information (e.g.,a contract or agreement) associated with the item 103 based on the association of the first identifier 112 of the first packet 110 and the second identifier 114 of the second packet 116.

[0023] Items 103 may be packaged for transport across multiple packaging levels. As mentioned above, the second package 116 (e.g., a pallet) may consist of a plurality of first packages 110-1, 110-2, and 110-n. For example, at least one item 103 may be packaged in a case (e.g., a first package 110), and the case may be packaged in a pallet (e.g., a second package 114 comprising a plurality of first packages 110) that is loaded into a container for transport. Thus, the association of the first identifier 112 of the first package 110 and the second identifier 116 of the second package 114 indicates a nested or tiered relationship between the first package 110 and the second package 116. Additional packaging levels may be used. In another example, at least one item 103 may be packaged in a carton (e.g., a first package 110), the carton may be packaged in a housing (e.g.,a second package 114 comprising a plurality of first packages 110), and the housing may be packaged in a pallet (e.g., a third package (not shown) comprising a plurality of second packages 114) that is loaded into a container for transportation.

[0024] As described in more detail below, this association provides for automatically and dynamically identifying an item 103 across packaging levels (e.g., the first package 110 and the second package 114) thereof and authenticating the transaction information associated with the item 103. The transaction information may be encrypted and / or it may be structured as a blockchain. The system 100 may generate a third identifier 117 (e.g., a machine-readable symbol, a label, a barcode, an RFID tag, a QR code, a Bluetooth Low Energy (BLE) beacon, etc.) indicating the transaction information (e.g., a contract or agreement), and the first user 104 may apply it to the second package 114.

[0025] The first user 104 may store, in a proprietary database 108 of the manufacturing facility 102, information associated with the item 103, including, but not limited to, a code of the item 103; one or more regulatory codes (e.g., a drug code, a dosage, and / or a strength); an expiration date of the item 103; temperature data and storage requirements of the item 103; package identifiers and packaging level assignments; Internet of Things (IoT) event data; proprietary and / or confidential manufacturing information (e.g., raw materials, suppliers, a manufacturing site, etc.); packaging information (e.g., packaging location, packaging date and / or time, manufacturer identification information, etc.); and shipping information.

[0026] The user 104 may also store the first identifier 112, the second identifier 116, the third identifier 117, and packaging information of the article 103 (e.g., packaging location, packaging date and / or time, manufacturer identification information, etc.) in a first shared database 152-1 that is accessible to authenticated users of at least two of the manufacturing facility 102, an article handling facility 126, and a transportation company or carrier (not shown).

[0027] In one embodiment, a worker (e.g., a first user 104) of a manufacturing facility 102 may transport the second package 114 to an item handling facility 126 (e.g., a distributor, such as a warehouse, a retail facility, and a transit facility, including, but not limited to, an airport, a depot, or the like). Thus, the first shared database 152-1 may access authenticated users of the manufacturing facility 102 and the item handling facility 126. In another embodiment, a worker (e.g., a second user 122) of a transportation company or transporting company may transport the second package 114 to the item handling facility 126. Thus, the first shared database 152-1 may access authenticated users of the manufacturing facility 102 and the transportation company or transporting company.

[0028] System 100 may include additional shared databases to enable access by any combination of authenticated users of the manufacturing facility 102, the item handling facility 126, the transportation company or carrier, and the like. Additionally, the steps performed by the first user 104, including but not limited to packaging, labeling, and transporting, may be performed by a single individual or by multiple individuals within a manufacturing facility 102.

[0029] As in Fig. 1, the second package 114 (e.g., a pallet) may be transported from a manufacturing facility 102 to the item handling facility 126 by the second user 122 of a transportation company or transport business. As mentioned above, the item handling facility 126 may be, for example, a retailer, such as a warehouse, a retail facility, and a transit facility, including, but not limited to, an airport, a depot, or the like. The second package 114 may be transported via a container 118 implemented as a storage unit attached to or stored within a vehicle 120 (e.g., a truck, a semi-trailer, or the like) operated by the second user 122, or a container 118 implemented as a storage area incorporated into at least a portion of a vehicle 120 (e.g.,a truck, a van, and an off-road vehicle (SUV)) operated by the second user 122.

[0030] The second user 122 may use a device 124, including, but not limited to, a tablet, a receiver or transceiver device (e.g., an RFID reader), and a scanner (e.g., a barcode scanner) for authentication and processing. For example, the second user 122 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 124 for authentication purposes. Upon authentication, the second user 122 may receive the second package 114 from the first user 104 of the manufacturing facility 102 and may use the device 124 to associate the second package 114 with the carrier or carrier (e.g., the second user 122) by processing the third identifier 117 via the device 124.This association may indicate the receipt of the second package 114 by the carrier or carrier from the manufacturing facility 102.

[0031] The second user 122 may also deposit (e.g., deliver) the second package 114 to a third user 130 of the item handling facility 126. Upon depositing the second package 114, the second user 122 may use the device 124 to associate the second package 114 with the item handling facility 126 (e.g., a third user 130) by processing the third identifier 117 via the device 124. This association may indicate the deposit (e.g., delivery) of the second package 114 by the transportation company to the item handling facility 126.

[0032] The second user 122 may store information associated with the transport of the second package 114 in a database 126 proprietary to the transport company or carrier, including, but not limited to, the dimensions and / or weight of the second package 114, identification information of the second user 122, the type of container 118 and / or vehicle 120, and route information and coordinates. The system 100 may store receive and deposit event data and associated timestamps (e.g., time and / or date) in addition to the associations in a first shared database 152-1 accessible by authenticated users of at least two of the manufacturing facility 102, an item handling facility 126, and the transport company or carrier.

[0033] As in Fig. 1, an article handling facility 126 may include loading bays 128-1, 128-2, and 128-3 (collectively referred to as loading bays 128 and generally referred to as a loading bay 128). The article handling facility 126 may include a portion of a building, such as a cross dock, or a portion thereof, including the loading bays 128.

[0034] For example, the loading bays 128 may be arranged along an exterior wall of the article handling facility 126 so that one or more containers 118 can be positioned from outside the article handling facility 126 near the loading bays 128. In other examples, fewer or greater numbers of loading bays 128 may be included. The loading bays 128 are illustrated as docking structures that provide access from inside the article handling facility 126 to an exterior of the article handling facility 126 where a container 118 is positioned. In other examples, one or more of the loading bays 128 may be implemented as a loading station within the article handling facility 126 to load or unload containers 118 handled within the article handling facility 126.

[0035] Each loading bay 128 may be configured to receive a container 118 such that one or more containers 118 may be positioned proximate to the loading bays 128 from outside the article handling device 126. As described above, a container 118 may be implemented as a storage unit attached to or stored within a vehicle 120 (e.g., a truck, a semi-trailer, or the like), or as a storage area integrated into at least a portion of a vehicle 120 (e.g., a truck, a sprinter van, and an (SUV)). The container 118 may have a substantially horizontal interior depth extending from an open end (e.g.,a wall having a door or other opening providing access to an interior of the container 118) of the container 118 extending to a closed end, a substantially horizontal interior width perpendicular to the depth, and a substantially vertical interior height.

[0036] Each loading bay 128 includes an opening, e.g., in a wall of the article handling device 126, that allows a third user 130 within the article handling device 126 to access an interior of the container 118 to inspect the second package 114 and to accept or reject the second package 114 based on the inspection from the second user 122. For example, when a container 118 is positioned at a loading bay 128 (e.g., with the open end of the container 118 substantially flush with the opening of the loading bay 128), the third user 130 can inspect the second package 114, accept or reject the second package 114 based on the inspection, and, if received, unload the second package 114 from the container 118 to a staging area (not shown) for processing.

[0037] The third user 130 may use a device 132, including, but not limited to, a tablet, a receiver or transceiver device (e.g., an RFID reader), and a scanner (e.g., a barcode scanner) for authentication and processing. For example, the third user 130 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 132 for authentication purposes. Upon authentication, the third user 130 may inspect the second package 114 to determine at least one condition (e.g., fair, tampered with, damaged, environmental, etc.) thereof, and the system 100 may associate the determined at least one condition with the transaction information by processing the third identifier 117 via the device 132.For example, by processing the third identifier 117 via the device 132, the system 100 may add the determined at least one condition of the second packet 114 to the transaction information.

[0038] The at least one condition may indicate a condition of the second package 114 as a whole and / or a condition of portions thereof (e.g., one or more of the first packages 110). The at least one condition may include, but is not limited to, one or more of fair (e.g., original, sealed, unadulterated, undamaged, or the like), tampered (e.g., unsealed, opened, torn, or the like), damaged (e.g., crushed, wet, or the like), and environmental (e.g., freezing, ambient, or the like). The system 100 may automatically and dynamically determine whether the particular at least one condition corresponds to the transaction information based on one or more of the first identifier 112 of the first package 110 and the second identifier 116 of the second package 114 associated with the transaction information.For example, if the transaction information indicates that the at least one item 103 is a medication vial and the particular at least one condition of the second packet 114 is fair, then the second packet 114 may be considered to comply with the transaction information. Alternatively, if the transaction information indicates that the at least one item 103 is a medication vial and the particular at least one condition of the second packet 114 is tampered with, then the second packet 114 may be considered to not comply with the transaction information.

[0039] If the system 100 determines that the at least one condition matches the transaction information, then the system 100 may display a message (e.g., text, an alert, a request, or the like) to the third user 130 via the GUI of the device 130 to receive the second packet 114 and / or transmit an input (e.g., keypress, tap, button press, or the like) via the GUI or an input device (e.g., a field, a keyboard, or the like) of the device 130 to confirm receipt of the second packet 114. If the system 100 determines that the at least one condition does not match the transaction information, then the system 100 may display a message (e.g., text, an alert, a request, or the like) to the third user 130 via the GUI of the device 130 to reject the second packet 114 and / or transmit an input (e.g.,keystroke, tap, key press, or the like) via the GUI or an input device (e.g., a pad, keyboard, or the like) of the device 130 to confirm the rejection of the second packet 114.

[0040] Upon receipt of the second package 114 (e.g., when the at least one condition matches the transaction information), the system 100 may modify the transaction information. For example, the system 100 may add a receive event to the transaction information to indicate that the second package 114 was received by the item handling device 126 and / or to notify (e.g., alert) the manufacturing facility 102 that the second package 114 was received by the item handling device 126. The third user 130 may deconstruct (e.g., disassemble) the second package 114 (e.g., a pallet) by processing the second identifier 116 of the second package 114 and processing the first identifier 112 of each first package 110 as each first package 110 is removed from the second package 114.

[0041] Based on the processing of the second identifier 116 and each first identifier 112, the system 100 may determine whether the association (e.g., nested or tiered relationship) of each first identifier 112 of each first packet 110 and the second identifier 116 of the second packet 114 corresponds to the transaction information. If the system 100 determines that the association of each first identifier 112 of each first packet 110 and the second identifier 116 of the second packet 114 corresponds to the transaction information, then the system 100 authenticates the transaction information. For example, the system 100 may add an authentication event to the transaction information indicating that the item 103 associated with the transaction information is authentic and / or that the conditions of the transaction information have been met.If the system 100 determines that the association of each first identifier 112 of each first package 110 and the second identifier 116 of the second package 114 does not match the transaction information, the system 100 may generate a notification (e.g., an alert). For example, the system 100 may add an alert to the transaction information indicating that at least one item 103 is fraudulent (e.g., a counterfeit), a fake item, and / or missing (e.g., if an insufficient number of first identifiers 112 are processed). In this way, the system 100 may ensure the integrity of the transaction information and facilitate the resolution of disputes between respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one carrier or transporter).

[0042] The item handling facility 126 may receive order information from an end user 142 for at least one item 103. For example, an end user (e.g., a customer or consumer) may submit order information for the at least one item 103 to be fulfilled by the item handling facility 126, where the order information may include, but is not limited to, a quantity of the at least one item 103, a shipping (e.g., delivery) address, delivery instructions, or the like. The system 100 may generate shipping information in response to the received order information. The shipping information may include, but is not limited to, a third package identification number (e.g., a package identification number), a location of the item handling facility 126, a shipping date and / or time, a shipping address, delivery instructions, or the like.Additionally, the system 100 may modify the transaction information based on the generated shipping information. For example, the system 100 may add the shipping information to the transaction information. The system 100 may generate a fourth identifier 138 indicating the modified transaction information, and the third user 130 may apply it to a third package 136 including the at least one item 103. For example, and as shown in FIG. Fig. 1, the third user 130 may apply third identifiers 138-1, 138-2, 138-3 (collectively referred to as third identifiers 138 and generally referred to as a third identifier 138) to third packets 136-1, 136-2, 136-3 (collectively referred to as third packets 136 and generally referred to as a third packet 136), respectively.

[0043] The third user 130 may store, in a proprietary database 134 of the item handling device 126, information associated with the at least one item 103, including, but not limited to, an inspection event (e.g., a date and / or time, a location, identification information of the third user 130, or the like), a particular condition of the second package 114, a receipt event or rejection event (e.g., a date and / or time, a location, identification information of the third user 130, or the like), an association of the first identifier 112 of the first package 110 and the second identifier 116 of the second package 114, compliance with the association (e.g., an authentication event or notification), and a shipping event (e.g., a date and / or time, a location, and / or identification information of the third user 130).

[0044] The system 100 may store the fourth identifier and the shipping information (e.g., the third package identification number, the location of the item handling facility 126, the shipping date and / or time, the shipping address, delivery instructions, or the like) in a second shared database 152-2, which is accessible by authenticated users of the item handling facility 126 and the carrier or transportation company. The system 100 may include additional shared databases to enable access by any combination of authenticated users of the manufacturing facility 102, the item handling facility 126, the transportation company, and the like.Additionally, the steps performed by the third user 130, including, but not limited to, inspection, receiving, rejection, labeling, and shipping, may be performed by a single person or by a plurality of persons of an article handling facility 126.

[0045] In logistics operations, a wide variety of items, such as packages and other cargo, can be transported from origins to destinations, often via a variety of intermediate locations. As in Fig. 1, third packages 136 may be transported from the item handling device 126 to destinations, such as residences 140-1, 140-2, and 140-3 (collectively referred to as the destinations 140 and generally referred to as a destination 140). The third packages 136 may be transported via a container 118 implemented as a storage unit attached to or stored within a vehicle 120 (e.g., a truck, a semi-trailer, or the like) operated by the second user 122, or a container 118 implemented as a storage area integrated into at least a portion of a vehicle 120 (e.g., a truck, a van, and an off-road vehicle (SUV)) operated by the second user 122.

[0046] The second user 122 may use the device 124, including, but not limited to, a tablet, a receiver or transceiver device (e.g., an RFID reader), and a scanner (e.g., a barcode scanner), for authentication and processing. For example, the second user 122 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the device 124 for authentication purposes. Upon authentication, the second user 122 may receive the third package 136 from the third user 130 of the item handling device 126 and may use the device 124 to associate the third package 136 with the carrier or transportation company by processing the fourth identifier 138 via the device 124. This association may indicate receipt of the third package 136 by the carrier or transportation company from the item handling device 126.

[0047] The third user 122 may also deposit (e.g., deliver) the third package 136 to an end user 142 (e.g., a customer or consumer) at a destination (e.g., destination 140-1). Upon depositing the third package 136, the second user 122 may use the device 124 to associate the third package 136 with the destination 140-1 (e.g., the end user 142) by processing the fourth identifier 138 via the device 124. This association may indicate the deposit (e.g., delivery) of the third package 136 by the carrier to the destination 140-1.

[0048] The second user 122 may store information associated with the transport of the third package 136 in a database 126 proprietary to the transport company, including, but not limited to, the dimensions and / or weight of the third package 136, identification information of the second user 122, the type of container 118 and / or vehicle 120, and route information and coordinates. The user 122 may also store the receive and deposit event data and associated timestamps (e.g., time and / or date) in a second shared database 152-2 accessible by authenticated users of the item handling facility 126 and the transport company or carrier.The system 100 may include additional shared databases to enable access by any combination of authenticated users of the item handling facility 126, the carrier or transportation company, and the like.

[0049] As mentioned above, the system 100 also includes a computing device 144 (e.g., a server) in communication with the devices 106, 124, and 132 (e.g., a smartphone, tablet, or mobile computer) of the respective first, second, and third users 104, 122, and 130 via a network 142 (e.g., a wired or wireless access point). For example, the computing device 144 may be in communication with the devices 106, 124, and 132 via respective communication links 143-1, 143-2, 143-4, and 143-3.

[0050] Computing device 144 includes a processor 146 (e.g., a controller, a central processing unit (CPU), a graphics processing unit (GPU), or a combination thereof) in communication with memory 148 (e.g., a non-transitory computer-readable storage medium) implemented as a suitable combination of volatile and non-volatile storage elements. For example, memory 148 may include a combination of volatile memory (e.g., random access memory (RAM)) and non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, etc.). Processor 146 and memory 148 each comprise one or more integrated circuits.

[0051] The memory 148 may store a plurality of computer-readable instructions in the form of code 150 (e.g., an application) executable by the processor 146 to perform functionality discussed in more detail below. For example, the code 150, when executed by the processor 146, configures the processor 146 to dynamically identify an item 103 across packaging levels thereof, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the item 103, and share detailed item handling data associated with the transaction information via shared first and second databases 152-1 and 152-2 during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a distributor, and / or at least one carrier or transporter).In other examples, code 150 may be implemented as a number of different applications or as a dedicated hardware element (e.g., an application-specific integrated circuit (ASIC)). Computing device 144 also includes a communications interface 154 so that computing device 144 can exchange data with other devices, including devices 106, 124, and 132, over network 142.

[0052] The code 150 could be programmed using any suitable programming language, including, but not limited to, C, C++, C#, Java, or any other suitable language. Additionally, the code 150 could be distributed across multiple computer systems in communication with each other via a communications network, stored in hardware, and / or stored and executed on a cloud computing platform, and remotely accessed by a computer system in communication with the cloud platform. The code 150 executed by the processor 146 could communicate with databases 152-1 and 152-2, which could be stored on the same computer system as the code 150 or on one or more other computer systems in communication with the code 150.

[0053] The computing device 144 stores the databases 152-1 and 152-2 in the memory 148. The database 152-1 may contain data indicating the first identifier 112, the second identifier 116, the third identifier 117, and packaging information of the article 103 (e.g., packaging location, packaging date and / or time, manufacturer identification information, etc.), and which can be accessed by authenticated users of at least two of the manufacturing facility 102, an article handling facility 126, and a transportation company or carrier (not shown). The database 152-2 may contain data indicating the fourth identifier, the third package identification number (e.g., a package identification number), the location of the article handling facility 126, shipping date and / or time, shipping address (e.g.,delivery), delivery instructions, or the like, and which can be accessed by authenticated users of the item handling facility 126 and the transport company or carrier.

[0054] Those skilled in the art will recognize that the functionality implemented by processor 146 via execution of code 150 may also be implemented by one or more specially designed hardware and firmware components, such as a field-programmable gate array ("FPGA"), an application-specific integrated circuit ("ASIC"), an embedded system, or other custom hardware components, without departing from the spirit or scope of the present disclosure. Fig. 1 is only one possible configuration, and the system 100 of the present disclosure may be implemented using a number of different configurations.

[0055] Fig. 2 is a flowchart illustrating processing steps performed by an embodiment of the system of the present disclosure of Fig. 1. The processing steps are described in connection with their performance in the system (e.g., by the computing device 144 in conjunction with the devices 106, 124, and 132). In general, by performing the processing steps, the system 100 can automatically and dynamically identify an item across packaging levels thereof, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the at least one item, and share detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one transportation company or transporter). Beginning at step 202, a first user 104 (e.g.,a manufacturing facility 102) at least one item 103, and the system 100 generates transaction information associated with the at least one item 103. Then, at step 204, a second user 122 (e.g., a transportation company or transport business) transports the at least one item 103 to a third user 130 (e.g., an item handling facility 126). At step 206, the third user 130 processes the at least one item 103. At step 208, the second user 122 transports the at least one item 103 to an end user 142 (e.g., a customer or consumer) of a destination 140 (e.g., a residence or business). Each of steps 202-208 is described below with respect to the . Fig. 3 - Fig. 7 described in more detail.

[0056] Fig. 3 is a flowchart illustrating step 202 of Fig. 2. At step 240, the system 100 generates a first identifier 112 to be applied to a first package 110 including the at least one item 103 based on a detected event. The first identifier 112 may include, but is not limited to, one or more of a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, a radio frequency identification (RFID) tag, a quick response (QR) beacon, and a Bluetooth low energy (BLE) beacon. The first identifier 112 displays, carries, and / or stores identification information (e.g., a serial number) of the at least one item 103. The first identifier 112 may be generated based on a detected event (e.g., a workflow trigger).The detected event may be associated with the item 103 and may include, but is not limited to, a purchase order, an inventory reallocation, and a threshold (e.g., a shelf life of the item 103). The first package 110 may be a first packaging level of the at least one item 103.

[0057] At step 242, the system 100 generates a second identifier 116 to be applied to a second package 114 that includes the first package 110. The second identifier 116 may include, but is not limited to, one or more of a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, an RFID tag, a QR beacon, and a BLE beacon. The second identifier 116 displays, carries, and / or stores identification information (e.g., a serial number) of the at least one item 103. The second package 114 may be a second packaging level of the at least one item 103.

[0058] An item 103 may be packaged for transport across multiple packaging levels. For example, at least one item 103 may be packaged in a casing (e.g., a first package 110), and the casing may be packaged in a pallet (e.g., a second package 114 comprising a plurality of first packages 110) that is loaded into a container for transport. In another example, the at least one item 103 may be packaged in a carton (e.g., a first package 110), the carton may be packaged in a casing (e.g., a second package 114 comprising a plurality of first packages 110), and the casing may be packaged in a pallet (e.g., a third package (not shown) comprising a plurality of second packages 114) that is loaded into a container for transport.At step 244, the system 100 associates the first identifier 112 of the first package 110 and the second identifier 116 of the second package 114. For example, the second identifier 114 may indicate, carry, and / or store identification information (e.g., a serial number) of the at least one item 103 and / or the first package 110. The association indicates a nested or tiered relationship between the first package 110 and the second package 114. The system 100 may extend the association to include additional packaging levels of the at least one item 103.

[0059] At step 246, the system 100 generates transaction information associated with the at least one item 103 based on the associated first identifier 112 of the first package 110 and the second identifier 116 of the second package 114, and packaging information of the at least one item 103. The packaging information may include, but is not limited to, a packaging location, a packaging date and / or time, and manufacturer identification information. The system 100 may transmit at least one of an alarm and a notification to an authenticated external system or database via at least one application programming interface in response to an event associated with the transaction information.At step 248, the system 100 generates a third identifier 117 indicating the transaction information, and the first user 104 may apply the third identifier 117 indicating the transaction information (e.g., a contract or agreement) to the second package 114. The third identifier 117 may include, but is not limited to, one or more of a machine-readable symbol, a label, a barcode, an RFID tag, a QR code, and a BLE beacon. At step 250, the system 100 may store the first identifier 112, the second identifier 116, the third identifier 117, and the packaging information of the at least one article 103 in a first shared database 152-1 accessible by authenticated users of at least two of a manufacturing facility 102, an article handling facility 126, and a transportation company or carrier.

[0060] Fig. 4 is a flowchart illustrating step 204 of Fig. 2 in more detail. At step 290, the second user 122 receives the second packet 114 from the first user 104 of the manufacturing facility 102. As mentioned above, the second user 122 may use a device 124 for authentication and processing. For example, the second user 122 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 124 for authentication purposes. Upon authentication, the second user 122 may receive the second packet 114 from the first user 104 of the manufacturing facility 102.

[0061] At step 292, the second user 122 may use the device 124 to associate the second package 114 with the carrier or transportation company (e.g., the second user 122) by processing the third identifier 117 via the device 124, and the system 100 may modify the transaction information by adding the association of the second package 114 with the second user 122 to the transaction information. This association may indicate the receipt of the second package 114 by the carrier or transportation company from the manufacturing facility 102.

[0062] At step 294, the second user 122 may deposit the second package 114 with a third user 130 of an item handling facility 126. For example, the second user 122 may transport and deliver the second package 114 to the third user 130 of an item handling facility 126. At step 296, the second user 122 may use the device 124 to associate the second package 114 with the item handling facility 126 (e.g., the third user 130) by processing the third identifier 117 via the device 124, and the system 100 may modify the transaction information by adding the association of the second package 114 to the third user 130 to the transaction information. This association may indicate receipt of the second package 114 by the item handling facility 126 from the transportation company or carrier.

[0063] At step 298, the system 100 may store receipt and deposit event data and associated timestamps (e.g., time and / or date) in addition to the associations in a first shared database 152-1 accessible by authenticated users of at least two of the manufacturing facility 102, an article handling facility 126, and the transportation company or carrier.

[0064] Fig. 5 is a flowchart illustrating step 206 of Fig. 2. The third user 130 may use a device 132 for authentication and processing. For example, the third user 130 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 132 for authentication purposes. Upon authentication, the third user 130 may inspect the second package 114.

[0065] At step 340, the third user 130 determines at least one condition (e.g., fair, tampered, damaged, environmental, etc.) of the second package 114. The at least one condition may indicate a condition of the second package 114 as a whole and / or a condition of portions thereof (e.g., one or more first packages 110). The at least one condition may include, but is not limited to, one or more of fair (e.g., original, sealed, unadulterated, undamaged, or the like), tampered (e.g., unsealed, opened, torn, or the like), damaged (e.g., crushed, wet, or the like), and environmental (e.g., freezing, environmental, or the like). At step 342, the system 100 may associate the determined at least one condition with the transaction information by processing the third identifier 117 via the device 132.For example, by processing the third identifier 117 via the device 132, the system 100 may add the determined at least one condition of the second packet 114 to the transaction information.

[0066] Then, at step 344, the system 100 may automatically and dynamically determine whether the determined at least one condition corresponds to the transaction information based on one or more of the first identifier 112 of the first packet 110 and the second identifier 116 of the second packet 114 associated with the transaction information. For example, if the transaction information indicates that the at least one item 103 is a drug vial and the determined at least one condition of the second packet 114 is fair, then the second packet 114 may be considered to comply with the transaction information. Alternatively, if the transaction information indicates that the at least one item 103 is a drug vial and the determined at least one condition of the second packet 114 is tampered with, then the second packet 114 may be considered to not comply with the transaction information.

[0067] If the system 100 determines that the at least one condition matches the transaction information, then the process proceeds to step 346. At step 346, the system 100 may display a message (e.g., a text, an alert, a request, or the like) to the third user 130 via the GUI of the device 130 to receive / accept the second package 114 and / or transmit an input (e.g., a keystroke, tap, button press, or the like) via the GUI or an input device (e.g., a field, a keyboard, or the like) of the device 130 to confirm receipt / acceptance of the second package 114. Alternatively, if the system 100 determines that the at least one condition does not match the transaction information, then the process proceeds to step 348. At step 348, the system 100 may display a message (e.g.,display a message (e.g., a text, an alarm, a request, or the like) to the third user 130 via the GUI of the device 130 to reject the second packet 114 and / or transmit an input (e.g., a keystroke, a tap, a button press, or the like) via the GUI or an input device (e.g., a field, a keyboard, or the like) of the device 130 to confirm the rejection of the second packet 114.

[0068] Fig. 6 is a flowchart illustrating step 346 of Fig. 5. Upon receipt / acceptance of the second package 114, the system 100 may modify the transaction information. At step 380, the system 100 may add a receipt event to the transaction information to indicate that the second package 114 was received / accepted by the item handling device 126 and / or to notify (e.g., alert) the manufacturing facility 102 that the second package 114 was received / accepted by the item handling device 126. At steps 382 and 384, the third user 130 may deconstruct (e.g., disassemble) the second package 114 (e.g., a pallet) by processing the second identifier 116 of the second package 114 and processing the first identifier 112 of each first package 110 as each first package 110 is removed from the second package 114.

[0069] At step 386, based on the processing of the second identifier 116 and each first identifier 112, the system 100 may determine whether the association (e.g., nested or tiered relationship) of each first identifier 112 of each first parcel 110 and the second identifier 116 of the second parcel 114 corresponds to the transaction information. If the system 100 determines that the association of each first identifier 112 of each first parcel 110 and the second identifier 116 of the second parcel 114 corresponds to the transaction information, then the process proceeds to step 390. At step 390, the system 100 authenticates the transaction information. For example, the system 100 may add an authentication event to the transaction information indicating that the item 103 associated with the transaction information is authentic and / or that the conditions of the transaction information have been met.Alternatively, if the system 100 determines that the association of each first identifier 112 of each first package 110 and the second identifier 116 of the second package 114 does not correspond to the transaction information, then the process proceeds to step 388. At step 388, the system 100 may generate a notification (e.g., an alert). For example, the system 100 may add an alert to the transaction information indicating that at least one item 103 is fraudulent (e.g., a counterfeit), a fake item, and / or missing (e.g., if an insufficient number of first identifiers 112 are processed). In this way, the system 100 may ensure the integrity of the transaction information and facilitate the resolution of disputes between respective logistics supply chain parties.

[0070] At step 392, the system 100 may generate shipping information for at least one item 103 in response to received order information for the at least one item 103. For example, the item handling facility 126 may receive order information for at least one item 103 from an end user 142 (e.g., a customer or consumer) to be fulfilled by the item handling facility 126. The order information may include, but is not limited to, a quantity of the at least one item 103, a shipping (e.g., delivery) address, delivery instructions, or the like. The shipping information may include, but is not limited to, a third package identification number (e.g., a package identification number), a location of the item handling facility 126, a shipping date and / or time, a shipping address, delivery instructions, or the like.

[0071] At step 394, the system 100 may modify the transaction information based on the generated shipping information and received order information. For example, the system 100 may add the shipping information and the order information to the transaction information. At step 396, the system 100 may generate a fourth identifier 138 indicating the modified transaction information, and the third user 130 may apply it to a third package 136 including the at least one item 103. Then, at step 398, the system 100 may store the fourth identifier 138 and the shipping information in a second shared database 152-2 accessible to authenticated users of the item handling facility 126 and the carrier or transportation company.

[0072] It is understood that the third user 130 may store, in a proprietary database 134 of the item handling device 126, information associated with the at least one item 103, including, but not limited to, an inspection event (e.g., a date and / or time, a location, identification information of the third user 130, or the like), a particular condition of the second package 114, a receipt / acceptance event or rejection event (e.g., a date and / or time, a location, identification information of the third user 130, or the like), an association of the first identifier 112 of the first package 110 and the second identifier 116 of the second package 114, compliance with the association (e.g., an authentication event or notification), and a shipping event (e.g., a date and / or time, a location, and / or identification information of the third user 130).

[0073] Fig. 7 is a flowchart illustrating step 208 of Fig. 2. At step 440, the second user 122 receives the third packet 136 from the third user 130 of the item handling device 126. As mentioned above, the second user 122 may use a device 124 for authentication and processing. For example, the second user 122 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the device 124 for authentication purposes. Upon authentication, the second user 122 may receive the third packet 136 from the third user 130 of the item handling device 126.

[0074] At step 442, the second user 122 may use the device 124 to associate the third package 136 with the carrier or transportation company (e.g., the second user 122) by processing the fourth identifier 138 via the device 124, and the system 100 may modify the transaction information by adding the association of the third package 136 with the second user 122 to the transaction information. This association may indicate the receipt of the third package 136 by the carrier or transportation company from the item handling facility 136.

[0075] At step 444, the second user 122 may deposit the third package 136 with an end user 142 (e.g., a customer or consumer) of a destination 140 (e.g., a residence or business). For example, the second user 122 may transport and deliver the third package 136 to the end user 142 of the destination 140-1. At step 446, the second user 122 may use the device 124 to associate the third package 136 with the destination 140-1 (e.g., the end user 142) by processing the fourth identifier 138 via the device 124, and the system 100 may modify the transaction information by adding the association of the third package 136 with the end user 142 to the transaction information. This association may indicate receipt of the third package 136 by the destination 140-1 from the carrier or transportation company.

[0076] At step 298, the system 100 may store receipt and deposit event data and associated timestamps (e.g., time and / or date) in addition to the associations in the second shared database 152-2, which can be accessed by authenticated users of the item handling facility 126 and the carrier or carrier.

[0077] As mentioned above, the system 100 may automatically and dynamically identify items across packaging levels of an item, track at least one attribute of transaction information (e.g., a contract or agreement) associated with the at least one item, and share detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a distributor, and / or at least one transportation company).

[0078] For example, a second package 114 (e.g., a pallet) comprising a plurality of first packages 110 with at least one item 103 may include a single first package 110 that has been determined to be damaged. In conventional systems, the damaged first package 110 may be tracked by only one logistics supply chain party (e.g., a carrier) at the shipping level. However, when an end user 142 (e.g., a customer or consumer) inspects an item 103 and determines that the item 103 is damaged, it is useful to know that the damaged item 103 was positioned in a different first package 110 of the second package 114 than the single first package 110 that was determined to be damaged.Thus, the present disclosure eliminates these and other problems with conventional systems and methods by automatically and dynamically identifying items across packaging levels of an item, tracking at least one attribute of transaction information associated with the at least one item, and sharing detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties.

[0079] Fig. Figure 8 is a diagram illustrating one embodiment of a system of the present disclosure for tracking item handling data during logistics operations. System 500 includes a computing device 144 communicatively coupled to devices 106, 124, 132, and 502. Devices 106, 124, 132, and 502 are each associated with a first user 104 (e.g., a manufacturing facility 102), a second user 122 (e.g., a transportation company or carrier), a third user 130 (e.g., an item handling facility 126), and an end user 142 (e.g., a customer or consumer of a destination 140-1).

[0080] As in Fig. 8, the computing device 144 may exchange data with each of the devices 106, 124, 132, and 502, e.g., via a network 142 implemented as any suitable combination of local and wide area networks and respective communication links 143-1, 143-2, 143-4, 143-3, and 508. As described below with respect to the Fig. 9 - Fig. 12, the system 500 provides for automatically and dynamically identifying an item across packaging levels thereof, tracking at least one attribute of transaction information (e.g., a contract or agreement) associated with the item, sharing detailed item handling data (e.g., event data and / or conditions) associated with the transaction information during logistics operations with respective logistics supply chain parties (e.g., a manufacturer, a retailer, and / or at least one carrier), and linking the detailed item handling data to an item being returned (e.g., via a Return Goods Authorization (RMA)). The components and devices of the system 500 of Fig. 8 share similarities with the system 100 of Fig. 1 and are, for the sake of brevity, presented in relation to Fig. 8 is not described in more detail. Fig. 8 is only one possible configuration, and the system 500 of the present disclosure may be implemented using a number of different configurations.

[0081] Fig. 9 is a flowchart illustrating processing steps performed by the embodiment of the system of the present disclosure of Fig. 8. The processing steps are described in connection with their performance in system 500 (e.g., by computing device 144 in conjunction with devices 124, 132, and 502). In general, by performing the processing steps, system 500 can automatically and dynamically identify an item across packaging levels thereof, track at least one attribute of transaction information associated with the item, share detailed item handling data associated with the transaction information during logistics operations with respective logistics supply chain parties, and link the detailed item handling data to an item being returned (e.g., via an RMA).

[0082] Beginning at step 602, an end user 142 (e.g., of a destination 140-1) packages at least one item 103 for return (e.g., to an item handling facility 126) in a return package 504, and the system 500 generates return transaction information associated with the at least one item 103. Then, at step 604, a second user 122 (e.g., a transportation company or transport enterprise) transports the at least one item 103 to a third user 130 (e.g., an item handling facility 126). At step 604, the third user 130 processes the at least one item 103. Each of steps 602-206 is described below with respect to the Fig. 10 - Fig. 12 described in more detail.

[0083] Fig. 10 is a flowchart illustrating step 604 of Fig. 9 in more detail. At step 640, the end user 142 identifies order information of the at least one item 103. For example, the end user 142 may connect to an item handling device 126 (e.g., via a website, portal, application, etc.) to identify the order information of the at least one item 103. The order information may include, but is not limited to, an identifier of an order (e.g., a code, confirmation number, serial number, etc.), a date of the order, a time of the order, an identifier (e.g., a serial number, Universal Product Code (UPC), Stock Keeping Unit (SKU), etc.) of the at least one item 103, a name and / or image of the at least one item 103, a quantity of an ordered item 103, and payment data for the order.At step 642, the system 500 may receive return identification information of the at least one item 103 based on the identified order information. The return identification information may include, but is not limited to, a reason or justification for the return and / or a description.

[0084] Steps 644 and 646 of the process are optional. At step 644, the system 500 receives at least one captured image of the at least one item 103. At step 646, the system 500 authenticates the return identification information based on the at least one captured image. For example, if the return identification information indicates that a damaged condition of the at least one item 103 is the reason or justification for returning it, then the system 500 may authenticate the return identification information based on at least one captured image depicting the damaged condition of the at least one item 103.

[0085] At step 648, the system 500 generates the return transaction information associated with the at least one item 103 based on the order information, the return identification information, and return shipping information (e.g., a tracking number, a date, a time, etc.). The system 500 may transmit at least one of an alert and a notification to an authenticated external system or database (e.g., a merchant, seller, etc.) via at least one application programming interface in response to an event associated with the return transaction information. At step 650, the system 500 generates a return identifier 506 indicative of the return transaction information, and the end user 142 may apply the return identifier 506 indicative of the return transaction information (e.g., a contract or agreement) to the return package 504.The return identifier 506 may include, but is not limited to, one or more of a machine-readable symbol, a label, a barcode, an RFID tag, a QR code, and a BLE beacon.

[0086] Fig. 11 is a flowchart illustrating step 604 of Fig. 9. At step 680, the second user 122 receives the return package 504 from the end user 142 of the destination 140-1. As mentioned above, the second user 122 may use a device 124 for authentication and processing. For example, the second user 122 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 124 for authentication purposes. Upon authentication, the second user 122 may receive the return package 504 from the end user 142 of the destination 140-1.

[0087] At step 682, the second user 122 may use the device 124 to associate the return package 504 with the carrier or transportation company (e.g., the second user 122) by processing the return identifier 506 via the device 124, and the system 500 may modify the return transaction information by adding the association of the return package 504 with the second user 122 to the return transaction information. This association may indicate the receipt of the return package 504 by the carrier or transportation company from the end user 142.

[0088] At step 684, the second user 122 may deposit the return package 504 with a third user 130 of an item handling facility 126. For example, the second user 122 may transport and deliver the return package 504 to the third user 130 of an item handling facility 126. At step 686, the second user 122 may use the device 124 to associate the return package 504 with the item handling facility 126 (e.g., the third user 130) by processing the return identifier 506 via the device 124, and the system 500 may modify the return transaction information by adding the association of the return package 504 with the third user 130 to the return transaction information. This association may indicate receipt of the return package 504 by the item handling facility 126 from the transportation company or carrier.

[0089] At step 688, the system 500 may store receipt and deposit event data and associated timestamps (e.g., time and / or date), in addition to the associations, in a shared database 152-2 accessible by authenticated users of an item handling facility 126 and the carrier or carrier.

[0090] Fig. 12 is a flowchart illustrating step 606 of Fig.9. As mentioned above, the third user 130 may use a device 132 for authentication and processing. For example, the third user 130 may enter a passcode and / or submit biometric data (e.g., a fingerprint) via a GUI of the mobile device 132 for authentication purposes. Upon authentication, at step 720, the third user 130 may process the return identifier 506 of the return package 504 via the mobile device 132, and the system 500 may determine the order information of the at least one item 103 based on the processing. At step 722, the system 500 may obtain transaction information associated with the at least one item 103 from a database 134 of the item handler 126 based on the determined order information.The transaction information may indicate the handling data of the at least one item 103 prior to the return of the at least one item 103 and may include an association of a first identifier 112 of a first package 110 comprising the at least one item 103 and a second identifier 116 of a second package 114 comprising the first package 110, wherein the association indicates a nested relationship, packaging information of the at least one item 103, and shipping information of the at least one item 103. At step 724, the system 500 may determine the associated first identifier 112 of the first package 110 and the second identifier 116 of the second package 114 based on the transaction information.

[0091] Then, at step 726, the system 500 may associate the return identification information of the item 103 with the associated first identifier 112 of the first package 110 and the second identifier 116 of the second package 114. At step 728, the system 500 may store the associated return identification information, the first identifier 112 of the first package 110, and the second identifier 116 of the second package 114 in the database 134 of the item handler 126. In this way, the item handler 126 may associate the return identification information of the item 103 with transaction information about the item 103 prior to the original shipment.

[0092] Specific embodiments have been described in the foregoing specification. However, those skilled in the art will recognize that various modifications and changes may be made without departing from the scope of the invention as set forth in the claims below. Accordingly, the specification and figures are to be considered in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of the present teachings.

[0093] The benefits, advantages, solutions to problems, and any element(s) that may cause a benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of any or all of the claims. The invention is defined solely by the appended claims, including any amendments made during the pendency of this application and any equivalents of those claims as issued.

[0094] Furthermore, in this document, relational expressions such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action, without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has," "having," "includes," "including," "containing," "contains," or any other variation thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, or contains a list of elements not only includes those elements, but may include other elements not expressly listed or inherent in such a process, method, article, or apparatus. An element that "comprises... a," "has...a", "includes... a", "contains... a" does not preclude, without further limitation, the existence of additional identical elements in the process, method, article, or apparatus comprising, having, including, or containing the element. The terms "a" and "an" are defined as one or more unless expressly stated otherwise herein. The terms "substantially", "generally", "approximately", "about", or any other version thereof are defined as being closely understood by one of ordinary skill in the art, and in one non-limiting embodiment, the term is defined to be within 10%, in another embodiment within 5%, in another embodiment within 1%, and in another embodiment within 0.5%.The term "coupled," as used herein, is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure "configured" in a particular manner is configured in at least that manner, but may also be configured in ways not listed.

[0095] Certain terms may be used herein to list combinations of elements. Examples of such terms include: "at least one of A, B, and C"; "one or more of A, B, and C"; "at least one of A, B, or C"; "one or more of A, B, or C." Unless expressly stated otherwise, the above terms include any combination of A and / or B and / or C.

[0096] It should be understood that some embodiments may include one or more specialized processors (or "processing devices") such as microprocessors, digital signal processors, custom processors, and field-programmable gate arrays (FPGAs), and unique stored program instructions (including both software and firmware) controlling the one or more processors to, in conjunction with certain non-processor circuitry, implement some, most, or all of the functions of the method and / or apparatus described herein. Alternatively, some or all of the functions could be implemented by a state machine that does not have stored program instructions or in one or more application-specific integrated circuits (ASICs) in which each function, or some combination of certain of the functions, is implemented as custom logic.Of course, a combination of the two approaches could be used.

[0097] Furthermore, an embodiment may be implemented as a computer-readable storage medium having computer-readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method described and claimed herein. Examples of such computer-readable storage media include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (read-only memory), a PROM (programmable read-only memory), an EPROM (erasable programmable read-only memory), an EEPROM (electrically erasable programmable read-only memory), and a flash memory.Furthermore, it is expected that, notwithstanding possible considerable effort and many design decisions motivated, for example, by available time, current technology, and economic considerations, those of ordinary skill in the art, guided by the concepts and principles disclosed herein, will readily be able to generate such software instructions and programs and ICs with minimal experimentation.

[0098] The Summary of Disclosure is provided to enable the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Moreover, it will be apparent from the foregoing Detailed Description that various features are grouped together in various embodiments for the purpose of simplifying the disclosure. This method of disclosure should not be interpreted to reflect an intent that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in fewer than all features of a single disclosed embodiment.Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as separately claimed subject matter.

Claims

[1] A method for tracking object handling data, comprising: Associating, by a first device of a first user, a first identifier of at least one first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package and the association indicates a nested relationship; Generating transaction information associated with the at least one item based on the association and packaging information of the at least one item; Generating and applying a third identifier that indicates the transaction information associated with the at least one item to the second package; and Tracking at least one attribute of the transaction information associated with the at least one item via the third identifier. [2] The method of claim 1, further comprising Authenticating the first user via the first device; and Generating the first identifier of the at least one first package comprising the at least one item based on a detected event. [3] The method of claim 1, further comprising Authenticating a second user via a second device; Assigning the second packet to the second user and adding the assignment of the second packet to the second user to the transaction information by processing the third identifier via the second device; and Associating the second packet with a third user and adding the association of the second packet with the third user to the transaction information by processing the third identifier via the second device. [4] The method of claim 3, further comprising Storing the first identifier, the second identifier, the third identifier and the packaging information in a first database, wherein the first database is shared by at least two of the first user, the second user and the third user, and the first user is a manufacturer, the second user is a transporter and the third user is a dealer. [5] The method of claim 3, further comprising Authenticating the third user via a third device; Determining at least one condition of the second packet; adding the determined at least one condition of the second packet to the transaction information by processing the third identifier via the third device; Determine whether the specified condition matches the transaction information; Receiving the second packet if the specified condition matches the transaction information; and Rejecting the second packet if the specified condition does not match the transaction information, where the particular at least one condition of the second packet specifies one or more of a fair, a tampered, a corrupted, and an environmental condition. [6] The method of claim 5, further comprising Adding a receive event to the transaction information based on receiving the second packet; Processing the first identifier of the at least one first packet and the second identifier of the second packet via the third device; Determining whether the association of the first identifier of the at least one first packet and the second identifier of the second packet corresponds to the transaction information; Authenticating the transaction information if the mapping matches the transaction information; and Add an alarm to the transaction information if the mapping does not match the transaction information. [7] The method of claim 6, further comprising Generating shipping information in response to received order information of the at least one item; Modifying the transaction information by adding the shipping information and the order information to the transaction information; Generating and applying a fourth identifier indicating the modified transaction information to a third package comprising the at least one item; Storing the fourth identifier and the shipping information in a second database, wherein the second database is shared with the second user and the third user, and the second user is a transporter and the third user is a dealer. [8] The method of claim 7, wherein the first identifier, the second identifier, the third identifier, and the fourth identifier are one or more of a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, a radio frequency identification (RFID) tag, a quick response (QR) beacon, and a Bluetooth Low Energy (BLE) beacon. [9] The method of claim 1, wherein the transaction information is one of a contract and an agreement and is encrypted or added to a blockchain. [10] A system for tracking object handling data, comprising: a first device; a second device; a third device; one or more processors; and a non-transitory computer-readable memory coupled to the first device, the second device, the third device, and the one or more processors, the memory storing instructions thereon that, when executed by the one or more processors, cause the one or more processors to: Associating, by the first device of a first user, a first identifier of at least one first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package and the association indicates a nested relationship; Generating transaction information associated with the at least one item based on the association and packaging information of the at least one item; Generating a third identifier that indicates the transaction information associated with the at least one item to be applied to the second package; and Tracking at least one attribute of the transaction information associated with the at least one item via the third identifier. [11] The system of claim 10, wherein the instructions, when executed, further cause the one or more processors to: Authenticating the first user via the first device; and Generating the first identifier of the at least one first package comprising the at least one item based on a detected event. [12] The system of claim 10, wherein the instructions, when executed, further cause the one or more processors to: Authenticating a second user via a second device; Assigning the second packet to the second user and adding the assignment of the second packet to the second user to the transaction information by processing the third identifier via the second device; and Associating the second packet with a third user and adding the association of the second packet with the third user to the transaction information by processing the third identifier via the second device. [13] The system of claim 12, wherein the instructions, when executed, further cause the one or more processors to: Storing the first identifier, the second identifier, the third identifier and the packaging information in a first database, wherein the first database is shared by at least two of the first user, the second user and the third user, and the first user is a manufacturer, the second user is a transporter and the third user is a dealer. [14] The system of claim 12, wherein the instructions, when executed, further cause the one or more processors to: Authenticating the third user via a third device; Receiving at least one specific condition of the second packet; adding the determined at least one condition of the second packet to the transaction information by processing the third identifier via the third device; Determine whether the specified condition matches the transaction information; Transmitting a notification to receive the second packet if the determined condition matches the transaction information; and Transmitting a notification to reject the second packet if the specified condition does not match the transaction information, where the particular at least one condition of the second packet specifies one or more of a fair, a tampered, a corrupted, and an environmental condition. [15] The system of claim 14, wherein the instructions, when executed, further cause the one or more processors to: Adding a receive event to the transaction information when receiving the second packet; Processing the first identifier of the at least one first packet and the second identifier of the second packet via the third device; Determining whether the association of the first identifier of the at least one first packet and the second identifier of the second packet corresponds to the transaction information; Authenticating the transaction information if the mapping matches the transaction information; and Add an alarm to the transaction information if the mapping does not match the transaction information. [16] The system of claim 15, wherein the instructions, when executed, further cause the one or more processors to: Generating shipping information in response to received order information of the at least one item; Modifying the transaction information by adding the shipping information and the order information to the transaction information; generating a fourth identifier indicating the modified transaction information to be applied to a third package comprising the at least one item; Storing the fourth identifier and the shipping information in a second database, wherein the second database is shared with the second user and the third user, and the second user is a transporter and the third user is a dealer. [17] The system of claim 16, wherein the first identifier, the second identifier, the third identifier, and the fourth identifier are one or more of a machine-readable symbol, a label, a temperature-sensitive marker, a barcode, a radio frequency identification (RFID) tag, a quick response (QR) beacon, and a Bluetooth Low Energy (BLE) beacon. [18] The system of claim 10, wherein the transaction information is one of a contract and an agreement and is encrypted or added to a blockchain. [19] An accessible machine-readable medium comprising instructions for tracking item handling data that, when executed, cause a machine to: Associating, by a first device of a first user, a first identifier of at least one first package comprising at least one item and a second identifier of a second package, wherein the second package comprises the at least one first package and the association indicates a nested relationship; Generating transaction information associated with the at least one item based on the association and packaging information of the at least one item; Generating a third identifier that indicates the transaction information associated with the at least one item to be applied to the second package; and Tracking at least one attribute of the transaction information associated with the at least one item via the third identifier.

Images