B2B eCommerce — sales portals between companies

Your B2B eCommerce has to follow the commercial rules you already have

Price lists per customer, tiered discounts, minimum quantities and pack multiples, deferred payment and credit limits, accounts with several users and approvals: in B2B the shop is the easy part. The hard part is making commercial terms talk to the ERP without duplicating them.

  • Price lists, discounts and terms per customer managed in a single source of truth
  • Company accounts with roles, permissions and approval workflows
  • ERP and CRM integration for customer records, prices, availability and orders
Let's talk about your project

We reply with a first read of your case, not a price list.

Tell us about your B2B project

Number of customers on price lists, management system in use and commercial rules: we start from here.

We will get back to you to understand context, priorities and the best way to intervene.

PrestaShop Expert ★★★Sylius Professional Solution PartnerSylius Solution PartnerSince 2011100+ projectsBased in Catania, Sicily

Do you recognise yourself in any of these situations?

These are the situations we hear most often from companies that sell to other companies. They are not design problems: they are rule problems.

  • Each of your customers has their own price list and terms, and today those rules live in the ERP and in your agents' heads: the site cannot show the right price to the right person.
  • Reorders still arrive by email, WhatsApp or phone with product codes typed by hand, and the back office re-keys them into the ERP, with the risk of errors on quantities and pack multiples.
  • The person buying from you is not one person: someone prepares the order, someone approves it and someone handles accounting, but the site allows one account per company, so the customer's internal process does not fit.
  • Your sales team fears that eCommerce will take their customers away, so the portal is not promoted and remains a duplicate of the paper catalogue instead of a tool that frees up the agents' time.

What you get from a B2B portal designed around your processes

Commercial terms stay consistent

  • We define which system is the authoritative source of the price.
  • Price lists, discounts and tiers are not duplicated by hand.
  • The customer sees online the same price the agent quotes.

The customer's purchasing process fits in

  • Several users for the same company, with distinct roles.
  • Permissions matrix: who sees prices, who orders, who approves.
  • Carts waiting for approval and notifications to approvers.

Reordering no longer goes through the back office

  • Search by SKU, manufacturer code and internal reference.
  • Quick order from a table, a file or a previous order.
  • Recurring lists, document history and shipment status.

What really changes in a B2B project

A B2B eCommerce is not a B2C shop behind a login. These are the constraints that change the architecture of the project, and they are also the questions we answer before writing a line of code.

Price is not a product attribute

In B2C the price sits on the product page. In B2B it depends on contract, customer group, quantity, currency, market and agreed promotions, and it may be shown net or gross depending on the profile. You need to decide where it is calculated, platform or ERP, and what happens when the two systems disagree.

Quantities, multiples and units of measure

Cartons, pallets, minimum orders, pack multiples, products sold by weight or by linear metre. A cart that accepts 'quantity 7' when the product is sold in multiples of 6 causes disputes in the warehouse: the rules have to be enforced in the cart, not explained in a note.

Technical catalogue and search by code

People reordering do not browse categories: they search for a code. Search must handle SKUs, manufacturer codes, the customer's internal reference, alternative codes and typos. For spare parts and components you need compatibility (machine, model, year) to avoid wrong orders and returns.

Quotes and negotiation

In many sectors the order does not start from the cart but from a request for quotation: configuration, quantities, lead times. The portal must track the request, allow the sales reply and turn the approved quote into an order without re-entering anything.

Deferred payment, credit limits and accounting blocks

Bank transfer at 30/60/90 days, RiBa (Italian bank collection), available credit limit, customers blocked for unpaid invoices. This information lives in the ERP and the portal has to read it to decide whether an order can be confirmed: the platform applies the rule, it does not invent it.

The role of the sales network

The agent must not be bypassed: they can order on the customer's behalf, see the history of their own portfolio and be credited for orders their customers place online. When the commission is protected, adopting the portal stops being a political problem.

