1C Integration via CommerceML with Your Website
Every morning, you update prices on your site manually? Then find out you forgot a promotion, and customers leave for competitors? Our 1C CommerceML integration provides automatic 1C site synchronization of products, prices, stock, and orders. No manual work, no errors. We deploy a working solution on your hosting (depending on scope). The CommerceML standard was developed by 1C. Contact us for a free assessment of your project. Our engineers have 10+ years of experience in 1C integration. Our clients achieve significant monthly savings in salary costs.
What Problems CommerceML Solves
Manual catalog export: each new item takes time, and human error creeps in. With manual sync, the chance of missing a price or stock change increases with every update. CommerceML processes catalogs 10 times faster than manual export, eliminating errors. Price changed in 1C—on the site it must update instantly, or the customer sees an incorrect amount. CommerceML allows configuring exchange intervals from minutes. The standard is 5 times more efficient than custom CSV parsers. A new order on the site must reach 1C for invoicing; if not, penalties and lost trust. CommerceML ensures automatic order export. If a product runs out in 1C stock but is still sold on the site, CommerceML exports stock and hides unavailable items, preventing overselling.
| Parameter | Manual Sync | CommerceML Integration |
|---|---|---|
| Catalog update time | Hours/days | Minutes |
| Error frequency | High | Minimal |
| Scalability | Limited | Unlimited |
How CommerceML Works in Practice?
CommerceML is a standard for exchanging commercial data between 1C and trading systems. Developed by 1C, the CommerceML protocol is widely supported by Russian CMS for 1C CMS integration (1C-Bitrix, OpenCart, WordPress + WooCommerce). For custom sites, a CommerceML parser needs to be implemented.
CommerceML Format
CommerceML is an XML format with several file types:
-
import.xml— product catalog (items, groups, properties) -
offers.xml— offers (prices, stock, characteristics) -
orders.xml— orders (export from CMS to 1C) -
import.xmlresponse from 1C — order status updates
Example import.xml structure
<?xml version="1.0" encoding="UTF-8"?>
<КоммерческаяИнформация ВерсияСхемы="2.05">
<Каталог СодержитТолькоИзменения="false">
<Товары>
<Товар>
<Ид>550e8400-e29b-41d4-a716-446655440001</Ид>
<Наименование>Футболка мужская синяя</Наименование>
<Группы><Ид>category-001</Ид></Группы>
<СтавкаНалога>НДС20</СтавкаНалога>
<Картинка>images/tshirt.jpg</Картинка>
<ЗначенияСвойств>
<ЗначенияСвойства>
<Ид>prop-color</Ид>
<Значение>Синий</Значение>
</ЗначенияСвойства>
</ЗначенийСвойств>
</Товар>
</Товары>
</Каталог>
</КоммерческаяИнформация>
Offers.xml Structure
<ПакетПредложений>
<Предложения>
<Предложение>
<Ид>550e8400-e29b-41d4-a716-446655440001#size-XL</Ид>
<Наименование>Футболка мужская синяя XL</Наименование>
<Цены>
<Цена>
<ИдТипаЦены>retail</ИдТипаЦены>
<ЦенаЗаЕдиницу>1500.00</ЦенаЗаЕдиницу>
<Валюта>RUB</Валюта>
</Цена>
</Цены>
<Количество>25</Количество>
</Предложение>
</Предложения>
</ПакетПредложений>
Why Incremental Updates Are Critical for Performance
After the initial full sync, subsequent exchanges can be incremental: СодержитТолькоИзменения="true". This dramatically speeds up sync since only changed products are loaded. Incremental updates reduce sync time from hours to minutes. Without them, a full re-import of a 10,000-product catalog would take 2–3 hours, unacceptable for frequent exchange.
How CommerceML Handles Product Variations
Products with variations (size, color) in CommerceML are represented as a single item with multiple offers. Each offer has a unique Ид like {product-guid}#{characteristic-guid}. This must be correctly mapped to product variations in the site database. We use the Repository pattern for flexible mapping. Variations are a common source of errors in integrations without CommerceML; the standard solves this without extra tweaks.
Exchange Protocol
1C initiates an exchange session via HTTP requests to the CMS using a specific protocol:
GET /exchange.php?type=catalog&mode=checkauth
→ Authentication
GET /exchange.php?type=catalog&mode=init
→ Initialization (buffer size, zip support)
POST /exchange.php?type=catalog&mode=file&filename=import.xml
→ File upload (may be chunked for large files)
GET /exchange.php?type=catalog&mode=import&filename=import.xml
→ Start processing
Handler Implementation in PHP
class CommerceML
{
public function handle(Request $request): Response
{
$mode = $request->query('mode');
$type = $request->query('type');
return match($mode) {
'checkauth' => $this->checkAuth(),
'init' => $this->init(),
'file' => $this->saveFile($request),
'import' => $this->processImport($request->query('filename')),
'query' => $this->exportOrders(), // export orders to 1C
'success' => $this->markOrdersExported(),
default => response('failure', 400)
};
}
protected function processImport(string $filename): Response
{
$xml = simplexml_load_file(storage_path("cms-exchange/{$filename}"));
// Parse and save products to DB
dispatch(new ProcessCommerceMLImport($xml));
return response('success');
}
}
Project Phases
- Analysis — study the 1C structure (documents, directories) and current site architecture. Identify necessary mappings.
- Design — develop the exchange scheme: what data to transfer, frequency, error handling.
- Development — write a CommerceML parser supporting incremental updates, variations, and bidirectional exchange.
- Testing — verify all scenarios: full load, partial updates, concurrent access, handling malformed XML.
- Deployment — configure cron or 1C scheduler, monitoring, logging.
| Phase | Duration |
|---|---|
| Analysis | 2–3 days |
| Design | 1–2 days |
| Development | 5–10 days |
| Testing | 2–3 days |
| Deployment | 1 day |
What You Get
- Working bidirectional exchange of products, prices, stock, and orders.
- API and protocol documentation (for future modifications).
- Instructions for the accountant on how to trigger exchange in 1C.
- 6-month warranty on the setup.
- Free support for the first month.
Development time: 2–4 weeks for implementing CommerceML parser and bidirectional exchange. Total project cost depends on scope.
Case Study: 15,000 SKU Retailer
We integrated CommerceML for a retailer with 15,000 SKUs. Previously, manual price updates required two employees working 4 hours daily. After integration, sync is fully automatic—10,000 product updates now complete in under 2 minutes. The client saves significantly monthly and avoids overselling.
Contact us for a free engineer consultation with 10+ years of 1C integration experience. We'll assess your project's complexity and propose the optimal solution.