WP Amelia is very close to be the best booking system – It’s only missing a few things to be perfect!
What we really miss is sharing of resources between appointments and events. For some wired reason it’s only possible to locate an event at a place, but not the actual room or theatre at that place. If that room is already occupied by an appointment when you have planned an event, you are in big trouble. The other strange thing is that resource is a free text group without any more possibility to define what kind of resource and add more information.
Let’s say that the resource is a room or theatre – Then you need tell what the capacity in number of seats is independently of the number of employees at work. If a customer orders several tickets for music concert, there is still a number of tickets left that independent of the number of employees at work at that time. If the resource is a table, then you need to tell the number of seats around the around the table. When ordering a table with a give number of seats, then there are still tables to be booked independent of the number of employees.
The point is, if you think generic, a dinner or a music concert is a Service in the same way as yoga session, classroom education, hairdressing consulting etc. In both cases you need employees and resources to be able to deliver what is ordered. Therefore, it does not matter if you call it an Appointment or an Event, it’s a Service both times in the end. If Appointment and Events was connected to the same pool of resources it would the be possible to use WP Amelia for almost everything, not only one to one service, but also one to many services.
In a longer run, maybe WP Amelia should be developed in a more generic way where Appointment is planning part of the service while the Event is marketing of an external event where you invite the public to join. The Appointment is where the Customers ask for service – The Event is where the Service provider invite the Customers to join a Service. In that way you can also do marketing for Appointments at the barber shop service and yoga sessions in social media etc.
In my opinion, a clearer division of different purpose of Appointments and Events would make the solution easier to work with since today you do must register almost the same in both modules. Therefor it would be better to handle the planning of the service in one module and the marketing of the service in another module. Then it would be easier to add more functionality that is requested to make the tool even better as a planning and marketing tool.
Make I ask you to forward this to your ticket developer team?
Sharing resources between appointments and events · Amelia WordPress Booking Plugin Feedback (wpamelia.com)
WP Amelia is very close to be the best booking system – It’s only missing a few things to be perfect!
What we really miss is sharing of resources between appointments and events. For some wired reason it’s only possible to locate an event at a place, but not the actual room or theatre at that place. If that room is already occupied by an appointment when you have planned an event, you are in big trouble. The other strange thing is that resource is a free text group without any more possibility to define what kind of resource and add more information.
Let’s say that the resource is a room or theatre – Then you need tell what the capacity in number of seats is independently of the number of employees at work. If a customer orders several tickets for music concert, there is still a number of tickets left that independent of the number of employees at work at that time. If the resource is a table, then you need to tell the number of seats around the around the table. When ordering a table with a give number of seats, then there are still tables to be booked independent of the number of employees.
The point is, if you think generic, a dinner or a music concert is a Service in the same way as yoga session, classroom education, hairdressing consulting etc. In both cases you need employees and resources to be able to deliver what is ordered. Therefore, it does not matter if you call it an Appointment or an Event, it’s a Service both times in the end. If Appointment and Events was connected to the same pool of resources it would the be possible to use WP Amelia for almost everything, not only one to one service, but also one to many services.
In a longer run, maybe WP Amelia should be developed in a more generic way where Appointment is planning part of the service while the Event is marketing of an external event where you invite the public to join. The Appointment is where the Customers ask for service – The Event is where the Service provider invite the Customers to join a Service. In that way you can also do marketing for Appointments at the barber shop service and yoga sessions in social media etc.
In my opinion, a clearer division of different purpose of Appointments and Events would make the solution easier to work with since today you do must register almost the same in both modules. Therefor it would be better to handle the planning of the service in one module and the marketing of the service in another module. Then it would be easier to add more functionality that is requested to make the tool even better as a planning and marketing tool.
Hello Paul,
Thank you for reaching out to us and for your suggestion.
I will have this suggestion passed on to our management and I hope that it will be implemented at some point in the future.
Please let me know if you have any other questions.
Kind Regards,
Uros Jovanovic
[email protected]
Rate my support
Try our FREE mapping plugin! MapSVG - easy Google maps, interactive SVG maps, and floor plans, choropleth maps and much more - https://wordpress.org/plugins/mapsvg-lite-interactive-vector-maps/
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables