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


CANDOR TMS · Shipper edition
A shipper journey from transport demand to service control.
Shipper vulnerabilities
Emails, files and orders do not provide a consolidated view of demand.
Availability, rates and constraints are compared too late or without shared evidence.
Tracking depends on calls and statuses whose source or freshness remains ambiguous.
Rate, service, evidence and amount are not reconciled in the same file.
Shipper cycle
Operational control
CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

Orders, volumes, dates, sites and constraints become a qualified portfolio before decision.
Test a scenario
Panel, rates, capacity, service and allocation rules remain visible with the decision.
Test a scenario
Available milestones reveal variances that genuinely require action.
Test a scenario
Control compares terms, actual service, evidence and invoice under the planned workflow.
Test a scenarioShipper lab
Sourcing events, responses, exception and allocationSituation
Demand is confirmed but no provider has accepted within the planned time.
Core capabilities

Selected capability
Bring orders, sites, dates, volumes and constraints into qualified transport demand.
Shipper composition
CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.

Demand, sourcing, allocations, tracking, evidence and reconciliations within scope.
Foundation
Orders, responses, statuses, documents and evidence shared under configured rights.
Scope dependent
Spend, service, capacity, variances and panel analysed with defined indicators.
Explore the module
Collection, sorting, consolidation, distribution, evidence and returns connected to the Shipper edition.
Explore the moduleSystem responsibilities
CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.
Owns demand, sourcing, allocation, tracking and service control.
Retain order, customer, item, terms and commercial document.
Owns inventory, fulfilment, dock, loading and shipment confirmation.
The provider executes and documents; finance approves and posts under its rules.
Shipper ecosystem
CANDOR Shipper owns demand, sourcing, allocation, tracking and transport control. ERP or OMS retains the order, WMS fulfils, the provider executes and finance posts.
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 brochureShipper questions
Organisations that procure or organise transport for their goods and manage a provider panel.
Not necessarily. Portal, API, EDI or files can be selected according to each partner’s equipment, volume and integration level.
Photos, signatures, scans, reservations and documents can join the file from mobility, portal or interface under defined rights and controls.
Yes in one shared view, provided rules, rights, events and responsibilities for each execution model remain distinct.
The file brings together contract, rate, service, available events and evidence. Tolerances, approvals, disputes and financial exchange are configured for the organisation.
Yes. A representative flow, identified panel and complete control validate data, rules, interfaces and adoption before extension.
Take back control
Map your demand, panel, evidence and controls to build an initial Shipper scope.