Service · Web development

Custom B2B e-commerce portal development.

A private webshop for business buyers, with customer-specific prices, volume tiers, credit limits and a deep integration with your ERP. Not a retail approach bolted onto a B2B flow, but a portal that fits how wholesalers, manufacturers and distributors actually sell.

Customer-specific pricesERP integrationPunchOutMulti-user accounts

B2B is not B2C with a login in front of it.

In B2C, an individual buys a product at a fixed price, pays with iDEAL or a credit card, and the transaction is done. In B2B, an organisation buys, sometimes through several buyers with an approval flow, on invoice, with a credit limit, at prices that differ per customer, and from a catalogue compiled for that one customer. The portal has to keep that context everywhere: the same product page shows customer A a different net price than customer B, with a tier that drops further at larger quantities, and customer C never sees that item at all because it falls outside their purchasing entitlement.

We build B2B e-commerce portals for wholesalers, manufacturers with direct B2B sales, specialty distributors and trade associations with group buying. Not a Shopify template with a per-customer pricing plugin on top, but custom software that fits your order management, your ERP and your sales process. That also means a portal that frees your account managers from manual quotes for standard items, and gives your customers the same 24/7 self-service they're used to in B2C, without losing the business agreements.

Three flavours of B2B e-commerce portal.

Which one fits depends on how many customers will use the portal, how complex your pricing structure is, and how deep the integration with your ERP and PIM needs to be. In the first conversation we'll advise which route fits.

Compact project · fixed sprint budget

Private customer portal with catalogue

A logged-in portal where your existing business customers can order products at their own prices. Order history, invoice download, repeat orders and simple multi-user accounts. Suitable if you have a limited number of regular customers and a relatively stable catalogue.

Per-customer price listsOrder historyInvoice downloadRepeat ordering
Mid-sized project · fixed sprint budget

Full B2B portal with workflow

For wholesalers and manufacturers with multiple buyers per customer, approval flows above a threshold amount, volume tiers and quote-to-order. Includes integration with your ERP for stock and invoicing, and with your PIM for product data. Standing orders and custom catalogues per customer group.

Approval workflowVolume tiersStanding ordersQuote-to-orderERP sync
Larger project · fixed sprint budget

Enterprise B2B portal with PunchOut & EDI

For specialty distributors and multi-tenant wholesalers supplying enterprise procurement systems. PunchOut/cXML for SAP Ariba, Coupa or Oracle Procurement. EDI integrations (EDIFACT, GS1) for automated order and invoice flows. Multi-warehouse, multi-location, white-label for industry associations.

PunchOut/cXMLEDI/EDIFACTMulti-warehouseWhite-labelMulti-tenant

What you get at the end.

A production-ready B2B e-commerce portal, integrated with your ERP and PIM, plus everything around it so you can manage and develop it further yourself.

  • The portal itselfProduction and staging environments, running in your cloud (AWS, Azure, GCP) or with us. With load balancer, monitoring and automatic backups.
  • ERP and PIM integrationsProduction-ready integrations with your existing backend (SAP, Exact, AFAS, Microsoft Dynamics) and PIM (Akeneo, Pimcore) for products, prices, stock and orders.
  • Complete codebase + documentationSource code in your own Git repository, build instructions, architecture overview and API documentation. No lock-in.
  • Admin guideWritten for your sales and operations team: how to set customer prices, configure catalogues per customer, manage credit limits and monitor orders.
  • End-user trainingSessions for your key users and account managers, plus a short video onboarding for buyers at your customers.
  • Maintenance contract (optional)Monitoring, security patches, keeping integrations up to date through ERP upgrades, and ongoing development in sprints.

Who we build B2B portals for.

The pages above are about what we build. Just as important is who we build it for. We work most with six types of organisation, because their sales process fits standard webshop platforms least well and benefits most from a portal built around your actual flow.

Wholesalers. Industrial, technical, chemical and food wholesalers with thousands of items, customer-specific agreements and multi-warehouse stock. Often with technicians or job planners on the other end who want to place a spare part or bulk order quickly.

Manufacturers with direct B2B sales. Producers that supply business customers directly, alongside (or instead of) a distribution channel. A spare parts catalogue with technical context often comes into play here too: exploded views, 3D models, serial number integration.

Specialty distributors. Medical, defence, lab supplies, precision technical components. Strict compliance on who may order what, certified product data and often an approval flow on both the buyer and supplier side.

D2B brands without a retail intermediary. Brands that sell directly to business customers without going through retail or a distributor: hospitality suppliers, professional beauty, business catering.

Trade associations with group buying. Cooperatives or trade associations that purchase jointly on behalf of their members. Sometimes white-labelled per member, with tiered discounts on aggregate volume.

B2B marketplaces. Platforms that bring multiple suppliers and buyers together. Really a separate discipline, so see our marketplace page for that context.

Which B2B functionality belongs in it.

Not every portal needs everything at once. But these are the building blocks we see most often, and they make a custom portal more valuable than a standard template.

Catalogue & pricing

Customer-specific prices, tiers and custom catalogues

