B2B Management runs your dealer and buyer order channel. The catalog, the cart, account groups and campaigns all sit in this module. The channel manager sets up account and product groups. The buyer adds a product to the cart and sees their own campaign price. Order lists arriving over WhatsApp and the question "which dealer sees which price?" disappear.
Mikro, Logo or Piconn can keep the invoice and the account record. EQLEM manages the dealer catalog, the cart and campaigns. If you prefer, you run the whole thing on one platform.
Let us be clear about scope. The management screens on Platform Web are mature and usable today. Buyer-facing B2B web and mobile apps are on a greenfield rewrite plan (D-056); the end-to-end order → shipment → invoice lifecycle is locked in the product plan (D-054 / D-057), with a separate application go. What we offer today is the management catalog, cart and campaign surfaces — buyer shipment, invoice, payment and returns are not coded yet.
Who is it for?
Dealer channel managers run platform definitions, account groups, product groups and users. Sales teams manage campaigns and price visibility. Dealers reach the cart, favourites and campaigns. Stock and sales teams attach the channel order to a document. IT aligns B2B sign-in and permissions with Dashboard & Sign-in.
You can do the management work on web today. When you plan the buyer side, take the early stage into account.
How it works
On Platform Web you set up B2B definitions, account groups, product groups and users.
The account group decides which price a dealer sees. The product group decides which products appear in their catalog. Together they build your dealer segmentation.
The cart, favourites and campaigns appear on both the platform and the buyer side. Stock visibility in the catalog rests on the Inventory card. Price and group rules are fed from Master Definitions.
Check that the stock card and the price list agree before you publish a campaign. If they do not, the order line raises a warning. Fix the master data first and publish the campaign afterwards.
Once an order arrives, the process continues through Sales and document entry. On the roadmap buyer lifecycle the order is approve → ship first → invoice on shipment; the buyer sees both PDF and e-document. Planned additions: catalog permission rules, buyer cart approval, credit-limit parameter (warn/block), transfer/record payment, returns/disputes and reports. Lists share the list experience rules. Permissions keep each account to its own product group. If you already run another system, system sync keeps accounts and stock aligned. Notifications pass on order and campaign events.
Benefits
The dealer catalog and price visibility sit on one platform.
The cart, favourites and campaigns make ordering easier for the dealer.
Your dealer sees the same stock figure you see.
The Platform Web side is mature, so the management work can be done today.
Early-stage screens are marked plainly, so the roadmap holds no surprises.
With modular licensing you can open B2B on its own.
Related modules
- Inventory Management — catalog stock
- Sales Management — the document after the order
- E-Commerce Management — the retail channel
- Dashboard & Sign-in — B2B sign-in
Related features
Permissions, list experience, modular licensing, system sync, notifications, document entry.
Short FAQ
Is B2B mobile ready? No. Buyer web and mobile are on a greenfield rewrite plan; application go is separate. Base your plan on Platform Web management.
Are buyer shipment and invoice available today? No. The order → shipment → invoice lifecycle is locked in the product plan; code go is pending.
Where are account groups managed? On Platform Web. Account groups, product groups and users are all managed there.
Next step
Start with a pilot using the platform definitions and a single account group. Try the buyer interface and the shipment/invoice lifecycle after application go, with a narrow catalog. Leave mobile to a second phase. Begin with Try Free, or choose from the Modules catalog.