💡 Three questions are in focus:
Is there already a list of supported TMS/DMS systems?
How is data transferred to downstream systems?
How does ExB integrate into existing EDI systems?
We provide a clear overview – based on the current state of our projects.
Are there standard integrations with TMS/DMS systems? In short: No – and that’s not necessary.
In short: No – and that’s not necessary.
In ongoing projects, ExB takes a pragmatic approach. Instead of directly plugging into transport management or document management systems, integration usually happens via an indirect approach. This means the surrounding systems (e.g., a TMS) export data in a standardized format – such as a CSV file on an SFTP server. ExB accesses these files, processes them, and delivers structured information back.
The advantage: This type of integration is independent of the system in use. Whether Comalog or another TMS – as long as an export is possible, ExB can process the data. This provides maximum flexibility without costly interface development.
Direct integrations – i.e., full access to the TMS/DMS – are technically possible but much more complex and so far have not been required. If needed for a specific project, implementation can be tailored accordingly.
How is data transferred to downstream systems?
Here too, ExB relies on proven mechanisms: The platform generates import files – for example, XML – and places them in a defined target location (such as an SFTP). From there, the target system can automatically take over.
The underlying principle: ExB integrates seamlessly into existing data flows without fundamentally changing them. Responsibility for the import lies with the target system – ExB provides reliable data. The workload for the IT department remains minimal.
EDI systems: Complement or competition?
EDI (Electronic Data Interchange) is a widely used standard for digital document exchange. Many companies therefore ask: How does ExB fit into existing EDI processes?
The answer: ExB does not replace an EDI system – and it doesn’t compete with it either. On the contrary, both solutions complement each other well. While EDI depends on structured, standardized data, ExB also processes analog and unstructured formats – such as scanned delivery notes, handwritten additions, or PDFs with individual layouts.
Direct integration into EDI systems is not yet available as a standard. Again, the focus is on an individual assessment: Which systems are in place? What data formats are used? Which interfaces are available?
Conclusion: ExB integrates where it makes sense – without major IT projects
The key to fast and effective system integration lies in the modular, file-based approach. Instead of complex direct connections, ExB builds on existing exports and imports – a solution that has proven robust and scalable in practice.
Direct connections, EDI integrations, or more complex scenarios are possible in principle, but require individual consideration. The rule of thumb: ExB adapts to the customer’s IT landscape – not the other way around.
Would you like to know how ExB fits into your system landscape?
Get in touch with us – we’ll find the most efficient way.
