Understand provider POD submission stages
Track signature, snapshot and final POD submission separately. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Courier & Logistics → Delivery Notes → Open note → Provider submission
What you’ll accomplish
Track signature, snapshot and final POD submission separately. 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 Admin Area → Courier & Logistics → Delivery Notes → Open note → Provider submission.
- Check the source record and choose the supported action.
- Save or submit once, then reopen the record and verify the result.
Fields and options to review
signature_pendingSignature upload/action has not completed.
snapshot_pendingSnapshot upload/action has not completed.
pod_pendingProvider POD payload remains to be submitted.
submittedAll required provider stages completed.
not_requiredInternal job or provider does not require submission.
Rules the system enforces
- Submission is staged so an earlier successful upload need not be repeated.
- Retries respect a 15-second rate limit.
How to confirm 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.