Your dealer places the order themselves and follows what happens next. They see their own price, fill a cart and place the order. Then they track shipment, invoice, payment and returns in the same portal. Order and "what's the status?" traffic arriving by phone, WhatsApp and spreadsheet goes down.
An order placed on the portal lands straight in your sales flow. You approve, ship and invoice on Platform Web; the dealer sees the same record in their own screen.
Who is it for?
For manufacturers and distributors that sell wholesale, brands with dealer networks, and any business taking regular B2B orders. Internal users (sales operations, finance, dealer channel managers) run the portal from the B2B Management module on Platform Web. External users (dealers, business buyers) work in the web portal or the mobile app.
The price, product group and stock information each dealer sees are set separately. User permissions decide who in the buyer company can order, who approves and who sees amounts.
What does it do?
The dealer searches the catalog, browses campaign products and brands, keeps favourites, fills a cart and places the order. If their company has an approval policy, the cart goes to an approver; once approved, the order is created.
After ordering, the dealer stays in the portal: they follow the order steps on a timeline, download the order PDF, see the shipment and cargo tracking number, download the invoice as a PDF and see its e-document status. They record their payment, open a return or dispute if needed, and create a service request.
How one database works
Orders, shipments and invoices placed through the portal are written into your existing sales and finance records; no separate B2B order world is built. Prices feed from shared definitions and stock from the stock card. With a portal setting, stock and account balance can be read from your existing system (Mikro, Logo); if the source is unreachable at that moment, the dealer sees "unknown", not a wrong zero.
So you are not taking orders on a separate site and exporting them to accounting later. The order goes into the operations record the moment it is placed.
Key capabilities
Sign-in and account
The dealer user signs in on their own sign-in screen. A user linked to more than one account chooses which account to work for at sign-in. Profile, address and permission details are visible in the portal.
Catalog and pricing
Products are presented with search, brand and campaign lists. The dealer-specific price is tied to the account group. Stock display is a portal setting: show the quantity, hide it, show the total of all warehouses, or hide out-of-stock products from the catalog. A user with the price-hiding permission sees no amounts on any screen or in any email.
Cart, approval and company carts
Stock can be reserved for products added to the cart. If the company has an approval policy, a completed cart goes to approval; the approver sees company carts and approves or rejects them with a reason. Approvers get one summary email a day for pending carts.
When the credit limit is exceeded, the dealer sees a warning by default. With a portal parameter, the seller can block cart completion when the overrun exceeds a tolerance.
Orders, shipments and invoices
The dealer sees orders, shipments and invoices in separate lists. A shipment can be partial; each shipment carries a cargo tracking number. The invoice downloads as a PDF; whether it is an e-Invoice or e-Archive and its e-document status (preparing, sent, accepted, rejected, error) are shown.
Payment and account balance
The dealer chooses the payment method, enters the reference number for a bank transfer and uploads the receipt. The portal shows the seller's bank accounts (IBAN). The "My account" screen gives a balance, risk and limit summary; for a user with the price-hiding permission, amounts are masked.
The portal does not take card payments through a new virtual POS. The seller's finance team matches the payment record or transfer notice to an account collection voucher.
Returns, disputes and service requests
The dealer opens a return request or a dispute, with a reason, for goods they received and sees the outcome (full acceptance, partial acceptance, rejection) in the portal. If the seller has the CRM module and the service request feature enabled, the dealer opens a service request, attaches files and follows it.
Web and mobile
The web portal and the mobile app offer the same surfaces. The buyer at a desk orders from the web; the dealer rep in the field orders from the phone. The mobile app needs a connection; carts and orders are not queued offline.
A typical order cycle
In the morning the dealer's buyer adds missing products from the catalog and completes the cart. Under company policy the cart goes to the dealer's purchasing manager for approval; the manager approves and the order is created. The seller's operations team approves the order on Platform Web; the dealer receives an approval email with the order PDF attached. The warehouse ships partially and the invoice is issued with the shipment. The dealer sees the cargo tracking number and invoice in the portal, makes the bank transfer and records it with its reference. Finance matches the record to a collection voucher.
That cuts out the chain of emailed orders, manual entry and phone calls asking for status.
Relationship to other products
- Platform Web: Pricing, accounts, stock, sales, finance and B2B order operations are managed here.
- Mobile: EQLEM Mobile is for internal teams; the dealer uses the B2B mobile app.
- Integration: Account and product cards in your existing system can be the master data the portal rests on; stock and balance can be read from there.
Price, stock and commercial control stay with you on Platform Web.
Before you open the portal
Settle four things: price lists, how much stock the dealer is shown, the cart approval rule, and whether a credit-limit overrun warns or blocks. A catalog with the wrong price or stock you don't have doesn't speed anything up, it just gets you into trouble. Your sales or IT team opens and authorizes dealer users.
When you need it
When phone orders no longer scale with your dealer count, price mistakes keep happening, or the sales team can't keep up with order entry and "where's my invoice?" calls. It usually opens after Platform Web and a tidy stock and price setup are in place.
Getting dealers to switch
If dealers keep using the phone and email, the portal stays empty. Start the pilot with dealers who are open to it and order a lot. Tell your sales team plainly: portal orders come first, manual entry is the exception. When someone disputes a price, fix the list rather than loosening portal rules, or every dealer will want a special case.
You can tell whether it works by watching the share of orders still arriving by phone and email, how many carts become orders, and how many days pass between approval and shipment. Abandoned carts and timings are tracked in the B2B reports.
FAQ
Is B2B a consumer marketplace? No. The focus is dealer and business-buyer orders. Consumer marketplace integrations sit in the E-Commerce module.
Can the dealer pay by card? The portal does not add a new virtual POS integration. The dealer records the payment or reports a bank transfer and can upload the receipt.
Is stock open to everyone? Policy is yours. You can show the quantity, hide it, or remove out-of-stock products from the catalog. Wrong stock display loses trust.
Who manages dealer users? Your sales or IT team opens portal users, binds them to an account group and authorizes them.
Does the mobile app work offline? No. The B2B mobile app needs a connection.
How to start
Lock the price list and account mapping before the portal opens. Pilot the first month with only your most active dealers. Give yourselves a time target for order approval and shipment. Turn on cart approval only for dealer companies that ask for it.
Next step
Try it free, or use a demo to go through your dealer scenario (price lists, stock display, cart approval, credit limit). For the seller-side screens, see B2B Management.