Yes, that is correct. Once you enable the WooCommerce service option, other payment methods will be disabled since WooCommerce supports the same payment methods. They have something called cash on delivery or similar if they change the title but this the same as our on sit option and for that reason all other payment are turned oof once you enable WooCommerce.
Hope this explains it.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
Well, this is not a perfect solution as there is a major difference in the payment processing flow.
1. The basic scenario should be (for probably lot of cases), the on-site payment. That is then nice, fast, easy and the appointment is then quickly confirmed so the UX is very smooth..
2. In some cases we wish to have the "reservation fee" to be taken on the booking process. Then it is OK to switch either to the Order Processing of the the WooCommerce cart. Unfortunately, the purchaser data are not copied from the reservation.. Is there potentially some filter to do so? Anyway, then the UX is bit worse (as more steps needed), but it is as it is..
3. There should be some options to force the reservation pre-payment for some specific customers who tend to trigger some number of no-shown.. BTW, is there any ready made solution for that? If not, is this somehow achievable by filters add/on actions on the WP side?
4. This way or another simply wondering why you decide to make WooCommerce vs. On-site as the "alternative" instead of the optional scenario. Is this somehow possible on your side to reconsider this rule? Other on-line payment options coexists... Switching to the WooCommerce payment unfortunately also eliminates the Appointment summary screen with buttons for adding the event to the calendars (Google / Outlook / Apple, Yahoo).. as well as the consistent summary of the booking as just made.
Unfortunately, currently, this feature is not built-in in Amelia. When WooCommerce is enabled all other payment methods are turned of since WooCommerce contains all them and this can not be altered I'm afraid.
As for your other questions I'm afraid that we didn't quite get what you want to achieve or what you are asking us exactly? Can you explain to us in a little more detail, and send us a couple of screenshots?
Also in general when you have several questions or issues please in te future open a new ticket, and we will help you there. In that way, issues and questions which are related to different subjects will be in separate tickets so other customers or our support agents can find them easily. Our policy is to have one issue or question per ticket because of the reasons that are described already.
Seems that parallel coexistence of the "on-site" payment & "WooCommerce" is impossible. Is this truly the case?
Turning on the "WooCommerce" disables the "on-site". Could you explain why is this so?
Hello Mariusz,
Thank you for reaching out to us.
Yes, that is correct. Once you enable the WooCommerce service option, other payment methods will be disabled since WooCommerce supports the same payment methods. They have something called cash on delivery or similar if they change the title but this the same as our on sit option and for that reason all other payment are turned oof once you enable WooCommerce.
Hope this explains it.
Should you have any further inquiries, we kindly request that you open separate tickets for each question and we will gladly help you there.
We wish you all the best.
Have a nice day.
Kind Regards,
Marko Davidovic
[email protected]
Rate my support
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
Hi Marko,
Well, this is not a perfect solution as there is a major difference in the payment processing flow.
1. The basic scenario should be (for probably lot of cases), the on-site payment. That is then nice, fast, easy and the appointment is then quickly confirmed so the UX is very smooth..
2. In some cases we wish to have the "reservation fee" to be taken on the booking process. Then it is OK to switch either to the Order Processing of the the WooCommerce cart. Unfortunately, the purchaser data are not copied from the reservation.. Is there potentially some filter to do so? Anyway, then the UX is bit worse (as more steps needed), but it is as it is..
3. There should be some options to force the reservation pre-payment for some specific customers who tend to trigger some number of no-shown.. BTW, is there any ready made solution for that? If not, is this somehow achievable by filters add/on actions on the WP side?
4. This way or another simply wondering why you decide to make WooCommerce vs. On-site as the "alternative" instead of the optional scenario. Is this somehow possible on your side to reconsider this rule? Other on-line payment options coexists... Switching to the WooCommerce payment unfortunately also eliminates the Appointment summary screen with buttons for adding the event to the calendars (Google / Outlook / Apple, Yahoo).. as well as the consistent summary of the booking as just made.
Best,
Mariusz
Hello Mariusz,
Unfortunately, currently, this feature is not built-in in Amelia. When WooCommerce is enabled all other payment methods are turned of since WooCommerce contains all them and this can not be altered I'm afraid.
As for your other questions I'm afraid that we didn't quite get what you want to achieve or what you are asking us exactly? Can you explain to us in a little more detail, and send us a couple of screenshots?
Also in general when you have several questions or issues please in te future open a new ticket, and we will help you there. In that way, issues and questions which are related to different subjects will be in separate tickets so other customers or our support agents can find them easily. Our policy is to have one issue or question per ticket because of the reasons that are described already.
Thank you for understanding.
Looking forward to your reply.
Kind Regards,
Marko Davidovic
[email protected]
Rate my support
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