B2B e-commerce development
Customer-specific pricing, account hierarchies, approval flows, quotes, credit limits and contract terms — the logic that makes a B2B portal work for customers who buy from you regularly.
What an enterprise B2B portal needs
Customer-specific pricing
Contract prices, volume tiers, customer groups, campaign overrides and currency rules — resolved live from the ERP or held in the commerce layer, whichever performs better for your catalogue size.
Account hierarchies
Parent companies, subsidiaries, cost centres, branches and buyers, each with their own permissions, delivery addresses, budgets and visible assortment.
Approval workflows
Order and budget approvals routed by value, cost centre or role, with a clear audit trail and notifications that do not get lost.
Quotes and negotiation
Quote requests from customers, editing and expiry dates for your sales team, and accepted quotes that turn into orders in one click.
Credit and payment terms
Credit limits and balances read from your finance system, invoice payment, partial shipments, and blocking rules that behave the way your credit controllers expect.
Procurement and punchout
OCI and cXML punchout into customer procurement systems, EDI order intake, and structured e-invoicing to European standards.
Need something that isn’t on the list? Talk to us about your project
B2B buyers are doing a job, not shopping
Repeat ordering, fast re-order from history, saved lists, bulk upload by SKU or part number, and stock visibility per warehouse matter far more than a polished product page. We design around the buying routine first.
Where a business sells both B2B and B2C from one catalogue, we build a shared product and inventory core with separate pricing, tax, presentation and checkout rules on top — rather than running two disconnected platforms.
- Fast re-order
- Order history, saved lists, CSV and SKU bulk upload.
- Complex catalogues
- Variants, compatibility, technical attributes, datasheets.
- Stock per warehouse
- Real-time availability and lead times by location.
- Self-service
- Invoices, documents, returns, users and permissions.
- Multi-country
- Tax, language, currency and legal entity separation.
- Sales-assisted
- Order on a customer’s behalf, see the portal as they see it, internal notes.
Alexela: a self-service sales and contract platform for the Latvian energy market
For Alexela we built a complete sales platform for a new market — covering contract management, invoicing and data exchange with local system operators — so that transactions could be executed cheaply and at volume. It is the same shape of problem as B2B commerce: the storefront is the small part; the account, contract and billing logic is the real system.
Common questions
Can you connect B2B pricing directly to our ERP?
Yes. We either call the ERP live for price resolution, or replicate the pricing rules into the commerce layer with scheduled and event-driven synchronisation. Which one is right depends on catalogue size, ERP response times and how often prices change — we compare both on your own data before you decide.
Do we need to replace our current webshop?
Often not. A common path is to keep the existing platform for B2C and build the B2B portal alongside it on shared product and customer data, then decide later whether to consolidate.
Can you support punchout and EDI?
Yes — OCI and cXML punchout, EDI order and invoice exchange, and European e-invoicing formats. These are frequently the deciding factor in whether large customers can buy from you at all.
Let’s talk about your commerce platform
Tell us what you are running today and where it is holding the business back. We will come back with an honest read on the architecture, the integration work involved, and what a realistic first phase looks like.
