Operational logistics, rethought

ToShift OS is an operating system for the operational logistics of manufacturers, retailers, freight forwarders and logistics service providers. Every role along your processes works in one system, from dispatchers to goods receiving to plant management. To do this, ToShift OS has four levels. The operational level runs day-to-day business, the administrative level maintains the processes. Management pulls up metrics, and the learning level turns deviations into improvements. ToShift OS sits on top of ERP, warehouse, transport and yard without replacing them. People no longer operate the systems. They run ToShift OS.

Mainly processes where someone currently moves data by hand from one system to another or has to make complex decisions. Examples are transport orders from emails into the TMS, Advanced Shipping Notices and delivery notes at goods receipt, dock assignment, recording dwell times, identifying and adjusting critical paths in plant logistics, detecting deviations, and checking freight invoices, for example against the SAP freight cost document. Everything is connected, and our agents propose concrete improvements for each individual process. You start with a single process from your own day-to-day business.

For manufacturers, retailers, freight forwarders and logistics service providers with their own operational logistics, such as companies with SAP EWM, SAP TM, LE-TRA or SAP LGM, and forwarders who transfer orders into their TMS. ToShift OS fits where processes today run by hand between inbox, phone, Excel and system, with people acting as the interface between the systems.

Yes. Each ToShift app takes over one process from start to finish and runs on its own, even without ToShift OS. On ToShift OS, the apps share knowledge and permissions, and a case continues across system boundaries.

No. ToShift OS sits on top of the existing systems and replaces none of them. SAP, TMS, warehouse and yard management remain the systems of record and continue to be operated as before. ToShift OS reads what comes in, prepares cases and writes back only what a person or a company rule has approved. No migration or parallel project is needed.

ToShift is neither an SAP integrator nor an IT consultancy. ToShift delivers an operating system that sits on top of the existing systems and works through their released interfaces, and with SAP without touching the core (Clean Core). The business team defines the processes in ToShift OS itself and changes them without an IT ticket and without consulting days. What is built there stays in-house.

Yes, through the interface the TMS provides. ToShift OS takes transport orders from emails, prepares them and, once approved, hands them over to the TMS. The TMS remains the system of record and is operated as before. Whether and how the vendor opens up its interface is something ToShift works out with the customer at the start.

Yes, through the interfaces released by SAP. Ready-made processes exist for LE-TRA and SAP TM (checking freight invoices against the SAP freight cost document), for SAP LGM (choosing the parcel carrier, including a print-ready label) and for yard and dock with ToShift YardOps, which also takes over SAP freight orders. For SAP EWM, the connection is scoped process by process.

All data is hosted in the EU, in a separate instance for each customer. Each company decides where that instance runs: in-house, on its own servers at an EU provider, or on ToShift servers in Germany. The software is the same in all three cases.

No. The data does not go to the providers of the language models. Steps that decide a case run on open language models that can be operated on your own servers. The model is interchangeable. The language models are used within the EU.

Routine work goes straight through. Where something deviates, a person decides. How independently an agent works is up to the company. There are three levels. The agent only reads and makes suggestions, it submits every case for approval, or it handles routine cases on its own within the defined limits. What goes to the TMS or SAP is decided by a person or a company rule, never by the language model alone. An agent never has more permissions than the role it takes on.

In the case, every recognized field is shown with its location in the document. If anything deviates from the Advanced Shipping Notice, the master data or a customer rule, the case stops and a person decides. The system reads barcodes, a language model reads free text, and a person reads handwriting. If there is no clear match, the case goes to the person responsible. Every step is traceable.

ToShift works with technology partners and networks from logistics and the digital economy. Technology partners are SAP, AGILOX and prismat, which develops SAP add-ons. Networks include the Open Logistics Foundation, Logistik-Initiative Hamburg, the BVL, Digital Hub Hamburg, Gründungswerft and TED AI. An overview is available on the partner page.

ToShift needs access to the inbox and to the affected systems such as SAP or TMS, plus alignment with the vendor or IT service provider. Also a contact on the business team with decision-making authority, and a description of the process with its rules. At the start, the business team approves every case. Its corrections become rules and entries in the knowledge base before routine cases run on their own.

Mainly how quickly the vendor of your system of record grants interface access. First, the dedicated instance, the inbox, the knowledge base and the approvals are set up. Then the agent runs alongside real cases. The handover into the system of record, such as SAP or TMS, follows as soon as access is in place.

The cost depends on scope and operating model: which processes are connected, and whether ToShift OS runs in-house, at an EU provider or at ToShift. That is why there are no fixed prices on the website. The Digital Maturity Assessment as a starting point is free, with no obligation.