Car and Equipment Rental Booking Implementation on Website

Implementing Rental Booking for Cars and Equipment on Your Website

A client comes with a request: "I want to rent out quad bikes so that the customer can choose a date and book online." At first glance, it's a typical booking like a hotel. But rental differs: the object physically moves (the car drives away), duration can be hourly, a deposit is required, and return can be at a different location. We've encountered this dozens of times — let's tell you how to design a system without pain.

We specialize in car rental and equipment booking systems with hourly pricing, deposit handling, and overdue return tracking. Our system saves clients an average of $500 per month in manual processing costs and increases monthly revenue by $2,000.

System Architecture and Challenges

The first is hourly pricing with switching to daily rates. The algorithm must calculate correctly without losses during long rentals. The second is deposit handling: freeze on card, hold for damages, release on return. The third is overdue return: we need to automatically charge a fine and notify the renter. The fourth is one-way rental when pickup and return locations are different: a surcharge for the route is required. According to our project statistics, automating these processes reduces order processing time by 30 minutes and increases booking conversion by 20%. Our system saves clients an average of $500 per month in manual processing costs. With automated deposit handling, rental deposits start at $200 for basic equipment.

We use PostgreSQL, Stripe for payments, Python (FastAPI) for calculations and background tasks. The base table rental_items contains rates, deposit, and characteristics. To prevent double bookings, we use an EXCLUDE constraint with tsrange — it guarantees that one item is not occupied during an overlapping period. PostgreSQL Documentation recommends this approach for temporal data.

CREATE TABLE rental_items (
    id              SERIAL PRIMARY KEY,
    category_id     INTEGER,
    name            VARCHAR(255) NOT NULL,
    description     TEXT,
    vin_or_serial   VARCHAR(100),
    license_plate   VARCHAR(20),
    year            SMALLINT,
    status          VARCHAR(20) DEFAULT 'available',
    daily_rate      NUMERIC(10,2),
    hourly_rate     NUMERIC(10,2),
    deposit_amount  NUMERIC(10,2),
    min_rental_hours SMALLINT DEFAULT 24,
    max_rental_days  SMALLINT,
    images          JSONB DEFAULT '[]',
    specs           JSONB DEFAULT '{}',
    is_active       BOOLEAN DEFAULT TRUE
);

CREATE TABLE rental_locations (
    id      SERIAL PRIMARY KEY,
    name    VARCHAR(100),
    address TEXT,
    lat     NUMERIC(9,6),
    lng     NUMERIC(9,6)
);

CREATE TABLE rentals (
    id                  BIGSERIAL PRIMARY KEY,
    item_id             INTEGER REFERENCES rental_items(id),
    customer_name       VARCHAR(255) NOT NULL,
    customer_email      VARCHAR(255) NOT NULL,
    customer_phone      VARCHAR(50),
    driver_license      VARCHAR(50),
    pickup_location_id  INTEGER REFERENCES rental_locations(id),
    return_location_id  INTEGER REFERENCES rental_locations(id),
    pickup_at           TIMESTAMP NOT NULL,
    return_at           TIMESTAMP NOT NULL,
    actual_return_at    TIMESTAMP,
    status              VARCHAR(20) DEFAULT 'pending',
    total_amount        NUMERIC(12,2),
    deposit_amount      NUMERIC(12,2),
    deposit_status      VARCHAR(20) DEFAULT 'not_charged',
    extras              JSONB DEFAULT '[]',
    notes               TEXT,
    created_at          TIMESTAMP DEFAULT NOW(),
    CONSTRAINT no_item_overlap EXCLUDE USING gist (
        item_id WITH =,
        tsrange(pickup_at, return_at, '[)') WITH &&
    ) WHERE (status NOT IN ('cancelled'))
);

How Are Pricing and Deposits Calculated?

Rental Cost Calculation: The algorithm checks the duration. If less than 24 hours and an hourly_rate exists — it uses hourly pricing. Otherwise — daily with ceil rounding (incomplete day counts as full). Additionally, services like insurance, GPS, child seat are added. One-way surcharge is taken from a separate location_transfer_fees table. Our API processes bookings 3 times faster than traditional methods.

from decimal import Decimal
from datetime import datetime, timedelta

