B2B Management brings your dealer and business-buyer sales onto one line, from the catalog to the service request:
Catalog → cart (approval if required) → order → shipment → invoice (PDF + e-document) → payment record → return or dispute → service request
You approve, ship and invoice the order on Platform Web. The buyer sees the same record in their own web or mobile portal: they follow order status, shipment, invoice and account balance without picking up the phone. Order lists arriving over WhatsApp, "where is my invoice?" calls and orders re-keyed by hand go down.
B2B orders are not written into a separate order world. Orders, shipments and invoices land in your existing Sales and Finance flow; the finance team sees B2B records in the same lists with a filter. Mikro or Logo can keep the accounting and account records.
The buyer web and mobile apps were written from scratch for this line. At first setup, the flow from cart approval to returns is verified with your own catalog and accounts.
Who is it for?
Seller operations approve or reject B2B orders, ship partially, issue the invoice on shipment and decide on return requests.
Dealer channel managers set up account groups, buyer users, catalog rules and the cart approval policy.
Finance sees the bank transfer the buyer reports, matches it to an account collection voucher and sets the credit-limit rule.
Service managers run service requests from dealers in the CRM service flow.
B2B buyers fill their cart from the catalog and follow their orders, shipments, invoices and service requests in their own portal. The buyer side is described on the B2B Portal page.
How it works
Setup and catalog rules
On Platform Web you set up B2B portal definitions, account groups, buyer users and product/service groups. The account group decides which price a dealer sees; the product group decides which products they see.
Catalog rules are portal settings and apply the same way on the buyer's web and mobile screens:
- Show or hide stock quantity, show the total of all warehouses, hide out-of-stock products from the catalog
- Read stock and balance from your existing system (integration); if the source is unreachable at that moment, the buyer sees "unknown", not a wrong zero
- Stock reservation for products added to the cart
- Price hiding: a buyer user with this permission sees no amounts in the catalog, cart, order, invoice or notification emails
- Working hours: outside the set hours the portal stays read-only
Cart and approval
If the buyer company has an approval policy, a completed cart goes to approval. A user without approval rights cannot create an order. The approver sees company carts in their own portal and approves or rejects them with a reason. Approvers get one summary email a day for pending carts.
Even if cart completion is processed twice at the same moment, only one order is created.
Credit limit: The default behaviour is a warning; the buyer sees the overrun and can continue. With a portal parameter you can block cart completion when the overrun exceeds a tolerance amount. If the account has no risk data, the order is not blocked.
Orders
B2B orders are listed in a dedicated order hub on Platform Web. You approve the order or reject it with a reason. The approval email reaches the buyer with the order PDF attached. The buyer follows the order steps as a timeline in their portal and downloads the order PDF.
Shipment and invoice
You ship first. A shipment can be partial; shipping more than the ordered quantity is blocked. You enter the carrier and cargo tracking number on the shipment, and you can issue the invoice together with the shipment if you want.
The buyer downloads the invoice as a PDF in their portal and sees the e-document status (preparing, sent, accepted, rejected, error). The invoice shows whether it is an e-Invoice or e-Archive. Sending the e-document runs through your e-Document module.
Payment record and account
The buyer records their payment in the portal: they choose the payment method, enter the reference number for a bank transfer and upload the receipt. The portal shows the bank accounts (IBAN) you define for the buyer.
Finance sees these records in the B2B payment list and matches them to an account collection voucher. The buyer follows balance, risk and limit on the "My account" screen.
This module does not add a new virtual POS integration. Payment records and transfer notices are used alongside your existing payment systems.
Returns and disputes
The buyer opens a return request or a dispute, with a reason, for goods they received. You accept the request fully, accept it partially or reject it. For the accepted quantity a return shipment (stock receipt) and a return invoice are created. A dispute creates no stock movement.
Service requests
If the CRM module and the service request feature are enabled, the buyer opens their own service requests in the portal, attaches files and follows them. On your side the requests run in the CRM service flow. The buyer sees only their own account's requests. Without CRM and the service request feature, this menu is not shown.
Notifications
Order approval and rejection, cart approval and rejection, cart converted to order and cart pending approval are sent by email. Notification sending is switched on in the portal settings. The same event does not send a second email. You follow the send log on Platform Web.
Reports and analytics
B2B reports show the cart-to-order conversion funnel, abandoned carts and process durations. You send buyers a reminder for abandoned carts. Reports export to Excel and PDF.
Access: web and mobile
All seller-side B2B screens are on Platform Web: definitions, accounts, catalog rules, orders, shipments, invoices, payments, returns, service requests, reports and the notification log.
The buyer side consists of two apps: the B2B web portal and the B2B mobile app. Both offer the same surfaces: sign-in, account selection for users linked to more than one account, catalog, campaign products, favourites, cart and company carts, orders, shipments, invoices, payments, returns, account balance and service requests.
The mobile app needs a connection. There is no offline queue for carts and orders.
Benefits
Orders, shipments, invoices, payments and returns move forward on the same record. You and your dealer do not keep two separate lists.
The buyer sees order, shipment and invoice status in their own portal. Status calls and emails go down.
B2B orders are written into your existing sales and finance flow. Your reports include dealer orders too.
Price hiding and catalog rules apply the same way on web, mobile and email. An amount hidden on one channel does not appear on another.
Cart approval and the credit-limit rule apply your commercial policy before an order is created.
With modular licensing you open B2B on its own; role permissions decide who sees which B2B screen.
Related modules
- Sales Management — the flow orders, shipments and invoices are written into
- Finance Management — accounts and collection vouchers
- Inventory Management — catalog stock and reservation
- e-Document Management — the e-Invoice and e-Archive the buyer sees
- CRM — B2B service requests
- Cargo / Shipping Management — carrier and consignment tracking
- Dashboard & Sign-in — B2B sign-in
Related features
Permissions, notifications, reporting, print templates, list experience, modular licensing, system sync.
Short FAQ
Can the buyer pay by card through a virtual POS? This module does not add a new virtual POS integration. The buyer records the payment or reports a bank transfer; your finance team matches it to an account collection voucher.
Does the order stop when the credit limit is exceeded? Not by default; the buyer sees a warning. With a portal parameter you can block cart completion when the overrun exceeds the tolerance.
Can a dealer order without seeing prices? Yes. A user with the price-hiding permission works with products and quantities; amounts are not shown in the catalog, documents or emails.
Does the B2B mobile app work offline? No. The mobile app needs a connection; carts and orders are not queued offline.
What do service requests require? The CRM module and the service request feature. Without them, the service request menu does not appear in B2B.
I use Mikro or Logo. Will the dealer see their own balance? With a portal setting, stock and account balance can be read from your existing system. If the source is unreachable at that moment, the buyer sees "unknown".
Who grants permissions at setup? Your tenant administrator assigns B2B screen permissions to roles. A user without them does not see the related menu.
Next step
Start with one account group and a narrow catalog. In the first stage, turn on catalog rules, order approval, shipment and invoicing. Add cart approval, payment records and returns in the second stage; turn on service requests when your CRM team is ready. Begin with Try Free, or choose from the Modules catalog.