Dealer-specific pricing, credit limits, quick order and approval flows. Core portal features, layered pricing logic, ERP integration and the real difficulty of rollout.
If dealer orders still arrive by email, WhatsApp and phone, your sales team spends most of its time typing orders. This article covers what a B2B dealer portal solves, its core features, how to build the pricing logic, and the real difficulty of rollout.
B2B selling does not resemble B2C. The same product goes to different dealers at different prices, payment is on terms rather than upfront, each dealer has a credit limit, orders sometimes pass through an approval step, and a basket may hold 300 lines rather than three. A standard e-commerce site covers none of this — which is why B2B orders are still processed by hand in most companies.
The cost of taking orders manually
- Sales team time. Typing incoming orders into the system, checking stock, confirming prices — none of it is selling.
- Errors. "Ten of the blue one" from WhatsApp written against the wrong SKU means a wrong shipment and a return.
- Delay. An order arriving outside working hours waits until the next day; the dealer can buy from a competitor.
- No visibility. Because dealers cannot see their balance, order history or stock, they call you for every question.
The fourth usually consumes the most time: a significant part of the sales team's day goes to "is this in stock", "what was in my order last month", "what is my balance". Every one of those is a question dealers could answer themselves.
Core features of the portal
| Feature | Problem it solves |
|---|---|
| Dealer-specific price list | Each dealer sees their own price; no price confirmation by phone |
| Real-time stock visibility | The "do you have it" question disappears |
| Account and balance | Balance, terms and payment history visible to the dealer |
| Credit limit control | Orders exceeding the limit go to approval automatically |
| Quick order (by SKU/barcode) | A 300-line order is entered in minutes |
| Order history and reorder | Repeat last month's order in one click |
| Quote and approval flow | Special price requests and internal approval inside the system |
| Document access | Invoices, delivery notes and statements downloadable |
The most underestimated item is quick order. Basket behaviour in B2B is completely different from B2C: dealers do not browse to discover products, they already know what they need. Being able to paste a SKU list or upload a spreadsheet can single-handedly determine whether the portal is adopted.
Pricing logic
- List price — the product's base price.
- Dealer group discount — by dealer tier (e.g. gold dealer 25%).
- Product or category specific rate — different discounts on certain items.
- Quantity break — a different price above 100 units.
- Campaign — periodic additional discount.
How these layers combine, and in what order, must be a written rule: do discounts stack, or does the most favourable one apply? Projects that start development before settling this spend weeks after go-live arguing about "wrong prices".
The source of the pricing logic also needs deciding: do the rules live in the ERP or the portal? The right answer is usually the ERP — cost and margin live there. We cover data ownership in detail in our ERP integration article.
No integration, no portal
| Data | Direction |
|---|---|
| Products, price lists, discount rules | ERP → portal |
| Stock | ERP → portal (immediate) |
| Account balance and limit | ERP → portal |
| Orders | Portal → ERP |
| Order status, shipment, invoice | ERP → portal |
Stale stock or balance data destroys the portal's credibility in its first week: a dealer who experiences "the portal said it was in stock but it wasn't" goes back to the phone and rarely opens the portal again.
User and permission structure
A dealer is not a single user. The typical structure: several users under one dealer account with different permissions — able to place orders, view only, or approve. On your side, regional managers need to see their own dealers.
Without this from the start you end up with three people sharing one password, losing both traceability and security.
The real difficulty: rollout
- Start with a pilot group. Begin with the 5–10 highest-volume dealers and fix things on their feedback.
- Offer an advantage through the portal. A small extra discount or priority dispatch on portal orders is the most effective way to change a habit.
- Enter the first order together. A first order placed while guiding them on the phone markedly raises adoption.
- Don't close the old channel abruptly. A gradual transition reduces resistance.
Measurement
The one meaningful indicator: what percentage of total orders comes through the portal? If that share is not climbing month over month, the portal is either incomplete or was never adopted. Two supporting numbers: sales team contact time per order, and the order error rate.
Common mistakes
- Trying to adapt a B2C site for B2B. Without pricing, limits and approval flows the portal does not work.
- Developing before pricing rules are settled. The most expensive cause of a stalled project.
- Showing stale stock and balance. One piece of wrong information permanently ends trust.
- Skipping quick order. A dealer forced to fill a basket line by line will not use the portal.
- Not planning the rollout. An unused portal is an unbuilt portal.
Conclusion
A B2B dealer portal is an investment that frees the sales team from data entry and returns them to selling. But the technical part is only one piece: clarity of pricing rules, reliability of the ERP integration and dealer adoption decide the outcome. Planned together, the portal removes the need to grow headcount as order volume grows.
For the build-or-buy decision see off-the-shelf or custom software — a dealer portal is a textbook example of a "process that differentiates you".
At Commerslab we build B2B dealer portals end to end, including ERP integration and pricing rules. See our custom web software development service or get in touch about your dealer process.
