Replies: 1 comment
|
Catalog Discovery does not guarantee inventory availability. If a charger is unavailable post reservation, the BPP SHOULD either In the second case, the BAP may choose to either bubble up the cancellation status or internally perform a discovery + ordering cycle and book another charger and update the user's reservation. To provide a good user experience, it might take over the payment collection flow so that the consumer does not need to keep paying for new reservations due to cancellations and delayed refund cycles. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
If reservationSupported: true, reservation flow is tightly coupled with catalog structure.
Reservation is a soft promise for future availability, but is actually poor predictor of it.
How can we best balance the customer experience & asset utilization.. Does reseravation needs to be reimagine to perform better?
A side problem:
beckn:availabilityWindowupdates require CPOs to guess session duration which is hard due to all above.beckn:isActive = falsemakes charger disappear from ALL discovery.isActiveis too coarse—it's a global kill switch, not a real-time indicator.Possible solution: @DevangMstryls suggested decoupling reservation from availability. Devang.. please comment/elaborate .. Happy to review.
++ @biodatanet, @ravi-prakash-v
All reactions