Jobs, stops, dispatch and status control

Enter receiver details correctly

Provide the identity and contact needed for dispatch and POD.

Audience: Courier operations staffPermission: Courier: Create/EditModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Jobs → Add/Edit Job

What this guide covers

Provide the identity and contact needed for dispatch and POD. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Exact step-by-step process

  1. Enter receiver name.
  2. Enter a syntactically valid receiver email.
  3. Enter receiver phone where available.
  4. Save and verify before dispatch.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

  • Assignment requires receiver name and a valid receiver email.
  • POD creation defaults to the saved receiver and delivery details.

Expected result and verification

  • 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.