Search Knowledge Base Articles

Getting Started – Logistics Module

Purpose

This guide helps logistics companies get started with the Thulo Logistics Module.
It explains what to set up first, who does what, and how daily operations flow, so teams can begin using the system without confusion.

This is the recommended starting point for all new tenants. Explore Concept Here

Who This Is For

  • Logistics company Admins (primary)

  • Staff / Agents (overview)

  • Customers (high-level understanding)

What the Logistics Module Helps You Do

The Logistics Module enables you to manage:

  • Customer shipment intake

  • Package and shipment handling

  • Pickups and consolidations

  • Invoicing and payments

  • Tracking and delivery

  • Customer and public visibility

It supports local and international logistics operations using a centralized configuration and permission-based execution model.

How the System Is Structured (Simple Explanation)

The system works in three layers:

  1. Admin Configuration
    Admins set up countries, shipping options, pricing, and permissions.

  2. Operational Execution
    Staff and agents create and process packages, shipments, and deliveries.

  3. Customer Interaction
    Customers submit pre-alerts, track shipments, and view invoices.

Each layer depends on the previous one.

Step 1: Admin – Initial Setup (Required First)

Before any logistics operation can start, the Admin must configure the system.

At minimum, Admins should configure:

These settings are tenant-wide and apply to all future operations.

Step 2: Admin – Staff & Permissions

Admins must create staff accounts and assign permissions.

Key points:

  • Staff permissions control what actions are allowed

  • Data visibility can be limited using Own vs Global

  • Branch-style operations are implemented using staff permissions (not branches)

Without correct permissions, staff cannot perform logistics actions.

Step 3: Customer – Prepare Shipment Information

Customers interact with the system through the customer portal.

Customers typically:

Customers cannot process packages or shipments.

Step 4: Staff – Daily Logistics Operations

Once setup is complete, staff handle daily operations:

  • Convert pre-alerts into Locker Packages

  • Create and approve Pickups

  • Group items into Consolidations (if required)

  • Create Shipments for delivery

  • Process invoices, assign drivers, and update statuses

All actions are status-driven and permission-based.

Step 5: Processing, Tracking & Delivery

After creation:

  • Invoices are generated for packages or shipments

  • Payments are recorded based on payment terms

  • Drivers are assigned

  • Tracking updates are shared with customers

  • Deliveries are completed with proof of delivery (if enabled)

Optional Public Tracking Pages can be enabled for external sharing.

Typical End-to-End Flow

A common logistics flow looks like this:

Admin Setup →
Customer creates Pre-Alert →
Staff creates Locker Package →
Pickup (if required) →
Consolidation (optional) →
Shipment →
Invoice → Payment →
Tracking → Delivery

Not all operations require every step.

Important Things to Know

  • There is no native branch entity

  • All settings are centrally managed by Admin

  • Staff permissions control operational separation

  • Consolidations do not generate invoices

  • Status controls what actions are available

Where to Go Next

Choose the section that matches your role:

Did you find this article useful?

Related Articles

';