Closed fregogui closed 3 months ago
This sounds more as place property and these are available in the Place object under placeProperties
array.
There is POWER
property defined in the code list.
It is expected to do filtering by the retailer or visually by the purchaser in the UI.
@fregogui : Shall the Power Plug be modeled as an ancillary product, i.e. meaning that the passenger pay extra for this service?
Hi, sorry for the delay.
Yes we want to sell the optional ancillary "power plug" allowing to seat on a a seat with a real power plug.
We have to find a way to send the information "this passenger has a power plug ancillary in its selected offer bundle" to the reservation GET /availabilities/place-map
API in order it return available seat having this power plug to this passenger (and not to the passenger not having this ancillary selected)
To be discussed in improvement on monetization of place reservation.
Some transporters condition seat selection to optional ancillaries (ex: if a passenger wants to choose an optional ancillary "power plug", only seats with power plugs should be displayed in the graphical seat selection).
Currently, it does not seem possible to condition
GET /availabilities/place-map
with an ancillary selection before creating the booking (only Reservation Offer Id seems to be a valid resourceId). Is this correct?In order to condition the seat map with ancillaries selection, it would be great to allow optional ancillaries offer ids in the query params of
GET /availabilities/place-map
. Does this seem reasonable?Thanks for your help.