Vigilo · AI operator for transport files
One continuous context, from request to control.
Vigilo connects the flows that create, enrich and verify a transport file. It adapts to your tools and operating methods, acts within its authorised scope and hands exceptions back with their context.
A simple definition
A transport file is not another software tool.
It is the continuity of information, documents, rules and actions needed to understand an operation. That context may remain distributed across several systems.
Vigilo works within that environment so the history of the file is not lost between the order, the actual operation and invoicing.
Request
What is requested and the information received.
Actionable file
The context, rules and data required to proceed.
Actual operation
What actually happened and the supporting documents.
Billable
What must be valued under the applicable rules.
Control
Differences between the plan, the actual operation and the invoice.
How Vigilo adapts to your environment
Your operating model shapes Vigilo, not the other way around.
There is no required TMS or imposed standard process. This adaptability comes from a shared product foundation followed by focused configuration. Every source, interface and action is tested in your environment before it goes live.
Sources and formats
Emails, documents, EDI, portals and customer-specific formats are connected to the same file.
Rules and decisions
Your routines, approval thresholds and exceptions become an explicit, supervised framework.
Software and action methods
Vigilo works with your TMS and business tools, through an API when appropriate or through the interface when needed.
Controls and permissions
Permissions, post-action checks and handoffs to your team are configured around your risk level.
Choose the first workflow
Start with order intake or invoice control.
Each scope is framed and deployed around its own sources, rules and authorised actions.
Upstream
Order intake
Understand the request, retrieve the relevant context, check completeness and prepare or perform the action in the TMS.
Explore this scopeDownstream
Invoice control
Reconcile the plan, the actual operation and the invoice, identify discrepancies and prepare the context needed to resolve them.
Explore this scopeThe right level of autonomy
What Vigilo handles depends on the approved framework.
A workflow is first understood, tested and supervised before any action is authorised within a stable scope.
Defined rules and access
Every action is tied to an authorised scope, rule and tool.
Traceable actions
The expected operation includes verification and logging.
Exceptions handed back
New, ambiguous or sensitive cases are handed back to a team member.
Next step
Where in the transport file would you like to start?
Choose a focused first workflow. We frame its sources, rules, possible actions and exceptions with your team.
Discuss your workflow