Planning under pressure
Priorities, availability and disruptions change faster than the operating plan.


CANDOR TMS · Carrier edition
A carrier journey connecting order, resources, mission and outcome.
Operational pressure
Priorities, availability and disruptions change faster than the operating plan.
Vehicle, driver, document or capacity is missing at allocation time.
Progress depends on calls and information whose source remains difficult to establish.
Services, evidence, charges and revenue are reconciled only after closure.
Carrier cycle
Operational control
CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.

Orders, routes, vehicles, drivers and constraints feed one plan.
Test a scenario
Instructions, milestones, incidents and evidence follow the driver through the configured journey.
Test a scenario
Availability, documents, due dates and immobilisation inform allocation when these data are integrated.
Test a scenario
Billable services, available charges, incidents and evidence create an explainable economic reading.
Test a scenarioCarrier lab
Cause, eligibility, decision, author and new allocationSituation
A planned mission must depart but the assigned driver is no longer available.
Core capabilities

Selected capability
Qualify customer files, missions, stages, priorities and operational constraints.
Carrier composition
CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.

Orders, planning, allocations, missions, evidence and billable items within scope.
Foundation
Driver mobilityMissions, instructions, milestones, incidents, reservations and POD under the configured journey.
Explore the module
Milestones, ETA, statuses and exceptions shared according to selected sources, rights and frequencies.
Explore the module
Collection, sorting, consolidation, distribution, evidence and returns connected to the Carrier edition.
Explore the module
Register, availability, due dates, interventions and immobilisation connected to operations.
Explore the module
Service, utilisation, available costs and mission outcome analysed under documented definitions.
Explore the moduleSystem responsibilities
CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.
Owns planning, allocations, missions, RAFIK, billable items and transport analysis.
Retain parties, posting, tax, matching and settlement under their rules.
Remains the specialised source for location, mileage or vehicle event under contract.
Issue orders, constraints, confirmations and evidence according to channel and rights.
Carrier ecosystem
CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.
Progressive deployment
Flows, actors, constraints and exceptions
Responsibilities, data and business rules
Events, interfaces and controls
Journeys, rights, alerts and documents
A representative and measurable scope
Adoption, extension and continuous improvement
Brochure and resources
Product brochure
Positioning, two editions, capabilities, modules, integrations and deployment method brought together in a reusable document.
Download the brochureCarrier questions
RAFIK owns the driver mobile journey. Exact scope depends on processes, devices, rights, network coverage and exchanges selected during scoping.
Yes when the available connector or APIs cover required data, rights, frequencies and responsibilities.
Not by default. CANDOR covers fleet functions useful to operations when selected. A specialised CMMS retains asset and workshop processes assigned to it.
Services, rates, time, distance, evidence and controls feed billable items. Approval, tax and final posting remain defined with ERP or finance.
Offline behaviour depends on the mobile journey, required data, device and selected configuration; it is verified during the pilot.
Yes. A representative operation validates planning, mobility, evidence, integrations and billing cycle before extension.
Control operations
Map one complete mission from planning to billing to build an initial Carrier scope.