Customer work, connected.

Help & supportMyAccount
Provider live jobs and external imports

Import an external job

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 create one internal job from a normalised provider record.

Audience: Courier operations staffPermission: Courier: CreateModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Live Jobs → Open external job → Import

What this guide helps you do

Create one internal job from a normalised provider record. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Check the external record and provider.
  2. Verify no internal job already has the provider/external ID.
  3. Select Import.
  4. Go to the new internal job.
  5. Check source, external reference, addresses, receiver, commercial fields and payload hash.
  6. Complete missing required data before dispatch.

Fields and options

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

Rules and limits

  • Duplicate provider/external ID combinations are protected.
  • The saved payload hash supports change/evidence comparison.
  • Imported data must still satisfy local dispatch rules.

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