The order comes in, the shipment is prepared, the vehicle is loaded and the delivery is recorded, all in one place. The order doesn't sit in a spreadsheet with the route somewhere else and the cargo in a third place.
The package is built from Sales, Fleet, B2B and Cargo. Mikro or Logo can keep the accounting and account records. EQLEM manages field sales and the shipment operation.
Let us be clear about scope. Sales is mature on web and supported by partial fields on mobile. The fleet mobile app is a prototype. The fleet web side is far broader. In B2B the dealer places the order in the web or mobile portal and follows shipment, invoice and balance there.
Who for
Built for wholesale distributors, businesses with a dealer network, and teams running field sales.
Sales operations run orders, dispatch notes and shipment preparation. The field team uses the visit route and the sales fields available on mobile. The fleet lead manages vehicle, driver and maintenance cards on web. Teams setting up a dealer channel handle the platform definitions. Logistics tracks incoming and outgoing shipments.
Typical scenario
An order comes in from a dealer or a customer. The shipment is prepared and the vehicle is loaded.
If your visit route is defined, the field day runs along that route.
Vehicle cards and assignments are kept on the fleet web side. Try the fleet mobile scenario in a limited way, as a prototype.
A cargo record is opened for the consignment. The dealer catalog is connected through the B2B definitions. A B2B order can be shipped partially, the cargo tracking number is entered and the invoice can be issued with the shipment; the dealer sees all of this in their portal. For stock visibility, Inventory warehouse and transfer vouchers are added.
Notifications carry shipment and field alerts. Reporting supports you with more than a dozen sales reports. If you already run another system, system sync plans the end-of-day transfer. Permissions decide who changes a route.
For the pilot, pick one warehouse, one route and web shipment. Write the fleet mobile app down as a prototype. Open the B2B portal with a few active dealers and a narrow catalog. Leave the cargo integration to a second stage, and settle the order, stock and shipment line first.
Primary modules
- Sales Management — orders, dispatch notes, invoices, shipment preparation, vehicle loading, visit routes
- Fleet Management — vehicles, drivers, maintenance and inspections; the mobile side is a prototype
- B2B Management — dealer catalog, cart approval, orders, shipments, invoices, payment records and returns; buyer web and mobile portal
- Cargo Management — incoming and outgoing shipments, carrier integration
Optional: Inventory, E-Document, CRM, Integration.
Shared features
Document entry, list experience, permissions, multi-company, notifications, reporting, modular licensing, system sync.
Benefits
Orders, shipments and routes run on the same sales line. The field team works the day from the route while the office closes the order and dispatch note on web. Vehicle records are visible on web (the mobile side is a prototype). The dealer channel connects through B2B, and the cargo record follows each consignment. In multi-branch setups, scope separation protects warehouse and dealer territory. With modular licensing you open Sales, Fleet, B2B and Cargo as you need them.
FAQ
Is fleet mobile live? No, it is a prototype. The fleet web side is far broader. Plan your field expectations accordingly.
What does the dealer order portal cover? The dealer orders from the catalog and follows shipment, invoice (PDF and e-document status), payment record, returns and account balance in the web or mobile portal. There is no new virtual POS integration for card payments; payment runs on records and bank transfer notices. Details are on the B2B Management page.
Next step
Start with orders, shipment preparation and the stock warehouse. Fleet mobile and B2B steps such as cart approval, payment records and returns can follow. Begin with Try Free, or open the package from Modules.