Warehouse and transportation logistics often live in separate systems: order accounting and finance in 1C:ERP, physical picking and putaway operations in WMS, and routes and trips in TMS. While these environments are not connected, the manager cannot see whether an order has been picked; the logistics specialist builds trips based on outdated stock levels; and receiving data diverges during partial deliveries. Below is an open analysis of what the 1C:ERP integration with WMS and TMS can actually do, both for 1C products and external systems, based on vendor documentation and integrator publications. This is an overview of the tool's capabilities, not a case study of a specific implementation.
What we connect and why
1C:ERP covers orders, purchasing, finance, and master data. WMS manages bin locations, picking, receiving, and equipment operations. TMS plans transportation, builds trips, and monitors vehicles. The business result of integration is one thing: a single data environment where stock, order statuses, and delivery stages are visible to every department in real time, without manual transfer or discrepancies.
Exchange mechanisms: documented, not custom-built
According to 1C documentation, exchange between 1C:WMS and accounting systems is implemented with built-in tools in the format XML and via web service with automatic data export/import and configurable exchange frequency. The exchange scheme can be adapted to the client's specifics. Standard integration is supported with 1C:ERP Enterprise Management, 1C:ERP Holding Management, 1C:Trade Management (rev. 11), and 1C:Integrated Automation (rev. 2). Likewise, 1C:TMS exchanges data with 1C:ERP, 1C:KA, and 1C:UT - it transfers master data and registers transportation demands for further processing.
This is an important architectural fork. Instead of adding exchange logic inside the ERP core, the integration business logic is moved into a documented exchange contract (XML/web service) alongside the system. The ERP core remains in its standard configuration - this simplifies updates, reduces support costs, and makes the environment portable: another team can maintain the exchange without rewriting it. The principle of "using a mature standard exchange mechanism instead of a custom-built one" applies directly here.
Shipment cycle: how documents move between departments
An RDV integrator publication describes a typical flow. A manager in 1C:ERP initiates shipment - the shipment plan is sent to WMS, and a picking/assembly task is created based on it. WMS processes the preparation, marking stages with statuses: New -> In assembly -> Assembled -> Checked -> Ready to ship. After receiving a signal from WMS that the goods have been assembled, the logistics specialist creates routes (trips) and sends them back to WMS. The warehouse prints labels with vehicle numbers and addresses, prepares UTD and transport waybills, and the driver picks up the goods at the assigned gate.
When WMS and TMS are connected, according to 1C documentation, the system automatically plans loading tasks based on the unloading order during delivery, and the transport department sees warehouse task processing stages in real time. This eliminates the classic gap: "the warehouse picked it, but logistics does not know."
Receiving cycle: where synchronization usually breaks
For receiving, the integrator documentation describes two schemes. The classic one: Supplier order -> receipt order -> receiving instruction -> UTD after actual receipt. Its weak point is partial deliveries: you need to determine in advance which part of the order goes into a specific order, otherwise synchronization drifts. The alternative via EDI: the supplier sends a UTD -> the invoice is registered in ERP -> a receipt order is created -> the data is sent to WMS. The choice of scheme is a project decision, and it should be fixed at the start because it determines how shortages and mis-sorted items will behave.
Equipment and end-to-end digital process
WMS works with data collection terminals, barcode scanners, label printers, RFID, and scales - this ensures an end-to-end digital process from inbound to outbound. The documentation separately highlights the transfer of digital marking codes between WMS and the accounting system during receiving and shipping, which is critical for marked goods categories. On the transportation side, 1C:TMS works together with 1C:GLONASS/GPS Satellite Monitoring Center to control mileage, fuel consumption, and route compliance.
External WMS/TMS - the same contract principle
The integration is not limited to the 1C product line. Because the exchange uses a documented format (XML/web service), an external system can stand in for WMS or TMS - the exchange contract stays the same: ERP sends shipment plans and master data, and receives statuses and actual data back. This reduces dependence on a single vendor and keeps the environment portable.
Business result: what changes in the process
A single environment removes three routine losses: the manager sees the actual order picking stage and does not promise impossible deadlines to the customer; logistics builds trips from actually picked orders, not planned stock levels; receiving is matched automatically, and partial deliveries do not create manual recounts. In process terms, this is a shift from sequential document handoff "by email and calls" to event-based real-time status synchronization - sales, warehouse, and logistics work from one version of order data throughout the journey from receiving to unloading at the customer site.
