1C:Trade Management for Sales, Warehouse, and Purchasing

1C:UT helps manage the commerce stack when item master data, prices, stock, orders, warehouses, and integrations with external channels are configured correctly. The first requirement is a normalized item master: the same products under different codes break stock synchronization across all channels at once. Before setting up integrations, we define the rules: which system is the source of truth for stock and prices (usually UT), which exchanges need to run in real time, and which ones should run on a schedule.

We configure the UT commerce stack and its integrations with external channels so the configuration remains standard and updatable.

• Sales and customer orders: statuses, reservations, payment control, and shipments.
• Purchasing: demand planning, supplier orders, and incoming goods control.
• Pricing: price types, discounts, and rules for updating prices by channel.
• Warehouse: order-based process, bin location storage, and stock counts.
• Integrations: online store, CRM, marketplaces (Ozon, Wildberries), banks, delivery services, and BI through standard 1C mechanisms: exchange plans, EnterpriseData, OData, and web services.
• Integration with 1C:Accounting for statutory accounting.

Errors usually arise not in the UT interface, but in the connections: stock does not match the website, orders are duplicated, statuses do not reach the CRM, and prices are updated with delays. The reason is almost always architectural: direct point-to-point exchanges, where one broken link affects the rest, and the lack of monitoring, so integrations fail silently. We build the stack through a single API or a bus: in a case involving a network of 200+ locations on 1C:Retail, one connector per entity replaced hundreds of direct connections and reduced the load on the central 1C:ERP.

• Integration audit: where data is lost, duplicated, or diverges between systems.
• Routing through a bus or a single API instead of direct connections.
• Asynchronous exchange and queues so traffic spikes do not stop the accounting system.
• Logging and alerts: integration errors are visible before the customer notices them.

Commerce processes become more transparent: fewer manual reconciliations, faster order processing, more accurate stock, and easier onboarding of new sales channels. An order from the website or marketplace enters UT without manual entry, and stock and prices are sent to the channels automatically, either by events or on an agreed schedule.

• Stock levels and prices on the website and marketplaces match the accounting data.
• Orders are not duplicated, and status updates reach the CRM and the customer.
• A new sales channel connects to the existing integration instead of becoming a separate project.
• Integration health is visible in monitoring, not discovered through customer complaints.