In a dealer channel, the trouble usually starts after the order, not at the moment it is placed. The order arrives on WhatsApp and someone keys it in by hand; the dealer phones to ask where the shipment is; the invoice goes by email; the bank transfer receipt gets lost in a separate thread. Catalog and cart are only the first link in that chain.
That is why the EQLEM B2B Management module was extended beyond catalog and cart. Seller and buyer work on the same record:
Catalog → cart (approval if required) → order → shipment → invoice (PDF + e-document) → payment record → return or dispute → service request
What is on the seller side?
On Platform Web, B2B orders are collected in a dedicated order hub. You approve the order or reject it with a reason; the approval email reaches the dealer with the order PDF attached. You ship first: a shipment can be partial, the carrier and cargo tracking number are entered, and the invoice can be issued with the shipment if you want.
You see the bank transfer the dealer reports in the payment list and match it to an account collection voucher. You accept a return request fully or partially, or reject it; for the accepted quantity a return shipment and a return invoice are created. If you use CRM, the dealer's service requests land in your CRM service flow.
B2B reports show cart-to-order conversion, abandoned carts and process durations. You send the dealer a reminder for an abandoned cart.
These records are not written into a separate B2B world: orders, shipments and invoices sit in your existing sales and finance flow.
What is on the dealer side?
The buyer web portal and the B2B mobile app were written from scratch and offer the same surfaces. The dealer user signs in and, if linked to more than one account, chooses which account to work for.
They fill the cart from the catalog. If their company has an approval policy, the cart goes to an approver; the approver sees company carts and approves or rejects them. After ordering, the dealer stays in the portal: they see the order steps, the shipment and cargo tracking number, the invoice and its e-document status. They record their payment with a reference number and receipt, follow balance and limit on the "My account" screen, and open a return or dispute if needed.
Deliberate limits
We state a few rules up front; set your commercial policy around them before you open the portal:
- Payment: B2B does not add a new virtual POS integration. Payment runs on records and bank transfer notices; your existing payment systems stay in place.
- Credit limit: The default behaviour is a warning. With a portal parameter you can block cart completion when the overrun exceeds a tolerance.
- Mobile: The B2B mobile app needs a connection; carts and orders are not queued offline.
- Price hiding: A dealer user with this permission sees no amounts in the catalog, documents or emails.
- Service requests: The CRM module and the service request feature are required.
How to start
Start with one account group, a few active dealers 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. At first setup, the flow from cart approval to returns is verified with your own catalog and accounts.
For the dealer side see B2B Portal; for the seller screens see B2B Management. To clarify your scenario, begin with Try Free or request a demo.