Hi Team,

We faced a critical issue yesterday related to our Flipkart API integration, which is used to update order statuses on the Flipkart panel.

As part of the current flow:

Once an order is picked, the invoice is generated from the Flipkart panel, which moves the order from “Pending Label” to “Pending RTD”.

This event is entirely dependent on Flipkart.

The second event is triggered when the order is marked “PACKED” in our Flex system.

At this stage, we push the RTD (Ready to Dispatch) confirmation via API, which allows the order to move from “Pending RTD” to “Pending Handover”.

However, yesterday, for certain orders, the second event was missed, due to which those orders did not move to the “Pending Handover” tab. As a result, the orders did not appear on the Ekart courier device, and hence pickup did not happen.

This issue is critical because:

Invoice generation alone is sufficient for order processing in Flex.

However, pushing the RTD event is mandatory for the order to move to the “Pending Handover” tab and appear in the courier pickup task.

If the RTD event is not pushed, the order gets blocked at Pending RTD, even though it is fully ready for dispatch.

We therefore request you to please explore and implement a mechanism to re-push the second (RTD) event automatically in case of failure. This will ensure:

Orders are not stuck due to transient API or server issues

Pickups can happen smoothly without manual intervention

Operational dependency risks are minimized

Request your urgent attention on this matter, given the direct impact on pickups and SLA.