Recommended platform for complex B2B

Sylius, when commercial rules call for a custom architecture

For B2B portals with articulated sales processes and deep integrations with ERP and CRM, we recommend Sylius, an open source platform built on Symfony. We are a Sylius Professional Solution Partner.

Discover the Sylius agency

What the project can include

The scope is defined together: these are the components that recur in B2B projects, not a package to buy as a whole.

Analysis and set-up

  • Map of existing commercial rules: price lists, discounts, terms and their exceptions
  • Roles and permissions matrix for company accounts
  • Definition of the authoritative source for prices, availability and customer records
  • Analysis of the current order flow, from informal channels to entry in the ERP

Private area and accounts

  • Registration with company validation and account status
  • Several users per organisation with distinct roles
  • Cart approval workflow with notifications
  • Order history, downloadable documents and multiple delivery addresses

Catalogue and ordering

  • Search by SKU, manufacturer code and customer reference
  • Technical filters on normalised attributes and product pages with documentation
  • Quick order from a table, a file upload or a previous order
  • Management of minimums, multiples, units of measure and shipping thresholds
  • Quote request and conversion of the quote into an order

Integrations and continuity

  • ERP/CRM integration for customer records, price lists, stock, orders and documents
  • Handling of sync errors with searchable logs
  • Tools for the sales network: ordering on the customer's behalf and portfolio view
  • Ongoing support after launch, with agreed priorities

Are we a good fit?

It is a good fit if

  • You already have a commercial structure with differentiated price lists and want to take it online without simplifying it
  • You use an ERP or management system that must remain the source of data
  • Your customers reorder often and today they do it by email or phone
  • You have a sales network to involve, not to replace

It probably isn't for you if

  • You are looking for a showcase online catalogue, with no prices or orders
  • You want to start without touching the management system and without any data integration
  • Your commercial rules are not formalised and nobody in the company can decide them
  • Your only selection criterion is the lowest quote

Frequently asked questions about B2B eCommerce

Yes, and it is the norm in B2B projects. You can manage price lists by group, individual prices, percentage discounts, quantity tiers and terms by category or brand. The real question is not whether it can be done, but where the price is calculated: if the ERP is the source, the platform reads and applies it; if the platform is the source, the ERP has to adapt. Deciding this first avoids years of misalignment.

Not necessarily, but it almost always pays off. Without integration, someone in the company has to maintain customer records, price lists and stock by hand in two systems, and over time the two drift apart. You can start with a partial sync (for example products and orders only) and extend it later, as long as that is a decision and not a postponement.

It depends on how you design it. If the portal handles repeat orders and access to documents and history, the agent gets time back for the advisory side of the job. For it to work, the agent must be credited for the online orders of their customers and be able to order on their behalf: these are project requirements, not details.

Yes. You can do it with two separate stores or with a single store that changes behaviour according to the user's profile. The choice depends on how far catalogue, prices, taxes and communication diverge: when the differences are many, two distinct stores cost less to maintain than a single store full of exceptions.

Yes, and it is one of the platforms we have worked on the longest: we are a PrestaShop Expert ★★★ agency. On price lists, multi-user accounts, approvals and ERP integrations, most of the work is custom development, not installing modules. When the requirements point to another platform, we tell you before, not after.

It depends almost entirely on the integrations and on the number of commercial rules to reproduce, not on the number of pages. The phase people underestimate most is normalising catalogue data: if codes, attributes and units of measure are not consistent in your management system, the time goes there. After the initial analysis we give you timings and phases in writing.

Have complex commercial rules to bring online?

Tell us how selling works today: first we understand the process, then we assess what makes sense to digitise and in what order.

No commitment: first we work out whether the project makes sense.

Let's talk about your B2B project

Management system in use, number of customers on price lists, type of commercial terms and how orders arrive today: this is enough for a first assessment.

We will get back to you to understand context, priorities and the best way to intervene.