Customer work, connected.

Help & supportMyAccount
Delivery notes, proof of delivery and public signing

Create a delivery note manually

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

Follow this guide to create a secure POD request for a job.

Audience: Courier operations staffPermission: Courier: CreateModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Delivery Notes → Create Delivery Note
Before you start
  • The job must contain receiver/delivery details.

What this guide helps you do

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.

Follow these steps

  1. Go to Delivery Notes.
  2. Select the job.
  3. Verify recipient name and valid recipient email.
  4. Set package quantity to at least 1.
  5. Create the note.
  6. Copy or send the generated public URL through the module.

Fields and options

TokenRandom 32-byte value represented as 64 hexadecimal characters.
ExpiryAt least one day from creation.
Initial statusopen.
Job POD stateawaiting_signature.

Rules and limits

  • The model defaults recipient/delivery data from the job.
  • A job normally reuses its existing delivery note instead of creating duplicates.

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