PrestaShop B2B - implementation, integrations, support
A PrestaShop B2B platform that talks to your ERP
I build and maintain online wholesale stores and B2B ordering portals: customer-specific price lists, credit limits, quick ordering by SKU and documents that flow into your ERP on their own. I have been working with PrestaShop for over 16 years and I personally run the whole project, from process analysis to support after go-live.
- Integrations with ERP, accounting, e-invoicing, warehouse and carriers
- A new platform, or taking over and developing an existing PrestaShop wholesale store
- PrestaShop 1.7, 8 and 9, B2B and B2C on one installation
- 16+years with PrestaShop
- 400+completed projects
- 30+own PrestaShop modules
- 1 personfrom analysis to support, no middlemen
Before we start
A wholesale store is not a shop with a different price list
PrestaShop has a “B2B mode” switch in its customer settings. It adds company fields, allowed outstanding amount, maximum payment days and a customer risk rating. It is a good starting point, but not a wholesale platform: it will not pull price lists from your ERP, it will not block an order when the credit limit is exceeded and it will not let a sales rep place an order on behalf of a customer.
The difference between B2C and B2B is not the theme, it is the process. A trade buyer does not browse categories - they know what they need and want to order it in two minutes, at their price and on their terms. That is why every project starts with how an order is handled in your company today: who takes it, where it is retyped and how many times.
Platform features
What I build on PrestaShop for B2B sales
Not every wholesaler needs everything. Below are the features I implement most often - some from proven ready-made modules, some written for a specific process. Always as modules, without touching PrestaShop core files, so the platform can be updated for years.
- 01
Company accounts and permissions
- registration with a VAT number validated in VIES and company data prefilled
- support for local company registers where they offer an API
- new accounts approved by a sales rep before prices are shown
- several users per company with roles: buyer, approver, accounting
- branches and multiple delivery addresses under one customer
- 02
Prices and trade terms
- customer and group price lists synchronised with the ERP
- tiered, quantity and product-group discounts
- net prices by default, prices hidden from guests
- contract prices with validity dates and promotions for selected companies only
- several currencies and price lists for EU markets
- 03
Quick ordering
- quick order form by SKU or EAN, with suggestions
- cart import from a CSV or XLSX file
- one-click reorder and shopping lists
- minimum order quantities and pack multiples: unit, carton, pallet
- stock from several warehouses and a real delivery date per product
- 04
Quotes and sales reps
- request for quote straight from the cart, answered with an individual price
- PDF quote with an expiry date that the customer turns into an order
- sales rep panel: orders on behalf of a customer, view of their terms
- customers assigned to account managers, with notifications about their orders
- mobile app for field sales reps (Flutter, iOS and Android)
- 05
Payments and documents
- trade credit: limit, balance and a block on overdue payments
- bank transfer with 7, 14, 30 or 60-day terms depending on the customer
- invoices, credit notes and delivery notes downloadable in the account, straight from the ERP
- e-invoices issued by the ERP or an invoicing integration (Peppol, KSeF, Factur-X)
- online payments (Stripe, PayPal, Mollie, Adyen) for new customers
- 06
Catalogue and product data
- large catalogues with tens of thousands of SKUs and advanced filters
- datasheets, declarations, certificates and manuals on the product page
- replacements, accessories and related products driven by data, not manual work
- XML or CSV offer feed for partners and dropshippers
- data import from a PIM, from manufacturers and from supplier wholesalers
B2B and B2C on one installation
Already running a retail store and want to open a wholesale channel? PrestaShop Multistore lets you run a separate wholesale store on its own domain, with a different theme, prices and access rules, but on a shared catalogue, stock and integrations. One back office, one ERP, two sales channels.
Integrations
PrestaShop as part of your system, not another data island
In B2B the store is rarely the source of truth. Prices, stock and customer records live in the ERP, invoices in accounting and parcels with the carrier. My job is to make these systems exchange data on their own, so your team stops retyping orders from e-mails into the ERP.
- ERP and order managementprices, stock, customers, orders
- Accounting and e-invoicinginvoices, credit notes, balances
- Warehouse and WMSreservations, picking, dispatch
- Carriers and palletslabels, tracking, pickups
job queue
sync logs
- Paymentsonline, deferred, limits
- Marketplaces and feedsAmazon, TikTok Shop, Google
- CRM and marketingleads, segments, automation
- Company dataVIES, company registers
ERP and order management
- SAP Business One
- Microsoft Dynamics 365 Business Central
- Odoo
- Sage
- Exact
- Comarch ERP
- enova365
- Subiekt nexo
Invoicing and accounting
- Xero
- QuickBooks
- wFirma
- Fakturownia
- Peppol
- KSeF
Multichannel sales
- BaseLinker
- Amazon
- TikTok Shop
- Google Merchant Center
- eBay
Logistics
- DHL
- DPD
- GLS
- UPS
- FedEx
- InPost
- pallet carriers
- fulfilment operators
Payments
- Stripe
- PayPal
- Mollie
- Adyen
- Przelewy24
Data, CRM and marketing
- VIES
- HubSpot
- Pipedrive
- Salesforce
- Mailchimp
These are the systems PrestaShop B2B platforms are most often connected to. Don’t see yours? If it has an API (REST, SOAP), database access, XML, CSV or EDI file exchange, or even an FTP export, it can be connected. I wrote and maintain, among others, the PrestaShop - wFirma integration, the TikTok Shop module, the InPost Merchant integration and stock synchronisation from six dropshipping wholesalers for one of my clients.
From my workshop
This is what the integrations I write look like
Real screens from the PrestaShop back office (Polish-language installations), not mock-ups. These are modules I designed and maintain myself: configuration in the panel, automation on order status, a sync queue and connection diagnostics. I build B2B integrations with ERP and warehouse systems the same way.
Click a screen to enlarge it. All my modules: PrestaShop modules →
How I work
Integrations that don't need rescuing later
Most wholesalers who come to me already have some integration. It works until someone adds a new warehouse, upgrades the ERP or the office internet goes down. Then orders disappear and stock levels drift for days. That is why I design integrations around a few rules I stick to regardless of the budget.
14:02:11 order #10482 → queue 14:02:12 ERP timeout retry 1/5 14:03:12 ERP SO/1182/2026 created 14:03:13 stock: 38 SKUs updated 14:15:00 group B prices: 312 updated 14:20:41 INV/2026/10/0931 e-invoice accepted 14:20:42 invoice → customer account ok
One source of truth for every piece of data
At the start we agree which system owns what: prices and stock in the ERP, descriptions and images in PrestaShop, customers where the sales team works. Without this, two integrations overwrite each other and nobody knows which price is real.
A queue instead of waiting for the ERP
The order goes into a queue and the customer sees the confirmation immediately. If the ERP on the office server happens to be off, nothing is lost - the job waits and runs when the system is back.
Incremental synchronisation
I send only what has changed since the last run. A full sync of 40 thousand SKUs every 15 minutes loads the server and the ERP, changes to 300 prices do not.
No duplicate orders
Every operation has its own identifier, so a retry after a network error will not create a second document in the ERP. A detail everyone remembers after shipping a customer two pallets instead of one.
Logs a human can read
A panel with the data exchange history and an e-mail alert when something fails. You see which order, when and why, instead of hearing it from the customer.
Code ready for the next versions
Modules and hooks instead of core modifications. Thanks to that, migrating from PrestaShop 8 to 9 does not mean rewriting the integrations - and support for version 8 ends in 2027.
Typical projects
Where a B2B project usually starts
- Starting point
The wholesaler takes orders by e-mail and phone, and sales staff retype them into the ERP.
What we buildAn ordering portal with customer price lists from the ERP. The order lands in the system as a document, without retyping, and the customer sees their invoices and balance.
- Starting point
A manufacturer sells through a distributor network and sends them price lists in Excel.
What we buildA partner zone: catalogue with technical documentation, contract prices, ordering and an XML offer feed for partner stores.
- Starting point
A retail PrestaShop store wants to start selling to businesses.
What we buildMultistore with a separate wholesale store on the same catalogue and stock, registration with VAT number and approval, net prices.
- Starting point
A wholesale store runs on PrestaShop 1.6 or 1.7 with modules nobody maintains any more.
What we buildAudit, migration plan to PrestaShop 9 keeping accounts, price lists and order history, integrations rewritten as maintained code.
Who runs the project
Experience you can't copy from the documentation
My name is Radosław Balcerzak. For over 16 years I have been designing, developing and maintaining PrestaShop stores, and in that time I have completed over 400 projects and written over 30 of my own modules. I have taken clients through successive PrestaShop versions up to 9, with their data, themes and integrations.
In B2B this experience counts twice. I know where PrestaShop is strong and where it needs extending, how a catalogue of tens of thousands of SKUs behaves and what happens to an integration when the ERP in the client’s office is switched off overnight. Besides PrestaShop I work with Symfony, which versions 8 and 9 are built on, as well as Sylius and Flutter - so I build integrations, panels and mobile apps for sales reps myself, without subcontractors.
You work directly with me: I talk to your sales team, write the code and take responsibility for the result. I work with business owners, agencies and IT departments, including projects for clients across the EU.
Radosław Balcerzak, Senior Web Developer
More about my experience →
Projects I work on
Selected stores and platforms I develop and maintain: integrations with suppliers and accounting, cross-border sales, custom modules.
malakoala.pl
Automatic stock synchronisation from six dropshipping wholesalers, invoices issued via the wFirma integration and product descriptions generated through an AI API.
See the project →
erea.be
A store operating on the Belgian market. Ongoing development support: maintenance, module development and changes to existing plugins.
See the project →
designlight.pl
LED lighting systems. Ongoing development work, custom modules, theme development, updates and security.
See the project →
How a B2B platform implementation works
No months of analysis that end up in a drawer. The platform starts earning after the first stage, and we add further features based on how your customers actually use it.
Sales process workshop
We talk to the people who take orders today. I write down where prices come from and how ordering, payment and documents work.
Specification and data map
You get a scope description, a data exchange map with the ERP and other systems, and a quote split into stages.
Implementation in stages
Core first: accounts, price lists, ordering and the ERP integration. Additional features in the next stages, without delaying the launch.
Tests on real data
We test on a copy with your products, customers and prices, then with a few trusted customers before the full launch.
Launch and customer onboarding
Account import, invitations for customers, instructions for the sales team. I am on hand in the first weeks.
Support and development
Updates, keeping integrations working when the ERP or carriers change, and new features when the need arises.
After launch
B2B platform support and development
A B2B platform grows with the company: new customers, warehouses, carriers and ERP changes keep coming. I also take over existing PrestaShop wholesale stores from other contractors - I start with an audit of the code and integrations to know where we stand.
Platform implementation
quoted in stagesafter the workshop and specification, split into core and additional features
Ongoing care and development
from €33 net / hwith ongoing cooperation, for the time actually worked. PrestaShop support →
One-off job
€37 net / ha fix, integration audit or consultation. PrestaShop support →
I can also host the platform on a server prepared for PrestaShop - PrestaShop hosting. Rates are shown in EUR, converted from PLN at the NBP mid rate. The start date is agreed after I review the project.
When PrestaShop is not the best choice for B2B
I say this on the first call, so I can say it here too. If you sell a few dozen products to a dozen regular customers, a B2B platform may be overkill - sometimes an order form and an integration with your invoicing software are enough. If, on the other hand, sales require a production configurator, multi-stage negotiations and capacity planning, a dedicated application, for example on Symfony or Sylius, will serve you better. In both cases I will help you choose a solution, even if it is not PrestaShop.
PrestaShop is a very good choice when you have from several hundred to tens of thousands of products, customers with different terms and a need to integrate with an ERP, and you want to own the code, with no platform subscription and the freedom to develop it for years.
Frequently asked questions about PrestaShop B2B platforms
Is PrestaShop suitable for a B2B platform?
Yes, as long as we treat it as a base to extend rather than a ready-made wholesale store. Built-in B2B mode, customer groups and specific prices cover the basics. ERP price lists, credit limits, quick ordering, multi-user accounts and integrations are added as modules. The result is a platform tailored to your process, with no subscription and code you own.
Can you integrate PrestaShop with my ERP, for example SAP Business One, Dynamics or Odoo?
Most likely yes. The approach depends on the system: the vendor API or SDK, direct database access or file exchange. Before I quote, I check your ERP version, the available data exchange methods and which data should flow in which direction.
How much does a PrestaShop B2B platform cost?
It depends on the number of integrations and features that must work from day one. That is why I quote in stages: first the core (accounts, price lists, ordering, ERP integration), then additional features. After the workshop you get a specification and a quote for each stage. Ongoing care and development after launch start from €33 net per hour.
How long does implementation take?
The first stage with the ERP integration usually takes from a few to a dozen or so weeks, depending on scope and how quickly we get access to the systems and test data. I give a specific schedule in the specification, after the workshop.
Can I run a B2C store and a B2B wholesale store on one installation?
Yes. Most often I do it with PrestaShop Multistore: two domains, separate themes, prices and access rules, but a shared catalogue, stock and integrations. The alternative is one store where a logged-in business customer sees their own price list and terms.
Will invoices from the platform go through e-invoicing (Peppol, KSeF, Factur-X)?
Yes, if invoices are issued by a system connected to the e-invoicing network - usually your ERP or invoicing software. The platform passes the order to that system, it issues the invoice, and the finished document returns to the customer account. I design it so that PrestaShop does not issue its own invoices in parallel.
Will you take over an existing PrestaShop wholesale store from another company?
Yes, it is a common start of cooperation. I begin with an audit: PrestaShop and PHP versions, modules, overrides, integrations and their logs. You get a list of risks and a plan of what to fix first, and then I take over care and development.
Can PrestaShop handle a large catalogue and many customers?
Yes, if it is configured well. With tens of thousands of SKUs and individual prices, the server, cache, database indexes, a fast search engine and incremental synchronisation instead of full imports all matter. These are things I plan from the start of the project, not after the first customer complaints.
Tell me about your B2B sales
Write how you take orders from businesses today, which ERP you use and what slows you down the most. I will reply with questions or a proposal for a call. If you already have a PrestaShop platform, include its address.
- You talk directly to the developer who will run the project
- You get a concrete answer on what can be done and in what order
- No obligation and no hard selling
Prefer to call? +48 609 880 234
B2B platform enquiry
The start date and timeline are agreed after I review the project.
The controller of the data provided in the form is balcerzak.it Radosław Balcerzak, ul. Słoneczna 11B, Rosko, Poland. Data is processed to answer your enquiry and possibly prepare an offer (Art. 6(1)(b) and (f) GDPR). Details, including how long enquiries are kept, in the Privacy Policy.