Elbuz imports a 1C catalog straight from CommerceML 2 exchange files: products, groups, prices and stock land in the base catalog without manual work.
When you need this:
- Your catalog lives in 1C — groups and product cards appear in Elbuz in one run.
- 1C prices and stock change daily — a scheduled template updates the same cards by Id.
- 1C has several price types — the catalog takes an offer's first price, so export the needed type first.
- You edit some cards in Elbuz — card flags stop the exchange from overwriting price or description.
Where to start: first catalog transfer from 1C with the “CommerceML2 (1C)” template.
What the 1C exchange can do
- Two files in one run — import.xml carries the catalog, offers.xml carries prices and stock; you can also import just one.
- Matching by Id — a repeat exchange updates the same cards, and offers (variants) are linked to the main product.
- Field transfer — name, SKU, manufacturer, description, weight, unit, specifications, photos, price and stock.
- Category tree — built from the 1C group classifier.
- Scheduled exchange — files are fetched by links without a manual run.
- Cleanup — with a checkbox, whatever is missing from the file is deleted from the catalog.
How to import an exchange: two files
A CommerceML exchange comes as two files, and 1C generates them separately:
- import.xml — the catalog itself: products (names, SKUs, groups, manufacturer, specifications, images) and the group classifier.
- offers.xml — the offer package: prices and stock for the same products.
The template form has two file fields to match: the first for products (import.xml), the second for offers (offers.xml). Both files are linked by a shared product identifier. A normal exchange imports both files together in one run.
1
Products file (import.xml)2
Offers file (offers.xml)- Products file field — choose import.xml with the catalog.
- Second file field — choose offers.xml with prices and stock.
What a single file updates
You can also import a single file: existing cards then get only what that file contains.
| What you imported | What updates in existing cards | New cards |
|---|---|---|
| Only import.xml | name, SKU, manufacturer, descriptions, category; price, stock and stock status stay as they were | created with price 0 and stock 0 |
| Only offers.xml (in the “Catalog” field) | price (except cards with “Fixed Price”), stock, stock status and specifications from the offer | not created unless the offer has a group that already exists in the catalog |
The exchange won't start without a file in the “Catalog” field, so to update prices you put offers.xml in that field — the program treats the offers themselves as the catalog. It reads only these nodes: Ид, Артикул, Наименование, Группы, Количество, Цены and specifications (ЗначенияСвойств, ХарактеристикиТовара).
What to know about an exchange with offers.xml alone:
- Name, SKU, manufacturer, short and full description, category and category links stay as they were. The exception is variant cards built from offers: their name and SKU come from the offer, as in a normal exchange.
- Specifications from the offer replace the card's entire specification list, including those from import.xml. Cards with “Do not update” or “Do not update attributes” keep their own.
- In cards flagged “Do not update”, price, stock, name and description stay as they were — the same applies to an exchange with import.xml alone.
How Elbuz recognizes a product from 1C
Every 1C product has an Id (the Ид node), a global identifier (GUID). Elbuz stores it in the system field “UUID” and uses it to match import.xml products, offers.xml prices and repeat imports. The GUID is stable, so a repeat exchange updates existing cards — more reliable than the SKU, which can change in 1C. Details: repeat import without duplicates.
A new card is created only when the product is linked to a classifier group. A product without a group (or with a group that is neither in the file nor in the catalog) is skipped silently, with no line in the log. Details: product without a category.
A special case is offers (product variants): their Id looks like GUID_товару#GUID_варіанту (product GUID # variant GUID). Elbuz recognizes this format and links the variant to the main product instead of creating a separate unlinked card.
Products that were already in the catalog without a 1C Id are not matched with the file's products: the product from the file gets a new card, and the old one stops updating. CommerceML has no way to keep apart products of two templates with the same identifier — details: two templates for the same product.
What the exchange writes to the card and how to protect your edits
From import.xml (the Товар node), these fields go to the card:
| CommerceML node | Card field in Elbuz |
|---|---|
Ид | UUID (the matching key) |
Артикул | product SKU |
Наименование (or the Полное наименование attribute) | product name |
Группы → Ид | category (by the group classifier) |
Изготовитель → Наименование | manufacturer |
Описание / the ОписаниеВФорматеHTML attribute | product description |
the Вес attribute | weight |
БазоваяЕдиница | unit of measure |
ЗначенияСвойств, ХарактеристикиТовара | product specifications / options |
Картинка (several) | photos |
From offers.xml (the Предложение node), price and stock are pulled in — they find their product by the same Id:
| CommerceML node | Card field in Elbuz |
|---|---|
Цены → Цена → ЦенаЗаЕдиницу | product price |
Цены → Цена → ИдТипаЦены | read but not written to the card (see price types) |
Цены → Цена → Валюта | read but not written to the card |
Количество | stock |
Fields are written from the file as is: if a node is missing, that card field stays empty. Every run with import.xml rewrites the name, SKU, manufacturer, category, short and full description in matched cards; 1C doesn't send a short description, so it becomes empty. What else a repeat run overwrites is in the overview.
Which price goes to the catalog if there are several price types
In 1C a product can have several prices of different types (retail, wholesale, purchase), each marked with its own ИдТипаЦены. Elbuz takes ЦенаЗаЕдиницу only from the first Цена in the Цены block, regardless of type; the other prices are skipped.
The template has no price type setting, and the currency isn't converted — the number goes into the price field as is. So set up the 1C export to put the needed type first in every offer, or export only that type. An offer without a Цены block gives the product a price of 0 (except cards with “Fixed Price”).
Specifications and variants
CommerceML has two sets: ЗначенияСвойств — properties from the classifier, and ХарактеристикиТовара — characteristics of a specific product that 1C builds variants on. Elbuz moves both into product attributes; the characteristics that distinguish offers become the basis of variants. You don't need to turn them on separately — they come with the rest of the exchange.
How to protect a card from being overwritten
Flags in the product card, in the “Import protection” group:
- “Do not update” — the exchange leaves the price, stock, main category, category links, name, descriptions and specifications alone.
- “Fixed Price” — protects only the price; category, manufacturer, SKU and stock update from the file.
- “Do not update attributes” — protects only the specifications; other fields update.
More on the flags and on photos in a repeat run: how to lock your value.
- Action or result
- Decision: the path depends on the answer
How categories are built from the classifier
Elbuz builds the category tree from the import.xml classifier (the Группы node): each group has its own Id and name, and nesting comes from nested groups. A product is linked to a group by the group's Id, so your 1C section structure is reproduced in your catalog.
Groups from 1C are regular catalog categories, not service ones: the program creates them with the status and export settings the database gives a new category by default. But they are tied to 1C by Id, and every exchange resets them to their state in 1C:
- You renamed or moved a group in the Elbuz tree — the next exchange restores the name (in the default catalog language) and the parent group from the file.
- You deleted a group in Elbuz — if it is still in import.xml, the next exchange creates it again as a new category and moves its products there.
- You moved products from a 1C group into your own category — the next exchange gives them back the category from the file. To keep a product in your category, use the “Do not update” flag.
The lasting fix for the structure is to change groups in 1C itself. The exchange doesn't touch orders or other documents, so moving products or deleting groups doesn't affect lines of documents already imported.
How to update your catalog from 1C regularly
The first exchange creates products, later ones update existing products by Id. The catalog (import.xml) is usually updated less often, prices and stock (offers.xml) more often, as a separate import. To avoid manual runs, set up a scheduled exchange.
The run goes through the operations center: you see the message “Import started — follow it in Operations”, and the run log is shown there. The log lines come in this order:
- Reading the files: the counters “Categories received from file” (every 100 groups), “Products received from file” and “Product prices retrieved from file” (every 1,000 items).
- Reading totals: “Total categories imported”, “Total items imported”, “Total product prices imported”.
- Writing to the catalog, then the final steps — formulas, integrity check, indexing — and the line “Data import completed!”.
If the file didn't reach the server (too large or the connection dropped), the exchange doesn't start, and the log shows “The file could not be sent to the server. It may be too large or the connection was lost”. How to check the result of a run: the log and “Run history”.
New prices and stock won't reach your website and marketplaces on their own: the exchange doesn't start exports. First the 1C exchange, then the export — details: when imported data moves on.
What happens to a product that disappeared from the exchange
It depends on a checkbox in the template form, in the “What to import” block: “Delete entries in the base catalog that are not in the imported file”. Without it, the exchange doesn't touch a card that's missing from the file: a product removed in 1C stays in the catalog with its old price and stock.
With the checkbox on, before writing, the exchange deletes from the base catalog all categories missing from the file's classifier and all products missing from the file — including manual ones and those from other sources. The CommerceML form has no narrowing “Check uniqueness of records…” checkbox. Products and variants found only in offers.xml count as present.
This is deletion, not disabling, and there is no undo button. Along with the product you lose descriptions, photos, specifications and links; supplier price list rows lose their matches, and import rules for deleted categories are deleted. In the log this step is labeled “Removing categories and products in the base catalog that are not in the file”.
With the checkbox on, offers.xml alone doesn't delete categories — it has no classifier. But it does delete products that aren't among the offers: an offers.xml with only part of your range removes the rest. Likewise, a partial import.xml deletes everything it doesn't include.
An empty file or a file without a classifier won't wipe the catalog — details: a product disappeared from the source. Without the “Flag: delete categories and products…” right, the checkbox in the form is inactive.
If the exchange broke off or created duplicates
The exchange broke off
What's left in the catalog depends on the stage:
- Break-off while reading files — the catalog hasn't changed: nothing is written to it while both files are being read. A file cut off in the middle of a product or offer — from your computer or by link — ends the exchange with the error “Could not read the file:” and a reason, also before writing.
- Break-off while writing — whatever was written stays: first deletion (if on), then categories, then products, specifications and photos. Stop is checked before deletion and after categories are written; after that, products and specifications are written to the end. If stop was pressed before that point, photos aren't downloaded.
- Action or result
- Decision: the path depends on the answer
Repeating the same exchange is safe: products and categories are found by Id, the manufacturer is looked up by name, and specifications are rewritten — nothing gets duplicated. What happens after a stop and why you can't run two runs at once: if a run broke off.
The exchange created duplicates
Duplicates appear when product Ids changed in 1C: to the program these are new products, so it creates new cards, and the old ones stay alongside and no longer update.
Find them in the base catalog grid by the “Source: name” column (the name of your CommerceML template) and “Date added” (the day of that exchange). Show the “Product ID (UUID string)” column next to them to compare Ids with 1C.
Delete the old cards, not the new ones: the exchange will keep looking for products by the new Ids and will recreate deleted new cards. First move any hand-checked content off the old cards. Bulk actions for this: if you imported the wrong data.
Scenarios
Move your catalog from 1C for the first time
Goal: bring into Elbuz a catalog you already keep in 1C. In the “CommerceML2 (1C)” template form, on the “Local file” tab, pick import.xml with “Select file - Catalog” and offers.xml with “Select file - Offer package”. Leave “Delete entries in the base catalog that are not in the imported file” off and click “Import”.
Result: a category tree from the classifier, product cards with the Id in the UUID field, and price and stock from offers.xml. New manufacturers are added to the directory, specifications become attributes, and the template name is recorded as the source of new cards. What you won't get: cards for products without a classifier group.
Do the first exchange on a small sample and check a few cards by eye.
Pull prices and stock from 1C on a schedule
Goal: have prices and stock from 1C update without manual runs. On the “External link” tab, enter the addresses where 1C publishes the files: “Link to product file (Catalog)” and “Price file link (Offer package)”. In the “Related settings” block, click “Schedule setup” and set up the run, and in the form header switch the template to “Active”.
1
Catalog link2
Offer package link3
Schedule setup- Link to the product file (Catalog).
- Link to the price file (Offer package).
- Schedule setup button.
Result: on schedule, the program fetches both files by their links and updates cards by Id. A template set to “Disabled” is skipped by the schedule. If the second link is empty, the exchange runs with the catalog alone: existing cards keep their prices and stock, new ones get price 0 and stock 0.
Remove from the catalog what was dropped in 1C
Goal: 1C is the single source of your range, and nothing extra should remain in Elbuz. Turn on “Delete entries in the base catalog that are not in the imported file” (you need the right for it) and always import the full import.xml together with offers.xml.
Result: before writing, the exchange deletes all categories and products missing from the file, including manual ones and those imported from other sources; there is no undo. Limit the range in the file, and the rest disappears from the catalog (see what happens to a product that disappeared).
Manage some cards manually, take the rest from 1C
Goal: for some products you set the price or description in Elbuz, and the exchange must not overwrite them. In the card of such a product, set “Fixed Price” (protects the price) or “Do not update” (protects price, stock, categories, name, descriptions and specifications).
Result: the rest of the catalog updates from 1C, and flagged cards stay yours. Stock in a card with “Fixed Price” still updates from the file (see how to protect a card).
What to do when the exchange imported the wrong data
| What you see | Why | What to do |
|---|---|---|
| The catalog arrived, but new products have price 0 and stock 0 | Only import.xml was imported: prices and stock live in offers.xml | Add offers.xml as the second file and run the exchange again (single file) |
| The catalog shows the purchase or wholesale price instead of retail | The offer's first price is taken; the price type is ignored | Put the type you need first in the 1C export (price types) |
| The catalog has fewer products than the file | A product without a classifier group doesn't get a card | Link the products to groups in 1C (how Elbuz recognizes a product) |
| Products that were in the catalog before the exchange didn't update, and new ones appeared next to them | The old cards have no 1C Id, or the Ids changed in 1C | Find duplicates by “Source: name” and “Date added” (duplicates) |
| “The file could not be sent to the server. It may be too large or the connection was lost” | The file didn't reach the server, so the exchange didn't start | Retry the import or provide the file by link (by link) |
| “Could not read the file:” with a reason | The file is cut off or corrupted; the catalog hasn't changed | Export the file from 1C again (exchange break-off) |
| The catalog has new prices, but the website shows old ones | The exchange doesn't start exports | Check when the export last ran (when data moves on) |
1C files must be in a correct encoding — usually or Windows-1251, whichever your configuration produces.
FAQ
Can I update only prices and stock from 1C?
Yes. Put offers.xml in the “Catalog” field: existing cards get updated price, stock, stock status and specifications, and other fields stay (what a single file updates).
Does Elbuz convert the currency of 1C prices?
No. The currency from offers.xml is read but not written to the card: the number goes into the price field as is (price types).
Why didn't the specifications import?
Specifications import automatically with the rest of the exchange. They come from the property-value and product-characteristic nodes (ЗначенияСвойств and ХарактеристикиТовара); if the 1C file doesn't have them, there is nothing to transfer. Cards with “Do not update” or “Do not update attributes” keep their own.
Can I import only part of the catalog from 1C?
Yes, if the deletion checkbox is off: only products from the file get updated. With the checkbox on, everything missing from the file is deleted (product disappeared from the exchange).
Does the exchange change orders and documents?
No, the exchange doesn't touch documents. Moving products or deleting groups doesn't affect lines of documents already imported.
Why did the description I wrote in Elbuz disappear after the exchange?
An exchange with import.xml rewrites the name and descriptions with what came from 1C; the short description becomes empty. The description survives only in a card with “Do not update” (how to protect a card).
Where to find it and who has access
- Menu
- Directories → Operations → Data import → the “CommerceML2 (1C)” template
- Access right
- the “Import” window in group permissions
- Deletion checkbox
- a separate right, “Flag: delete categories and products in the base catalog that are not in the uploaded file”
- Prepare
- import.xml and offers.xml exported from 1C, or links to them
1
CommerceML2 (1C) template- The CommerceML2 (1C) template row in the list.
Other import methods and how they differ are covered in the data import overview.
Related topics
- If you're still choosing how to import your catalog — data import overview.
- If you need to send the catalog and prices from Elbuz back to 1C — export to CommerceML.
- If a file from a supplier or website is XML/YML rather than CommerceML — import from XML / YML.
- If the format is non-standard and fields need manual mapping — universal import.
