Logistack Overview

LogiStack — Software Overview

LogiStack is an all-in-one logistics and courier software platform that lets transport companies quote, dispatch and deliver with speed and precision.

Logistack is an operations platform for courier and logistics teams. It centralizes admin tools, content/configuration, and integrations so day-to-day work is consistent and auditable.

This page describes the Logistack software at a high level.

Purpose

• Provide a reliable, secure back-office for logistics operations.
• Standardize documents and guidance via an internal knowledge base.
• Make proofs of delivery (POD) easy to store, find, and export.
• Offer a stable interface (API) for systems that need to integrate.

Who uses LogiStack

• **Admins / Managers** – manage content, branding, review PODs and send invoices.
• **Support / Dispatch** – handle questions and maintain operational docs.

Key capabilities

• Staff Management – Can include any type of staff members - see more on Staff, their permissions and how to add, edit or delete staff.
• Company Settings – Add company information - name, full address, phone, email etc - see more on Logistack Invoicing
• Fleet Management – Add, edit and delete vehicles - but used for info on MOT, Servicing dates etc - see more on Fleet management
• **Customers** – At the heart of Logistack - read our detailed article on Logistack Customers
• **Auditability** – optional logging on admin actions (e.g., uploads, restores).

• **POD management** – receive, store, and review proof-of-delivery images; filter and export as needed.
• **Content control** – upload and version the internal knowledge base (kb.json).
• **Branding** – apply or roll back CSS overrides safely.
• **Integrations** – stable API surface for system-to-system workflows.
• **Auditability** – optional logging on admin actions (e.g., uploads, restores).

How it fits together (high level)

1. Admin utilities run under your secure API domain (HTTPS).
2. Knowledge base and CSS are managed through uploads and stored server-side with backups.
3. POD images are retained server-side for later review/export.
4. External systems can connect via the API where permitted.

Day-to-day tasks (admins)

• Update the internal knowledge base by uploading kb.json.
• Apply brand changes via custom-overrides.css (use cache-busting when linking).
• Review and export POD images from the gallery.
• Use the private support hub for tickets and change requests.

Governance & good practice

• **Security:** HTTPS only; strong secrets; least-privilege access; avoid placing personal or sensitive data into public channels.
• **Backups:** include database, /kb/, /uploads/, and configuration files. Keep a small number of recent backups for quick restore.
• **Change control:** record what changed, when, and by whom (e.g., upload logs); announce notable changes in the support hub.
• **Privacy:** delete or anonymise data in line with policy; restrict who can access admin utilities.

Glossary

Knowledge base (KB)

Internal help content stored in kb.json.

POD

Proof of Delivery – image(s) or documentation confirming completion.

Branding override

The optional CSS file used to adjust admin appearance.

Where to next

• Admin Guide — practical steps for uploads, branding, and POD review
• Support workflow — how to raise issues and track responses
• Change management — how software changes are proposed and released