search

polarbeardesign / dds_app

2nd Gen
2 stars 0 forks source link

Issues with rides #12

Open polarbeardesign opened 9 years ago

polarbeardesign commented 9 years ago

Finite number of seats? Close advanced sales 48 hours before 'Rides' SEO on page. Track purchases?

bryancross commented 6 years ago

Finite number of seats?

Suggest booking to capacity, then accepting standbys. Ideally standbys would pay, and get a refund if they don't get a seat. Standbys would get a confirmation email, if they decline they lose their seat and the next standby gets an email. Airline reservation system redux

Close advanced sales 48 hours before

Is there a business reason for this? Squadron personnel booking rides should be using the webpage to do so, in which case they'd have real-time access to the advanced sales data.

Track purchases?

Seems useful for data mining, e.g., the 12 planes of Xmas data you generated a while back. Seems unlikely we'll get much in the way of repeat business, so little use for a Frequent Flyer program...

polarbeardesign commented 6 years ago

wrote this a while ago - obviously.

RE seats, went with selling the number of seats available per ride - if we have defined ride times. Otherwise people just buy seats and we make up a ride time.

RE closing sales - that should have read end pre-purchase discount 48 hours before. - but we aren't doing or enforcing that.

And we do try to track purchases for 12 planes, analytics/demographics, etc. But it comes from back end, after people fill out their forms. Would like to get forms directly on an iPad at the airshows - some units are trying that.

Frequent Flyer - if you saw that in the code - is more for members to track their flights, just for fun.