Activate and upgrade the Courier module safely
Follow this guide to use the supported activation and version-upgrade flow so required tables and options exist. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Modules → Courier & Logistics Management
Before you start
- Create a platform backup using the organisation’s approved release process.
- Verify the platform version satisfies the module requirement 3.0.*.
What you’ll accomplish
Use the supported activation and version-upgrade flow so required tables and options exist. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Upload or deploy the complete module directory.
- Activate the module from Modules.
- Allow the activation hook to run install.php.
- Reload the admin area so the module upgrade check can apply any newer schema version.
- Go to Courier & Logistics → Dashboard and confirm the schema-ready view loads.
Fields and options to review
Module version2.0.0 in the supplied package.
Platform requirement3.0.*.
InstallerCreates module tables, indexes and default options; future version checks reuse the installer.
Rules the system enforces
- Do not manually create isolated tables instead of running the supported installer.
- Do not remove install.php after activation because upgrade checks depend on it.
How to confirm it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
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.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.