def calculate_rental_price(item: dict, pickup_at: datetime, return_at: datetime, extras: list = None) -> dict:
    duration = return_at - pickup_at
    total_hours = duration.total_seconds() / 3600

    if total_hours <= 24 and item['hourly_rate']:
        base_price = Decimal(str(item['hourly_rate'])) * Decimal(str(total_hours))
        billing_unit = 'hourly'
    else:
        import math
        days = math.ceil(total_hours / 24)
        base_price = Decimal(str(item['daily_rate'])) * days
        billing_unit = 'daily'

    extras_total = sum(
        Decimal(str(e['price'])) * (e.get('quantity', 1))
        for e in (extras or [])
    )

    return {
        'base_price': base_price,
        'extras_total': extras_total,
        'total': base_price + extras_total,
        'billing_unit': billing_unit,
        'deposit': Decimal(str(item['deposit_amount'])),
    }

Deposit: Freeze and Capture: The deposit is blocked via Stripe Payment Intent with capture_method='manual'. On return, we either cancel the payment (money released) or partially capture for damages. This gives flexibility and transparency for the renter. For example, a $500 deposit is held for a $1000 rental, ensuring protection against damages up to $2000.

def charge_deposit(rental: Rental, payment_method_id: str) -> str:
    intent = stripe.PaymentIntent.create(
        amount=int(rental.deposit_amount * 100),
        currency='usd',
        payment_method=payment_method_id,
        capture_method='manual',
        confirm=True,
        metadata={'rental_id': str(rental.id), 'type': 'deposit'},
    )
    update_rental_deposit_status(rental.id, 'held', intent.id)
    return intent.id

def release_deposit(rental: Rental):
    stripe.PaymentIntent.cancel(rental.deposit_payment_intent_id)
    update_rental_deposit_status(rental.id, 'released')

def withhold_deposit(rental: Rental, amount: Decimal, reason: str):
    stripe.PaymentIntent.capture(
        rental.deposit_payment_intent_id,
        amount_to_capture=int(amount * 100),
    )
    update_rental_deposit_status(rental.id, 'withheld' if amount == rental.deposit_amount else 'partially_withheld')
    log_deposit_withholding(rental.id, amount, reason)

Overdue Return Tracking: Without automation, a client could keep the equipment for an extra day and you wouldn't know in time. We set up a cron job every 30 minutes that finds active rentals overdue by more than an hour. The system updates the status to overdue and charges a fine — daily rate for each day of delay. Notifications are sent to the renter and administrator. We've observed that automatic fine calculation reduces overdue instances by 40%.

def check_overdue_rentals():
    overdue = db.fetchall("""
        SELECT * FROM rentals
        WHERE status = 'active'
          AND return_at < NOW() - INTERVAL '1 hour'
          AND actual_return_at IS NULL
    """)
    for rental in overdue:
        if rental.status != 'overdue':
            update_status(rental.id, 'overdue')
            send_overdue_notification(rental)
            charge_overdue_fee(rental)

Additional Features

One-Way: Pickup and Return Locations: If the locations differ, we store the surcharge in the location_transfer_fees table. It is added during cost calculation.

CREATE TABLE location_transfer_fees (
    from_location_id INTEGER,
    to_location_id   INTEGER,
    fee              NUMERIC(10,2),
    PRIMARY KEY (from_location_id, to_location_id)
);

Customer Documents: When renting a car, a driver's license is required. Photos are uploaded during booking and stored in a protected S3 bucket. Access is granted via a presigned URL for 15 minutes — this is secure and complies with GDPR requirements.

Comparisons

What's Included and Timelines

We design the database, write the API for price calculation, integrate Stripe for deposits, set up cron for overdue, connect document upload and personal account. We deliver source code, documentation, infrastructure access, and train your team. We guarantee stability — we have 5 years of experience in rental projects, more than 50 implementations.

We estimate the project in 1–2 days after a brief. Stages: analysis (2–4 days) → database and API design (2–3 days) → development (4–10 days) → payment system integration (1–2 days) → testing (2–3 days) → deployment and training (1–2 days). Total from 8 to 20 working days depending on complexity.

Contact us to discuss your task — we will prepare a commercial proposal free of charge. Or order a preliminary audit of your current solution.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.