Understand provider-job normalisation

Map provider payload fields into the module’s common live-job structure. 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.

What you’ll accomplish

Map provider payload fields into the module’s common live-job structure. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Go to the provider.
2. Check valid mapping JSON.
3. Map provider paths for external ID, collection, delivery, times, vehicle/load and amounts.
4. Save.
5. Test and inspect the normalised Live Jobs result.

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

• Mapping JSON must decode successfully.
• Normalisation supports associative provider payloads and configured data paths.
• Do not map secrets into job fields.

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.

Continue with related guidance