- Who is this for?
- Transport operations teams, transport managers and IT teams
- Question addressed
- Structure the management of multichannel inbound transport flows.
Key takeaways
- The same shipment may be created through EDI and later amended by email or phone.
- Every event must retain its source, timestamp and effect on the record.
- The priority is to link information to the correct context, not to force every channel into the same format.
- Conflicts between two sources require either a precedence rule or an escalation.
Why a single channel is not enough
A portal may create the order, a phone call may bring the time slot forward and an email may attach the corrected document. If each channel is handled in a separate queue, the team must manually reconstruct the timeline before every decision.
The right model is therefore not an “automated inbox”, but a transport record that receives events. The record maintains the current state while retaining previous versions and the reason for every change.
A typical multichannel sequence
- 0108:12 · EDI
A new order provides a customer reference and the initial data.
- 0208:29 · Portal
A time slot is confirmed and added to the record.
- 0310:04 · Email
The customer changes the number of pallets and attaches a document.
- 0411:17 · Transcribed call
The contact asks to be notified before arrival.
- 05After processing
The TMS and the audit history must reflect the retained information and its sources.
Continuity rules to define
- which identifiers can link an event to a record;
- which source takes precedence for each type of information;
- which changes may be applied automatically;
- which timing conditions or changes require validation;
- how to retain a trace of a replaced value;
- who receives events that cannot be linked to a record.
Start with an observable scope
A pilot can begin with one order type and two common channels. The initial objective is to measure linkage quality and understand the exceptions before adding further sources or authorizing more actions.
This progression prevents theoretical coverage from being mistaken for reliable operation. A channel is truly covered when it is observed, understood, linked and controlled within the relevant workflow.
Frequently asked questions
Direct answers
Can phone calls become part of the transport record?
A transcript or written summary can become an event when the channel, consent and expected quality have been properly defined. The site does not imply that this capability is active everywhere.
How should conflicting information be handled?
The workflow applies the approved precedence rule or routes the decision to the team with both sources.
Do all tools need to be centralised?
No. Vigilo connects the context while keeping data and actions in the tools selected for the workflow.
Sources and methodology
This resource describes Axonovia's product approach based on transport workflows. The examples are illustrative and do not constitute a performance commitment or a universally applicable contractual rule.
Product review: Axonovia team · next review recommended before 31 August 2027 or following a material change in scope.