Each customer sees their own net price, their own volume tiers, and only the products their organisation is entitled to buy. A chemical wholesaler shows different items to a laboratory than to a water treatment plant. The catalogue filters per customer, with pricing calculated centrally.

Per-customer price listsVolume tiersCustom catalogueContract pricing
Account structure & flow

Multi-user accounts with approval flow

One customer account with multiple buyers, roles (purchaser, work planner, fitter), cost centre allocation and approval flows above a threshold amount. Standing orders for recurring purchases, quote-to-order for quote-to-contract-to-order, and custom payment terms per customer.

Multi-userApproval workflowStanding ordersQuote-to-orderCost centre
Integration & procurement

ERP, PIM, PunchOut and EDI

Deep two-way integration with SAP, Exact, AFAS or Microsoft Dynamics for products, prices, stock, orders and invoices. PIM sync with Akeneo or Pimcore. PunchOut/cXML for enterprise procurement, EDI/EDIFACT for automated order flows, and GS1 standards where relevant. Multi-warehouse and multi-location support for distribution organisations.

SAP / Exact / AFAS / DynamicsAkeneo / PimcorePunchOut / cXMLEDI / EDIFACTGS1

When a custom B2B portal is the right choice.

Not every B2B organisation needs a custom solution. For commodity sales at standard prices, Shopify Plus or BigCommerce often work fine. We come into the picture when one or more of these patterns apply.

Pricing complexity

Every customer has their own price list

You work with hundreds or thousands of customer-specific price agreements, volume tiers and contract prices. A standard webshop with a single global price and a few discount codes can't handle that. You need per-customer price lists that come straight from your ERP.

Procurement integration

Enterprise customers via PunchOut

Your largest customers order via SAP Ariba, Coupa or Oracle Procurement. They expect you to offer a PunchOut catalogue or receive cXML order messages. That's not a plug-in; it's a protocol implementation.

ERP depth

Stock, credit and invoices in your ERP

Your source of truth lives in SAP, Exact, AFAS or Dynamics. Stock levels, credit limits per customer, outstanding invoices and payment terms all come from there. A portal needs to connect to it in real time or near real time, not via a nightly CSV export.

Multi-user organisations

One customer, multiple buyers

At your customers, several people often place orders: a purchaser, a work planner, an engineer. With approval flows above a threshold, cost-centre allocation and role-based permissions. That calls for a proper account model, not a collection of separate user accounts.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a B2B e-commerce project works.

1

Introduction and discovery

We map out which customers will use the portal, how your pricing structure works, which ERP and PIM you have, and which procurement integrations are relevant. We also talk to a few purchasers at your customers to understand how they order today: by email, by phone, via Excel forms or through an outdated portal. That's often where the real room for improvement lies. Not a sales pitch, but a working session that's immediately useful to you.

2

Architecture and data model

A workshop with your IT and sales teams. We map the product, pricing and account model, design the ERP and PIM integrations, and define how approval flows and credit limits work technically. This is also where we choose between real-time API calls to your ERP and a synchronised caching layer, depending on your ERP's performance characteristics. At the end: scope, planning, an architecture document and a first interactive screen flow.

3

Building in sprints

A working build every sprint. First the catalogue and authentication, then customer-specific prices and the order flow, then ERP sync and invoicing. The procurement integrations, PunchOut and EDI come last, if they are in scope. You test with real product data, and a few key customers run an early pilot. The pilot steers scope decisions for the rest of the build: sometimes a feature we had planned as a big one turns out not to be needed, while another detail proves critical.

4

Rollout & support

A phased rollout to your customer base, starting with the most digitally savvy purchasers. Training sessions for account managers who explain the portal to customers, video onboarding for your customers, and a helpdesk runbook for your operations team. Ongoing management covers security, maintenance of the ERP integration when you upgrade, and further development in a fixed sprint rhythm. We stay involved for as long as you want us to; we don't sell you a project and disappear.

Standard B2B platforms and when we recommend them.

We don't always build custom. For many B2B organisations a standard platform is the right choice: faster to launch, predictable licensing, and an ecosystem of plug-ins. We help you choose, and implement or integrate where needed.

SAP Commerce Cloud (Hybris) is the enterprise market leader for large international B2B organisations with a deep SAP installation. A logical choice if you already run an SAP stack and have the organisational scale for an implementation partner. Adobe Commerce (Magento Commerce) remains strong where a lot of customisation is needed on a standard platform, with a large developer ecosystem.

commercetools and Spryker are the modern headless choices: API-first with a flexible front end, and Spryker in particular is strong in B2B flows. They are often a good match for scale-ups that want to serve multiple customer types, channels or brands quickly from a single commerce layer. See also our headless commerce page.

OroCommerce is built specifically for B2B, with strengths in custom catalogues, quote-to-order and B2B account models. BigCommerce and Shopify Plus serve the mid-market segment with B2B extensions; workable if your flow is relatively standard. WooCommerce with B2B plug-ins can be enough for simpler portals in the SME segment.

