Customer work, connected.

Help & supportMyAccount
Troubleshooting and operational controls

Operational go-live checklist for Courier

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Verify the complete module before accepting live jobs.

Audience: Courier operations staffPermission: Courier: AdministratorModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics

What this guide helps you do

Verify the complete module before accepting live jobs. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Verify module activation/upgrade and schema ready.
  2. Create least-privilege roles.
  3. Configure general settings and operations email.
  4. Onboard compliant drivers and available compliant vehicles.
  5. Create/sync customers.
  6. Test a draft job through dispatch, statuses, public POD, completion, invoice and journal.
  7. Test provider feeds/webhook/POD if used.
  8. Test BP fuel if used.
  9. Run cron twice and verify duplicate controls.
  10. Run instant reports and reconcile source records.

Fields and options

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules and limits

  • Use test records/provider sandbox before live credentials and customer work.

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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page