Manual requests
Requests to transport companies go by email and in Excel; the dispatcher plans trips by eye - empty mileage, idle time, fuel overruns.
We implement, customize, and integrate TMS for your landscape: 1C, warehouse, telematics, and EDI. Routing, monitoring, dispatching, and shipment control in one environment. We are accountable for business results, not software licenses.
Our clients
Definition
TMS (Transport Management System) is a transport management system. It handles what happens between the shipper's warehouse and the recipient's warehouse: transport requests, carrier and rate selection, trip and route planning, shipping documents, and delivery cost calculation.
| System | What it manages | Where its scope ends |
|---|---|---|
| TMS | Transport: request, rate and carrier, trip and route, cargo status in transit, transport documents, delivery cost | At the warehouse gate, TMS does not know what is happening inside the warehouse |
| WMS | Warehouse: receiving, putaway, location-based storage, picking, shipment, inventory count | At the warehouse gate, WMS does not know where the cargo went or how it moved |
| ERP | Company resources and accounting: orders, procurement, finance, cost, settlements | At the operations level: detailed planning of trips and warehouse tasks does not live in ERP |
So the question of "TMS or ERP" is usually framed incorrectly: ERP remains the accounting system and source of the order, TMS plans and executes the transport, and WMS prepares the cargo for shipment. The practical work during implementation is not choosing one system instead of another, but the handoffs between them: request from ERP, shipment from WMS, documents to the EPD state system, and closing and payment back into accounting.
"TMS" in CIS transcription and TMS are the same. Industry texts also use the terms "transport management system" and "freight management system."
Pain
Requests to transport companies go by email and in Excel; the dispatcher plans trips by eye - empty mileage, idle time, fuel overruns.
Orders, routes, and statuses live in different systems and do not match.
A customer calls for a status update - there is no exact answer; costs are calculated after the fact, and KPIs are not visible.
To let a contractor see anything, they are given access to the entire ERP. When there are many systems and they are not connected, the problem is not TMS, but the interfaces.
Workflow
A transport moves through five responsibility handoffs. The TMS covers planning and execution, but the request comes from ERP, documents go to the EPD state system, and closing and payment return to 1C. A break at any handoff stops not the trip, but the settlement for it.
Request -> rate and carrier -> trip -> documents (ETTN/EPD state system) -> closing and payment
Application
Rate and selection
Trip
Documents
Closing and payment
Approach
We implement, customize, and integrate the transport system into your landscape - 1C, warehouse, telematics, and EDI - and take responsibility for results at the interfaces.
You can replace TMS, add a carrier, open a warehouse, or connect a customer without rewriting the entire landscape.
Trip costs and KPIs are visible in real time, not only in after-the-fact reports.
We replace components individually instead of rewriting the monolith. Contractors and customers see their shipments through a portal - without access to the full ERP.
Scope of work
Trip planning and route building with delivery windows, tonnage, and zones in mind. We reduce empty mileage and manual planning.
We connect telematics: position, route, fuel consumption, and deviations. We link the data with TMS and 1C instead of keeping it in a separate portal.
A single dispatcher workspace: trip allocation, statuses, SLA, and execution control.
B2B portal and delivery statuses: the customer sees where the cargo is without calling; the carrier works in its own workspace.
We connect TMS with 1C, WMS, telematics, EDI, and marketplaces through an integration layer. Requests, documents, and statuses move between systems automatically.
Deadline
Starting September 1, 2026, the transport waybill, transport order (request), and freight forwarding documents are issued only electronically and sent to the EPD state system under Federal Law No. 140-FZ dated 07.06.2025. There is no transition period in the law. Only one relief is announced: until March 1, 2027, if a paper waybill is used, the inspector is limited to a verbal warning. This does not cancel the obligation to issue documents electronically.
For the transport landscape, this means the document step of the route stops being a paper appendix to the trip and becomes part of execution: the ETTN is issued at the moment of the event, signed with a qualified electronic signature, and sent to the EPD IS operator. If your 1C configuration cannot do this, waybills are processed outside accounting and diverge from the EPD state system. What exactly to check in 1C and how to make it in time is covered in the article. ETRN and GIS EPD in 1C: mandatory transition by September 1, 2026.
Impact
We calculate the impact for your fleet and routes before the project starts, rather than promising a market average. What we measure: empty mileage, trip cost, OTIF and delivery window compliance, dispatcher planning time, fuel consumption, and the share of manual operations. How we measure impact -> breakdown.
Integration
Orders, customers, and finance stay in ERP/UT, while TMS handles shipments and transport costs. Data is not duplicated or split.
TMS ↔ 1C, TMS ↔ WMS, and TMS ↔ telematics through an integration bus, not with one-off hacks. The system can be replaced without stopping the others.
The carrier and the customer see their shipments in their own portal - without access to the full ERP. This is a KT.Team strength.
We load trip and cost data into a data warehouse for dashboards and KPIs.
FAQ
No. We are an integrator: we implement, customize, and integrate the transport system into your landscape and take responsibility for results at the interfaces, not for delivering licenses.
Yes. We adapt it to your processes and connect TMS with 1C, WMS, telematics, and EDI through an integration bus.
Through a B2B portal: everyone works in their own workspace and sees only their trips and statuses, without access to the full ERP.
Adapted to your fleet and routes before the project starts. We measure empty mileage, trip cost, OTIF, dispatcher time, fuel consumption, and the share of manual operations.
The document step is closed on the accounting system side and by the EPD IS operator, not inside the TMS. We check whether your 1C configuration supports electronic transport documents, connect the operator, and link ETTN issuance to trip events so the document is issued at shipment time, not after the cargo.
The obligation depends on your role in the transport, not on its share of revenue: it applies to shippers, carriers, freight forwarders, and consignees. Even if you only receive cargo, without a signed acceptance title the transport is not closed in the EPD state system.
Yes. We start with processes and data: which transport flow to take first, which systems already exist, and what must stay in 1C. We choose the system for this landscape, not for lock-in to one product.
Cases
Checked on: 13.08.2026