Transport and Logistics

Narsik Logistics Control Hub

PTL Logistics ERP and Financial Operations Platform

Narsik Logistics Control Hub is an internal ERP created to manage the daily work of a Part Truck Load logistics company.

IndiaMarket
3.5 MonthsTimeline
4 DevelopersTeam
Transport and LogisticsIndustry
Narsik Logistics Control Hub

Project Overview

Narsik Logistics Control Hub is an internal ERP created to manage the daily work of a Part Truck Load logistics company.

It works separately from the public website. The website helps customers view services, send enquiries, book shipments and check tracking updates. The Control Hub is used by the company’s team to handle GR bookings, trips, branch movement, deliveries, customer payments and vendor expenses.

The system keeps shipment and account information together. Employees can follow each consignment from booking to delivery and also check its charges, payments, adjustments and related costs from one place.

What We Built

We built the Control Hub with separate sections for operations, accounts, fleet records and employee access. It includes GR booking, trip planning, Challan generation, shipment tracking, Proof of Delivery, customer ledger, payments, vendor expenses, internal chat and audit records. The system also controls status changes, document creation, financial entries and branch access. This helps employees manage their work without relying on different registers and files.

Client Background

Parmeshwar Sharma runs a transport and logistics business that handles Part Truck Load shipments. In this service, one vehicle may carry goods for several customers. Each shipment can have a different route, freight charge, payment term and handling need. As the business grew, managing bookings, trips, payments and vendor costs through separate records became difficult. The client needed one internal system that could keep daily operations organised and give the team a clear view of shipment and account information.

Project Overview

Project Scope

The work covered the following areas across the Control Hub:

  • Business and workflow planning
  • UI/UX design
  • Frontend, backend and API development
  • PostgreSQL database setup
  • Customer, GR, trip and Challan management
  • Shipment tracking and POD handling
  • Driver, vehicle and vendor management
  • Customer payments, trip costs and vendor dues
  • Employee roles and branch access
  • Internal chat and notifications
  • Document generation, reports and audit logs
  • Performance, security, testing and deployment

Target Audience

The platform is mainly used by:

  • Booking, dispatch and warehouse teams
  • Drivers and delivery teams
  • Fleet and vendor managers
  • Customer-support staff
  • Finance and accounts teams
  • Branch managers
  • System administrators
  • Business owners and management

Objectives

The main objectives were to:

  1. 01Manage daily PTL operations in one system
  2. 02Track shipments from booking to delivery
  3. 03Connect GR bookings with customer charges
  4. 04Simplify trips, Challans and POD handling
  5. 05Maintain accurate payments and vendor records
  6. 06Control access by employee role and branch
  7. 07Support future branches and business growth

Business Challenge

PTL logistics involves several activities that need to stay connected. One vehicle may carry goods for different customers, branches and destinations.

  1. 01Booking, tracking, payment and delivery records were kept in different files. This made it hard for employees to check the full shipment journey.
  2. 02Delivery and payment also did not always move together. A shipment could be delivered with payment still pending, or payment could be received before delivery.
  3. 03Manual balance updates, repeated vendor entries, duplicate document numbers and scattered employee messages made daily work harder to manage.
  4. 04The main challenge was to bring shipment movement, payments, branch work and employee access into one reliable system.

Our Solution

We built Narsik Logistics Control Hub to bring shipment, payment, branch and employee work into one system.

  • Booking, tracking, delivery and payment records are now linked with the same GR. This helps employees check the complete shipment journey without searching through different files.
  • Delivery and payment are managed separately, so the team can clearly see whether a shipment is delivered, paid or still pending.
  • The system also keeps customer balances updated, saves vendor details for reuse and generates document numbers safely. Internal messages, branch access and employee permissions are managed within the Control Hub.
  • This gives the business a clearer and more reliable way to handle daily logistics work.

Key Features

The platform includes the following key features:

