Create a courier job
Follow this guide to create an internal job with collection, delivery, receiver, route, load and commercial details. 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 → Jobs → Add Job
Before you start
- Create or select the correct courier customer.
What you’ll accomplish
Create an internal job with collection, delivery, receiver, route, load and commercial details. 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 Jobs and select Add Job.
- Select source and enter any external reference.
- Select the customer.
- Enter collection and delivery addresses and time windows.
- Enter receiver name, valid receiver email and phone.
- Enter distance, duration, vehicle/load requirements, weight and notes.
- Enter quoted, agreed, VAT, currency and cost values.
- Save the job.
- Go to the job detail and verify the generated stops and margin.
Fields and options to review
Required receiver dataReceiver name and valid receiver email are checked before assignment/POD.
RouteCollection and delivery plus optional waypoints.
Commercial valuesQuoted amount, agreed revenue, VAT, currency, driver/other costs.
Lifecycledraft, available, quoted, assigned, accepted, en_route_collection, collected, en_route_delivery, completed or cancelled.
Paymentnot_invoiced, draft, sent, part_paid, paid, overdue or disputed.
Rules the system enforces
- Collection and delivery details must represent the real job.
- Dispatch requires agreed revenue greater than zero.
- Gross margin is agreed revenue minus driver cost minus other costs.
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.