Open your PrestaShop shop to professionals

The visitor chooses their path: “I am an individual” or “I am a business”, two buttons added under the login form, each one leading to its own page (/compte-particulier and /compte-professionnel). You can close registration for individuals, show a CMS presentation page before the pro registration and have professionals accept their own terms of sale.

Each form is built field by field: text, text area, switch, single or multiple choice list, radio buttons, checkboxes, file upload (a certificate of incorporation, for example), information message and date. Each field has its label in each language and can be required. The first address can be asked for at registration.

• SIRET: 14 digits and check key verified locally, then, if you turn it on, existence of the establishment checked with the INSEE Sirene API, with your own access key.
• Intra-community VAT number: format checked while typing according to the country, then, if you turn it on, verified with VIES, the European Commission service.
• A “Subject to VAT?” question can come before the field.

Each field can be shown or not, and can be required. A pro customer whose SIRET or VAT number is missing can be reminded by email: you set the gap between two reminders and their maximum number, then have the tokenised address shown in the back office called once a day (cron task at your host or native scheduled tasks module). A customer who completes their details leaves the queue.

Three zones, each set separately: your shop's country, the European Union, the rest of the world. For each one, you choose the pro customer's groups and default group; your shop's tax rules then apply the right regime. The module sets no rate.

Your shop has no pro groups yet? The module creates the three groups on request, and aligns their access rights (categories, carriers, payment and other modules) with those of the default customer group, without ever removing a right. Without this alignment, a customer placed in a new PrestaShop group finds an empty catalogue.

Your company accounts created before the module can be brought in in one click: they receive the groups of their zone on top of those they already have. A customer without an address, so without a known country, is never moved.

Turn on manual approval: a pro account is created inactive, the customer is told that their request is being reviewed, and you find the pending accounts in the back office. One click activates the account and the customer receives an email. You also choose the emails sent to the customer and to the merchant (account creation and update) and the employees notified.

• “Catalog reserved for businesses”: prices are hidden from visitors, through the native “Show prices” setting of the Visitor and Guest groups. Instead of the price, the theme shows “Sign in to see prices”, with the links to log in and to open a pro account.
• “Also hide the catalog from visitors”: categories and products are closed to visitors through native category access (home included, root excepted). They lead to the native “access denied” page (403), completed by the “Reserved for businesses” block.

Everything is put back as before when you turn these options off or uninstall the module.

Google reCAPTCHA (v2 or v3, with an adjustable threshold) or Cloudflare Turnstile, with your own keys. The provider's script only loads on the module's two registration pages, and only when the protection is on.

The files sent by your customers (certificates, supporting documents) are stored outside the module folder, in var/lnk_b2baccount/, which a module update does not touch. They are never served directly: only the back office opens them, for a logged-in employee. Under Apache, an .htaccess refuses all access. Nginx ignores .htaccess files: add the block given in the FAQ to your server configuration.

On uninstall, the fields, the values entered by your customers, their attachments and the reminders are kept by default. Deleting them is asked for in two steps, under “Advanced”.

Figures measured on the delivered module, gzip-compressed (level 9). The form script: 2.4 KB (2,378 bytes), loaded only on the module's two registration pages. The stylesheet: 1.6 KB (1,551 bytes), loaded only on the login and registration pages (and on the identity, addresses and order pages, where the pro fields are shown). Nothing on the home page, categories or product pages. The four renderings of the theme contract (instead of the price, reserved page, account status, registration link) add no stylesheet and no script of the module: the theme styles them.

A single settings page, in tabs, on the common skin of the LNK modules: at most twelve visible settings per screen, rare settings folded under “Advanced”. The form fields are translated in each language of the shop. The module page and the forms read from right to left in Arabic.

Theme contract lnk.b2b.account/1, designed for the LNK B2B theme and usable by any theme that calls its hooks:

• displayLnkB2bPriceLogin instead of the price (product card, list view, product page);
• displayLnkB2bRestricted in the “access denied” page;
• displayLnkB2bStatus: “Business account active” or “legal information to complete”, nothing for a visitor, compatible with page caching;
• {widget name='lnk_b2baccount' mode='link'}: the “Open a business account” link.

Without these hooks, PrestaShop keeps its native behaviour. Templates can be overridden in the theme.

Forms, reminders and settings per shop; the module page always shows the scope of what you save. A new shop receives the forms, a deleted shop is cleaned up. The reserved catalogue settings are common to all shops, like PrestaShop's customer groups.

Each version is verified by a real installation: PrestaShop 1.7.8 and 8.1 for the 2.1.N package, PrestaShop 9.0 for the 2.9.N package. The tests cover installation, display, the back office and uninstallation.