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
In the meeting of 2024/11/22 we talked about selling travelpasses by using the OSDM specification. In the presentation the following topics were highlighted.
Selling Passes
Flexibility during purchase
a. Customers want to travel but don’t know where to go. Just an idea of one or more countries.
b. Customers travel when they want (activation of induvidual travel days)
c. Optional reservations when needed, last minute decision by the customer
Carriers rules
a. EU / NoN EU citizin (inbound / outbound travel) (Different product portofolio)
b. Cannot compete with point 2 point tickets
Regional passes instead of p2p tickets like Discoverholland and Euregio ticket (NS)
OSDM Challenges with passes.
OSDM works with the concept of an “offer request”
a. tripSpecification (Customer doesn’t know where he want to go)
b. tripSearchCriteria (Customer doesn’t know where he want to go)
c. nonTripSearchCriteria (places, for OCP which country to visit)
d. offerSearchCriteria (travelClass and ProductTags {EU|INT, GP|OCP, 1|2|3m, 4|5|7d)
e. anonymousPassengers (age, dob, residency)
Selling passes is more like a product shop approach
a. Shopping cart idea
b. Customer select a pass and buys it. Therefore he needs to know the price.
Passes have different rules, like which carriers can be used, only in a region.
Questions that surface are:
Q1. Does the products api need more get operations?
Q2. What is the best way to request a pass offer?
Q3 Are the elements in offer sufficient?
Q4. How do I sell a reservation to pass holder?
Q5. How do I get a pass status?
etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the meeting of 2024/11/22 we talked about selling travelpasses by using the OSDM specification. In the presentation the following topics were highlighted.
Selling Passes
a. Customers want to travel but don’t know where to go. Just an idea of one or more countries.
b. Customers travel when they want (activation of induvidual travel days)
c. Optional reservations when needed, last minute decision by the customer
a. EU / NoN EU citizin (inbound / outbound travel) (Different product portofolio)
b. Cannot compete with point 2 point tickets
OSDM Challenges with passes.
a. tripSpecification (Customer doesn’t know where he want to go)
b. tripSearchCriteria (Customer doesn’t know where he want to go)
c. nonTripSearchCriteria (places, for OCP which country to visit)
d. offerSearchCriteria (travelClass and ProductTags {EU|INT, GP|OCP, 1|2|3m, 4|5|7d)
e. anonymousPassengers (age, dob, residency)
a. Shopping cart idea
b. Customer select a pass and buys it. Therefore he needs to know the price.
Questions that surface are:
Q1. Does the products api need more get operations?
Q2. What is the best way to request a pass offer?
Q3 Are the elements in offer sufficient?
Q4. How do I sell a reservation to pass holder?
Q5. How do I get a pass status?
etc.
Beta Was this translation helpful? Give feedback.
All reactions