We do not replace those platforms for commodity sales. We build custom when: you need deep ERP or PIM integration that standard connectors can't handle, your industry has specific flows that don't fit a standard platform, you need to run multi-tenant for a wholesale chain or industry association, you want AI-augmented features (product recommendations based on order history, dynamic pricing within contract limits), or you need to offer white-label per member or partner. If you're unsure, we'll give you honest advice on which way to go, even if that means no project for us.

Compliance, security and legal.

B2B portals process representatives' data, pricing agreements, financial data and sometimes certified product information. That raises a series of compliance questions that we take into account from the very first sprint.

GDPR

Customer representatives' data

Although the end buyer is an organisation, you store personal data of buyers and technicians. We build in data minimisation, retention rules, export functionality and correct permissions at customer-account level as standard.

B2B legal framework

Less consumer protection

General terms and conditions, payment terms, exclusions and retention of title look different in B2B than in B2C. We make sure order confirmations, invoicing and T&Cs are legally watertight for your context, in collaboration with your legal team.

Financial

Credit limit and tax

Real-time credit limit checks from your ERP, correct VAT treatment for intra-Community and non-EU deliveries, and correct invoice numbering in line with Dutch Tax Authority requirements. With a Peppol connection, we integrate directly with your e-invoicing stack.

AI Act

Transparency in recommendations

If the portal offers AI-based product recommendations or dynamic pricing, it must be clear that this is automated and which data the system uses. Under the AI Act, that calls for transparency mechanisms, audit logs and human oversight for higher-risk use cases.

Frequently asked questions.

What clients usually want to know before we start a B2B e-commerce project.

What exactly is the difference between a B2B and a B2C webshop?
B2C sells to consumers at fixed prices, paid upfront via iDEAL or credit card. B2B sells to organisations, often with customer-specific prices, credit limits, payment on invoice, approval flows above a threshold amount and custom catalogues per customer. Technically it's a different data model: you don't sell to a user, but to an account with multiple users and specific agreements. That's why a B2C platform with a per-customer pricing plug-in usually doesn't get you there.
Do you replace SAP Commerce Cloud (Hybris), Adobe Commerce or Spryker?
For enterprise organisations with large international catalogues and complex organisational structures, that is rarely wise: SAP Commerce Cloud, Adobe Commerce, commercetools and Spryker are the right choice there, possibly with an implementation partner. We come into the picture with scale-ups and mid-market wholesalers that are too complex for Shopify or BigCommerce, but for whom enterprise platforms are overkill in terms of licensing and consultancy. Or with highly industry-specific flows that are hard to fit into standard platforms.
How exactly does a PunchOut integration work?
PunchOut is a protocol in which your enterprise customer opens a session to your catalogue from their own procurement system (SAP Ariba, Coupa, Oracle Procurement, Jaggaer), selects products at their customer-specific prices, and sends the shopping cart back as a cXML order into their own approval flow. The order then reaches you via cXML or OCI. It is the standard enterprise purchasing departments expect. We implement it on your portal with the right authentication and mapping.
How do you handle customer-specific pricing and volume tiers?
In most cases the pricing structure lives in your ERP: price lists per customer or customer group, tiered discounts, and contract prices with validity dates. The portal retrieves that data via an API or a sync layer and caches it where needed for performance. We implement the calculation rule (net price for customer X on product Y at quantity Z) once, centrally, so web, mobile and point of sale all show the same price.
Which ERP and PIM systems do you integrate with?
For ERP, regularly SAP (S/4HANA and Business One), Exact, AFAS, Microsoft Dynamics 365 Business Central and Odoo. For PIM, Akeneo, Pimcore and, to a lesser extent, Plytix or contentserv. We prefer to use official APIs; where those are missing or slow, we build a sync layer with its own database. See also our approach to smart API integrations.
What about payment on invoice and credit limits?
B2B buyers expect to pay on invoice with a payment term, not just by iDEAL or credit card. Each customer often has a credit limit held in your ERP. For every order, the portal checks in real time whether it fits within the limit, and if not, it blocks the order or asks for prepayment. For customers without a credit facility, we also support IBAN bank transfer, iDEAL Zakelijk and, if needed, credit card.
Do you work with our IT department and our existing suppliers?
Almost always. We hand over knowledge in the final sprints, deliver an incident runbook, and agree clear responsibilities for maintenance up front. If you already have a supplier for your ERP or PIM, we work directly with their architects on the integration agreements.
What determines the cost of a project like this?
Three main factors: the number and complexity of customer-specific flows (one catalogue for everyone versus dozens of variations), the depth of the ERP and PIM integration (read-only catalogue versus full bidirectional order and invoicing sync), and the procurement integrations (web shop only versus PunchOut, EDI, cXML). We give an initial indication after a brief introductory conversation.

Talk to us about your B2B e-commerce portal.

A half-hour introductory conversation, with no obligation. We listen to how your business sales currently work, take a brief look at your ERP and pricing structure, and give you direction on how to move forward, even if you ultimately don't opt for a custom solution. You can also read more about a headless commerce platform, a marketplace or a specific vendor portal.

Edit content