[Picflick]

Hi,
Question 1 – Please explain the order and triggers of emails that will be sent to the vendor when they purchase a subscription. I see many types listed in the WooCommerce >> Emails tab and am not sure which get triggered when? (new vendor order, new vendor account, new vendor subscription?!?!?!) Please explain for each step in the sign up journey.
Question 2 – Have you fixed the error that administrators will need to approve vendors before their status is set as ‘vendor’. You supplied me with custom code (see below) for the vendor’s status to be set to ‘pending vendor’ first.
Question 3 – I used Loco Translate to amend all ‘vendor’ wording to ‘photographer’. Will this interfere with the back-end coding? Example: this code that you previously supplied:

/*Add functionality so that the admin needs to approve a vendor after subscribing*/
add_action('mvx_vendor_purchased_subscription', 'set_role_pending');
function set_role_pending($user_id){
	$user = new WP_User($user_id);
	$user->set_role('dc_pending_vendor');
	$user_pass = $user->user_pass;
	$email = WC()->mailer()->emails['WC_Email_Vendor_New_Account'];
	$email->trigger($user_id, $user_pass, false);
	$email_admin = WC()->mailer()->emails['WC_Email_Admin_New_Vendor_Account'];
	$email_admin->trigger($user_id);
}

Do I need to change the set_role to ‘dc_pending_photographer’, email titles, etc.?
Thanks, PicFlick

Attachments:

1. 

   Emails.jpg
   

2. 

   Emails-1.jpg
   

[Sangita Support Squad]

Hello There, Thanks for getting in touch with us. Our replies are inline with your queries –

Question 1 – Please explain the order and triggers of emails that will be sent to the vendor when they purchase a subscription. I see many types listed in the WooCommerce >> Emails tab and am not sure which get triggered when? (new vendor order, new vendor account, new vendor subscription?!?!?!) Please explain for each step in the sign up journey.
>>In the default configuration of the membership module, when a vendor registers by subscribing to a membership plan, the following email notifications are sent:
To the admin:

New vendor account notification
New order notification

To the vendor:

Account creation confirmation
Order completion notification
New vendor subscription confirmation

This automated email process keeps both parties informed of the registration and subscription events(https://prnt.sc/sGXnQysw9vgK).

Question 2 – Have you fixed the error that administrators will need to approve vendors before their status is set as ‘vendor’. You supplied me with custom code (see below) for the vendor’s status to be set to ‘pending vendor’ first.
>>Let me clarify the standard process and your custom requirements:
Standard flow:

— Users register and subscribe to a membership package.
— Upon successful registration and order completion, they automatically become active vendors.
— If registration or order placement is incomplete, they remain as pending vendors..

Now as you wanted to implement a custom flow on your end that even after the successfull registration also the users will come as pending vendors hence we provided you with a custom code as per that.

Question 3 – I used Loco Translate to amend all ‘vendor’ wording to ‘photographer’. Will this interfere with the back-end coding?
>> The translations you’ve made don’t impact the underlying code. You can use the provided code as it is without any modifications to the backend.

If you need any further help, please don’t hesitate to ask.

[Picflick]

Thank you so much. I’ll come back if have more questions 🙂

[Sangita Support Squad]

Sure. If you need any further assistance from our end please do let us know.
Also,it would be really great if you can give us 5/5 review here:
https://wordpress.org/support/plugin/dc-woocommerce-multi-vendor/reviews/#new-post.
This would motivate the team further to do their job more efficiently.

[Picflick]

Hi,
Relating to Question 2 above… The flow you described contradicts with the functionality that is offered – see attached. In this image the toggle option describes the ability for Admins to evaluate sellers before. So surely they are not automatically approved as active vendors if ‘manual’ is selected?! Wouldnt they then be in the ‘pending vendor’ state until ‘approved’. Please explain.
Thank you

[Sangita Support Squad]

Hi @Picflick, Let me walk you through the default vendor registration flow in MultiVendorX.

In the free version of MultiVendorX, when a user registers through the vendor registration form, their approval depends on the “Approve Vendor” settings. If it’s set to “Automatically,” the user is immediately redirected to their vendor store upon form submission and is registered as a vendor. However, if the setting is “Manually,” the user will be listed as a pending vendor after submitting the form, and only after manual approval from the admin will they become a vendor.

For registrations with membership plans, once the user selects and purchases a plan, they are registered as a vendor. If they do not complete the registration process, they will appear as a pending vendor. Please note, membership plan registrations are not dependent on the “Approve Vendor” settings.

Please review the above flow on your end, and let us know if you have any further questions.

[Picflick]

Ah okay I see! So the standard ‘vendor registration’ is different to the ‘membership subscription’.
Confirming my understanding that…
1. if a user applies through vendor registration then the ‘Approve vendor’ settings will be applied.
2. if a user purchases a membership they are automatically approved to ‘vendor’ status.
Is this correct?
Thank you

[Sangita Support Squad]

@Picflick, If the membership module is enabled, users will automatically become vendors upon registration. If the membership module is not enabled, the “Approve vendor” settings will apply instead.

[Picflick]

Noted. Thank you!!!!

[Sangita Support Squad]

You’re welcome! If you need any further assistance, please do let us know.

[Sangita Support Squad]

We haven’t received a response from you in a while, so we assume your query has been resolved. We will be closing this thread, but if you need any further assistance in the future, please don’t hesitate to create a new support ticket.

[Author]

Posts