This International Application claims priority from a Patent application filed in India having Patent Application No. 202021010515, filed on March 12, 2020, and titled “SYSTEM AND METHOD TO MANAGE LAST MILE PRODUCT DELIVERY-RELATED ISSUES OF SELLERS”.

BACKGROUND

Embodiments of the present disclosure relate to a system for management of issues in an electronic commerce platform and more particularly to a system and a method to manage last mile product delivery related issues of sellers.

Last mile delivery is defined as movement of one or more goods from a transportation hub to a final delivery destination. The last mile delivery nowadays is one of the main challenges in the logistics. As, customers increasingly turn to e- commerce to meet their purchasing needs, fast shipping is not simply something the customers feel good about having. It’s a realistic expectation in any e-commerce shopping experience, wherein the customers expect more from delivery experiences than ever before. Businesses or sellers have understood that they need to perfect the last mile delivery processes in order to be successful in maintaining a healthy relationship with the customers for both long term and short-term basis. Offering the last-mile delivery service and return experiences by the sellers improves conversion rates, purchase activity and brand loyalty. But the sellers while offering the last mile delivery service faces one or more challenges which are overcome by various available systems.

Conventionally, the system available for the last mile delivery process for a product delivery is managed by involving manual intervention. However, such manual intervention of the conventional system leads to increase in generation of one or more errors. Also, such system leads to increase in number of shipments returns of products in the last mile delivery process due to logistic inefficiencies. Moreover, such conventional system also lacks in providing coordination between one or more stakeholders involved in the last mile delivery process.

Hence, there is a need for an improved system and a method to manage last mile product delivery related issues of sellers.

BRIEF DESCRIPTION

In accordance with an embodiment of a present disclosure a system to manage last mile product delivery related issues of sellers is disclosed. The system includes a seller issue receiving subsystem configured to receive one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller. The system also includes a seller issue analysis subsystem operatively coupled to the seller issue receiving subsystem. The seller issue analysis subsystem is configured to determine a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique. The seller issue analysis subsystem is also configured to identify a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository. The system also includes a seller issue resolution subsystem operatively coupled to the seller issue analysis subsystem. The seller issue resolution subsystem is configured to identify one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time (TAT). The seller issue resolution subsystem is also configured to resolve the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. The seller issue resolution subsystem is also configured to generate one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached. In accordance with another embodiment of the present disclosure, a method for managing last mile product delivery related issues of sellers is disclosed. The method includes receiving, by a seller issue receiving subsystem, one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller. The method also includes determining, by a seller issue analysis subsystem, a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique. The method also includes identifying, by the seller issue analysis subsystem, a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository. The method also includes identifying, by a seller issue resolution subsystem, one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time. The method also includes resolving, by the seller issue resolution subsystem, the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. The method also includes generating, by the seller issue resolution subsystem, one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached.

To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which: FIG. 1 is a block diagram of a system to manage last mile product delivery related issues of sellers in accordance with an embodiment of the present disclosure;

FIG. 2 illustrate a schematic representation of an exemplary embodiment of a system to manage last mile product delivery related issues of sellers of FIG. 1 in accordance with an embodiment of a present disclosure;

FIG. 3 illustrates a block diagram of a computer server in accordance with an embodiment of the present disclosure; and

FIG. 4 is a flow chart representing the steps involved in a method to manage last mile product delivery related issues of sellers of FIG. 1 in accordance with the embodiment of the present disclosure.

Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

DETAILED DESCRIPTION For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.

Embodiments of the present disclosure relate to a system and a method to manage last mile product delivery related issues of sellers. The system includes a seller issue receiving subsystem configured to receive one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller. The system also includes a seller issue analysis subsystem operatively coupled to the seller issue receiving subsystem. The seller issue analysis subsystem is configured to determine a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique. The seller issue analysis subsystem is also configured to identify a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository. The system also includes a seller issue resolution subsystem operatively coupled to the seller issue analysis subsystem. The seller issue resolution subsystem is configured to identify one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time (TAT). The seller issue resolution subsystem is also configured to resolve the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. The seller issue resolution subsystem is also configured to generate one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached.

