How to Integrate 1C:Public Catering with 1C-Bitrix for Food Delivery

How to Integrate 1C:Public Catering with 1C-Bitrix for Food Delivery

When integrating 1C:Public Catering with a Bitrix-based website, the main problem is the mismatch between the nomenclature structures. The accounting system uses dishes, tech cards, modifiers, and semi-finished products, while the online store expects a flat catalog with prices. Without proper exchange setup, the site catalog will be incomplete and orders won't be correctly transferred to the software. One of our clients — a chain of 8 pizzerias — faced the issue that the standard exchange didn't transfer modifiers (size, dough, toppings), so each item had to be entered manually. The solution took 12 working days and saved 20 hours of manual labor per week, reducing effort by 80%.

Nomenclature in Public Catering: What's Different

In 1C:Public Catering, the "Nomenclature" directory is extended with specific types: Dishes, Semi-finished products, Goods, Services. A delivery site only needs Dishes (and sometimes Goods — packaged drinks). Semi-finished products are not uploaded to the site — they are internal production objects. A typical catalog contains 50 to 200 dishes per outlet.

How to Properly Transfer Modifiers from 1C:Public Catering?

The dish "Margherita Pizza" may have modifiers: size (25/30/35 cm), dough type (thin/thick), extra toppings. In the 1C module, modifiers are a separate directory linked to the dish via "Modifier groups". The CommerceML standard does not have a tag for modifiers — they need to be transmitted via AdditionalProps or through characteristics.

On the Bitrix side, modifiers are implemented as SKUs or as custom properties with a JSON structure. Both approaches work; SKUs are simpler for a standard catalog, JSON is more flexible for complex combinations. Using JSON for modifiers is 3-5 times more efficient than SKUs in terms of catalog management. Let's compare them in a table.

For simple dishes (size only), characteristics work well. For complex combinations (size × dough × toppings), JSON reduces the number of items by 3–5 times.

Transfer Scheme for Modifiers via Characteristics

In 1C:Public Catering, enable the transmission of modifier groups as dish characteristics.

<!-- Example XML for a dish with modifiers -->
<Товар>
  <Ид>abc-123</Ид>
  <Наименование>Pizza Margherita</Наименование>
  <ХарактеристикиТовара>
    <ХарактеристикаТовара>
      <Ид>size-25</Ид>
      <Наименование>Size 25 cm</Наименование>
      <Цена>450</Цена>
    </ХарактеристикаТовара>
    <ХарактеристикаТовара>
      <Ид>size-30</Ид>
      <Наименование>Size 30 cm</Наименование>
      <Цена>650</Цена>
    </ХарактеристикаТовара>
  </ХарактеристикиТовара>
</Товар>

Bitrix reads the characteristics and creates SKUs. Each SKU has its own price. This works for simple modifiers (size). For complex combinations (size × dough × toppings), the number of SKUs explodes: 3 sizes × 2 doughs × 10 toppings = 60 SKUs per dish. In that case, it's better to transfer modifiers as JSON in a custom dish property and handle them on the frontend.

Menu and Categories

In the accounting software, a menu is a separate object that links dishes to outlets and times of day. On the site, this is usually just catalog sections (Hot, Cold, Drinks). Mapping: "Nomenclature type" or "Nomenclature group" in Public Catering → info block section in Bitrix.

Problem: a dish can belong to multiple menu categories (e.g., "Business lunch" and "Main dishes"). Standard CommerceML transfers one group. Multiple section binding needs to be implemented via a custom handler or an additional "Extra categories" property.

Troubleshooting Order Delivery to 1C:Public Catering

Food delivery orders from the site must go to the system as "Delivery order" or "Sale". Standard CommerceML creates customer orders, but the module needs a link to delivery address, delivery time, and zone.

The delivery address is transferred via order properties. In Bitrix, it's the standard buyer profile fields. In the XML order, they fall into the Counterparty → Addresses section. Public Catering may not read non-standard address fields during import — a handler on the 1C side is needed. In our practice, we solved this with a custom module that transforms the address into a format understandable by the software.

Case Study: Pizza Chain (from Our Practice)

A chain of 8 pizzerias: a single Bitrix site, each outlet has its own 1C:Public Catering database (not centralized). Task: a unified catalog with prices (same prices), but orders must go to the specific outlet's database based on the delivery zone.

Solution: central catalog export from a "master" Public Catering database to Bitrix (once a day). Orders are routed on the site: delivery zone determined by address → select the endpoint of the specific outlet → order sent to the appropriate database.

Each outlet's database has its own exchange URL in Bitrix (multiple exchange nodes, one per outlet). The router is a custom component in local/components/.

Implementation time: 12 working days including testing all outlets. Integration setup costs from 50,000 rubles for a single outlet to 150,000 rubles for a chain. Savings on manual operations can be up to 30,000 rubles per month. The solution eliminated 80% of manual data entry.

Integration Setup Process

What's Included in the Setup

• Analysis of data schema in 1C:Public Catering and Bitrix.
• Development of a custom handler for modifiers (if required).
• Configuration of multiple exchange nodes (for chains).
• Documentation and instruction handover.
• Warranty support for 30 days after launch.

Our experience: 8+ years in 1C and Bitrix integrations, over 30 projects for food service establishments. We guarantee correct exchange and provide compliance certificates if needed.

Contact us for a project assessment — we'll prepare a commercial proposal within 2 days. Get a consultation with an engineer to discuss integration details.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.