Create a courier customer
Create the operational customer and synchronise it with the core CRM customer when configured.
Exact navigationAdmin Area → Courier & Logistics → Customers → Add Customer
What this guide covers
Create the operational customer and synchronise it with the core CRM customer when configured. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Open Customers and select Add Customer.
- Enter company, primary contact, email, phone and address.
- Choose a two-letter country code.
- Set payment terms, markup, VAT treatment and three-letter currency.
- Add notification email addresses.
- Save.
- Open the linked core customer to verify synchronisation.
Fields, choices and supported possibilities
Payment termsNon-negative; invalid/empty input falls back to 30 days.
MarkupNon-negative customer default.
CurrencyThree-letter code.
CountryTwo-letter code.
Notification emailsAdditional recipients used with the customer email in relevant job/POD events.
Code-backed validations and workflow rules
- The accounting service searches for a matching core client and creates/updates the client and primary contact as needed.
- Do not create a duplicate merely because a core customer already exists; verify the link.
Expected result and verification
- 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.