The operating system for operational logistics
ToShift OS reads emails and documents and creates cases from them in ERP, warehouse, transport and yard. People no longer operate the systems. They run ToShift OS.
ToShift OS is the interface
ToShift OS picks up what comes in from email, WhatsApp and SAP, and writes the result back. If a case needs a decision, it goes to your team first.
Your systems remain the system of record. No migration or parallel project is needed.
Chat
You ask ToShift OS as you would a colleague, and every answer names its source.
Knowledge base
This is where your company's orders, documents and rules live.
Agents
They read documents, fill in fields and put deviations in front of you for a decision.
Case management
It shows, across all systems, where a case stands and what it is waiting for.
Permissions
An agent never has more permissions than the role it works in.
Who works on what in ToShift OS
Drivers, goods receiving, the business team and plant management work in the same system, each with their own view.
Goods receipt in ToShift OS
The example follows one delivery in five steps. If the quantity deviates, goods receiving decides.
Advanced Shipping Notice
06:58: The Advanced Shipping Notice (ASN) from Nordkamp Spedition comes in as a plain email. ToShift OS reads it and creates the inbound delivery in SAP.
Document at the gate
Goran, driver · operational07:12: Goran photographs his delivery note and needs neither an app nor an account. ToShift OS extracts license plate, delivery note number, carrier and items. Goran confirms in his language.
The system reads barcodes, a language model reads free text, a person reads handwriting. AI is only used where it is needed.
Matching
Tobias, goods receiving · operational07:14: ToShift OS matches the document to the delivery and proposes a dock. Normally the case goes straight through here. In this example the quantity deviates, 380 instead of 400 units, and Tobias decides.
Call-off
Goran, driver · operational07:16: Goran gets his dock assignment via WhatsApp. No shouting, no waiting at the gatehouse.
Unloading
08:05: The truck is unloaded. ToShift OS reports the status back to SAP. Every step carries a timestamp.
Flag
ToShift OS analyzes the unloading reports: for dangerous goods, load securing was flagged only at the dock three times in four weeks. It reports the deviation to Melanie on the business team and proposes changing the process.
Whether the process is changed is up to Melanie.
Change rule
Melanie, business team · administrativeMelanie accepts the flag and specifies in the chat: load securing check after the vehicle check, mandatory only for dangerous goods. ToShift OS submits the changed process for approval.
For the change, the business team needs neither an IT ticket nor consulting days. What it builds stays in-house.
Analysis
Stefan, plant management · managementStefan asks the chat how long trucks stay at each dock. ToShift OS answers with a table and a dashboard.
Orders & shipments
Search …Inbound delivery 180000051
Created from the ASN email, 06:59 · written back to SAP
From: dispo@nordkamp-spedition.de
Subject: ASN Holstenau Riem
Hi all, our truck NMS-NK 447 will arrive at your München-Riem site around 07:15 today.
We have 400 type B hinges on board, delivery note LS-2026-0913. The driver is Goran.
Regards from Dispatch
Approvals
Search …Approvals
1 document waiting · delivery note from the gate, matched against the ASN
| Field | ASN | Document at gate | |
|---|---|---|---|
| Supplier | Nordkamp Spedition | Nordkamp Spedition | |
| License plate | NMS-NK 447 | NMS-NK 447 | |
| Material | Type B hinges | Type B hinges | |
| Quantity | 400 pcs | 380 pcs | ASN 400 · Document 380 |
Orders & shipments
Search …Inbound delivery 180000051
Nordkamp Spedition · NMS-NK 447 · timestamp per step
| Time | Who | Step |
|---|---|---|
| 06:58 | ToShift OS | ASN read, inbound delivery created in SAP |
| 07:12 | Goran | Document confirmed at the gate |
| 07:14 | Tobias | Quantity deviation reviewed, dock 3 confirmed |
| 07:16 | ToShift OS | Call-off to Goran |
| 08:05 | ToShift OS | Unloading reported · Confirmation to SAP |
Chat
Search …| Date | Carrier | Finding at the dock |
|---|---|---|
| Sep 17 | Kortland Logistik | Straps missing |
| Sep 24 | Nordkamp Spedition | Load shifted |
| Oct 1 | Kortland Logistik | Straps missing |
Chat
Search …Chat
Search …| Date | License plate | Carrier | Dock occupancy |
|---|---|---|---|
| Sep 22 | HH-KL 2210 | Kortland Logistik | 71 min |
| Sep 15 | HH-KL 2210 | Kortland Logistik | 66 min |
| Sep 15 | NMS-NK 447 | Nordkamp Spedition | 22 min |
Sample data. Companies, order and times are fictitious.
- 06:58
Advanced Shipping Notice
The Advanced Shipping Notice (ASN) comes in as a plain email, and ToShift OS creates the inbound delivery in SAP.
- 07:12
Document at the gate
Goran photographs his delivery note, and ToShift OS reads it.
- 07:14
Matching
The quantity deviates, 380 instead of 400 units, and Tobias decides.
- 07:16
Call-off
Goran gets his dock assignment via WhatsApp.
- 08:05
Unloading
The truck is unloaded, and ToShift OS reports the status back to SAP.
Sample data. Companies, order and times are fictitious.
Choose your own level of sovereignty
ToShift OS runs in-house, at an EU provider or with us. The software is the same in all three cases.
In-house
ToShift OS runs on your hardware in your network. Your data stays in your network.
At an EU provider
You run ToShift OS under your own contract with an EU provider, no server room of your own required.
At ToShift
We run a dedicated instance for you on a server in Germany.
Hosting is always in the EU.
Your data does not go to the language model providers.
Steps that decide a case run on open language models that you can swap out and run yourself.
The apps for individual processes
The apps take over individual processes between dock and invoice. They are available individually or connected on ToShift OS.
See the apps