FIG. 1 is a block diagram of a system (100) to manage last mile product delivery related issues of sellers in accordance with an embodiment of the present disclosure. The system (100) includes a seller issue receiving subsystem (110) configured to receive one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller. As used herein, the term ‘seller issues’ is defined as one or more complaints or problems of the seller related to one or more stakeholders associated a product delivery when a product is dispatched from the seller side. In one embodiment, the one or more seller issues may include at least one of a fake attempt by a logistics partner, delivery percentage, urgent delivery, product return request, change of payment option from cash on delivery (COD) to prepaid option, address and contact number update, schedule parcel delivery, an incorrect product received by a customer, prepaid order delivered without acceptance by a customer, change request for cash on delivery (COD) amount, return to origin (RTO) wrong product delivered, self-collect, turnaround time (TAT) limit crossed for first attempt and reattempt or a combination thereof. In one embodiment, the one or more formats may include at least one of a text format, an audio format or a combination thereof.

In some embodiment, the fake attempt provided by the logistics partner may include a false reason provided by the logistics partner for failure in the delivery process of the product. In such embodiment, the fake remark provided by a logistics partner may include at least one of customer refuse to accept a shipment, customer ask for cancellation of an order, customer phone was unreachable, customer was unavailable at delivery address, customer address was incorrect, customers does not need the shipment or a combination thereof. In another embodiment, the delivery percentage issue associated with the seller may include issue faced by the seller in case of decrease in rate of the delivery success percentage associated with the product. In yet another embodiment, the urgent delivery issue associated with the seller may include one or more challenges such as limitation in number of resources, limited stock availability, huge traffic in case of sale season and the like. In such embodiment, the one or more challenges may be faced by the seller during the urgent delivery request received from the customer. In one embodiment, the product return request may create an issue for the seller when a genuine reason for the return by the customer is unknown and unacceptable by the seller.

In another embodiment, the change of the payment option from the COD to the prepaid option may create the issue for the seller as the seller may not be informed at prior and may create unnecessary confusion. In yet another embodiment, the address and the contact number update may initiate a problem for the seller may not be aware of a customer’s contact details which leads to miscommunication. In one embodiment, the incorrect product received by the customer may include an issue faced by the one or more sellers when a wrong product is delivered by an e- seller or a product is intentionally exchanged by a delivery personnel. In another embodiment, the prepaid order delivered without acceptance by the customer may create one or more issues for the one or more sellers in tracking or identifying a person who has accepted the customer’s order. In yet another embodiment, the change request from the customer for the cash on delivery (COD) amount may include an issue such as arranging an exact change amount by the seller to return to the customer when the customer is unaware about the COD amount. In such embodiment, the seller may also be unable to receive the COD amount from the customers due to customer’s unawareness which may further leads to monetary loss of the one or more sellers. In one embodiment, the self-collect option may create an issue for the one or more sellers to track and match the number of shipments collected intentionally with total number of shipments dispatched to the delivery centre for out for delivery (OFD). The reattempting option of the delivery for the shipment may create an issue for the one or more sellers as the seller may need to invest time and effort for arranging the one or more resources in order to deliver such shipments. The system (100) also includes a seller issue analysis subsystem (120) operatively coupled to the seller issue receiving subsystem (110). The seller issue analysis subsystem (120) is configured to determine a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique. The natural language processing technique understands the context of the one or more received customer issues in human language and processes it further to be understandable or interpreted by a computer.

The seller issue analysis subsystem (120) is also configured to identify a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository). As used herein, the term ‘TAT’ is defined as a period of time from time of submission or proposal of a process to the time of the completion or resolution of the process. In one embodiment, the TAT may be identified to analyse the time taken for resolution of a seller issue. In such embodiment, the TAT is dependent upon a international time zone.

