Contact person: Business Client

Phone:Show

Email:Show

Location: Indore, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"We need a custom database system to manage all vehicle operations currently tracked in Google Sheets. The goal is to consolidate stock management, bookings, invoicing, and reporting into a single, efficient system to minimize manual work, prevent double entries, and reduce errors.

Key Features / Requirements:

Stock Management

Central table for all vehicle data (Chassis No, Model, Fees, Base Cost, Country-specific increments, etc.)

Ability to handle multiple vehicles per container

Booking Management

Link bookings to vehicles (Chassis No)

Manual ETD/ETA input

Booking status updates

Invoicing Module

Auto-generate invoices from stock selection

Apply country-specific rules (fixed % increments)

Status tracking (paid, pending, etc.)

Document Handling

Upload and link inspection/export documents to vehicles

Optional limited versioning for documents

Reports & Dashboards

Weekly & monthly summaries (vehicles sold, shipped, invoices generated)

Real-time stock status for internal users

Filterable and exportable reports by country, status, sales

User Access Control

Roles: Admin (full access), Agents (restricted by country), Internal Users (full access)

Database Design

Use PostgreSQL or MySQL

ACID-compliant relational structure

Scalable for future expansion (e.g., ERP integration)

UI/UX

Spreadsheet-like forms for easy data input

Search, filtering, and sorting similar to Google Sheets

Use Airtable setup as reference for mockups and relationships

What’s Not Needed:

Automatic notifications or updates

CI/CD pipelines or staging environments

Integration with external APIs (shipping or accounting)

Extensive training or documentation (Airtable serves as reference)

Deliverables:

Fully functional database system with all modules above

SQL scripts for database setup

Admin and agent login functionality

Basic instruction on usage

Budget: Open to discussion, but should reflect reduced scope after excluding unnecessary items

Timeline: 4–6 weeks for initial deployment" (client-provided description)