senn-techTranslogica TMS: Transport-Management on-prem
A freight forwarder without a TMS is like a craftsman without a toolbox — theoretically capable of working, practically blind. Translogica is our system for that, and it runs on-premises for good reason.
What a TMS must accomplish
Dispatch, route planning, shipment recording, loading lists, freight documents, shipment tracking, invoicing — a TMS must be able to do all of this, and it must be able to do it fault-tolerantly. If the system goes down, the trucks don’t stop, but the dispatchers don’t know where to go.
Translogica covers the entire cycle and brings industry modules for freight forwarding, building materials trade, silo transport, and more. It’s not a generic logistics tool, but one that speaks the language of the industry.
Why on-prem?
Cloud-based TMS means: when the internet fails, dispatching grinds to a halt. On-prem on a local server means: the database runs in the internal network, and clients reach it via LAN. The internet uplink may fail — work continues.
This is no theoretical scenario. Excavators in the industrial zone, BGP peering issues with the provider, construction crews severing fiber optic cables — all of this has already happened.
Integrations and Customization
Translogica communicates with Winline via SQL interfaces, with external partners via EDIFACT and APIs, and recently also with our MCP server — so an agent can retrieve current shipment status data without anyone having to manually export.
Integration into n8n workflows is running: a status change triggers customer notification, delivery proof by email, exceeding the planned arrival time triggers escalation.
Fault Tolerance in the TMS
The rule of thumb is simple: the TMS database runs on the same SQL Server cluster as Winline, backup policy is identical, recovery time in a disaster scenario is under two hours. This is no luxury, but the foundation for ensuring that nothing stands still in logistics.
The Limits
Translogica is not a SaaS product and does not feel like one. Setup and updates require planning, the client is Windows-only, and the interface is optimized for function, not design awards. Those expecting a modern web UI will frown. Those wanting a system that keeps 200 trucks running will appreciate it.
Conclusion
On-prem logistics software is a decision for operational reliability. Translogica delivers that — without frills, but with the functionality that freight forwarders truly need. Its greatest strength: it keeps running even when externally nothing else does.
Why do you run Translogica on-prem instead of in the cloud?+
A cloud TMS paralyzes dispatch when the internet fails. On-prem, the database runs in the internal network and clients reach it via LAN — the internet uplink may fail and work continues. This is no theoretical scenario: excavators in the industrial zone, BGP peering issues at the provider, or a severed fiber optic cable have all already happened.
How does Translogica integrate with our existing systems?+
Translogica communicates with Winline via SQL interfaces, with external partners via EDIFACT and APIs, and recently also with our MCP server, so an agent can retrieve shipment status data without a manual export. In n8n workflows, a status change triggers customer notifications, sends delivery proofs by email, and escalates when the planned arrival time is exceeded.
What are the downsides of Translogica as an on-prem system?+
Translogica is not a SaaS product and does not feel like one. Setup and updates require planning, the client is Windows-only, and the interface is optimized for function, not design awards. In return, it keeps running even when externally nothing else does. The TMS database sits on the same SQL Server cluster as Winline, with recovery time under two hours.