The system (100) also includes a seller issue resolution subsystem (130) operatively coupled to the seller issue analysis subsystem (120). The seller issue resolution subsystem (130) is configured to identify one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time (TAT). In one embodiment, the one or more stakeholders corresponding to the one or more determined seller issues may include at least one of a logistics partner, a customer or a combination thereof.

The seller issue resolution subsystem (130) is also configured to resolve the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. In one embodiment, the predefined set of issue resolution rules may include a set of rules for resolution of the one or more determined seller issues corresponding to the one or more identified stakeholders based on consideration of a plurality of actionable parameters. In such embodiment, the plurality of actionable parameters may include at least one of a status of an identified stakeholder, a code of an identified stakeholder, remark of an identified stakeholder or a combination thereof. In some embodiment, the plurality of actionable parameters may be collected from a server through one or more methods. In such embodiment, the one or more methods may include a push method or a pull method. The seller issue resolution subsystem (130) is also configured to generate one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached.

In a specific embodiment, the system (100) further includes an issue notification subsystem (not show in FIG. 1) operatively coupled to the seller issue resolution subsystem (130). The issue notification subsystem is configured to send a notification of one or more generated actionable insights to the one or more identified stakeholders via a plurality of notification means when breaching of the identified turnaround time (TAT) corresponding to the one or more stakeholders is determined in real-time. In some embodiment, the plurality of notification means may include an automated call, a text message, a web-based message, an email and the like.

FIG. 2 illustrate a schematic representation of an exemplary embodiment of a system (100) to manage last mile product delivery related issues of sellers of FIG. 1 in accordance with an embodiment of a present disclosure. The system (100) helps in managing a last mile delivery process with defined turnaround time which helps e- sellers and logistics partners to deliver shipment to buyers within stipulated amount of time and reduce shipment return to origin (RTO). For example, the system (100) identifies one or more stakeholders involved and exact reasons for shipment return in the last mile delivery process and upon identification, the system (100) enables coordination between the one or more stakeholders to reduce the shipment return and improve delivery ratio of the shipment.

Let us assume that a customer ‘A’ (105) ordered a product such as a watch from an ecommerce website ‘B\ Now, before the product gets out for delivery (OFD) from a seller’s ‘Z’ (108) place, a shipment status is sent to the customer ‘A’ (105) through one or more communication channels to keep the customer informed and updated during a journey of delivery of the product from the seller’s end. Once, the product reaches the customer ‘A’ (105) via a logistics partner ‘C’ (115), one or more seller issues associated with the product delivery are identified and received by a seller issue receiving subsystem (110). Here, the one or more seller issues may be received in one or more formats which may include either a text format, an audio format or a combination thereof. Once, the one or more seller issues are received, such one or more received issues are analyzed by a seller issue analysis subsystem (120) in order to determine the context by using a natural language understanding technique.

For example, if the seller (108) is facing an issue corresponding to cash on delivery (COD) amount not ready with the customer (105). In such a scenario, the seller issue analysis subsystem (120) is configured to identify a reason for the issue i.e. why an exact change amount is not ready with the customer. Here, the reason may include at least one of a lack of prior notification related to delivery of the shipment, lack of awareness of the customer corresponding to the delivery of the product, variation in the amount after order completion due to one or more reasons, lack of COD amount availability with the customer or a combination thereof. Here, upon analysis of the one or more reasons, a turnaround time (TAT) corresponding to the seller’s issue is identified based on comparison of the received seller’s issue with a similar type of prestored seller issue stored in an issue repository (125).

Upon identification of the TAT by the seller issue analysis subsystem (120), one or more stakeholders associated with the seller issue are also identified by a seller issue resolution subsystem (130). For example, the one or more stakeholders may include the customer or the logistics partner. So, here, for the issue of the COD amount not ready with the customer, the stakeholder involved is customer (105) and the logistics partner (115). Later, the seller issue resolution subsystem (130), also resolves the determined seller issue within the identified turnaround time (TAT) by coordinating with the customer (105) using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. Here, the plurality of actionable parameters may include at least one of a status of an identified stakeholder, a code of an identified stakeholder, remark of an identified stakeholder or a combination thereof.

