US 12,462,215 B2
Unified view operator interface system and method
Jennifer Lynn Bebout, Austin, TX (US); Carson Bennett Krieg, Austin, TX (US); Matthew Howitt, Austin, TX (US); Clinton Frederick Miller, Austin, TX (US); Olivier Jean Marie Modica, Austin, TX (US); Sebastian Kuruvilla Karivelithara, Austin, TX (US); and Christopher Richter, Leander, TX (US)
Assigned to CONVEY, LLC, Austin, TX (US)
Filed by CONVEY, LLC, Austin, TX (US)
Filed on Feb. 12, 2024, as Appl. No. 18/438,697.
Application 18/438,697 is a continuation of application No. 17/895,824, filed on Aug. 25, 2022, granted, now 11,900,311.
Application 17/895,824 is a continuation of application No. 16/241,521, filed on Jan. 7, 2019, granted, now 11,436,555, issued on Sep. 6, 2022.
Claims priority of provisional application 62/614,181, filed on Jan. 5, 2018.
Prior Publication US 2024/0185174 A1, Jun. 6, 2024
Int. Cl. G06Q 10/0835 (2023.01); G06Q 10/083 (2024.01); G06Q 10/0833 (2023.01)
CPC G06Q 10/08355 (2013.01) [G06Q 10/0833 (2013.01); G06Q 10/0838 (2013.01)] 18 Claims
OG exemplary drawing
 
1. A shipping management system interfacing with a plurality of carrier systems associated with a plurality of carriers, comprising:
a memory storing a set of computer executable instructions; and
a processor coupled to the memory and configured to execute the set of computer executable instructions to cause the processor to:
establish, for each carrier system of the plurality of carrier systems, (i) a first integration path, and (ii) a second integration path that supports communication via an application programming interface (API) of that carrier system,
for each carrier system of the plurality of carrier systems:
receive, via the first integration path, a set of shipping report files associated with a carrier corresponding to that carrier system,
extract, from each shipping report file of the set of shipping report files, a set of shipments of the carrier,
receive, via the API associated with the second integration path and based on the set of shipments, a set of updated shipment status information associated with the set of shipments, and
extract, from the set of updated shipment status information received via the API, a shipment record of the carrier,
for each shipment record that was extracted:
parse the shipment record to determine a status code or exception type in the shipment record, wherein the shipment record identifies a tracking number for that shipment, and
enrich the shipment record, including:
apply a rule to the tracking number of the shipment record to determine that a format or pattern of the tracking number is not compatible with the respective carrier, and
correct an assigned carrier for the shipment record based on the format or pattern of the tracking number,
based on (i) the status code or exception type and (ii) the shipment record that was enriched, generate normalized shipping information for the shipment record by setting the status code or exception type in the shipment record to a normalized status code or exception type, and
store the normalized shipping information in association with a user account.