Key feature groups sized by number of capabilitiesCustomer and cargo detailsGR number generationBilty printingBooking correction and cancellationGR and Booking ManagementTrip planningRoute, vehicle and driver assignmentCapacity checksChallan generationTrip and Challan ManagementShipment status timelineBranch movement updatesPublic trackingProof of DeliveryShipment Tracking and DeliveryGR-linked chargesPart and advance paymentsOutstanding balancesPayment allocationCustomer Ledger and PaymentsDriver and vehicle recordsOwned and vendor fleetVendor detailsTrip historyFleet and Vendor ManagementRole-based permissionsEmployee accessBranch-level data controlRoles and Branch AccessGR, Challan and receipt recordsPrinting and reprinting historyCancellation, payment and status logsDocuments and Audit LogsClear dashboardsSimple formsSearch and filtersMobile-friendly screensUser Experience
04GR and Booking Management
01

GR and Booking Management

  • Customer and cargo details
  • GR number generation
  • Bilty printing
  • Booking correction and cancellation

Development Process

We started by checking how the client handled bookings, branch movement, trips, deliveries and payments. This helped us understand which records were separate and what needed to work together inside the Control Hub.

Technical Challenges and Solutions

01

Linking GR booking with customer charges

The booking and its charge were saved together, so neither record was missed.

02

Preventing duplicate document numbers

Separate number sequences were used for each branch.

03

Keeping shipment status consistent

The same status flow was followed across booking, trip, tracking and POD.

04

Handling cancelled bookings

A correction entry was added instead of deleting the original charge.

05

Managing part and advance payments

Payments were adjusted against pending charges, while extra amounts were kept as customer credit.

06

Controlling branch access

Employees could only use approved actions and view assigned branch records.

07

Avoiding repeated vendor details

Vendor vehicles and drivers were saved once and reused for future trips.

08

Keeping messages connected

Conversations were linked with the related GR or trip.

09

Saving activity history

Important changes were stored in permanent audit logs.

Technology Stack

Frontend
Next.js logo

Next.js

Programming Language
TypeScript logo

TypeScript

Backend
NestJS logo

NestJS

Database
PostgreSQL logo

PostgreSQL

ORM
Prisma ORM logo

Prisma ORM

Styling
Tailwind CSS logo

Tailwind CSS

Architecture
Modular Monolith logo

Modular Monolith

Design Decisions

The design was kept simple so employees could complete daily logistics work quickly and find information easily. Important decisions included:

  • Role and branch-based dashboards
  • Simple GR booking with customer creation
  • Clear shipment and payment status
  • Search, filters and document actions
  • Buttons based on user permissions
  • Separate customer and vendor finance
  • Chat linked with shipments
  • Responsive screens with clear messages

SEO Work

The Control Hub is a private ERP, so its internal pages do not need public SEO. SEO work was focused on the public website and tracking page. The main work included:

  • Clear page titles and descriptions
  • Simple public URLs
  • Mobile-friendly pages
  • Faster page loading
  • Canonical URLs
  • XML sitemap
  • Robots.txt setup
  • Noindex rules for private pages

Performance Optimization

Performance work included:

  • Server-side pagination
  • PostgreSQL indexing
  • Faster database and dashboard queries
  • Branch and year-based search
  • Limited table results
  • Fewer unnecessary API requests
  • Smaller file and POD image sizes
  • Reusable master records
  • Mobile performance testing

Security

Security measures included:

  • Secure login
  • Protected pages and APIs
  • Role and branch access
  • Permission-based actions
  • Safe data and file handling
  • Financial data protection
  • Login and audit records
  • Controlled printing
  • HTTPS security
  • Branch and year-based document numbering
  • Protected record links

Architecture Diagram

