Variable arrivals
Actual volumes and priorities may emerge after the first plan has been built.
Back to CANDOR TMS
Absorb the volume.
CANDOR TMS · Parcel operations module
Absorb the volume.
Keep every parcel in the flow.
Connect collection, sorting, consolidation, distribution, evidence and returns in one timeline, without creating a third CANDOR edition.
Parcel operations extend CANDOR TMS: they are neither a standalone solution nor a third edition beside Shipper and Carrier.
Product positioning
One operational module. Two possible editions.
The organisation’s actual role determines the edition. Parcel operations add parcel, collection, consolidation and distribution context to the selected CANDOR foundation.
01 · If you organise and control the service
Shipper edition
Centralise demand, build service rules, allocate partners and control evidence, costs and commitments.
Explore this edition
02 · If you execute with your resources or partners
Carrier edition
Compose collection, sorting, routes and distribution with your depots, drivers, vehicles, subcontractors and billing rules.
Explore this editionOperational pressure
When volume rises, every information break becomes a service break.
Misrouted parcel
A dock, route or status error can make investigation longer than corrective action.
Route under pressure
Capacity, time windows, traffic, absences and failed deliveries require visible trade-offs.
Incomplete evidence
A missing signature, reservation or status update weakens service and financial control.
End-to-end parcel flow
From first scan to closure, a parcel never loses its context.
Each hand-off turns a physical unit into an actionable event, with an identified responsibility and next action.
Decision lab
Test the situations that can overturn a route.
The lab does not promise an automatic decision: it shows the facts to reconcile, the trade-off to make and the evidence to retain.
Selected option, reason, approval and affected parcels01 / 04
A priority batch arrives after sorting closes.
Context
The parcels are qualified, but their volume and commitments change the capacity of routes already built.
Signals to examine
- Volume and destinations
- Residual capacity
- Service windows
Expected decision
Reopen a route, create an additional departure or postpone under validated priority rules.
Retained evidence
Selected option, reason, approval and affected parcels
Module capabilities
Compose the module around your actual responsibilities.
Each capability is activated, configured and connected to the Shipper or Carrier edition selected during scoping.
Selected capability
Parcel and service catalogue
Structure units, formats, weights, volumes, services, priorities, destinations and useful flow constraints.
Data qualified before planningSystem responsibilities
One shared timeline, responsibilities that remain distinct.
CANDOR composes the mission and its events. Source systems retain their own truth: commercial order, physical inventory, identity, telematics and accounting.
ERP / OMS
- Owns
- Customer, item, sold service, terms and commercial document.
- Exchanges
- Demand, reference, destination, terms and status update.
WMS / hub
- Owns
- Physical receipt, location, material sorting, dock, fulfilment and loading.
- Exchanges
- Unit, availability, hand-off, shipment and physical exception.
CANDOR TMS
- Owns
- Plan, route, allocation, mission, event, evidence and transport control.
- Exchanges
- Instruction, status, exception, evidence and billable item.
Finance / partners
- Owns
- Finance approves and posts; the partner executes and documents under its rights.
- Exchanges
- Rate, evidence, pre-bill, invoice, payment and dispute.
Connected architecture
One shared timeline, responsibilities that remain distinct.
CANDOR composes the mission and its events. Source systems retain their own truth: commercial order, physical inventory, identity, telematics and accounting.
Source, frequency, version and recovery are defined flow by flow.CANDORParcel
ERP / OMS
WMS
CANDOR RAFIK
Telematics
Customer portal
Carriers
Finance / BI
Controlled deployment
Start with one depot, one service and one complete loop.
Scope
Volumes, services, actors, sites and constraints
Map
Scans, statuses, responsibilities and exceptions
Connect
Reference data, orders, mobility and interfaces
Configure
Sorting, routes, rights, evidence and alerts
Pilot
A representative collection-distribution loop
Extend
Depots, services, partners and improvement
Resources and methods
Explore the module with immediately usable material.
CANDOR TMS: editions, capabilities and architecture
Position Parcel Operations within the CANDOR foundation and its two business editions.
Download the brochure
Map a parcel flow before configuring routes
Identifiers, events, evidence and responsibilities to clarify.
Explore guides
Connect fulfilment, distribution, evidence and control
Understand boundaries between WMS, TMS, mobility and finance.
Explore cases
Move from scan events to operational control
Build useful visibility without confusing signal and decision.
Explore webinarsFrequently asked questions
Clarify the module’s role before discussing features.
01Is CANDOR TMS Parcel Operations a standalone solution?+
No. Parcel Operations is a CANDOR TMS module. It extends the Shipper or Carrier edition determined by the organisation’s actual role.
02Does Parcel Operations become a third edition?+
No. The two organisational editions remain Shipper and Carrier. Parcel context is composed within the relevant edition.
03How do we choose the parent edition?+
Scoping examines who owns demand, planning, execution, resources, subcontracting, evidence and billing.
04Does the module cover every parcel flow?+
The exact scope depends on confirmed services, volumes, sites, actors, equipment, interfaces and rules. Universal coverage is not assumed.
05Can it exchange with an existing WMS and ERP?+
Yes through available standard connectors, APIs, EDI or files, with a source of truth, version, frequency and recovery procedure defined for each flow.
06Which events can feed tracking?+
Scans, mobility statuses, telematics, portals and interfaces can contribute after their meaning, quality, timestamp, priority and distribution rights are validated.
07How can we start without disrupting operations?+
A pilot limits scope to one depot, one service, one complete loop, a representative volume and recovery procedures before extension.
Your next step
Let’s map one complete parcel flow, not a feature list.
Start with one depot, one service, its events and exceptions to build a useful, verifiable Parcel Operations scope.