Understand the Courier controller-action map
Follow this guide to use the exact code flow behind every admin workspace. 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 goTechnical reference → controllers/Courier_logistic_management.php
What you’ll accomplish
Use the exact code flow behind every admin workspace. 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 Technical reference → controllers/Courier_logistic_management.php.
- Check the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields and options to review
Dashboardindex, dashboard_data.
Operationsoperations, operations_data.
Driversdrivers, driver, driver_document, document_download, document_status.
Vehiclesvehicles, vehicle.
Customerscustomers, customer.
Jobs/Dispatchjobs, dispatch, job, job_view, assign, job_status.
Providerslive_jobs, live_jobs_feed, import_external_job.
PODdelivery_notes, create_delivery_note, delivery_note, resend_delivery_note.
Financecreate_core_invoice, finance, create_settlement, settlement_status, add_expense.
Reportsinstant_report, instant_report_pdf, instant_report_email.
Settingssettings, test_bp_fuel, sync_bp_fuel, test_provider, sync_invoices.
Deletedelete with entity allowlist and permission check.
Rules the system enforces
- Private requirePermission and JSON response helpers enforce server-side control.
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.