1C:Trade Management Integration with Website
1C:UT (Trade Management) is a specialized configuration for automating trade operations: purchases, sales, warehouse, pricing, CRM. For online stores, it's the most complete of 1C configurations: contains "Customer Order" objects, complex pricing, warehouse management, and logistics.
What Gets Synchronized
From 1C to Website:
- Nomenclature with characteristics (color, size) and additional attributes
- Nomenclature groups (categories)
- Stock by warehouses (indicating which warehouse has the product)
- Prices by price types (retail, wholesale, segment discounts)
- Nomenclature images
- Barcodes
From Website to 1C:
- Customer orders
- Counterparty data (individuals, legal entities)
- Payment statuses
Complex Pricing
1C:UT supports multiple price types and automatic discounts. On the website this is reflected:
// Request price for specific customer segment
$priceRequest = [
'Nomenclature' => $sku,
'Characteristic' => $variantCode,
'Quantity' => $quantity,
'CounterpartyID' => $customer1cId, // for individual prices
'PriceDate' => date('d.m.Y')
];
// 1C will return price with discounts, customer price group applied
Stock by Multiple Warehouses
If the store has multiple warehouses (retail + online), determine which warehouse has the product:
// 1C response about stock
[
['Warehouse' => 'Main Warehouse', 'Stock' => 15],
['Warehouse' => 'Retail Store', 'Stock' => 3],
]
// Show total stock or breakdown for self-pickup
Reservation When Ordering
After creating an order on the website, 1C:UT can reserve goods:
{
"OperationType": "OrderCreation",
"ReserveGoods": true,
"Number": "WEB-12345",
"Goods": [...]
}
If reservation fails (product sold out between stock check and order creation) — 1C returns an error, order on website is moved to "requires clarification" status.
Order Statuses from 1C
1C:UT manages order statuses: new → confirmed → picked → handed to delivery → closed. Webhook or polling synchronization returns these statuses to the website for displaying to the buyer.
Configuration Features
UT exists in editions 10.3 and 11.x — they have different object structures and API methods. Edition 11 supports REST API via OData, simplifying integration. Edition 10.3 — only SOAP or COM.
Development Timeline: 6–10 weeks, including 1C configuration analysis, exchange development, and testing with real data.