Search Knowledge Base Articles

Logistics Module – Overview & Concepts

Purpose

This article provides a high-level understanding of how the Thulo Logistics Module works.
It explains the core concepts, entities, roles, and overall workflow so users know what the system does before using individual features.

This article is the starting point for all other Logistics documentation.

Who This Is For

  • Logistics company Admins

  • Staff / Agents performing logistics operations

  • Customers using the logistics portal

  • Anyone new to the Logistics Module

What the Logistics Module Does

The Thulo Logistics Module is designed to manage the complete lifecycle of logistics operations, including:

  • Customer shipment intake

  • Package handling and consolidation

  • Shipment creation and delivery

  • Invoicing, payment, and tracking

  • Customer and public visibility

It supports local and international logistics operations within a single system and integrates with core Thulo features such as users, permissions, invoices, and tracking.

Core Logistics Concepts

Recipient

A Recipient represents the destination contact for a shipment.

  • Created and managed by customers

  • Used when creating shipments and consolidations

  • Reusable across multiple shipments

Pre-Alert

A Pre-Alert is advance shipment information submitted by a customer.

  • Created from the customer portal

  • Notifies the logistics company of incoming packages

  • Converted by staff into locker packages

  • Becomes read-only after submission

Locker Package

A Locker Package represents an individual package received or expected by the logistics company.

  • Created by staff (or converted from a pre-alert)

  • Contains package details such as weight, dimensions, and recipient

  • Used as the base unit for further logistics processing

Pickup

A Pickup is a request to collect packages from a customer location.

  • Can be created by customers or staff

  • Requires staff approval

  • Approved pickups lead to package or shipment creation

Consolidation

A Consolidation groups multiple packages or shipments together.

  • Used to optimize handling and shipping

  • Does not generate its own invoice

  • Tracking and delivery occur at the package or shipment level

Shipment

A Shipment is the final outbound unit sent for delivery.

  • Created from locker packages, pickups, or consolidations

  • Includes shipping company, mode, and delivery time

  • Generates an invoice and tracking record

Invoice & Payment

Invoices are generated for:

  • Locker Packages

  • Shipments

Key rules:

  • Consolidations do not generate invoices

  • Delivery processing is typically blocked until payment requirements are met

  • Payment terms are defined by Admin configuration

Tracking & Delivery

Tracking provides visibility into shipment progress.

  • Internal tracking for staff and admins

  • Customer portal tracking for customers

  • Optional public tracking page for external sharing

Delivery includes:

  • Driver assignment

  • Status updates

  • Proof of delivery (if enabled)

End-to-End Logistics Flow

At a conceptual level, the logistics lifecycle follows this order:

Customer → Pre-Alert → Locker Package → Pickup →
Consolidation (optional) → Shipment →
Invoice → Payment → Tracking → Delivery

Not all workflows require every step, but all operations follow this logical structure.

Status-Driven System Design

The Logistics Module is status-based.

This means:

  • Actions are enabled or restricted based on current status

  • Users cannot skip required steps

  • Status changes control:

    • Who can act

    • What actions are available

    • When tracking and delivery occur

This design ensures operational consistency and accountability.

User Roles (High-Level)

The Logistics Module involves multiple roles:

  • Admin – Configures settings, pricing, users, and permissions

  • Staff / Agent – Performs logistics operations and processing

  • Driver – Handles pickup and delivery actions

  • Customer – Creates pre-alerts, manages recipients, tracks shipments

Each role has specific permissions and visibility, which are explained in detail in the Roles & Permissions documentation.

Important Design Notes

  • The system does not have native branch entities

  • Branch-style operations are implemented using staff permissions and data visibility

  • All logistics settings are tenant-wide

  • Pricing, taxes, and rules are centrally managed by Admins

Where to Go Next

Depending on your role:

Did you find this article useful?

Related Articles