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 comprising:
a memory configured with:
a set of carrier-specific mapping rules for a plurality of carriers; and
carrier credential information associated with a user account;
a processor coupled to the memory; and
a non-transitory computer readable medium comprising a set of computer executable instructions, the computer executable instructions executable by the processor to:
connect to a plurality of carrier systems corresponding to the plurality of carriers;
provide respective carrier credentials from the user account to each carrier system of the plurality of carrier systems;
receive, from each carrier system, a set of carrier-specific shipment records associated with a set of shipments based on the provided respective carrier credentials;
for each received carrier-specific shipment record:
parse the carrier-specific shipment record to determine a status code in the carrier-specific shipment record;
apply a carrier-specific mapping rule for that carrier to the status code in the carrier-specific shipment record;
based on applying the carrier-specific mapping rule, determine that the status code in the carrier-specific shipment record either starts with or ends with an input status code of the carrier-specific mapping rule;
generate normalized shipping information for the carrier-specific shipment record, by setting the status code in the carrier-specific shipment record to a normalized status code as specified by the carrier-specific mapping rule;
store the normalized shipping information in association with the user account;
receive, via a user interface, a request for shipments associated with the user account; and
generate a unified view interface to present a unified view of shipments associated with the user account, the unified view indicating the normalized status codes for the set of shipments across the plurality of carriers and enabling a user to request additional data on the set of shipments.
2. The shipping management system of claim 1 , wherein the computer executable instructions are executable to receive the set of carrier-specific shipment records from a particular carrier via a plurality of integration paths.
3. The shipping management system of claim 1 , wherein the computer executable instructions are executable to determine if each carrier-specific shipping record represents an existing shipment at the shipping management system and, based on a determination that a given carrier specific shipping record does not correspond to an existing shipment, create a new shipping record.
4. The shipping management system of claim 1 , wherein the computer executable instructions are executable to extract a first set of carrier-specific shipment records from a first carrier of the plurality of carriers from a shipment record file provided by the first carrier.
5. The shipping management system of claim 4 , wherein the computer executable instructions are executable to extract a second set of carrier-specific shipment records from a first carrier from API response data.
6. The shipping management system of claim 1 , wherein at least a subset of the carrier-specific mapping rules include a resulting exception flag.
7. The shipping management system of claim 1 , wherein the computer executable instructions are executable to request carrier specific shipment records using a web service API.
8. The shipping management system of claim 1 , wherein the computer executable instructions comprise instructions executable to receive carrier-specific shipment records via a document interchange.
9. A computer program product comprising a non-transitory computer readable medium storing a set of computer executable instructions, the set of computer executable instructions comprising instructions executable by a processor to:
access a memory configured with:
a set of carrier-specific mapping rules for a plurality of carriers; and
carrier credential information associated with a user account;
connect to a plurality of carrier systems corresponding to the plurality of carriers;
provide respective carrier credentials from the user account to each carrier system of the plurality of carrier systems;
receive, from each carrier system, a set of carrier-specific shipment records associated with a set of shipments based on the provided respective carrier credentials;
for each received carrier-specific shipment record:
parse the carrier-specific shipment record to determine a status code in the carrier-specific shipment record;
apply a carrier-specific mapping rule for that carrier to the status code in the carrier-specific shipment record;
based on applying the carrier-specific mapping rule, determine that the status code in the carrier-specific shipment record either starts with or ends with an input status code of the carrier-specific mapping rule;
generate normalized shipping information for the carrier-specific shipment record, by setting the status code in the carrier-specific shipment record to a normalized status code as specified by the carrier-specific mapping rule;
store the normalized shipping information in association with the user account;
receive, via a user interface, a request for shipments associated with the user account; and
generate a unified view interface to present a unified view of shipments associated with the user account, the unified view indicating the normalized status codes for the set of shipments across the plurality of carriers and enabling a user to request additional data on the set of shipments.
10. The computer program product of claim 9 , wherein the computer executable instructions comprise instructions executable to receive the set of carrier-specific shipment records from a particular carrier via a plurality of integration paths.
11. The computer program product of claim 9 , wherein the computer executable instructions comprise instructions executable to determine if each carrier-specific shipping record represents an existing shipment at the shipping management system and, based on a determination that a given carrier specific shipping record does not correspond to an existing shipment, create a new shipping record.
12. The computer program product of claim 9 , wherein the computer executable instructions comprise instructions executable to extract a first set of carrier-specific shipment records from a first carrier of the plurality of carriers from a shipment record file provided by the first carrier.
13. The computer program product of claim 12 , wherein the computer executable instructions comprise instructions executable to extract a second set of carrier-specific shipment records from a first carrier from API response data.
14. The computer program product of claim 9 , wherein at least a subset of the carrier-specific mapping rules include a resulting exception flag.
15. The computer program product of claim 9 , wherein the computer executable instructions comprise instructions executable to request carrier specific shipment records using a web service API.
16. The computer program product of claim 9 , wherein the computer executable instructions comprise instructions executable to receive carrier-specific shipment records via a document interchange.