Customer work, connected.

Help & supportMyAccount
Jobs, stops, dispatch and status control

Complete a job with signed POD

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Close the job only when local evidence satisfies the model.

Audience: Courier operations staffPermission: Courier: EditModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Jobs → Open job → Change Status
Before you start
  • The delivery note must be signed and include a non-empty snapshot.

What this guide helps you do

Close the job only when local evidence satisfies the model. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Go to the job and delivery note.
  2. Check signer, signature, snapshot, condition, timestamp and hashes.
  3. Change status to completed if the POD signing flow did not already do it.
  4. Check resources are released.
  5. Check invoice and journal creation/reconciliation.

Fields and options

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

Rules and limits

  • en_route_delivery may move to completed or cancelled.
  • completed has no further status transition.
  • Completion without signed POD plus snapshot is rejected.

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

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page