Courier and Logistics Management module overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains how drivers, vehicles, customers, jobs, dispatch, POD, finance, provider feeds and automation connect.
- The module must be installed and its schema must be ready.
What this guide helps you do
Understand how drivers, vehicles, customers, jobs, dispatch, POD, finance, provider feeds and automation connect. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to the dashboard.
- Check live operational, compliance and finance counts.
- Use the grouped menu to move into the relevant register.
- Complete the workflow in the register and verify its history, notification or linked accounting record.
Fields and options
Rules and limits
- The module uses soft deletion for supported entities so historic links remain available.
- Every state-changing action is permission checked and audited.
- Completion is evidence-led: a job cannot complete without a signed POD containing a snapshot.
Check it worked
- The selected workflow remains connected to its source record, status history and downstream records.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
