Create a vehicle record
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 add a fleet asset with capacity, ownership, allocation and compliance dates.
Where to goAdmin Area → Courier & Logistics → Vehicles → Add Vehicle
What this guide helps you do
Add a fleet asset with capacity, ownership, allocation and compliance dates. 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 Vehicles and select Add Vehicle.
- Enter registration, make, model and descriptive details.
- Select vehicle type and ownership.
- Assign a default driver only when appropriate.
- Enter payload, cubic capacity, fuel and odometer details.
- Enter MOT, tax, insurance and other monitored dates.
- Save and verify availability/compliance.
Fields and options
RegistrationNormalised to uppercase with spaces removed.
Ownershipcompany, driver, leased or hired.
Availabilityavailable, assigned, maintenance or unavailable.
Compliancecompliant, pending, action_required or expired.
External referencesOperator licence, Courier Exchange and telematics identifiers where used.
Rules and limits
- Use the actual registration as the unique operational identifier.
- Dispatch still checks the current availability and compliance state.
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
Was this guide useful?Your response is stored only in this browser.