Skip to content
Budget and decisions

How much does a B2B portal cost?

From $13,500 to $33,600 (€12,000–€30,000)excl. VAT for most B2B ordering portals, more for a multi-area platform: the ranges, what moves them, and how to build your budget.

By Damien Ladurelle · Updated · 7 min read

Contents
  1. Price ranges
  2. How a budget is built: an example
  3. What drives the price
  4. Costs after go-live
  5. When a custom portal is not the right choice
  6. How a B2B portal project works
In short

A custom B2B portal usually costs $13,500 to $20,200 (€12,000–€18,000)excl. VAT for an essential ordering portal, and $20,200 to $33,600 (€18,000–€30,000)excl. VAT once it connects to your ERP, with payments and invoices. A multi-area platform (customers, distributors, sales reps) is quoted individually, above $33,600 (€30,000)excl. VAT.

A B2B portal lets your business customers see their catalog, prices, orders and invoices, and order without picking up the phone or sending an email. Its price depends less on the number of pages than on the complexity of your commercial rules and the tools it has to connect to. Here are the ranges I work with, how they are built, and the costs to plan for afterward.

Price ranges

Amounts exclude VAT and cover a first version in production. The quote becomes fixed after the scoping phase.

Type of portal What it includes Indicative budget Timeline
Essential ordering portal Customer accounts, private catalog, customer-specific prices, ordering, history, back office $13,500 to $20,200 (€12,000–€18,000)excl. VAT 2 to 3 months
Connected portal The essential portal + ERP connection, online payment, PDF invoices and notes, dashboard $20,200 to $33,600 (€18,000–€30,000)excl. VAT 3 to 4 months
Multi-area platform Customer, distributor and sales rep areas, multiple languages, advanced rules, AI Custom quote, above $33,600 (€30,000)excl. VAT 3 to 6 months or more

For a range that fits your case, the estimator calculates a budget in one minute from the features you select.

How a budget is built: an example

My estimator starts from a base price, adds functional modules, then applies multipliers. An illustrative example for a B2B portal with a customer area, online payment and an ERP connection, used by more than 50 accounts:

Item Amount excl. VAT
Business app base €6,000
Accounts and roles €1,500
Customer area €2,500
Back office €2,000
Online payment €1,500
ERP connection €2,000
Data migration (customers, products, prices) €800
Subtotal €16,300
More than 50 users (×1.2) €19,560

Add premium design (×1.15) and the budget goes past $24,700 (€22,000)excl. VAT; add multiple languages (€1,000) for export, and so on. This calculation gives an order of magnitude: the fixed quote comes after scoping, once your pricing rules and your ERP have been reviewed.

What drives the price

  1. Pricing rules. One price per product is simple. Customer-specific price lists, discounts by family, volume pricing and time-limited promotions take more design and testing. See customer-specific pricing for B2B.
  2. The ERP connection. Often the most uncertain item: it all depends on the ERP, its API, and the direction of data (stock and prices to the portal, orders to the ERP).
  3. User types. A buyer, an approver, a sales rep ordering on behalf of a customer, a distributor managing its own resellers: each profile adds screens and permissions.
  4. Catalog size. A few hundred products display simply; tens of thousands of SKUs with variants need careful search and filters.
  5. Data migration. Customers, contacts, delivery addresses, order history: the older and more scattered, the longer it takes.

Costs after go-live

A custom portal is not billed per connected customer. Recurring costs are:

  • hosting: from a few tens to a few hundred euros a year depending on traffic;
  • usage-based third-party services: online payments, email sending, possibly AI. For example, Stripe lists for France 1.5% + €0.25 per payment with a standard European Economic Area card and €0.35 per SEPA Direct Debit (Stripe pricing, checked in October 2026, per transaction; rates vary by country);
  • maintenance and new features, as a fixed fee or by the hour, after the 3 months of included support.

To compare with an off-the-shelf B2B solution billed monthly, run the numbers over 3 to 5 years: the method is explained in the 3-year total cost of SaaS versus custom software.

When a custom portal is not the right choice

To be clear: a custom portal does not make sense for everyone.

  • Few business customers who order rarely: an order form or a structured email is enough.
  • The same prices and terms for everyone: the B2B module of an off-the-shelf e-commerce platform may do the job.
  • An ERP that already offers a decent customer portal: turn it on and configure it.
  • A budget below $13,500 (€12,000)excl. VAT for a real connected portal: it is better to start with a smaller scope than a rushed portal.

Custom work makes sense when your commercial rules are your competitive edge, when your teams spend hours re-entering orders, or when your customers expect key-account-level service.

How a B2B portal project works

  1. A 30-minute call to understand your customers, pricing rules and ERP.
  2. Scoping (1 to 2 weeks): first-version scope, pricing rules, ERP flows, fixed quote.
  3. Clickable mockups (1 to 3 weeks): a few trusted customers can test them.
  4. Development in batches: accounts and catalog first, then ordering, ERP connection and payment.
  5. Launch to pilot customers, then to everyone, with data migration and training for your teams.

Payment follows the same rhythm: a 50% deposit at the start, the balance according to the schedule in the quote. The source code and rights are transferred to you once paid in full. The client portal page describes the solution in detail, and the full terms are on the pricing page.

Frequently asked questions

Can a B2B portal handle different prices for each customer?

Yes, and that is the main reason to go custom. Price lists, discounts by product family, free shipping thresholds, payment terms: rules are pulled from your ERP or defined in the portal. Their complexity drives the budget, which is why they need to be listed during scoping.

Should a B2B portal offer online payment?

Not always. Many business customers pay on invoice at 30 or 60 days. Card or direct debit payment is useful for new customers, small orders or export. It is then added as a separate module.

How long does it take to launch a B2B portal?

Allow 2 to 3 months for an essential portal, and 3 to 6 months for a portal connected to your ERP with several user types. Launch can start with a group of pilot customers.

What are the costs after go-live?

Hosting (a few tens to a few hundred euros a year), third-party fees such as online payments, and maintenance. There is no license per connected customer: adding 200 customers to the portal does not change the bill.

Not sure about your project?

Let’s talk for 30 minutes: I’ll tell you honestly which option I would choose in your place.

Book a 30-minute call Version française