You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add additional fulfillment status to retail API contract to indicate delivery delay due to consignee not available or consignee wants delivery at a later date
#100
Open
kishorgandham opened this issue
Apr 3, 2023
· 0 comments
The current fulfilment status list does not contain any codes that can help seller app communicate to buyer app that delivery is delayed due to consignee not answering calls, wrong address or destination location closed (office closed on weekend) or consignee's preference to take delivery at a later time/date etc...
As the buyer app can cancel order if the TAT is exceeded, the seller app needs a mechanism to communicate reason for delivery delays to buyer apps in case of exception scenarios.
The current fulfilment status list does not contain any codes that can help seller app communicate to buyer app that delivery is delayed due to consignee not answering calls, wrong address or destination location closed (office closed on weekend) or consignee's preference to take delivery at a later time/date etc...
As the buyer app can cancel order if the TAT is exceeded, the seller app needs a mechanism to communicate reason for delivery delays to buyer apps in case of exception scenarios.
See the following sample tracking URLs for some of the production ONDC orders where delivery was delayed due to the above reasons mentioned:
https://sleepyowl.shiprocket.co/tracking/NDD1434314
https://ordr.live/trk/21134110778470
https://ordr.live/trk/21134110778444
https://ordr.live/trk/21134110778433
The text was updated successfully, but these errors were encountered: