1C:Accounting Integration with Website: Automate Order Exchange

Note: when an e-commerce store grows, manually transferring orders into 1C:Accounting becomes a bottleneck. Managers spend hours copying data, and errors in INN or amounts lead to tax discrepancies. We design integration that eliminates the human factor and reduces order processing time to seconds. Our earliest clients noticed a 90% drop in primary document errors and a threefold increase in invoicing speed. For example, when an order comes in, the site sends JSON to a 1C REST endpoint, where a sales document is automatically created. This eliminates manual entry and ensures that data in 1C and on the site are identical. Without such integration, one in ten orders required rechecking — managers spent up to 15 minutes per document. With automation, the process takes 2-3 seconds.

Note: as stated in the official 1C:Accounting documentation, HTTP services ensure secure data exchange when using JWT. Integration investments pay back in an average of 4 months, and automation savings can reach 500,000 rubles per year.

Problems Solved by Integration

Main technical complexities we eliminate:

• Inventory discrepancies: item sold on the site but not written off in 1C — leads to negative stock. Integration synchronizes movements in real time.
• Duplicate counterparties: a customer registers with different emails — duplicates appear in 1C. Our algorithm matches by INN or phone.
• Invoice delays: legal entities require an invoice before payment — without integration it's a manual operation. The site generates a PDF via an HTTP request to 1C in 2-3 seconds.

How We Choose the Integration Method

There are two main options: an HTTP service in 1C and an external processing via COM connection. We use the HTTP service for most clients because it doesn't require a Windows server and is easier to maintain. COM connection is justified when the exchange load exceeds 10,000 documents per day — then performance is higher. The HTTP service is configured 3 times faster than a COM connection and does not require a dedicated Windows server.

For a medium-sized online store (up to 500 orders per day), the HTTP service offers the best price/quality ratio. We implemented it on the stack: Laravel 11 on the backend, 1C:Accounting 3.0 with a published REST endpoint.

1. Publish a REST service in the 1C configuration.
2. Set up JWT authentication.
3. Develop JSON transmission from the site.
4. Test on a database copy.
5. Launch into production.

Example of Sales Document Creation (Code)

$payload = [
    'OperationType' => 'SalesDocumentCreation',
    'OrderNumber'   => $order->id,
    'Date'          => $order->created_at->format('d.m.Y'),
    'Organization'  => 'LLC "Store"',
    'Counterparty'  => [
        'Name'  => $order->customer_name,
        'INN'   => $order->customer_inn,
        'Email' => $order->customer_email
    ],
    'Items' => $order->items->map(fn($item) => [
        'SKU'        => $item->sku,
        'Quantity'   => $item->quantity,
        'Price'      => $item->unit_price / 100,
        'VATRate'    => '20%'
    ])->toArray()
];

Invoice for Legal Entities

Legal entities often ask for an invoice before payment. The site requests a PDF invoice from 1C in a couple of seconds. Without integration, this takes up to 15 minutes of manual work.

$invoice = Http::post("{$this->baseUrl}/invoice/create", [
    'order_id' => $order->id,
    'customer' => ['inn' => $inn, 'kpp' => $kpp, 'company' => $company]
]);
$pdfUrl = $invoice['pdf_url'];

Synchronizing the Item Catalog

The item catalog from 1C:Accounting is the basic product reference. We export it via XML exchange or a direct request to the HTTP service. Frequency: once per hour for prices, once per day for names and characteristics. If instant synchronization is needed (e.g., for promotions), we set up webhooks.

Why Trust Our Integration?

We have 5+ years of experience developing 1C integrations, with over 50 successful projects. We guarantee the result and provide a single point of contact at all stages. We use certified solutions and official 1C:Accounting documentation.

What's Included in the Work

• Documentation of the exchange scheme and access rights
• Setup of API user permissions in 1C
• Development and debugging of the HTTP service or processing
• Testing on a database copy (100+ scenarios)
• Training of your managers
• 1 month of support after launch

Work Process

Timeline and Cost

Development time — from 4 to 7 weeks, depending on 1S customization. Cost is calculated individually after analyzing your configuration. Order 1C integration today — our engineer will contact you within an hour. To get a quote, contact us — we'll send a commercial proposal within a day.

1C:Enterprise Integration: Product, Order, and Stock Exchange

Monday morning. The manager opens the site and sees that the item sold out on Friday is still listed as "in stock". Three customers have already paid for a product that doesn't exist. We encounter this pain regularly: the lack of synchronization between 1C and the online store hurts revenue and reputation. We solve the problem end-to-end — setting up the exchange so that the accounting system and the storefront update synchronously, without data loss, and with consistency guarantees.

1C is the accounting system of most Russian companies. The site is the storefront. They must speak the same language and do so regularly, reliably, and without data loss. Our experience: over 50 successful integrations for clients with catalogs from 500 to 200,000 SKUs.

Why isn't standard CommerceML always sufficient?

CommerceML is a standard exchange protocol supported by 1C:Trade Management, 1C:Integrated Automation, and several other configurations. WooCommerce, Shopify, and other CMS have plugins for CommerceML (e.g., "1C-Bitrix" for their products, separate plugins for WordPress). Flow: 1C initiates exchange → sends a ZIP archive with XML to the site endpoint → site parses and updates the catalog.

CommerceML format is XML with its own schema: КоммерческаяИнформация, Классификатор, Каталог, ПакетПредложений. Categories, products, characteristics, images, prices, stock. The main difficulty: the hierarchy of characteristics in 1C and product attributes on the site do not always match one-to-one. Mapping is needed. For a deep understanding of the protocol, we recommend documentation on Wikipedia — Wikipedia: CommerceML.

How we overcome CommerceML limitations

For non-standard 1C configurations or when CommerceML is not suitable — we write an HTTP service in 1C (built-in since version 8.3) and interact via REST JSON. This gives full control over the data structure and synchronization frequency, but requires development from a 1C programmer.

For enterprise tasks with multiple accounting systems — Message Broker (RabbitMQ, Apache Kafka) as an intermediary. 1C publishes events to a queue, the site subscribes and processes them. Guaranteed delivery, buffering when one side is unavailable.

What we synchronize and how

Catalog (products, categories, attributes). The most voluminous part. Full export on first run, delta updates thereafter. When importing CommerceML: parse XML via PHP SimpleXML or XMLReader (for large files — only XMLReader, otherwise memory limit). Match products by GUID from 1C, which we store in a separate database field. If a product is deleted in 1C, we hide it on the site, not delete (order history may reference it).

Stock and prices. This is a separate ПакетПредложений in CommerceML, updated more often than the catalog. It's critical to do it atomically: not update stock one by one, but in a transaction. Otherwise, during the update, the user may see an inconsistent state. Frequency: once an hour for calm mode, once every 5–15 minutes for active trading.

Orders. Two-way exchange. Site → 1C: new order is sent with items, quantities, prices, customer contact info. 1C → site: order status (paid, assembled, shipped, delivered). For order transfer — either the same CommerceML (Документы block) or a direct REST call when an order is created on the site.

What typical problems do we solve?

Duplicate products. A 1C operator created an item with a typo in the SKU, then fixed it. On the site — two items. Solution: matching by GUID from 1C (not by SKU), GUID is immutable.

Cyrillic in XML and encodings. 1C historically works with Windows-1251. A CommerceML file may come in CP1251, PHP expects UTF-8. mb_convert_encoding() or iconv() in the first lines of the parser — mandatory.

Timeouts during large exports. A catalog of 100,000 items is 50–200MB XML. PHP default execution time of 30s is insufficient. Solution: CLI command (Laravel Artisan or Symfony Console) run via cron, without HTTP timeout. Or chunked processing via XMLReader with partial commits to the database.

Images. 1C can transmit images as Base64 inside XML (bloats file by 1.3x) or as file links. The second option is preferable. Download asynchronously, convert to WebP, place in media library.

Case: auto parts online store, 85,000 SKUs. Synchronization via CommerceML every 30 minutes. Problem: full export took 18 minutes, resulting in a new export starting while the old one was still running. Solution: lock via Redis (SET nx ex), delta export (only changed items in the last 2 hours via filter in 1C), processing via queue with 20 parallel workers. Sync time: 18 minutes → 2.5 minutes, no conflicts.

Comparison of integration methods

CommerceML in typical scenarios is 2-3 times faster than REST for catalog synchronization due to binary packing of XML and compact format. However, if custom exchange logic is required, REST provides full flexibility.

Process and timeline

Audit of 1C configuration (version, configuration type, export capabilities) → data mapping design → development of receiver on site and sender in 1C → testing on real data → schedule setup → monitoring of first exchanges.

Participation of a 1C programmer on the client side is mandatory, or we involve a trusted specialist.

| Scenario | Timeline | | CommerceML, catalog + stock, WooCommerce | 2–4 weeks | | Two-way order exchange | +2–3 weeks | | Custom 1C configuration, REST API | 4–8 weeks | | Enterprise: multiple 1C databases, data bus | 2–4 months |

What's included in the result (deliverables)

• Documentation: mapping scheme, data formats, error handling logic.
• Configured synchronization schedule with execution logs.
• Access to monitoring (Grafana/ELK — by agreement).
• Training for managers: how to run manual exchange, how to read logs.
• Post-launch warranty support — 2 weeks (issue fixing).

Get a consultation

We will evaluate your project within one business day — email us or use the chat. The integration cost is calculated individually based on project complexity. With over 7 years of experience in 1C integrations, we guarantee stable synchronization without surprises.