CANDOR TMS · Shipper edition

Control your flows,
your carriers and every committed euro.

A shipper journey from transport demand to service control.

01 / 05

Shipper vulnerabilities

What weakens transport promise, capacity and spend.

01

Fragmented demand

Emails, files and orders do not provide a consolidated view of demand.

02

Uncertain capacity

Availability, rates and constraints are compared too late or without shared evidence.

03

Declarative service

Tracking depends on calls and statuses whose source or freshness remains ambiguous.

04

Hard-to-explain invoice

Rate, service, evidence and amount are not reconciled in the same file.

Shipper cycle

From demand to control, a connected chain of decisions.

01DemandFlow and constraints
02SourcingPanel and terms
03SelectionDocumented criteria
04Transport orderAssigned mission
05TrackingMilestones and exceptions
06EvidencePOD and reservations
07ControlService and spend

Operational control

Decide with a shared reading of demand, actual execution and evidence.

CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

01

Consolidated transport demand

Orders, volumes, dates, sites and constraints become a qualified portfolio before decision.

Test a scenario
02

Explainable selection

Panel, rates, capacity, service and allocation rules remain visible with the decision.

Test a scenario
03

Exception-oriented tracking

Available milestones reveal variances that genuinely require action.

Test a scenario
04

Spend reconciled with service

Control compares terms, actual service, evidence and invoice under the planned workflow.

Test a scenario

Shipper lab

Resolve situations where service, cost and capacity diverge.

Sourcing events, responses, exception and allocation

Situation

No response for the slot

Demand is confirmed but no provider has accepted within the planned time.

Signals to examineEligible panelNon-negotiable constraintsEscalation threshold
Expected decisionExpand under the rules, compare impacts and submit the exception to the authorised role.
Retained evidenceSourcing events, responses, exception and allocation

Core capabilities

Control the service without absorbing execution-system responsibilities.

Selected capability

Demand and consolidation

Bring orders, sites, dates, volumes and constraints into qualified transport demand.

  • The demand, capacity, time window and constraints required for « Demand and consolidation » are acknowledged before departure.
  • « Demand and consolidation » milestones, incidents and evidence remain linked to the mission and their source.
  • Every « Demand and consolidation » variance retains the decision, cost, informed party and next action.

Shipper composition

A control foundation extended according to network and exchanges.

CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

Shipper foundation

Freight procurement control

Demand, sourcing, allocations, tracking, evidence and reconciliations within scope.

Foundation
Partner module

Carrier portal

Orders, responses, statuses, documents and evidence shared under configured rights.

Scope dependent
Control module

CANDOR BI

Spend, service, capacity, variances and panel analysed with defined indicators.

Explore the module
CANDOR TMS module

Parcel operations

Collection, sorting, consolidation, distribution, evidence and returns connected to the Shipper edition.

Explore the module

System responsibilities

The Shipper orchestrates transport. Every actor retains its execution.

CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

01CANDOR Shipper

Transport decision

Owns demand, sourcing, allocation, tracking and service control.

  • Demand and panel
  • Allocation and tracking
  • Transport control
02ERP · OMS

Commercial order

Retain order, customer, item, terms and commercial document.

  • Source order
  • Customer and item
  • Commercial invoice
03WMS

Physical fulfilment

Owns inventory, fulfilment, dock, loading and shipment confirmation.

  • Physical inventory
  • Fulfilment
  • Loading
04Carrier and finance

Execution and posting

The provider executes and documents; finance approves and posts under its rules.

  • Field mission
  • POD and event
  • Financial posting

Shipper ecosystem

Connect order, fulfilment, transport and control without blurring roles.

CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

CANDORTMS
ERP
OMS
WMS
Procurement
Finance
Carriers
EDI

Progressive deployment

Start with one flow, one panel and one complete control.

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 shipper 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

Shipper questions

Clarify panel, evidence, billing and integrations.

01Who is the Shipper edition for?+

Organisations that procure or organise transport for their goods and manage a provider panel.

02Must carriers use CANDOR TMS?+

Not necessarily. Portal, API, EDI or files can be selected according to each partner’s equipment, volume and integration level.

03How is delivery evidence managed?+

Photos, signatures, scans, reservations and documents can join the file from mobility, portal or interface under defined rights and controls.

04Can we manage internal fleet and providers?+

Yes in one shared view, provided rules, rights, events and responsibilities for each execution model remain distinct.

05How is the freight invoice reconciled?+

The file brings together contract, rate, service, available events and evidence. Tolerances, approvals, disputes and financial exchange are configured for the organisation.

06Can we start with one flow?+

Yes. A representative flow, identified panel and complete control validate data, rules, interfaces and adoption before extension.

Take back control

Make every freight euro an explainable decision.

Map your demand, panel, evidence and controls to build an initial Shipper scope.

Talk to an expert