Unified view operator interface system and method
A shipping management system comprises a memory configured with a set of carrier-specific mapping rules for a plurality of carriers. The system includes a non-transitory computer readable medium comprising a set of instructions executable by a processor to: apply carrier-specific mapping rules to carrier-specific records received from the respective carrier to map status codes or descriptions in the carrier-specific records from the respective carrier to generate normalized shipping information for shipments, the normalized shipping information comprising normalized status codes; store the normalized shipping information in association with the user account; receive a request for shipments associated with the user account; and generate an unified view user interface to present a unified view of shipments associated with the user account, the unified view comprising normalized statuses or descriptions for shipments across the plurality of carriers and controls to allow a user to request additional data on individual shipments.
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.
2 . The shipping management system of claim 1 , wherein to correct the assigned carrier for the shipment record, the processor is configured to:
correct the assigned carrier to a correct carrier based on the format or pattern of the tracking number.
3 . The shipping management system of claim 1 , wherein to correct the assigned carrier for the shipment record, the processor is configured to:
gather a plurality of carriers each of which matches the format or pattern of the tracking number, and
pick a correct carrier from the plurality of carriers.
4 . The shipping management system of claim 3 , wherein to pick the correct carrier from the plurality of carriers, the processor is configured to:
pick, using a rule, the correct carrier from the plurality of carriers.
5 . The shipping management system of claim 1 , wherein to enrich the shipment record, the processor is further configured to:
infer an origin or destination location for the shipment record based on a tracking event included in the shipment record.
6 . The shipping management system of claim 1 , wherein to enrich the shipment record, the processor is further configured to:
modify a timestamp of the shipment record.
7 . A computer-implemented method of interfacing with a plurality of carrier systems associated with a plurality of carriers, the computer-implemented comprising:
establishing, 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:
receiving, via the first integration path, a set of shipping report files associated with a carrier corresponding to that carrier system,
extracting, from each shipping report file of the set of shipping report files, a set of shipments of the carrier,
receiving, 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
extracting, 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:
parsing, by the at least one processor, 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
enriching, by the at least one processor, the shipment record, including:
applying 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
correcting 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, generating, by the at least one processor, 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
storing the normalized shipping information in association with a user account.
8 . The computer-implemented method of claim 7 , wherein correcting the assigned carrier for the shipment record comprises:
correcting the assigned carrier to a correct carrier based on the format or pattern of the tracking number.
9 . The computer-implemented method of claim 7 , wherein correcting the assigned carrier for the shipment record comprises:
gathering a plurality of carriers each of which matches the format or pattern of the tracking number, and
picking a correct carrier from the plurality of carriers.
10 . The computer-implemented method of claim 9 , wherein picking the correct carrier from the plurality of carriers comprises:
picking, using a rule, the correct carrier from the plurality of carriers.
11 . The computer-implemented method of claim 7 , wherein enriching the shipment record further comprises:
inferring an origin or destination location for the shipment record based on a tracking event included in the shipment record.
12 . The computer-implemented method of claim 7 , wherein enriching the shipment record further comprises:
modifying a timestamp of the shipment record.
13 . A computer program product comprising a non-transitory computer readable medium storing a set of computer instructions executable by a processor to:
establish, for each carrier system of a 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.
14 . The computer program product of claim 13 , wherein to correct the assigned carrier for the shipment record, the processor executes the set of computer instructions to:
correct the assigned carrier to a correct carrier based on the format or pattern of the tracking number.
15 . The computer program product of claim 13 , wherein to correct the assigned carrier for the shipment record, the processor executes the set of computer instructions to:
gather a plurality of carriers each of which matches the format or pattern of the tracking number, and
pick a correct carrier from the plurality of carriers.
16 . The computer program product of claim 15 , wherein to pick the correct carrier from the plurality of carriers, the processor executes the set of computer instructions to:
pick, using a rule, the correct carrier from the plurality of carriers.
17 . The computer program product of claim 13 , wherein to enrich the shipment record, the processor executes the set of computer instructions further to:
infer an origin or destination location for the shipment record based on a tracking event included in the shipment record.
18 . The computer program product of claim 13 , wherein to enrich the shipment record, the processor executes the set of computer instructions further to:
modify a timestamp of the shipment record.