Processing order experience data across multiple data structures

A non-transitory processor-readable storage medium having stored therein program code of one or more software programs, wherein the program code when executed by at least one processing device causes the at least one processing device:

• to process data, obtained from a first set of data structures, pertaining to multiple orders placed with an enterprise by one or more users, wherein the first set of data structures contains multiple data structures, each comprising data, parsed from at least one set of order transactions data, associated with one or more distinct respective portions of the order transactions, and wherein processing the data is carried out, without input from the one or more users, by an eventing platform and comprises consolidating at least a portion of the obtained data into a single order view, enabling performance of scalable operations with respect to orders in connection with the enterprise;
• to extract information pertaining to multiple pre-defined attributes from the processed data and processing the extracted information into a second set of data structures, wherein the multiple pre-defined attributes comprise (a) one or more attributes pertaining to delivery commitment comprising at least one of an earliest estimated delivery date indicated at the time of order submission and a latest estimated delivery date indicated at the time of order submission, (b) one or more attributes pertaining to order processing performance comprising one or more order-related timestamps, (c) one or more attributes pertaining to order cancellation comprising one or more cancellation reasons, (d) one or more attributes pertaining to order-related communication preferences comprising at least one of a preference for an order acknowledgement communication medium, a preference for an order confirmation communication medium, a preference for an order shipped notification communication medium, and a preference for an order cancellation communication medium, (e) one or more attributes pertaining to order returns comprising one or more return-related timestamps, (f) one or more attributes pertaining to order status comprising order tracking information, and (g) one or more attributes pertaining to customer care comprising information pertaining to one or more customer inquiries pertaining to an order;
• to determine a negative weightage scale for at least a portion of the multiple pre-defined attributes by querying multiple users, via one or more dynamic user interfaces, pertaining to order experience issues;
• to attribute a value to each of the multiple pre-defined attributes, wherein the value attributed to each of the multiple pre-defined attributes is based at least in part on the negative weightage scale assigned to the given attribute;
• to calculate order experience scores for the multiple orders based at least in part on applying at least one algorithm to at least one of the extracted information pertaining to the multiple pre-defined attributes in the second set of data structures and the value attributed to each of the multiple pre-defined attributes;
• to generate at least one benchmark order experience value attributed to at least one portion of the enterprise, wherein the at least one benchmark order experience value is based at least in part on the calculated order experience scores;
• and
• to perform one or more operations related to order experience within the enterprise based at least in part on the at least one benchmark order experience value, wherein performing one or more operations comprises:
• automatically generating, using at least one web application programming interface, one or more pictorial representations of one or more dynamic order timeline views comprising one or more disruption points;
• and
• automatically updating, on a predetermined temporal basis and using the at least one web application programming interface, at least a portion of the one or more pictorial representations of the one or more dynamic order timeline views.

An apparatus comprising:

• at least one processing device comprising a processor coupled to a memory;
• the at least one processing device being configured:
• to process data, obtained from a first set of data structures, pertaining to multiple orders placed with an enterprise by one or more users, wherein the first set of data structures contains multiple data structures, each comprising data, parsed from at least one set of order transactions data, associated with one or more distinct respective portions of the order transactions, and wherein processing the data is carried out, without input from the one or more users, by an eventing platform and comprises consolidating at least a portion of the obtained data into a single order view, enabling performance of scalable operations with respect to orders in connection with the enterprise;
• to extract information pertaining to multiple pre-defined attributes from the processed data and processing the extracted information into a second set of data structures, wherein the multiple pre-defined attributes comprise (a) one or more attributes pertaining to delivery commitment comprising at least one of an earliest estimated delivery date indicated at the time of order submission and a latest estimated delivery date indicated at the time of order submission, (b) one or more attributes pertaining to order processing performance comprising one or more order-related timestamps, (c) one or more attributes pertaining to order cancellation comprising one or more cancellation reasons, (d) one or more attributes pertaining to order-related communication preferences comprising at least one of a preference for an order acknowledgement communication medium, a preference for an order confirmation communication medium, a preference for an order shipped notification communication medium, and a preference for an order cancellation communication medium, (e) one or more attributes pertaining to order returns comprising one or more return-related timestamps, (f) one or more attributes pertaining to order status comprising order tracking information, and (g) one or more attributes pertaining to customer care comprising information pertaining to one or more customer inquiries pertaining to an order;
• to determine a negative weightage scale for at least a portion of the multiple pre-defined attributes by querying multiple users, via one or more dynamic user interfaces, pertaining to order experience issues;
• to attribute a value to each of the multiple pre-defined attributes, wherein the value attributed to each of the multiple pre-defined attributes is based at least in part on the negative weightage scale assigned to the given attribute;
• to calculate order experience scores for the multiple orders based at least in part on applying at least one algorithm to at least one of the extracted information pertaining to the multiple pre-defined attributes in the second set of data structures and the value attributed to each of the multiple pre-defined attributes;
• to generate at least one benchmark order experience value attributed to at least one portion of the enterprise, wherein the at least one benchmark order experience value is based at least in part on the calculated order experience scores;
• and
• to perform one or more operations related to order experience within the enterprise based at least in part on the at least one benchmark order experience value, wherein performing one or more operations comprises:
• automatically generating, using at least one web application programming interface, one or more pictorial representations of one or more dynamic order timeline views comprising one or more disruption points;
• and
• automatically updating, on a predetermined temporal basis and using the at least one web application programming interface, at least a portion of the one or more pictorial representations of the one or more dynamic order timeline views.