For example, for the issue like the COD amount not ready with the customer, if the logistics partner ‘C’ (115) has also given the remark as same that COD amount not ready, in such a case, the predefined set of rules tries to verify the authenticity of the remark provided by the logistics partner (115) for resolution of the seller issue. For such verification, the seller issue resolution subsystem (130) first fetches the plurality of actionable parameters from a cloud server by using a Pull method. Now, if the status provided by the logistics partner ‘A’ (115) is ‘undelivered’, code as Ό6’ and remark as ‘COD amount not ready with the customer’, then immediately, the code provided by the logistics partner ‘A’ (115) is mapped with a prestored standard remark corresponding to the code. Here, the prestored standard remark corresponding to the standard remark is stored in a database. Again, upon mapping, if the standard remark also shows that ‘COD amount was not ready with the customer’ and the reason is due to lack of awareness of the customer, then the customer (105) which is the stakeholder associated with the seller issue is sent an actionable insight. Similarly, the seller issue resolution subsystem (130) also identifies if there is any problem arising from the sellers’ end related to the delivery of the product to the customer (105). For example, if the seller has not informed the logistics partner (115) about initiation of the product.

Again, if the seller issue resolution subsystem (130) identifies the standard remark as ‘COD amount not ready with the customer due to lack of delivery notification sent by the logistics partner’, the logistics partner ‘A’ (115) corresponding to the issue of the seller is identified and further the actionable insight is sent. Here, the actionable insight may be notified to the one or more identified stakeholders by an issue notification subsystem (140) via a plurality of notification means when breaching of the TAT corresponding to the one or more stakeholders is identified in real-time. For example, the plurality of notification means may include an automated call, a text message, a web-based message, an email and the like. Thus, an artificial intelligence driven approach helps in understanding the context of the seller’s (108) input and inform the respective logistic partner or the customer through the plurality of notification means in order to take necessary action for managing the last mile delivery process.

FIG. 3 illustrates a block diagram of a computer server in accordance with an embodiment of the present disclosure. The server 200 includes processor(s) 230, and memory 210 operatively coupled to the bus 220. The processor(s) 230, as used herein, means any type of computational circuit, such as, but not limited to, a microprocessor, a microcontroller, a complex instruction set computing microprocessor, a reduced instruction set computing microprocessor, a very long instruction word microprocessor, an explicitly parallel instruction computing microprocessor, a digital signal processor, or any other type of processing circuit, or a combination thereof.

The memory 210 includes a subsystem stored in the form of executable program which instructs the processor 230 to perform the method steps illustrated in FIG. 1. The memory 210 has following subsystem: a seller issue receiving subsystem (110), a seller issue analysis subsystem (120) and a seller issue resolution subsystem (130).

The seller issue receiving subsystem (110) configured to receive one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller. The seller issue analysis subsystem (120) is configured to determine a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique. The seller issue analysis subsystem (120) is also configured to identify a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository. The seller issue resolution subsystem (130) is configured to identify one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time (TAT). The seller issue resolution subsystem (130) is also configured to resolve the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters. The seller issue resolution subsystem (130) is also configured to generate one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached. The bus (220) as used herein refers to be internal memory channels or computer network that is used to connect computer components and transfer data between them. The bus (220) includes a serial bus or a parallel bus, wherein the serial bus transmit data in bit-serial format and the parallel bus transmit data across multiple wires. The bus (220) as used herein, may include but not limited to, a system bus, an internal bus, an external bus, an expansion bus, a frontside bus, a backside bus and the like.

