04 Parties & CRM
Vendors
Vendor onboarding and vendor list access.
Illustrations on this page are conceptual examples — not screenshots of the live system.


How you can use it
The same Fleet module supports different transport models — pick the scenarios that match your operation.
Vendors in daily operations
Vendor onboarding and vendor list access.
Client & partner records
Vendors for sales, billing, and CRM teams — typical in Bangladesh contract carriage businesses.
Fuel, workshop, and supplier vendor…
Teams use Vendors when they need fuel, workshop, and supplier vendor types — without maintaining a separate spreadsheet or WhatsApp thread.
Linked to fuel, garage, and…
Teams use Vendors when they need linked to fuel, garage, and inventory spend — without maintaining a separate spreadsheet or WhatsApp thread.
Benefits for your team
What improves when vehicle data lives in one place instead of spreadsheets and phone calls.
Fuel, workshop, and supplier vendor…
Vendors helps because fuel, workshop, and supplier vendor types — recorded inside the VMS audit trail instead of informal channels.
Linked to fuel, garage, and…
Vendors helps because linked to fuel, garage, and inventory spend — recorded inside the VMS audit trail instead of informal channels.
Vendor-wise purchase and payment history
Vendors helps because vendor-wise purchase and payment history — recorded inside the VMS audit trail instead of informal channels.
Supports branch-level vendor restrictions
Vendors helps because supports branch-level vendor restrictions — recorded inside the VMS audit trail instead of informal channels.

Makes daily work easier
Less chasing, less re-entry, fewer surprises on the morning dispatch board.
- Vendors supports view, list — so users do not jump between unrelated tools for the same task.
- Less manual follow-up: fuel, workshop, and supplier vendor types
- Less manual follow-up: linked to fuel, garage, and inventory spend
- Less manual follow-up: vendor-wise purchase and payment history
- Branch-scoped access means local teams open Vendors without seeing other depots' records.
Multi-user & mobile-ready
Different roles see different slices — desktop for planning, mobile for field, dashboard for leadership.
- Operations lead (desktop)Plans and supervises Vendors with full register access, filters, and exports.
- Branch user (tablet / laptop)Works on branch-scoped Vendors records — no cross-branch data leakage.
- Field staff (mobile)Submits or confirms Vendors tasks from phone — limited permissions, faster updates.
- Manager / approverReviews exceptions, approvals, and summaries inside Vendors without re-keying data.
- Owner / executive (dashboard)Reads KPI widgets fed by Vendors — not day-to-day data entry screens.

Works with your other modules
Fleet is the vehicle master — other modules read from it so data stays consistent across the platform.
- ContactsVendors and Contacts share the same platform data — no duplicate entry between modules.
- AgentsVendors and Agents share the same platform data — no duplicate entry between modules.
- File ManagerVendors and File Manager share the same platform data — no duplicate entry between modules.
- ReportsReport hub aggregates Vendors metrics for branch and management packs.
- HomeDashboard widgets surface Vendors KPIs on login.
