Jobs, stops, dispatch and status control

Understand job sources and external references

Identify whether a job was created internally or imported from a provider.

Audience: Courier operations staffPermission: Courier: ViewModule v2.0.0
Exact navigationAdmin Area → Courier & Logistics → Jobs → Open job

What this guide covers

Identify whether a job was created internally or imported from a provider. 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. Open the job.
  2. Review Source, Provider and External Job ID/reference.
  3. Use these values when comparing provider payloads, sync logs and webhooks.

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

  • Provider ID plus external job ID protects against duplicate authoritative imports.
  • Payload hashes assist evidence and change comparison.

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.