
www.rsisinternational.org
INTERNATIONAL JOURNAL OF LATEST TECHNOLOGY IN ENGINEERING,
MANAGEMENT & APPLIED SCIENCE (IJLTEMAS)
ISSN 2278-2540 | DOI: 10.51583/IJLTEMAS | Volume XV, Issue V, May 2026
driver mode.
The driver receives the assignment along with navigation instructions optimized through the Google Maps
Directions API and further refined using a Dijkstra-based algorithm on the backend. This routing logic helps
avoid traffic congestion, roadblocks, and delays, ensuring faster and more reliable deliveries.
As the delivery proceeds, the driver’s live location is contin- uously updated and displayed within the mobile
application. Clients can track the vehicle’s movement in real time, view the estimated time of arrival (ETA),
and receive live updates at key checkpoints. This level of visibility greatly improves the customer experience
by offering complete transparency throughout the process.
Simultaneously, the admin panel provides real-time mon- itoring of the delivery. The dashboard displays the
driver’s position, current delivery status, and route information. If unexpected delays or route deviations occur,
administrators have the ability to intervene, communicate with the driver, or reassign the task if needed.
This scenario highlights the seamless interaction among the client, driver, and administrator, showcasing how
the system streamlines task management, communication, and navigation. It reflects the practical impact of
integrating automation and artificial intelligence into logistics operations, resulting in smarter, faster, and more
transparent delivery workflows.
Security and Data Privacy
To maintain a secure environment, the system utilizes Firebase Authentication combined with role-based access
con- trol (RBAC) and PIN-locked access to map interfaces. All communication between the client and server
is encrypted via HTTPS, protecting data from potential eavesdropping or tampering. Firestore security rules are
carefully configured to restrict access to sensitive logistics information, allowing only verified users with
appropriate permissions to perform authorized actions.
In addition, the system keeps detailed access logs and audit trails to track user interactions across the platform.
These records support system integrity monitoring and provide crit- ical insights for investigating security
breaches or suspicious activity.
Limitations
While the proposed logistics automation system delivers notable improvements in areas such as real-time
tracking, streamlined booking, and administrative control, there are several limitations that present opportunities
for enhancement in future versions.
One key constraint lies in the manual process of delivery cost estimation. Currently, administrators assess
pricing based on their judgment of factors like distance and route com- plexity. Although this approach allows
flexibility, it restricts scalability and introduces the risk of inconsistency or human error. The lack of a dynamic
pricing engine—driven by data such as historical delivery metrics, package weight, and distance—prevents the
system from offering automated, real- time cost suggestions.
Another limitation is the use of a static, keyword-based AI chatbot in the client application. While it is effective
for responding to predefined user queries, it lacks the capability to understand user intent or handle natural,
free-form conversa- tion. This reduces the system’s ability to offer personalized support and limits the user
experience to fixed command inputs.
In addition, features related to delivery scheduling and warehouse management are still in their foundational
stages. Deliveries are currently assigned without leveraging pre- dictive models or automated dispatch
algorithms. Similarly, deeper warehouse functions—such as inventory validation, environmental condition
monitoring (e.g., temperature), and in-warehouse package tracking—are not yet integrated into the system.
Lastly, the platform’s dependence on third-party services, particularly the Google Maps Platform, creates an
external vulnerability. Any disruptions, API quota limits, or pricing model changes from these services could