PrestaShop B2B Readiness: Wholesale Roadmap

A trade buyer wants a price without VAT, an account with terms and a quote, and a consumer shop answers none of that. The Presta Shop B2B & Wholesale Readiness Audit walks that buyer's path through your store, from registration to VAT and payment terms, and returns a PDF plan of what to fix and in what order.

Selling to businesses is not selling to consumers, and most Presta Shop stores are missing the pieces trade buyers treat as basic: a wholesale tier, ex-VAT display for logged-in trade accounts, a VAT number captured and validated, net terms, a quote route, a minimum order. This audit walks the whole trade path on your store and records which of those it can already do natively, which need a module and which need custom work, then returns a roadmap ordered by what unlocks revenue fastest.

At 590 euro it is the step before you commit budget to a B2B build.

Findings are ranked before they are described, so the first thing you read is what to do first. Example document with invented data: your version names your store, your URLs and your modules.

Merchants moving into wholesale, mixed consumer and trade stores that keep hitting limits, and anyone whose business customers are asking for account pricing, net terms or a quote process the store cannot deliver. It also suits agencies wanting an expert second opinion before scoping a wholesale build. Readiness is assessed on Presta Shop 1.6, 1.7, 8 and 9, including multistore and multi-currency setups, on any theme.

We walk the real wholesale account journey the way a trade buyer would, and check each stage against what Presta Shop can actually deliver natively, with modules, or only with custom work. The path is:

• register as a business (company fields, VAT number capture)
• get the account approved (manual vetting, assignment to a customer group)
• see trade pricing (group price lists, ex-VAT display, quantity breaks)
• build an order (minimums, fast reorder, restricted catalogue visibility)
• request a quote or order on terms (quote workflow, net-30/60, purchase order, credit limit)
• check out with the right tax (intra-EU reverse charge, VAT validation, tax-by-group)

Every gap found is scored by business impact (does it block trade orders or merely inconvenience them) and effort (configuration vs module vs custom build), so the roadmap is ordered by what unlocks revenue fastest.

Typical readiness gaps read like this. Prices shown inclusive of VAT to logged-in trade customers who expect ex-VAT, which is a tax-display setting per customer group rather than a rebuild. No VAT number field at registration and no intra-EU reverse charge, so EU business orders are taxed wrongly. A single customer group with no wholesale tier, forcing manual discount codes. No quote route for buyers who will not check out at list price.

No minimum-order rule, so trade orders arrive below your handling threshold. An open catalogue where contract pricing should be login-gated. Each gap names who it blocks and the closing route, configuration, an existing module or custom work, with the trade-off stated.

You do not need a B2B theme. B2B is pricing, tax and workflow, not a skin, and a theme rebuild bought for this reason is wasted money. Where a customer group plus a price rule solves the requirement, we will not scope a module for it, and we do not assume you need the full enterprise stack when two targeted pieces close the real gaps.

The aim is the minimum sound footing that lets you take trade orders.

This is the assessment and the roadmap. The groups, price lists, terms, VAT handling and account flows are built separately, and that routes into Custom Module Development or into configuring B2B tooling you already own, quoted honestly either way. We do not review your consumer funnel here, so if you also sell B2C, pair this with the conversion audit. The full checklist, the readiness scoring model and a sample gap matrix live in the tabs below.

We build and maintain the open-code B2B tooling Presta Shop merchants run, including trade accounts, deferred payment terms and EU VAT validation, and we run a store ourselves, so the roadmap reflects what holds up in production. It also means we can tell you which requirements 1.7, 8 and 9 handle natively, which need a module, and where an update to a closed pricing or tax product could quietly reach your live prices, which is a risk worth costing before you buy anything.

See all Expert Services.

Symptom, the evidence it was drawn from, why it happens on Presta Shop, the fix, the effort and how to confirm it worked. Written so a developer can act without asking a follow-up question.

One ZIP installs on every Presta Shop release from 1.6 through the current 9.x, and runs on PHP 7.1 and…