# US 2026/0120044 A1 · Supply chain management, tracking, and integration platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0120044 A1
- Document ID: US20260120044A1
- Status: Published application
- Kind: A1
- Application number: 19/431,989
- Filed: 2025-12-23
- Published: 2026-04-30
- Earliest claimed: 2021-08-30
- Assignees: FourKites, Inc.
- Applicants: FourKites, Inc.
- Inventors: Chris Stauber; Adam G. Pasztory; Sajid Ali Mudassar; Muhammad Waqas Khan; Jeffrey Wehner
- Web page: https://patentgrep.com/patent/US20260120044A1

## CPC

- G06Q 10/0833: Tracking
- G06V 30/414: Extracting the geometrical structure, e.g. layout tree; Block segmentation, e.g. bounding boxes for graphics or text
- G06V 30/418: Document matching, e.g. of document images
- G06V 30/127: {with the intervention of an operator}
- G06V 30/40: Document-oriented image-based pattern recognition
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06V: IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING

## Abstract

Systems, methods, and non-transitory media are provided for supply chain management, tracking, and integration. An example method can include receiving, via one or more processors, a document associated with a booking of a shipment; extracting, via the one or more processors, data in the document associated with the booking of the shipment; based on the extracted data, generating a shipment record in a shipment management system; and based on the shipment record, tracking the shipment associated with the booking.

## Claims

### Claim 1

A method comprising:
receiving, a processor, a document associated with a booking of a shipment;
determining, based on validating one or more data elements extracted from the document, that the document is associated with a validation exception, wherein validating includes at least one of validating content of the one or more data elements and verifying that one or more required fields of the document are associated with an extracted data element;
determining whether the document corresponds to an existing shipment record based on at least one identifier included in the one or more data elements;
in response to determining that the document corresponds to the existing shipment record, determining a version of the document relative to previously received documents associated with the existing shipment record;
updating the existing shipment record based on the document in response to determining that the document corresponds to an updated version;
reconciling data from the document with data from the previously received documents associated with the booking using a semantic matching process configured to identify non-meaningful differences between corresponding data elements; and
based on the one or more data elements, generating or updating a shipment record in a shipment management system.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
extracting the one or more data elements from the document based on recognizing one or more data element types included in the document, the one or more data element types comprising at least one of a field, a topic, a label, and a semantic meaning; and
generating the shipment record further based on the recognizing of the one or more data element types.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
in response to determining that the document is associated with the validation exception, initiating a remediation workflow that includes generating an exception status associated with the document and requesting corrective information.

### Claim 4 (depends on 1)

The method of claim 1, wherein the document is received via at least one of an email from a party that created the booking, a system of the party that created the booking, and an application-programming interface associated with the system of the party that created the booking.

### Claim 5 (depends on 1)

The method of claim 1, wherein validating the document based on the one or more data elements is performed prior to creating the shipment record and further includes generating a validation status associated with the document, the validation status comprising at least one of an exception status, an in-progress status, and a valid status.

### Claim 6 (depends on 5)

The method of claim 5, wherein validating the document based on the one or more data elements further comprises at least one of validating data types of extracted data elements included in non-null fields of the document, verifying that the one or more required fields included in the document are not null, verifying that the document does not contain a virus, verifying a format of the document, verifying that the document can be processed by the shipment management system, verifying that data elements included in the document can be extracted via the processors verifying that the one or more data elements included in the document can be recognized via the processor, and verifying that a carrier identified in the one or more data elements matches at least one of an expected carrier and one of a set of known carriers.

### Claim 7 (depends on 5)

The method of claim 5, wherein the validation status comprises the exception status, the method further comprising:
generating the exception status in response to detecting at least one of an incorrect data type of an extracted data element included in a non-null field of the document, one or more required fields of the document are missing data, the document contains a virus, the format of the document does not match one or more predetermined formats, the document cannot be processed by the shipment management system, data in the document cannot be extracted via the processor, the data in the document cannot be recognized via the processor, and a carrier identified in the one or more data elements does not match at least one of an expected carrier and one of a set of known carriers.

