Decide who gets to see your wholesale prices — new accounts stay inactive until someone at your shop approves them.
Meta description (149 chars): Hold new PrestaShop accounts until an administrator approves them. Both sides are told by e-mail, no account reaches your prices first. Free MIT module.
A B2B shop shows different prices to different customers, and often hides them from the public entirely. An account created in ten seconds by anyone with an e-mail address defeats that:
- Prices stay with your customers — a competitor cannot register and read your price list
- Someone checks the company first — a VAT number, an order history, a phone call
- The customer knows what is happening — a message on screen and an e-mail, not silence
- No account slips through — verification happens at registration, not at the first order
When someone registers, the module deactivates the account, logs the visitor back out and sends them to the sign-in page with a message explaining that the account is waiting for approval. Your shop gets an e-mail with the details. The moment an administrator activates the account in Customers, the customer receives an e-mail with a link to sign in.
- Nothing to remember — approval is the usual "Enable" switch on the customer, no separate screen
- Both sides are told — a notice to the shop at registration, an invitation to the customer at approval
- One e-mail per account — editing an already active customer does not send the invitation again
- Own table for pending accounts — nothing is added to PrestaShop's
customertable - One switch — turn verification off and registration goes back to normal
With Only company accounts on, the registration form gets an account type choice (private person
or company). A company account requires the company name and a tax number, saved in the customer's
company and siret: a Polish NIP is checked by its checksum, an EU VAT number in VIES when
m4p_viesintegration is enabled (an unavailable VIES does not block registration). Only company
accounts are held. Pending accounts are listed in Customers → Accounts to approve:
Approve activates the account and assigns the group picked in its row (preselected with Group
after approval, or "Do not change the group"); Reject activates it as a regular account. Both
are form buttons. The customer gets an e-mail either way: "activated" for a held account, "price list
updated" when approval assigns a group to an active account, otherwise "company account approved". Switching Enable on for a pending
account in Customers also counts as approval; other edits of a pending account leave it in the queue.
With Account active before approval on, a company account is not held: the customer stays signed in, goes from the registration page to the home page and shops at the default customer group's prices. The account waits in Accounts to approve, and the shop gets the usual e-mail. Approve assigns the group and sends the "price list updated" e-mail; Reject leaves it a regular account.
A signed-in customer sees a one-time notice at the top of the home page content: after registering a
company account with Account active before approval on, and after approval assigns a group. The home
page stays cacheable – a small script loads the notices from an uncached module controller and shows them
as a theme alert (.alert.alert-success.m4p-cv-notice, first in #wrapper > .container, otherwise in
#notifications). Each notice is removed once shown.
The module does not reject anyone by itself. It stops the account and tells you; the decision stays with a person.
| PrestaShop | 1.7.6 – 9.x |
| PHP | 7.2.5+ |
| Requirements | a working shop e-mail configuration |
| Optional | m4p_viesintegration for VIES checks of EU VAT numbers; without it only the Polish NIP checksum is verified |
| Multistore | Settings and pending accounts are shared across shops |
| Themes | Messages use the theme's standard notifications and alert classes |
The module performs no core overrides. It creates two tables, m4p_pending_verification and
m4p_customerverify_notice, and one back-office tab, and removes them on uninstall.
- Upload and install the module from Modules → Module Manager.
- Open the module configuration and set the address for notifications, or leave it empty to use the shop e-mail.
- Register a test account in the front office — it should stay inactive and you should get an e-mail.
- Activate that customer in Customers and check that the invitation arrives.
| Setting | Description |
|---|---|
| Company account verification | Turns verification on. Off means registration works as usual. |
| Only company accounts | Adds the account type choice with company name and tax number, and holds only company accounts. |
| Account active before approval | On: the account works right after registering with the default customer group; approval only changes the group. Off: the account stays inactive until approved. |
| Group after approval | Added to the customer and set as the default group on approval; the queue preselects it in each row. |
| Only the group after approval | On: the approved account keeps only that group, so prices and a full-page cache keyed on the customer's group follow it. Off: the group is added next to the existing ones. |
| Notification e-mail | Where the notice about a new account is sent. Empty means the shop e-mail. |
How do I approve an account? In Customers, open the account and switch Enable on. That is the whole workflow — the module watches that change and sends the invitation.
What does the customer see right after registering? A message saying the account is waiting for approval. They are signed out, because the account is not active yet. With Account active before approval on, they stay signed in and see a notice on the home page that the company account request was received.
Does an existing customer get the e-mail again when I edit their details? No. The invitation is sent once, when an account that was waiting for approval becomes active.
What happens to accounts created before the module was installed? Nothing — they are untouched and stay active. Verification applies to registrations from now on.
What happens to pending accounts when I uninstall the module? The tables are dropped. The accounts stay in PrestaShop, inactive, and you activate them by hand.
Keywords: PrestaShop account approval, B2B registration, wholesale customer verification, manual account activation, hide prices from public.
MIT — see LICENSE. Free to use commercially, fork and modify; keep the copyright notice.
Bug reports and pull requests are welcome — see CONTRIBUTING.md. For security issues, follow SECURITY.md instead of opening a public issue.
Built by Nice Code — we build B2B stores on PrestaShop.
© Nice Code sp. z o.o. (Modules4Presta) — released under the MIT license.