Create a delivery note manually
Create a secure POD request for a job.
Exact navigationAdmin Area → Courier & Logistics → Delivery Notes → Create Delivery Note
Before you begin
- The job must contain receiver/delivery details.
What this guide covers
Create a secure POD request for a job. 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
- Open Delivery Notes.
- Select the job.
- Confirm recipient name and valid recipient email.
- Set package quantity to at least 1.
- Create the note.
- Copy or send the generated public URL through the module.
Fields, choices and supported possibilities
TokenRandom 32-byte value represented as 64 hexadecimal characters.
ExpiryAt least one day from creation.
Initial statusopen.
Job POD stateawaiting_signature.
Code-backed validations and workflow rules
- The model defaults recipient/delivery data from the job.
- A job normally reuses its existing delivery note instead of creating duplicates.
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.