Understand external completion without local POD | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/understand-external-completion-without-local-pod Publisher: Pixie Technologies LLC Delivery notes, proof of delivery and public signing Understand external completion without local POD Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Prevent a provider webhook from closing a job without local evidence. Audience: Courier operations staff; Permission: Courier: View; Module v2.0.0; Where to goAdmin Area → Courier & Logistics → Jobs → Open externally updated job What this guide helps you do Prevent a provider webhook from closing a job without local evidence. 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 the webhook/sync log. - Go to the job and delivery note. - Verify local state remains awaiting_signature when signed proof is missing. - Complete the local POD flow. Fields and options This action uses the values already stored on the selected source record. Review that record before continuing. Rules and limits - An external completion event does not bypass the signed-POD-and-snapshot rule. 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 Create a delivery note manually (https://pixiecrm.com/help-centre/create-a-delivery-note-manually)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)