RouteFlow

Problem and context

Nepal lacks a unified digital platform connecting freight manufacturers with logistics companies. Finding a logistics partner typically relies on informal networks or direct phone calls, a process with no price transparency, no competitive comparison, and no structured workflow for managing a shipment from booking to delivery.

RouteFlow addresses this by providing a platform where manufacturers can publish shipment orders, logistics companies can submit competitive bids, and manufacturers can select the offer that best meets their requirements.

Main features

• ·Role-based access for manufacturers, logistics companies, and administrators
• ·Shipment order management
• ·Competitive bidding system
• ·Real-time communication
• ·Route visualization
• ·Payment processing
• ·Shipment workflow management

My responsibilities

I designed and built the complete system independently as a final-year academic project. This included the database schema, the backend API, the frontend application, role-based access control, real-time features, payment integration, and deployment to Vercel and Render.

Technology stack

Frontend

Next.js 16, TypeScript (deployed on Vercel)

Backend

Node.js, Express.js (deployed on Render)

Database

MongoDB Atlas

Technical challenge

Integrating a payment gateway was the most significant technical challenge. I had no prior experience with payment integration, and the documentation for the provider's testing scenarios was limited. Solving it required working through the provider's sandbox environment methodically, testing failure cases I could not find documented, and tracing API responses to understand what the integration expected rather than what the documentation described.

What I learned

Building a complete system (from database schema to deployed UI) in a single project clarified how architectural decisions compound. Early choices about data shape, API contract, and role separation made later features either easier or harder to add. Payment integration, specifically, taught me to read provider documentation critically rather than assuming it is complete.