Create a delivery note manually | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/create-a-delivery-note-manually Publisher: Pixie Technologies LLC 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 staff; Permission: Courier: Create; Module v2.0.0; 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 - Go to Delivery Notes. - Select the job. - Verify 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 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. Related guides Understand automatic POD creation at dispatch (https://pixiecrm.com/help-centre/understand-automatic-pod-creation-at-dispatch)Use the public POD link (https://pixiecrm.com/help-centre/use-the-public-pod-link)Capture a POD signature (https://pixiecrm.com/help-centre/capture-a-pod-signature)Capture a delivery snapshot (https://pixiecrm.com/help-centre/capture-a-delivery-snapshot)