PrestaShop is already a catalog, cart, and PDF invoice engine. The addons worth voting on in 2026 sit where EU B2B law and warehouse reality diverge from those three screens. Core can print a VAT number on an invoice without ever asking VIES whether the number is live. Reverse charge is not a native tax outcome. A customer can change their company identifier after the first order and break the ERP match. Payment-pending orders do not always reserve stock the way a B2B desk expects. Agencies have been listing these as project boilerplate for years; GitHub’s B2B foundations thread makes the same inventory of gaps explicit.

A useful PrestaShop addon draft is a back-office page with the cyan header and dark menu merchants already know — not a WordPress dashboard and not a Shopify admin. The first release should do one legal or stock job: VIES plus a reverse-charge mention, a proforma before payment, a warehouse transfer, a combination-level low-stock digest.

How to judge a module proposal

Name the PrestaShop version, the tax-address setting, and the order state that triggers the job. Say what will not ship: a full accounting suite, a replacement for native cart rules, or XML already handled by a local e-invoicing specialist. Then vote. DraftPlugins will not list a module on PrestaShop Addons until the community threshold is reached and a release exists.