Fragmented data
Needs, rates, capacity and statuses circulate through heterogeneous files and exchanges.
CANDOR TMS · Transport Management System
Centralise your transport.
Control every movement.
Bring needs, constraints and responsibilities together before building the plan.
01 / 05
Silent losses
What weakens margin, service and decision capacity.
Fragile plan
Unavailability or delay challenges the plan without making the trade-off visible.
Late evidence
POD, reservations and documents arrive after controls or remain difficult to attach.
Opaque outcome
Planned cost, executed service, actual charge and invoice do not always share one file.
An end-to-end flow
From demand to control, every stage remains connected.
Operational benefits
Transport control based on connected facts.
CANDOR owns the plan, allocations, mission and transport control. ERP, WMS, finance, telematics and partners retain their own responsibilities.
01
An explainable transport plan
Rules, constraints, options and approvals used to build the plan remain visible.
Test a scenario
02
Execution qualified by events
Every status retains its source, timestamp, freshness and impact on the mission.
Test a scenario
03
Evidence connected to the commitment
Documents, incidents and POD remain linked to the relevant order, mission and control.
Test a scenario
04
Analysis connected to actual execution
Service, cost, capacity and provider are analysed from validated definitions and sources.
Test a scenarioDecision lab
Resolve situations that change the plan or outcome.
Cause, options, decision, author and revised planSituation
Capacity unavailable
The planned resource is no longer available while a delivery commitment exists.
Signals to examineFile constraintsAlternative capacityCost and service impact
Expected decisionCompare authorised options, make the trade-off visible and publish a coherent revised plan.
Retained evidenceCause, options, decision, author and revised plan
Functional scope
Explore CANDOR TMS without confusing orchestration and source systems.
Selected capability
Transport demand
Collect, qualify, consolidate and prioritise needs with their context.
- The demand, capacity, time window and constraints required for « Transport demand » are acknowledged before departure.
- « Transport demand » milestones, incidents and evidence remain linked to the mission and their source.
- Every « Transport demand » variance retains the decision, cost, informed party and next action.
Two responsibilities, two editions
Choose the perspective that matches your business.
CANDOR TMS · Transport Management System
CANDOR TMS Shipper
For organisations that express demand, source and manage providers, monitor service and control freight spend.
Explore this edition
CANDOR TMS · Transport Management System
CANDOR TMS Carrier
For operators that plan fleet and drivers, execute missions, collect evidence and manage their outcome.
Explore this editionModular composition
A transport foundation extended by clearly named modules.
CANDOR owns the plan, allocations, mission and transport control. ERP, WMS, finance, telematics and partners retain their own responsibilities.
Driver mobilityCANDOR RAFIK
Missions, instructions, milestones, incidents and field evidence according to the configured mobile journey.
Explore the module
Transport visibility
CANDOR Tracking
Milestones, ETA, statuses and exceptions shared according to genuinely available sources, rights and frequencies.
Explore the module
Control module
CANDOR BI
Indicators, dimensions, alerts and analyses connected to validated events and definitions.
Explore the module
Edition-dependent module
Fleet and maintenance
Availability, due dates and interventions when this scope is selected for carrier operations.
Explore the module
Exchange module
EDI and interfaces
Messages, controls, monitoring and recovery for explicitly configured flows and partners.
Explore the module
CANDOR TMS module
Parcel operations
Collection, sorting, consolidation, distribution, evidence and returns connected to the selected Shipper or Carrier edition.
Explore the moduleSystem responsibilities
Information moves. Its owner does not disappear.
CANDOR owns the plan, allocations, mission and transport control. ERP, WMS, finance, telematics and partners retain their own responsibilities.
Transport plan and control
Owns transport demand, plan, allocation, mission, events and controls within the selected scope.
- Plan and mission
- Events and exceptions
- Transport reconciliation
Order and master data
Retain commercial orders, parties, items, terms and documents according to architecture.
- Source order
- Parties and items
- Commercial terms
Physical warehouse execution
Owns physical inventory, fulfilment, loading and shipment confirmation within its scope.
- Inventory and fulfilment
- Dock and loading
- Shipment
Specialised sources and processing
Retain financial posting, location, vehicle data or partner service under their contracts.
- Finance and settlement
- Position and vehicle
- Partner event
Connected architecture
Explicit exchange contracts, not assumed real time.
CANDOR owns the plan, allocations, mission and transport control. ERP, WMS, finance, telematics and partners retain their own responsibilities.
CANDORTMS
ERP
OMS
WMS
Finance
Telematics
EDI
BI
Controlled deployment
Start with one complete, representative flow.
Observe
Flows, actors, constraints and exceptions
Scope
Responsibilities, data and business rules
Map
Events, interfaces and controls
Configure
Journeys, rights, alerts and documents
Pilot
A representative and measurable scope
Deploy
Adoption, extension and continuous improvement
Resources and methods
Explore CANDOR TMS with immediately useful material.
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
Frequently asked questions
Clarify role, scope and success conditions.
01What is the difference between Shipper and Carrier?+
Shipper starts from shipping demand, sourcing and provider control. Carrier starts from orders, resources, drivers, missions and operating outcome.
02Is Messaging a third edition?+
No. Messaging is a CANDOR TMS module. The only two organisational editions are Shipper and Carrier.
03Is geolocation always available?+
It depends on authorised sources, selected telematics or mobility, exchange frequency and project rights.
04Can existing ERP, WMS and finance systems be integrated?+
Yes when available connectors, APIs, EDI or files cover required data and controls. Scoping documents version, frequency, responsibility, error and recovery for every flow.
05SaaS or on-premise?+
Both models are available. The choice depends on operational, security, integration and continuity constraints validated with the project.
06How can we start without disrupting operations?+
With a representative flow, clear responsibilities, controlled data, a pilot and extension criteria defined before rollout.
Your next step
Make transport readable before optimising it.
Map one flow, its decisions, sources and evidence to define the right edition and scope.