B2B Portal Development
We develop B2B portals connected to your ERP: dealer portals and ordering systems, corporate customer portals and supplier portals. Together, we scope ordering, company-specific pricing, stock and account flows according to the access your existing system provides.
Who it is for
B2B portal development means building a self-service application around your ERP for partners to manage orders, pricing and accounts. Dealers and customers place orders and track account balances; suppliers confirm your purchase orders and report shipments.
When is it needed?
- Sales: representatives spend their day entering telephone orders into the ERP.
- Sales management: discount, promotion and payment-term rules exceed an off-the-shelf package's settings.
- Accounting and support: calls about balances, invoices and “Where is my order?” repeat every day.
- Purchasing: supplier confirmation and shipment dates get lost in correspondence.
When is it unnecessary?
- If your pricing rules are simple and your workflows standard, your ERP's B2B module or an off-the-shelf package is sufficient.
- If only a few dealers place regular orders, an order form may work for a while.
- If a package lacks just one feature, keep it and develop only that component.
Scope
We agree the scope together during discovery. The example below is a typical first release for a distributor's dealers.
Catalogue and search
Search by product code, barcode or synonym; pack-size and minimum-quantity rules.
Company-specific pricing
Dealer group, contract, volume discounts and promotions; each dealer sees only its own prices.
Basket and repeat ordering
Build a basket from a previous order; bulk entry by code or Excel.
Order tracking
Approval, preparation, dispatch and delivery status; shipment tracking number.
Trade account
Balance, credit limit, payment terms and account statements; invoice and delivery-note downloads.
Roles and approvals
Company users, approval thresholds and branch permissions; an administration panel for your team.
Outside this example's scope
- Replacing the ERP or redesigning pricing rules
- Supplier portal and mobile app (later stages)
- Licence, payment gateway and cloud fees (charged to your accounts)
Assumptions
- The ERP has an API or regular export capability and a test environment.
- Pricing and discount rules are defined in the ERP.
- The first release launches with a pilot group of dealers.
- Duplicate customer and product records are identified during discovery.
Portal types and core features: What is a B2B portal?
Example scenarios
Explore the use cases
Each scenario starts with a role's working day. The first translates today's telephone dealer order into a portal flow.
-
Dealer order
- Role
- The dealer's warehouse manager
- Input
- Previous orders, dealer-specific pricing and promotions, stock
- Action
- The basket is filled from last month's order; the dealer owner approves it if the limit is exceeded.
- Output
- An order transferred to the ERP; notifications to the dealer and representative
-
Contract-based repeat order
- Role
- The hospital's purchasing specialist
- Input
- Contract prices, departmental requests, previous orders
- Action
- Requests are combined in one basket; a manager approves products outside the contract.
- Output
- An approved order; delivery tracking, invoices and delivery notes on one screen
-
Purchase order confirmation
- Role
- The supplier's sales contact
- Input
- Open ERP purchase orders and delivery dates
- Action
- The supplier confirms or proposes a date, then reports the delivery note on dispatch.
- Output
- An updated ERP delivery date, advance warehouse notification and delay alert
Example screens
Product concept: a solution study through interface designs, not an interactive demo or customer project. X Dağıtım and X Medikal are fictional; the screen data is illustrative. All product concepts
Integrations
Integration details
The portal does not replace the ERP. We determine which system manages products, prices, stock and customer records; draft orders may live in the portal, while confirmed orders and dispatch status are tracked in the ERP. For each dataset, we document an owner, transfer frequency and acceptable delay. The flows below are adapted to the ERP's API and licensing capabilities.
| System | Examples | Transferred data | Direction and frequency |
|---|---|---|---|
| ERP: catalogue and pricing | Logo, Netsis, Mikro, SAP | Products, units, prices and discount rules | From the ERP when changes occur; final check in the basket |
| ERP: stock and accounts | The same ERP | Stock, balances, limits and open invoices | From the ERP at short intervals; real-time limit check on ordering |
| ERP: orders | The same ERP | Orders, dispatch status and shipment tracking | Orders sent immediately to the ERP; status returned |
| Electronic documents | Authorised e-document integrator | e-Invoices, e-Delivery Notes and their status | Sent to the portal when created; the portal does not issue documents |
| Payments | Payment gateway, bank | Card payments towards account balances, bank-transfer notifications | Immediate; receipts recorded in the ERP account ledger |
If the ERP is unavailable
Display when the data was last updated. If a price, stock level or credit limit cannot be verified, save the record as a draft or request awaiting approval. “Your request was received” and “The ERP confirmed the order” are separate states. Design transfers with a consistent job ID, bounded retries and reconciliation for uncertain outcomes; do not rely solely on a resend button.
Flow plan: The path of an order through the ERP and dealer portal
Who is responsible for each issue?
Example scenario: a dealer reports a difference between the portal price and the price confirmed by the ERP. The portal team checks the transfer time and version, the ERP owner verifies the calculated price, and the sales owner confirms the applicable commercial rule. The technical team does not make discount decisions independently.
The proposal assigns these responsibilities: ERP access and field definitions; development and monitoring of the portal connection; and acceptance of business rules. It also identifies who first receives an error report and how it is passed to the next responsible person. The data ownership table is the starting point for this division of responsibilities.
Product names are examples and do not imply a partnership.
Process
Steps in our process
-
01
Discovery
We observe dealers and representatives at work, documenting pricing rules and ERP fields.
1–2 weeks -
02
Definition & Prototype
The ordering screen is tested with real dealers in week 3; the first-release scope is documented.
2–3 weeks -
03
Build
Weekly working-software demos; orders tested end to end in the ERP test environment.
Two-week sprints,
first release target: weeks 6–12 -
04
Grow & Operate
Roll out from a pilot dealer group to the whole network, adding modules in stages.
Ongoing
This is an illustrative schedule assessed once access and pilot scope are clear; the final duration is determined during discovery. Step-by-step details: how we work
Budget and timeline
We do not publish a price list: pricing rules and integrations have the greatest impact on a portal's budget. You receive a written proposal at the end of the discovery sprint.
- Products and pricing
- Discount, promotion and payment-term rules.
- Integrations
- The ERP API; electronic documents, payments and shipping.
- Portal types
- Dealers, customers, suppliers: which are included in the first release?
- Roles and approvals
- Company roles, approval limits and branches.
- Channels
- Browser or app-store application; barcodes.
- Transition and support
- Dealer transition plan and support hours.
- Discovery sprint
- 2 weeks Fixed scope, fixed fee
- First release
- 6–12 weeks A first release scoped together, rather than the entire project
- Dealer network
- In stages Region by region after the pilot group
Delivery terms
Delivery and maintenance details
The portal is your product: code, accounts and dealer data are held by you from day one.
Code and intellectual property
Transfer of project-specific code and designs, third-party licences and usage rights are defined separately in the contract.
Accounts
Repository, domain, cloud, payment gateway and email-sending accounts are registered to you from the outset.
Documentation
Architecture, API documentation and ERP field-mapping tables are kept in the repository and updated with every release.
Tests
Price calculations and ERP transfers are covered by automated tests; a release that fails testing does not go live.
Handover
Code is handed over to your team through joint sessions, with a short user guide for dealers.
Maintenance and support
Maintenance scope, support hours and response targets are agreed in writing; month-end workloads are included in the plan.
What do we check before expanding from pilot dealers to the whole network?
Example scenario: the order flow is tested in the ERP test environment with two dealers using different price lists. A working screen alone is not enough to approve a wider rollout.
- Pricing and access: each dealer must see only its own prices, account information and documents; a price changed after adding an item to the basket must be explained before the order is confirmed.
- Stock and orders: distinguish displayed stock from reserved stock. Define when the ERP reserves stock and who releases it on cancellation.
- Outage: verify that resending a transfer with a missing response does not create a second order, and that the responsible person can find the pending record.
- Operations: assess whether a pilot dealer can complete an order without help, along with the support route and unresolved errors; use these findings to decide whether to add the next dealer group.
This is an example checklist we can adapt together, not a customer result. Do not assume reservation or cancellation behaviour that the ERP does not support. The ERP guide details data and error-handling responsibilities.
Frequently asked questions
What information should we bring to a dealer portal discussion?
Explain how an order is received and approved today, the dealer, customer or supplier roles, and which ERP you use. Include known rules for price groups, stock visibility, account limits and the first pilot group; simply flag anything not yet decided.
If you have API or export documentation, we can discuss the available access. Do not share ERP passwords, access keys, real customer records or price lists in the form. The data ownership table is a starting point for discussing which information belongs in which system.
Can dealers order from a phone?
Yes. The portal also works in a phone browser, which is enough for most dealers to reorder, view balances and track orders. If barcode scanning, push notifications or an app-store download is required, we add a mobile app connected to the same backend. A visit and ordering app for sales representatives is a separate product: field sales application.
What role will sales representatives have?
The portal removes order-entry workload without replacing representatives. Representatives can place orders for their dealers, and dealers' own orders can count towards their representative's targets. We agree these rules with sales management during discovery: if representatives do not support the portal, dealer adoption slows down.
How are permissions set up for dealers with branches?
Each company has a main account and branches. A user's role—preparing baskets, approving orders or viewing invoices only—and accessible branches are defined separately. Orders above a set amount go to an authorised approver. Account information is shown centrally or by branch according to the ERP structure.
Can we migrate from an off-the-shelf B2B package?
Yes. Since products, prices and account data usually reside in the ERP, the main migration covers users, delivery addresses and open orders. Pricing or promotion rules defined in the package are also documented during discovery. The systems run alongside each other for a period, and dealers migrate in groups. We check the old package's export capabilities during discovery.
Can dealers see each other's prices?
No. Each request is filtered by the company in the session; another company's prices, account information and orders are not visible in either the interface or API. Automated tests check this rule in every release, and administrator access is logged.
Can we see your reference projects?
We present product concepts instead of a customer reference list: the two portals on this page are interface designs for fictional companies. To limit risk, we suggest starting with a fixed-fee discovery sprint or a pilot for one dealer group, with repository access from day one.
Next step
Tell us how your dealer orders work today. Let's assess the ERP connection and initial user group together, then clarify the scope needed for a discussion or pilot.
How do dealer orders and manager approvals work?
Try the pricing, credit-limit and approval flow in a fictional dealer portal. View the same order as a dealer and a manager; no real order is created.
Plan the integration
In the ERP integration library, compare the general options. Businesses using SAP can explore Service Layer and dealer ordering decisions, while Business Central users can review API and webhook flows. For an initial ordering setup, use the free dealer order form.