Integration Library
How to Design a B2B Dealer Ordering Portal with Mikro ERP
An introduction to customer, product, order and authorisation design for using Mikro ERP data in a dealer portal.
- Mikro ERPMaster records and commercial rules
- Authorised integration serviceMapping, queuing and result checks
- Dealer portalPermitted views and transaction requests
A dealer portal is more than a website displaying a product list. Each dealer needs the correct prices, stock information, order history and permissions. For businesses using Mikro ERP, the first step is not copying data but defining which system finalises dealer transactions.
Technical starting points
MikroAPI documentation includes account, stock and order operation groups. These are data access points to investigate for those areas. Price lists, discounts, permissions and order cancellation must be separately verified against suitable endpoints and ERP rules.
Core portal modules
Dealer identity and role: One dealer cannot see another's prices or orders. Users are linked to a dealer and, where required, multiple branches.
Catalogue: Show product codes, descriptions, images, sales units and conditions for ordering. ERP data and catalogue images may come from separate sources.
Basket and quote: Before an order is sent, assess account limits, minimum quantities, commercial terms and stock checks.
Order history: A request created in the portal and an order accepted by the ERP may have different statuses. Show both separately.
Example data model
| Area | Source or decision |
|---|---|
| Dealer code | Mapped to the ERP account record |
| User role | Portal access management |
| Product code | ERP stock record |
| Commercial price | Verified against company pricing rules |
| Order status | Tracked through portal and ERP events |
| Error logs | Technical monitoring system |
Pre-launch checklist
- Define a unique reference that prevents the same order being submitted twice.
- Do not tell the user an order was received if saving it failed.
- Show account details and dealer prices only to authorised users.
- Do not unnecessarily retain tokens, passwords or personal data in logs.
- Test maintenance, lost connections and high-traffic scenarios.
Off-the-shelf solution or custom portal?
An existing solution may suffice for a standard catalogue and basic ordering. A custom portal becomes more useful as dealer segments, field teams, commercial exceptions, automatic approvals and multi-warehouse rules grow more complex.
What happens to an order if the ERP connection fails?
Example scenario: A dealer submits the same basket twice. The portal first generates its own record number and saves a single request. If the ERP response is lost, it does not blindly create the record again; it checks for a match using the reference in the ERP. If reliable reference lookup or deduplication is unavailable, the transaction is sent for human review. A portal reference alone does not guarantee ERP deduplication.
| Stage | Information shown to the dealer |
|---|---|
| Request saved in the portal | Request received; awaiting ERP confirmation |
| Awaiting commercial checks | Awaiting approval; no claim that stock is reserved |
| ERP record verified | ERP reference and verified status |
| Outcome uncertain | Under review; please do not place the order again |
You can explore this flow in the dealer ordering demo using sample data. During setup, confirm the available API package, licence, company and financial year, and service-user permissions with the ERP owner.
Mikro version, API service and pilot requirements
The starting point here is the on-premises MikroAPI service; do not assume the same endpoints exist for JumpBulut or a different product family. Record the ERP product family, version and patch, MikroAPI version, company and financial year together. Mikro's documentation treats service installation and the API Key licence separately; an installed ERP does not mean API access is ready. Mikro API installation and access documentation.
Pilot requirements: an authorised ERP owner, a test company isolated from production, available account, stock and order methods, service-user scope, warehouse and price-list rules, and the expected ERP result for a sample order. If there is a licence or MAG warning, first follow the MikroAPI licence-error diagnostic sequence.
Example data direction: Accounts, products, available stock and approved prices flow from ERP to portal; new order requests flow from portal to ERP. Editing account or stock master records in both systems requires separate scope with field ownership and conflict resolution defined.
Sources and verification
Example flows are architectural recommendations, not claims of completed client projects or vendor partnerships. Technical sources checked: 17 October 2026. Installation version, licence and permissions must be verified separately.
Adapt it to your business workflow
ERP integration planning guide. Explore the B2B portal development scope for further reading; we can assess your current process together.
Let's discuss your needs →