ToShift Apps for individual processes
Each app takes over one process from start to finish and works through the interfaces of your systems. For yard and dock, ToShift YardOps adds a dedicated system.
Processes that still run by hand
Four examples from daily business at the site and the plant gate.
- Call-off
The call-off arrives as a browser notification. The driver doesn't see it, and both sides wait.
- Delivery note
The delivery note is handed over on paper at the plant gate, entered by hand and later searched for in the archive.
- Dwell time
Arrival and completion are reported to dispatch by phone. The call often doesn't happen, and without a timestamp the dwell time cannot be proven.
- Freight invoice
The freight invoice deviates from the costs SAP expects. Manual checks miss duplicates and risk overpayment.
Each process, managed in one app
Each app covers one process and runs on its own. ToShift YardOps manages arrival, dock and call-off at the site.
ToShift YardOps
- The driver checks in at the plant gate via QR code, without an app or account, and receives the safety briefing in their language.
- They upload their document. YardOps recognizes references, product group and quantity, and the driver confirms.
- YardOps creates a new case or matches it to the expected delivery.
- The driver gets their place in the queue and the call-off in the messaging app they chose at check-in.
- The dock display guides them in, then they check out.
The driver confirms the recognized details. If there is no clear match, plant security decides.
YardOps
Queue
North site
The control room sends the call-off, and the message lands in the chat the driver checked in with. Sample data.
Driver communication
- The TMS assigns a stop, and the driver receives it in their messaging app.
- The driver reports arrival by button, voice message or photo of the delivery note.
- They report problems the same way, such as wrong dock, goods not ready, waiting time or missing papers.
- Once they're done, they report that too.
- The app calculates the dwell time and writes it to the TMS.
Dispatch sees arrival, problems and dwell time in the cockpit and decides what follows.
Driver communication
A-1001 · Route 4711
Order A-1001
Arrival and completion by button, the dwell time lands in the TMS. Sample data.
Parcel integration
- One click on “Print labels” at the packing station sends the shipment from LGM to the app.
- The app selects the carrier by suitability, zones and price comparison.
- It creates the label as a PDF and for label printers (ZPL), with scannable barcodes and tracking number.
- Customs and dangerous goods documents are also created in the app.
- Label and tracking go back to LGM, as do cancellations, returns and tracking updates.
You define the rules for choosing the carrier. Every choice comes with a reason.
Parcel integration
Search …Parcel shipment
HU 4000012877
DE → US, zone ROW
2.4 kg, no dangerous goods
The carrier is selected by your rules, and the decision comes with a reason. Sample data.
Freight cost audit
- Invoices come in via EDI, PDF, portal or CSV.
- The app matches each invoice to the SAP freight cost document and gives the reason for the match.
- It checks every cost item against tolerances and detects duplicates and consolidated invoices.
- For clarification cases, it prepares the clarification email.
- The confirmed cost status goes back to SAP before posting.
Approval and posting are decided by rule and by a person, never by a language model. Clarification cases are decided by your accounts payable team.
Freight cost audit
Search …Invoices received today
Invoice inbox
Invoice RE-2026-1187 charges 90 minutes of waiting time. Freight cost document 4400012345 contains no waiting time. Please provide proof of the dwell time at the unloading point.
Anything that deviates becomes a clarification case. Your accounts payable team approves. Sample data.
How the apps work
Available individually, cleanly connected
You get one app for one process.
The apps work through the interfaces of your systems. At the dock, they use your yard management system or ToShift YardOps.
On ToShift OS, the apps share knowledge and permissions, and a case continues across system boundaries.
Data and knowledge base belong to you and are held in open formats. Hosting is in the EU.
