B2B platforms for orders between companies.
The problemBusiness customers order by email and phone, and every price and repeat order goes through one of your employees.
A portal where your business customers see their own prices and terms, send requests for quotes and repeat orders, while your team receives well-organised requests.
Repeat order№ 3187 · 14.10
- Cement CEM II 42.5 N40
- Tile adhesive C2TE12
- Profile CW 5060
Requests for quote2 active
- No. 214 · “East” siteQuote received
- No. 213 · “North” warehouseIn progress
Your pricesPrice list “Partner B” · excl. VAT
It fits when
- You sell to companies with different prices, discounts or payment terms.
- Orders come by email, phone or in spreadsheets and are entered by hand.
- Customers order the same products regularly.
- Large quantities go through a quote before they become an order.
If you mostly sell to consumers at the same prices, an online store is the simpler and cheaper solution.
How the work changes
- TodayOrders by email and phone, retyped into the ERP AfterThe customer orders at their own prices; the order has a status
- TodayEvery regular order is dictated again AfterRepeat order from history, changing only the quantities
- TodayQuotes get lost in emails AfterRequest, quote and confirmation in one document with a history
What we build
What the solution includes.
Numbers 01–04 are also marked on the sample interface at the top of the page.
-
01
Company accounts and roles
One company, several users: buyer, approver, administrator. Each one sees and does only what is allowed.
-
02
Individual prices and terms
Price lists per customer or group, volume discounts, payment and delivery terms.
-
03
Request for quote
The customer sends quantities and requirements; your quote becomes an order with one confirmation.
-
04
Repeat orders
Order history, templates for regular requests and quick adding by product code.
-
05
Order approval
An order above a set amount waits for approval by the person responsible at the customer’s company.
-
06
Documents
Invoices, pro forma invoices and confirmations in one place, when your system provides them.
Comparison
B2B platform or an online store?
They differ in who buys, how the price is set and how the order goes through.
| Criterion | Online store | B2B platform |
|---|---|---|
| Customers | Every visitor | Approved companies with accounts |
| Prices | The same for all, with promotions | Individual per customer or group |
| Order | Cart and payment | Cart, request for quote, approval |
| Payment | Card, cash on delivery | By invoice, on agreed terms |
| Repeat orders | Rarely | Main scenario |
| Users | One person | Several people with different roles |
Before we start
Advantages
- Less manual entry of orders
- The customer sees their prices and terms at any time
- History and repeat orders in one place
What to plan for
- Analysis of the pricing rules before the scope is set
- Data quality: codes, units of measure, price lists
- The exchange with the ERP depends on the system’s interfaces
Process
How we work.
-
01
Analysis
Your customers, pricing rules, data and systems. We don’t set a scope without analysis.
Result: rules and data described
-
02
Scope and plan
The project is split into stages; the most important scenarios come first.
Result: phased plan
-
03
Development
We build stage by stage, with test access for your team.
Result: working stages
-
04
Pilot
The portal starts with a few selected customers and is adjusted to real work.
Result: scenarios verified
-
05
Launch and growth
We open it to all customers and continue with support.
Result: a working portal
What we need from you: A list of customers and terms, the pricing rules, access to the ERP or a data export, a person responsible for decisions.
What we clarify before we quote
The answers determine the scope, timeline and price. You don’t need to know them all — we clarify them in the first call.
- 01How many business customers do you have, and what are the pricing rules?
- 02Which data is kept in the ERP: customers, prices, stock?
- 03What roles exist on the customer’s side: buyer, approver, administrator?
- 04Which scenarios come first: order, quote, approval, documents?
Technologies
The business logic, roles and data — in Python, PHP or Java depending on the systems the portal works with; the interface — in JavaScript and React. In simpler cases, an extension of an existing platform. The choice follows the analysis.
- Python
- PHP
- Java
- JavaScript
- React
Questions
Questions about B2B platforms.
General questions about price, timeline, handover and support are in Contact.
Can the B2B portal work together with an online store?
Yes.
The two channels can share a catalogue and stock while prices and rules differ. Whether they will be one system or two connected ones, we decide during the analysis.
How are the prices set for each customer?
By price lists, discounts and volume rules.
If the prices are already kept in the ERP, the portal reads them from there instead of duplicating them.
Do we have to have an ERP?
No.
The portal can manage customers, prices and stock on its own. If you have an ERP, the exchange is planned around the interfaces it provides.
Can we start with a smaller scope?
Yes, and we usually recommend it.
First accounts, prices and orders; then requests for quotes, approval and documents.
Do you have business customers with different terms? Describe how they order today.
The form has a service selected; you can change it.