Changes After the Platform

  1. 01

    GR bookings, charges and shipment details were managed separately.

    Each confirmed GR now stores the booking, customer charge and shipment details together.

  2. 02

    Shipment updates and statuses were available in different places.

    One timeline shows the full shipment journey and current status.

  3. 03

    Vendor vehicle and driver details were entered for every trip.

    Vendor details can be saved once and reused.

  4. 04

    Customer balances and payments were managed manually.

    Charges and payments are recorded properly, and balances are calculated automatically.

  5. 05

    Cancelled charges could lose their original record.

    Correction entries keep the complete financial history safe.

  6. 06

    Branch data was difficult to control.

    Employees can only view and manage their assigned branch records.

  7. 07

    Shipment-related messages were scattered.

    Messages remain connected with the related shipment.

  8. 08

    Document reprints and important changes were difficult to check.

    Print details and activity logs show what was changed, when and by whom.

Results

For Operations Teams

  1. 01Teams can manage GR bookings, trips, dispatch, tracking and delivery through one clear workflow.

For the Client

  1. 01The client gets a reliable ERP for handling daily logistics work across different users and branches.

Business Impact

Narsik Logistics Control Hub reduced manual entries and made daily work more organised. Important actions, payment changes, document activity and shipment-related messages are now recorded properly. This makes it easier to check work and find errors. The system also gives the business a stronger base for adding more branches, employees, customers, vehicles and shipments in the future.

Business Impact
4,850 per monthTotal GR Bookings
Business Impact
185Active Trips
Business Impact
3.2 hoursAverage Dispatch Time
Business Impact
91%On-Time Delivery Rate
Business Impact
94%POD Completion Rate
Business Impact
₹18.5 lakhPending Customer Payments
Business Impact
₹2.4 lakhDaily Payment Collection
Business Impact
₹7.8 lakhVendor Amount Due
Business Impact
1.9 secondsAverage Page-Load Time
Business Impact
320 msAverage API Response Time

Visual Identity

Visual Identity

NNarsik Logistics Control Hub

Aa

Narsik Logistics Control Hub

Color

  1. F97316
    01Primary Orange249 115 22
  2. 0F172A
    02Dark Navy15 23 42
  3. 2563EB
    03Blue37 99 235
  4. 16A34A
    04Green22 163 74
  5. D97706
    05Amber217 119 6
  6. DC2626
    06Red220 38 38
  7. FFFFFF
    07White255 255 255
  8. F8FAFC
    08Light Gray248 250 252
  9. E2E8F0
    09Border Gray226 232 240
  10. 64748B
    10Text Gray100 116 139

Type

  1. 01 · Primary4 weights

    Inter

    ABCDEFGHIJKLMNOPQRSTUVWXYZ
    abcdefghijklmnopqrstuvwxyz
    0123456789

    • Bold
    • Semibold
    • Medium
    • Regular

Client Testimonial

Our team was facing difficulty in managing shipment and payment records through separate processes. The TISA team understood the problem and built a practical platform that brought the main work together. The system is reliable and easy for our employees to use.
P
Parmeshwar Sharma

Future Scalability

The platform can be expanded with features such as:

  1. 01

    GST and tax calculation

  2. 02

    Automatic payment reminders

  3. 03

    WhatsApp and SMS updates

  4. 04

    Customer and driver mobile apps

  5. 05

    Live GPS and route planning

  6. 06

    Bank and accounting software integration

  7. 07

    Delay prediction and faster background processing

Lessons Learned

We gained several useful lessons from this project:

  1. 01

    Logistics and payment workflows should be planned together

  2. 02

    Clear status rules make daily operations easier

  3. 03

    Original financial records should always remain available

  4. 04

    Access control should be planned before development

  5. 05

    Audit history should be included from the beginning

  6. 06

    The system should remain easy to expand

Conclusion

Narsik Logistics Control Hub is an internal PTL logistics ERP that brings shipment handling, payments and branch operations together. It helps the team track each consignment, manage related records and handle daily logistics work more efficiently. The platform also provides a reliable base for future branches and business growth.