FIG. 4 is a flow chart representing the steps involved in a method to manage last mile product delivery related issues of sellers of FIG. 1 in accordance with the embodiment of the present disclosure. The method (300) includes receiving, by a seller issue receiving subsystem, one or more seller issues associated with a product delivery in one or more formats via a user interface associated with a seller in step 310. In one embodiment, receiving the one or more seller issues associated with the product delivery in the one or more formats may include receiving the one or more seller issues which may include but not limited to, at least one of a fake attempt by a logistics partner, delivery percentage, urgent delivery, product return request, change of payment option from cash on delivery (COD) to prepaid option, address and contact number update, schedule parcel delivery, an incorrect product received by a customer, prepaid order delivered without acceptance by a customer, change request for cash on delivery (COD) amount, return to origin (RTO) wrong product delivered, self-collect, turnaround time (TAT) limit crossed for first attempt and reattempt or a combination thereof.

The method (300) also includes determining, by a seller issue analysis subsystem, a context of the one or more received seller issues upon recognition of a language of the one or more received seller issues by using a natural language processing technique in step 320. The method (300) also includes identifying, by the seller issue analysis subsystem, a turnaround time (TAT) corresponding to one or more determined seller issues based on comparison of the one or more received seller issues with one or more prestored seller issues stored in a seller issue repository in step 330. In one embodiment, identifying the TAT corresponding to the one or more determined seller issues based on the comparison of the one or more received seller issues with the one or more prestored seller issues may include identifying the TAT corresponding to the one or more determined seller issues by comparing a prestored TAT associated with one or more similar prestored seller issues.

The method (300) also includes identifying, by a seller issue resolution subsystem, one or more stakeholders corresponding to the one or more determined seller issues upon identification of the turnaround time (TAT) in step 340. In one embodiment, identifying the one or more stakeholders corresponding to the one or more determined seller issues may include identifying the one or more stakeholders which may include at least one of a logistics partner, a seller or a combination thereof.

The method (300) also includes resolving, by the seller issue resolution subsystem, the one or more determined seller issues within an identified turnaround time (TAT) by coordinating with the one or more identified stakeholders using a predefined set of issue resolution rules, wherein the predefined set of issue resolution rules includes one or more instructions considering a plurality of actionable parameters in step 350. In one embodiment, resolving the one or more determined seller issues within the identified TAT by coordinating with the one or more identified stakeholders using the predefined set of issue resolution rules may include resolving the one or more determined seller issues using the predefined set of issue resolution rules which considers the plurality of actionable parameters such as at least one of a status of an identified stakeholder, a code of an identified stakeholder, remark of an identified stakeholder or a combination thereof. In such embodiment, the plurality of actionable parameters may include at least one of a status of an identified stakeholder, a code of an identified stakeholder, remark of an identified stakeholder or a combination thereof.

The method (300) also includes generating, by the seller issue resolution subsystem, one or more actionable insights for the one or more identified stakeholders to manage the one or more last mile product delivery issues of the sellers when the identified turnaround time (TAT) corresponding to the one or more identified stakeholders is breached in step 360. In one embodiment, generating the one or more actionable insights for the one or more identified stakeholders may include generating information which may be acted upon or utilised by the one or more identified stakeholders for better decision making in order to manage the last mile delivery process. In a preferred embodiment, the method (300) further includes sending, by an issue notification subsystem, a notification of one or more generated actionable insights to the one or more identified stakeholders via a plurality of notification means when breaching of the identified turnaround time (TAT) corresponding to the one or more stakeholders is determined in real-time. In one embodiment, sending the notification of the one or more generated actionable insights may include sending the notification through an automated call, a text message, a web-based message, an email and the like.

Various embodiments of the present disclosure provides a system which improves the delivery ratio and reduces the chances of return to origin of the shipment.

Moreover, the present disclosed system also identifies the correct stakeholder corresponding to the seller issues and helps in resolution of the issue within a predetermined TAT for making the management of the last mile delivery process faster and less error prone. Furthermore, the present disclosed system reduces cost of the system by avoiding the need for affording the manual assistance for collecting one or more seller issues and resolving such issues through manual intervention.

In addition to, the present disclosed system is a centralized engine which make sure that results, alerts and actions are being achieved within a predefined interval of time for resolution of the issues.

It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.

While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.

The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.