Hello, I'm looking through your site and docs and I don't see mentions of hotels, booking per days as opposed to per hours, having different prices per season. Are these things possible?
Also how does your plugin store data, does it use it's own database tables or does it strictly use CPTs and post meta (easier to extend with my own code)?
Finally how developer friendly is the plugin, is there a list of hooks/filters?
I apologize for the delayed response, we don't work on weekends.
And thank you for your interest in Amelia.
1. Amelia was created as a plugin for appointment booking mostly, so it's not the best option for the hotel reservations, probably.
We have two types of bookings: Services and Events. Both of them should have pre-set duration and, in order to avoid overbooking, should be connected to an Employee.
2. We don't interfere with any data, all the information is being stored in your database, so it's absolutely GDPR-friendly since there's an option that allows the customers to delete their profiles.
3. Amelia isn't an open-source plugin, so we don't provide the source code due to our company's policy. But there are webhooks that can be used for integration with another tool/service. You can find more information about webhooks settings here.
If you have any other questions, please let us know.
Hello, I'm looking through your site and docs and I don't see mentions of hotels, booking per days as opposed to per hours, having different prices per season. Are these things possible?
Also how does your plugin store data, does it use it's own database tables or does it strictly use CPTs and post meta (easier to extend with my own code)?
Finally how developer friendly is the plugin, is there a list of hooks/filters?
Hi, Slim!
I apologize for the delayed response, we don't work on weekends.
And thank you for your interest in Amelia.
1. Amelia was created as a plugin for appointment booking mostly, so it's not the best option for the hotel reservations, probably.
We have two types of bookings: Services and Events. Both of them should have pre-set duration and, in order to avoid overbooking, should be connected to an Employee.
2. We don't interfere with any data, all the information is being stored in your database, so it's absolutely GDPR-friendly since there's an option that allows the customers to delete their profiles.
3. Amelia isn't an open-source plugin, so we don't provide the source code due to our company's policy. But there are webhooks that can be used for integration with another tool/service. You can find more information about webhooks settings here.
If you have any other questions, please let us know.
Best Regards.