### Claim 8 (depends on 1)

The method of claim 1, wherein validating the content of the document comprises determining whether at least a portion of the one or more data elements matches at least a portion of data included in the existing shipment record.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
based on the shipment record, predicting at least one of a shipment route, stop, delay, event, progress, statistic, and information related to the shipment.

### Claim 10 (depends on 1)

The method of claim 1, wherein validating the content of the document comprises: receiving an additional document; and
determining that data in the additional document does not match data in the shipment record.

### Claim 11

A computing device, comprising:
at least one memory; and
at least one processor coupled to the at least one memory and configured to:
receive a document associated with a booking of a shipment;
determine, based on validating one or more data elements extracted from the document, that the document is associated with a validation exception, wherein validating includes at least one of validating content of the one or more data elements and verifying that one or more required fields of the document are associated with an extracted data element;
determine whether the document corresponds to an existing shipment record based on at least one identifier included in the one or more data elements;
in response to determining that the document corresponds to the existing shipment record, determine a version of the document relative to previously received documents associated with the existing shipment record;
update the existing shipment record based on the document in response to determining that the document corresponds to an updated version;
reconcile data from the document with data from the previously received documents associated with the booking using a semantic matching process configured to identify non-meaningful differences between corresponding data elements; and
based on the one or more data elements, generate or update a shipment record in a shipment management system.

### Claim 12 (depends on 11)

The computing device of claim 11, wherein the at least one processor is configured to:
extract the one or more data elements from the document based on recognizing one or more data element types included in the document, the one or more data element types comprising at least one of a field, a topic, a label, and a semantic meaning; and
generate the shipment record further based on the recognizing of the one or more data element types.

### Claim 13 (depends on 11)

The computing device of claim 11, wherein the at least one processor is configured to:
in response to determining that the document is associated with the validation exception, initiate a remediation workflow that includes generating an exception status associated with the document and requesting corrective information.

### Claim 14 (depends on 11)

The computing device of claim 11, wherein the document is received via at least one of an email from a party that created the booking, a system of the party that created the booking, and an application-programming interface associated with the system of the party that created the booking.

### Claim 15 (depends on 11)

The computing device of claim 11, wherein validating the document based on the one or more data elements is performed prior to creating the shipment record and further includes generating a validation status associated with the document, the validation status comprising at least one of an exception status, an in-progress status, and a valid status.

### Claim 16 (depends on 15)

The computing device of claim 15, wherein validating the document based on the one or more data elements further comprises at least one of validating data types of extracted data elements included in non-null fields of the document, verifying that the one or more required fields included in the document are not null, verifying that the document does not contain a virus, verifying a format of the document, verifying that the document can be processed by the shipment management system, verifying that data elements included in the document can be extracted, verifying that the one or more data elements included in the document can be recognized, and verifying that a carrier identified in the one or more data elements matches at least one of an expected carrier and one of a set of known carriers.

### Claim 17 (depends on 15)

The computing device of claim 15, wherein the at least one processor is configured to:
generate the exception status in response to detecting at least one of an incorrect data type of an extracted data element included in a non-null field of the document, one or more required fields of the document are missing data, the document contains a virus, the format of the document does not match one or more predetermined formats, the document cannot be processed by the shipment management system, data in the document cannot be extracted, the data in the document cannot be recognized, and a carrier identified in the one or more data elements does not match at least one of an expected carrier and one of a set of known carriers.

### Claim 18 (depends on 11)

The computing device of claim 11, wherein validating the content of the document comprises determining whether at least a portion of the one or more data elements matches at least a portion of data included in the existing shipment record.

### Claim 19 (depends on 11)

The computing device of claim 11, wherein the at least one processor is configured to:
based on the shipment record, predicting at least one of a shipment route, stop, delay, event, progress, statistic, and information related to the shipment.

### Claim 20 (depends on 11)

The computing device of claim 11, wherein the at least one processor is configured to:
receive an additional document; and
determine that data in the additional document does not match data in the shipment record.
