EN Search Partner portal NavigatorTalk to an expert
CANDOR TMS solution

Choose a TMS: scope shipper, carrier, fleet and delivery evidence

Start from orders, constraints, resources, assignments, evidence and reconciliation rules rather than a tracking map.

Take the assessmentNavigator
For: Transport, logistics, operations, fleet, customer service, finance and IT leaders
01 · Short answer

What to clarify before discussing a solution

The signal

Routes are adjusted outside the system, field events arrive through messages and reconciliation requires investigation.

The answer

Which operating model should prevail across demand, planning, field execution, evidence and invoicing?

The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.
The expected outcome

An explicit TMS scope by role, flow and operating mode, with a defined demonstration scenario and KPIs.

02 · Structural decisions

Four decisions to make before configuration

These decisions make the scope testable and prevent structural choices from being discovered during the project.

01

Distinguish shipper and carrier responsibilities

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

02

Define constraints and replanning latitude

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

03

Choose the expected field events

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

04

Connect service delivered, reservations and reconciliation

The decision must specify the rule, its owner, the required data and the evidence used to accept it.

03 · Scope

A readable end-to-end flow

Scope is not a list of modules. It is a chain of events, ownership and decisions.

1Transport demand
2Planning and assignment
3Driver assignment
4Tracking and exception
5POD and reconciliation

In the first scoping

  • One representative flow and its useful variants
  • Authoritative events and minimum data
  • Roles, decisions and escalation times
  • Acceptance criteria and baseline measurement

To sequence in waves

  • Additional sites, activities or populations
  • Rare variants that do not condition the pilot
  • Automations whose rule is not yet stable
  • Advanced dashboards after source reliability

To decide explicitly

  • Distinguish shipper and carrier responsibilities
  • Define constraints and replanning latitude
  • Choose the expected field events
  • Connect service delivered, reservations and reconciliation
04 · Roadmap

From direction to measured improvement

  1. 1Navigator
  2. 2Personalised review
  3. 3Scoping workshop
  4. 4Wave-based deployment
  5. 5KPI measurement

Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.

05 · Metrics

Measure to decide, not to fill a dashboard

Every KPI needs a definition, a source, a cadence and an associated decision.

KPIFormulaSourceDecision
OTIFOn-time, in-full deliveries ÷ total deliveriesOrders, shipments and proof of deliveryPrioritise the causes that weaken the customer promise
Transport cost per unitConsolidated transport costs ÷ units deliveredServices, kilometres, charges and invoicingArbitrate transport plan, utilisation and providers
Empty kilometresUnladen kilometres ÷ total kilometresRoutes, geolocation and assignmentsRedesign routes and trip chaining
Complete delivery evidenceDeliveries with usable evidence ÷ closed deliveriesPOD, statuses, reservations and documentsReduce disputes and accelerate closure
Assessment

Assess your readiness

Six questions, an immediate reading and priorities adapted to your answers.

Start
06 · Business scenario

A scenario spanning planning, field and finance

Situation
An organisation manages its own fleet and external carriers. Operating decisions do not always leave usable evidence.
Approach
Scoping follows a real order from creation to reconciliation, documents each responsibility and tests exceptions affecting cost, time or evidence.
Target outcome
The TMS is assessed on control of the complete flow and the quality of decisions it enables.
This scenario illustrates a scoping method. Outcomes must be established with data from the selected scope.
07 · Frequently asked questions

Useful answers before the first discussion

01Where should we start in practical terms?

Choose a representative scope spanning “Transport demand” and “Planning and assignment”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.

02Do all existing systems need replacing?

No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.

03What data should be prepared before a workshop?

Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure OTIF. The quality of examples matters more than the quantity of documents.

04How should the right pilot scope be chosen?

Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.

05How can scope changes during the project be limited?

Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.

Next step

Turn this guide into a personalised review

Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.

  1. 1Navigator
  2. 2Personalised review
  3. 3Scoping workshop
  4. 4Wave-based deployment
  5. 5KPI measurement
NavigatorPlan a discussion with an expert
08 · Continue

Complementary guides

Guides by suite
EMS Commerce suite

Unify omnichannel commerce

Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.

  • Catalogue and pricing
  • Available-to-promise inventory
  • Order and allocation