Let vendors define their password during registration

An extension for Multi-Vendor that lets a vendor applicant choose their own password right in the registration form, instead of waiting for a message with a password generated by the store.

The first minutes after registration shape how a new partner remembers the start of your relationship. In stock Multi-Vendor the vendor fills in a long form, submits it and is left empty-handed, because the panel password only arrives by e-mail. If mail delivery lags or a spam filter finds the message suspicious, contact breaks off exactly when the partner was most committed. The Vendor Password at Registration add-on closes that gap: the vendor types the password themselves, and the account is created with it straight away.

Key Features

- A new profile field type called Password, available on the standard type list next to text fields and select lists.

- A field that masks the characters typed in the vendor registration form, exactly the way a vendor expects it to behave.

- The password entered by the applicant goes straight into the administrator account of the new company, with no involvement of the store team.

- Once used, the password is replaced with a string defined by the administrator, so it never stays in the database in readable form.

- Support for several registration forms at once, since one configuration can point at multiple password fields.

- Compatibility with the vendor plan selector, confirmed on Multi-Vendor releases from 4.10.1 through 4.20.1.

Deployment takes a few minutes and needs no developer. The entire configuration fits in two fields: you point at the profile field the vendor will type the password into, and you set the text that takes its place once the account exists

Screenshot 1

You create the password field where you create every other vendor form field. A new entry called Password appears on the type list, and apart from choosing it, the configuration is no different from an ordinary text field, required status and form order included

Screenshot 2

This is what the vendor applicant sees. The password masks the characters typed, so it can be entered even with someone nearby, while the plan selector and the remaining fields work alongside it without any clash. That detail matters in practice, because the add-on shares its place in the form with the vendor plans mechanism

Screenshot 3

On the profile fields list the new field behaves like any other: you set its position in the form, the description the vendor sees and whether it is required. Outside the registration form the add-on hides it on purpose, so the password never surfaces in views where it serves no role

Screenshot 4

The application reaches the vendor list and waits for an administrator decision, while the company administrator account already holds the password chosen by the vendor. Once approved, the partner signs in immediately, with no hunt for a credentials message

Screenshot 5

The Vendor Password at Registration add-on removes one of the most common reasons for support tickets in the first minutes with a new partner. The vendor signs in right after registering, the password stays theirs alone, and the store no longer depends on mail deliverability.

Feel free to contact us and purchase the add-on!