Realistic plan
Transport uses the real state of picking, docks and capacities.
Capabilities Unified transport & distribution
Capability · Unified transport & distribution
Transport and distributionshould never be managed separately.
Connect order, allocation, picking, dock, route, delivery, proof and cost in one flow, without blurring each system’s responsibility.
A capability shaped by your flows, rules and field evidence.
01 / 0402 / 0403 / 0404 / 04
Visible execution
Operations, customer and partners share understandable milestones.
Connected proof
POD, reservation, return and document remain attached to the correct record.
Reconciled cost
Planned service is compared with what was actually executed.
Decision framework
Connect promise, responsibility and proof.
Unification does not mean one system does everything. It means each relay receives the right event, makes its decision and returns usable proof.
Gaps to eliminate
What weakens day-to-day decisions.
Each gap connects an observable situation to a business consequence. Diagnosis then verifies frequency, impact and cause.
Unknown readiness
TMS plans without knowing whether goods or dock will be ready.
Waiting, replanning and extra costMisaligned statuses
Order, shipment and mission use different identifiers and milestones.
End-to-end view rebuilt manuallyPartners outside the flow
Carriers, drivers and customers communicate by email or phone.
Late decision and scattered proofDisconnected finance
Billing, dispute and cost cannot retrieve actual execution.
Margin and service hard to explainOperational journey
A chain of decisions, not a stack of screens.
Each transition identifies the participant, responsible system and expected proof.
1
Demand
Create transport demand
Order, destination, window, units, constraints and service are qualified.
- Owner
- ERP / OMS
- Proof
- Identifiable requirement
2
Allocation
Confirm origin
Site, stock and availability date become firm for transport.
- Owner
- OMS / WMS
- Proof
- Expected shipment
3
Picking
Make physical flow ready
Picking, control, consolidation, weight, volume and dock are confirmed.
- Owner
- PROTECH WMS
- Proof
- Ready to load
4
Transport plan
Assign capacity and mission
Equipment, carrier, driver, sequence and slots are planned.
- Owner
- CANDOR TMS
- Proof
- Mission acknowledged
5
Execution
Track useful milestones
Loaded, departed, ETA, incident, arrived and delivered return from their sources.
- Owner
- TMS / mobile / partners
- Proof
- Timestamped events
6
Close
Reconcile proof and finance
POD, reservation, return, cost and billing are consolidated.
- Owner
- TMS / ERP / finance
- Proof
- Defensible transport record
Decision lab
Change context. Follow what genuinely needs to happen.
These scenarios are illustrative: they show decision logic and responsibilities without claiming to simulate your actual outcomes.
Long-haul transport
Synchronise dock with scarce capacity
Transport slot is firm but picking is slipping.
Reprioritise the wave or reassign the slot based on customer impact.
New decision shared by WMS, TMS and customer.
B‑AGILEdecision flowERP / OMSPROTECH WMSCANDOR TMSMobilité / portailsBI
Urban parcel
Absorb late volume without losing the route
Priority parcels arrive after initial close.
Compare insertion, dedicated shuttle or deferment using SLA and capacity.
Choice, cost and impacted customers retained.
B‑AGILEdecision flowERP / OMSPROTECH WMSCANDOR TMSMobilité / portailsBI
Store replenishment
Serve the store without shifting the stockout
A critical store falls below threshold while a route is being built.
Integrate the need if stock, dock and capacity remain compatible.
Availability, sequence and ETA recalculated.
B‑AGILEdecision flowERP / OMSPROTECH WMSCANDOR TMSMobilité / portailsBI
E-commerce delivery
Turn delivery failure into a controlled action
Recipient is absent and proof is incomplete.
Qualify reason, replan or return based on contract and preference.
New action linked to the order and parcel.
B‑AGILEdecision flowERP / OMSPROTECH WMSCANDOR TMSMobilité / portailsBI
Responsibility architecture
Unify the flow without pretending one system does everything.
The responsibilities below form a reference architecture to adapt to the existing IT landscape.
ERP / OMS
Carries commitment- Owns
- Order, promise, customer and management billing
- Publishes
- Requirement and priority
PROTECH WMS
Carries fulfilment- Owns
- Stock, units, picking, consolidation and dock
- Publishes
- Ready, weight, volume and departure
CANDOR TMS
Carries transport- Owns
- Resource, mission, route, milestones and cost
- Publishes
- Assignment, ETA and status
Mobilité / portails
Carries the field- Owns
- Instruction, acknowledgement, proof and interaction
- Publishes
- Events and documents
BI
Carries insight- Owns
- Definitions, history and reconciliation
- Publishes
- Service, cost and exceptions
Actionable cockpit
Shared shipment timeline
Value comes from a reliable sequence: validated demand, confirmed ready, assigned vehicle, departure, ETA, POD, dispute and invoice.
- OTIFConnect promise to outcome
- Dock waiting timeSeparate transport delay from warehouse unavailability
- Cost per missionExplain transport margin
- Complete PODAccelerate close and billing
Operational view · example
Unknown readinessMisaligned statusesPartners outside the flow
Success conditions
What must be true before automation.
Reconciliable identifiers
Order, shipment, logistics unit, mission, delivery and proof link without re-entry.
Governed events
Each milestone has a source, frequency, owner and recovery rule.
Integrable partners
Portal, app, API, EDI or file are selected based on partner and risk.
Controlled access
Customer, driver, carrier and operations see only their scope.
Related B‑AGILE solutions
Compose the right scope.
A capability may be carried by a full suite, a standalone solution or an existing system. Diagnosis decides.
Suite
EMS Logistics
Integrated response for warehouse, transport, record and control.
Explore SolutionCANDOR TMS
Plans, assigns, tracks and closes transport missions.
Explore SolutionPROTECH WMS
Picks, consolidates, controls and confirms physical flow.
Explore SolutionESSOR ERP
Carries order, master data, management and financial reconciliation.
ExploreGo further
Content to prepare a real discussion.
Frequently asked questions
Decide with the right boundaries.
Which systems must be connected?
Only those carrying a useful flow responsibility: order, fulfilment, transport, proof, finance or customer information.
Does TMS replace WMS?
No. WMS carries stock and fulfilment; TMS carries resources, missions and transport execution.
How are exceptions managed?
With a qualified event, owner, action window, decision and closure feedback linked to the record.
Can a carrier connect without an app?
Yes, via portal, EDI, API or file depending on maturity and required events.
Are ETAs always real time?
No. Frequency and accuracy depend on source, connectivity and calculation method.
Can we start with a pilot flow?
Yes. One site, one carrier and one delivery type can validate identifiers, events and adoption.
Your context first
Unify the decision flow, from stock to customer.
Identify the decisions, data, responsibilities and pilot that will deliver observable value.