4,850 per month
Transport and Logistics
NARSIK ERP
PTL Logistics ERP and Financial Operations Platform
Narsik Logistics ERP is an internal ERP created to manage the daily work of a Part Truck Load logistics company.
IndiaMarket
3.5 MonthsTimeline
4 DevelopersProject Team
Transport and LogisticsIndustry
Executive Summary
NARSIK Logistics ERP
- Client
- Parmeshwar Sharma
- Market
- India
- Industry
- Transport and Logistics
- Timeline
- 3.5 Months
- Team
- Project Team - 4 Developers
- Services
- AI SaaS Development, Custom Software Development, AI Workflow Automation
- Technology
- Next.js, TypeScript, NestJS, PostgreSQL
- Primary Outcome
- 4,850 per month Total GR Bookings
Verified project metrics
Project Outcomes
Narsik Logistics ERP 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.
Project Overview
Narsik Logistics ERP 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 ERP 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 ERP 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 Scope
The work covered the following areas across the ERP:
- 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:
- 01Manage daily PTL operations in one system
- 02Track shipments from booking to delivery
- 03Connect GR bookings with customer charges
- 04Simplify trips, Challans and POD handling
- 05Maintain accurate payments and vendor records
- 06Control access by employee role and branch
- 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.
- 01Booking, tracking, payment and delivery records were kept in different files. This made it hard for employees to check the full shipment journey.
- 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.
- 03Manual balance updates, repeated vendor entries, duplicate document numbers and scattered employee messages made daily work harder to manage.
- 04The main challenge was to bring shipment movement, payments, branch work and employee access into one reliable system.
Our Solution
We built Narsik Logistics ERP 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 ERP.
- This gives the business a clearer and more reliable way to handle daily logistics work.
Before → After
Before
GR bookings, charges and shipment details were managed separately.
After
Each confirmed GR now stores the booking, customer charge and shipment details together.
Before
Shipment updates and statuses were available in different places.
After
One timeline shows the full shipment journey and current status.
Before
Vendor vehicle and driver details were entered for every trip.
After
Vendor details can be saved once and reused.
Before
Customer balances and payments were managed manually.
After
Charges and payments are recorded properly, and balances are calculated automatically.
Before
Cancelled charges could lose their original record.
After
Correction entries keep the complete financial history safe.
Before
Branch data was difficult to control.
After
Employees can only view and manage their assigned branch records.
Before
Shipment-related messages were scattered.
After
Messages remain connected with the related shipment.
Before
Document reprints and important changes were difficult to check.
After
Print details and activity logs show what was changed, when and by whom.
Delivery ownership
THE TISA's Role
Product Strategy
Discovery
UX/UI Design
Backend Engineering
Frontend Engineering
Integrations
QA
Key Features
The platform includes the following key features:
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 ERP.
Technical Challenges and Solutions
Technology Stack
Next.js
TypeScript
NestJS
PostgreSQL
Prisma ORM
Tailwind CSS
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 ERP 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
Results
For Operations Teams
- 01Teams can manage GR bookings, trips, dispatch, tracking and delivery through one clear workflow.
For the Client
- 01The client gets a reliable ERP for handling daily logistics work across different users and branches.
Project Showcase
Visual Identity
Visual Identity
NNARSIK Logistics ERP
InterAa
NARSIK Logistics ERP
Color
- #2563EB01Blue37 99 235
- #0F172A02Dark Navy15 23 42
- #DC262603Red220 38 38
- #FFFFFF04White255 255 255
- #F8FAFC05Light Gray248 250 252
- #E2E8F006Border Gray226 232 240
- #64748B07Text Gray100 116 139
Type
- 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.
Parmeshwar Sharma
Future Scalability
The platform can be expanded with features such as:
- 01
GST and tax calculation
- 02
Automatic payment reminders
- 03
WhatsApp and SMS updates
- 04
Customer and driver mobile apps
- 05
Live GPS and route planning
- 06
Bank and accounting software integration
- 07
Delay prediction and faster background processing
Lessons Learned
We gained several useful lessons from this project:
- 01
Logistics and payment workflows should be planned together
- 02
Clear status rules make daily operations easier
- 03
Original financial records should always remain available
- 04
Access control should be planned before development
- 05
Audit history should be included from the beginning
- 06
The system should remain easy to expand
Conclusion
Narsik Logistics ERP 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.
Building Something Similar?
Talk with THE TISA about the architecture, timeline, team, and technology required for your project.