CANDOR TMS · Carrier edition

Your fleet moves.
Your margin should follow.

A carrier journey connecting order, resources, mission and outcome.

01 / 05

Operational pressure

What weakens carrier availability, service and margin.

01

Planning under pressure

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

02

Unavailable resources

Vehicle, driver, document or capacity is missing at allocation time.

03

Opaque field execution

Progress depends on calls and information whose source remains difficult to establish.

04

Late margin insight

Services, evidence, charges and revenue are reconciled only after closure.

Carrier cycle

From order to outcome, a mission with uninterrupted context.

01OrderMission to organise
02PlanningRoute and constraints
03AllocationVehicle and driver
04ExecutionMilestones and incidents
05PODEvidence and reservations
06BillingBillable services
07MarginRevenue and charges

Operational control

Connect plan, field execution, evidence and economic reading.

CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.

01

Planning connected to resources

Orders, routes, vehicles, drivers and constraints feed one plan.

Test a scenario
02

A guided, documented mission

Instructions, milestones, incidents and evidence follow the driver through the configured journey.

Test a scenario
03

A more readable fleet

Availability, documents, due dates and immobilisation inform allocation when these data are integrated.

Test a scenario
04

Outcome by mission

Billable services, available charges, incidents and evidence create an explainable economic reading.

Test a scenario

Carrier lab

Resolve disruptions that shift mission, service or margin.

Cause, eligibility, decision, author and new allocation

Situation

Driver unavailable

A planned mission must depart but the assigned driver is no longer available.

Signals to examineSkills and documentsTime and availabilityRoute and customer impact
Expected decisionCompare eligible resources, document the trade-off and republish relevant instructions.
Retained evidenceCause, eligibility, decision, author and new allocation

Core capabilities

Control operations without turning the TMS into accounting or telematics.

Selected capability

Orders and operations

Qualify customer files, missions, stages, priorities and operational constraints.

  • The customer, offer, price, terms and rights required for « Orders and operations » come from responsible master data.
  • « Orders and operations » approval, change and acceptance remain linked to the same commercial commitment.
  • A « Orders and operations » cancellation or exception retains its reason, customer impact and next action.

System responsibilities

The Carrier organises and proves. Specialised systems retain their role.

CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.

01CANDOR Carrier

Transport operations

Owns planning, allocations, missions, RAFIK, billable items and transport analysis.

  • Mission and route
  • Driver and resource
  • POD and billable item
02ERP and finance

Posting and settlement

Retain parties, posting, tax, matching and settlement under their rules.

  • Customer and account
  • Accounting entry
  • Settlement
03Telematics

Location and vehicle data

Remains the specialised source for location, mileage or vehicle event under contract.

  • Authorised location
  • Mileage
  • Vehicle event
04Customers and subcontractors

Partner commitments and events

Issue orders, constraints, confirmations and evidence according to channel and rights.

  • Customer order
  • Outsourced mission
  • Partner document

Carrier ecosystem

Connect customers, field, fleet and finance through governed exchanges.

CANDOR Carrier owns planning, allocations, missions, RAFIK mobility, billable items and transport analysis. ERP or finance retains posting; telematics remains a specialised source.

CANDORTMS
ERP
Finance
Telematics
Mobility
Customers
Subcontractors
EDI

Progressive deployment

Start with one operation, one team and one billing cycle.

01

Observe

Flows, actors, constraints and exceptions

02

Scope

Responsibilities, data and business rules

03

Map

Events, interfaces and controls

04

Configure

Journeys, rights, alerts and documents

05

Pilot

A representative and measurable scope

06

Deploy

Adoption, extension and continuous improvement

Brochure and resources

Prepare carrier scoping with concrete material.

All resources

Product brochure

A concise view of CANDOR TMS.

Positioning, two editions, capabilities, modules, integrations and deployment method brought together in a reusable document.

Download the brochure

Carrier questions

Clarify fleet, RAFIK, telematics, billing and deployment.

01Is CANDOR RAFIK included?+

RAFIK owns the driver mobile journey. Exact scope depends on processes, devices, rights, network coverage and exchanges selected during scoping.

02Can existing telematics be integrated?+

Yes when the available connector or APIs cover required data, rights, frequencies and responsibilities.

03Does maintenance replace a CMMS?+

Not by default. CANDOR covers fleet functions useful to operations when selected. A specialised CMMS retains asset and workshop processes assigned to it.

04How is billing prepared?+

Services, rates, time, distance, evidence and controls feed billable items. Approval, tax and final posting remain defined with ERP or finance.

05Is offline operation guaranteed?+

Offline behaviour depends on the mobile journey, required data, device and selected configuration; it is verified during the pilot.

06Can we start with one team?+

Yes. A representative operation validates planning, mobility, evidence, integrations and billing cycle before extension.

Control operations

Make margin follow the actual pace of the fleet.

Map one complete mission from planning to billing to build an initial Carrier scope.

Talk to an expert