Courier customers and CRM synchronisation

Synchronise a courier customer to the core CRM

Follow this guide to create or update the core client/contact from the Courier form. 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.

Audience: Courier operations staffPermission: Courier: CreateModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Customers → Add/Edit

What you’ll accomplish

Create or update the core client/contact from the Courier form. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Save a customer with company and contact information.
  2. Allow the accounting service to find or create the core client.
  3. Verify a primary contact exists when an email was supplied.
  4. Verify the customer is placed in the intended core client group when configured.

Fields and options to review

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

Rules the system enforces

  • Matching uses company/email logic from the accounting service.
  • Only destination-table fields are written.

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.