↑↓ selectEnter openEsc close

    1. Elbuz

    How to send your catalog and prices from Elbuz to 1C via CommerceML

    12 min readUpdated

    Elbuz builds a CommerceML XML file that 1C's standard exchange processor accepts: product cards, properties, prices, quantity. No custom code needed.

    When you need this:

    • Accounting is in 1C, catalog and prices in Elbuz — items and prices go to 1C in one file or two.
    • Items already exist in 1C — the template sends only prices and quantity daily.
    • 1C picks up the file itself — Elbuz puts it on FTP or at a permanent link on schedule.
    • Something went out wrong — the next file overwrites values without duplicates.

    Where to start: create a CommerceML template and set the quantity for each stock status.

    What the CommerceML export can do

    • Catalog and offer package — together, separately, or as two files, whatever your 1C processor expects.
    • Product card — SKU, barcode, description, groups, details and properties, with a permanent ID.
    • Three price types plus your own — retail, RRP, cost price and custom fields of the “price” type.
    • Quantity by stock status — your own number for each status, or the actual stock.
    • Delivery to FTP — both files in one run, on a schedule.
    • Trial run — for one product before the first exchange.

    How to create a template and choose documents

    In the “Data export” window, click the add template button and choose the “CommerceML2 (1C)” type. The form is short: no selectors or text templates, since the standard defines the structure. You only decide which parts to export and where photo links come from. Product filtering, schedule and delivery work as in any template: where product filtering is set.

    Two documents: “Catalog” and “Offer package”

    CommerceML describes a product with two documents, and mixing them up is the main reason a file “is accepted but updates nothing”.

    • Catalog — what the product is: name, description, SKU, barcode, category, properties, photos. There are no prices here at all.
    • Offer package — the price and how many: prices by type and quantity. Basically a price list that refers to catalog products by ID.

    In the form, these are two checkboxes — “Export product “Catalog”” and “Export “Offer Package”” — and they work independently. The first import is done with both; once the items exist in 1C, keep only the offers.

    The “Export “Offer Package” as a separate file” checkbox splits the documents into two files: _offers is added to the price file name, so export_1c_commerceml2.xml also produces export_1c_commerceml2_offers.xml. In a new template, this checkbox is already selected. If your processor expects one file, clear it: catalog and offers go one after another under a shared root node.

    The document follows schema version 2.07 in encoding, with the generation date in the root. The catalog is marked as complete, not as a set of changes: 1C gets the full picture every time.

    What goes into the file

    WhatWhat's in itWhen it's sent
    IDThe product's permanent internal code in Elbuz: 1C uses it to recognize the same item in later files, so a repeat doesn't create duplicates. A variant has two codes separated by #: the main product's and its ownalways
    Main fieldsSKU, barcode, name, description and groups. A product in several categories goes into the file once, with all its categories in the groups blockalways
    DetailsManufacturer, contact, category, contact's SKU, dimensions: weight, height, width, depth. An empty dimension arrives blank, not as zeroalways
    PropertiesProperties from the card's attributes tab. The file first gets a property directory with names, then products refer to the ones they need“Export product attributes” checkbox
    Custom fieldsYour own catalog fields — added to the details. Fields of the “price” type become separate price types in the offer package“Export custom fields” checkbox
    Group treeYour active categories — whether or not they still have products after filtering. An empty group in 1C is normal, not a failurealways

    Products without a category aren't exported to CommerceML at all: a product is described together with its group. The other filtering conditions are the same for all formats — why a product didn't make it into the file.

    Prices: three types plus your own

    The offer package starts with a list of price types. The program always declares three; their names in the file are in Russian, and that's exactly how 1C will see them:

    Price typeWhere it comes from
    Розничная (Retail)the product's main price
    Розничная РРЦ (Retail RRP)the recommended price
    Цена себестоимость (из прайс листа) (Cost price from the price list)the supplier's purchase price

    With “Export custom fields”, one more type is added for each of your custom fields of the “price” type; in a new template, this checkbox is off. Each type is declared with a currency and tax. There's one currency — the store's main currency; it isn't set per product.

    The quantity goes into the offer next to the prices. The price is per unit, the unit of measure is “piece”, and the factor is one; these values are fixed.

    Zero “Розничная” and “Цена себестоимость” prices go into the file as zero. A zero RRP isn't written to the offer at all. If products without a price shouldn't reach 1C, exclude them with product filtering in the template.

    Quantity doesn't come from stock

    The number 1C receives as quantity is set in the “Stock-based update setup” window — a button in the “Related settings” section of the template card. Each stock status there has a value in the “Quantity” column, and that's what goes into the file.

    • The program fills the rows itself: “In stock” — 1000, “Pre-order” — 500, the rest — 0. Set your own numbers before the first exchange.
    • The product's actual stock is sent when its status isn't in the list or the status row is turned off with the “Active” checkbox.
    • There's one quantity per product: the document has no per-warehouse breakdown.
    • The “Product status on site” and “Title on site (in file)” columns don't affect this file — they're for other export types.

    Photos: the file gets links, not images

    The “Export product photos” checkbox adds a text path to the image, not the image itself. The address has two parts:

    • a fixed beginning — the “Product Image Link” field, for example https://site.com/images/. Macros in curly braces aren't substituted here;
    • the path of the file itself — the program adds it.

    The “Show subdirectories in product photo link” checkbox keeps the storage folder structure in the address. Clear it if the receiving side expects a flat list of file names.

    How the file gets to 1C

    The file doesn't enter 1C on its own: Elbuz puts it on your FTP or keeps it at a link, and the exchange processor on the 1C side imports it. The chain is complete when both steps are done:

    1. a run has finished in Elbuz — the “Export” button, “Export all templates”, or the schedule;
    2. the file import has been started in 1C.

    Until the second step is done, the new prices won't be in your accounting. The document is built from the catalog at the moment of the run: if prices just arrived from a supplier price list, the base catalog update has to finish first, and only then the export.

    When the offers are in a separate file, both files go to FTP in one run: the log shows “Files exported via FTP: 1 of 2”, then “2 of 2”. If the server rejected them, the same line shows its response code — see where the file goes for what it means.

    If the server address or user name is empty in “FTP Setup”, delivery is silently skipped: the log shows no error or FTP line, the run ends with “Data export completed”, and the file sits at the link. This is the most common “everything is green, but 1C has nothing” case. Fill in server and user, then click “Check Connection”.

    How to check the file and the run result

    Trial run before the first exchange

    The flask button in the card header — “Trial export of one product” — opens the “Export template check” window. You can leave the “Product ID” field empty: the first product that meets the conditions is used. The window shows:

    • the line “Checked on product: #‹code› ‹name›”;
    • the XML itself — the first 200 KB: in CommerceML, even a one-product trial pulls in the full category classifier;
    • a summary — “No problems found: the export was built correctly and every macro was substituted.” or a list of errors with line number and position.

    The file goes nowhere: not to FTP, not to the cloud, not to the link in the card.

    What the run log shows

    Yellow diamonds are where a run can take a different path. Both “Stop” branches lead to “stopped by the user”, and the file then goes nowhere. A failed cloud upload leads to “NOT completed” — the link in the template stays old. The branch without FTP ends with the same “completed” as with FTP.
    yesnoyesno“Stop” clickedyesno“Stop” clickedyesno — silentlyyesno — error in the log“Export” or scheduleA stop rule with the “Stop the export”action fired?Export stopped by a stop rule“Export product “Catalog”” on?The catalog is built in batches of5000 products“Export “Offer Package”” on?Offers in batches of 5000 — into thesame file or a separate _offers fileExport stopped by the user! — linkand date stay from the previous runData export NOT completed — linkand date stay from the previous runServer and user filled in under “FTPSetup”?Files go to FTPCloud mode: was the file uploadedto cloud storage?Link, size and date are updatedData export completed
    • Start or end
    • Action or result
    • Decision: the path depends on the answer

    The Operations center log keeps two counters, one per document: “Export products ‹N› of ‹M›” — the “Catalog” cards, then “Export product prices ‹N› of ‹M›” — the offers. ‹N› grows in batches of 5000 products; ‹M› is how many products matched the template. With both documents, the catalog is read twice, so prices only is twice as fast.

    At the end, the log gives a link to the finished file: two — to the catalog and to the prices — if the offers are a separate file, or one. The last line is “Data export completed” and “Time elapsed: ‹hh:mm:ss›”. The other log lines are the same as for other formats: run log.

    In the “Data export” list, the “File”, “Last export” and “In stock” columns update after the run. An empty or suddenly shrunken file shows up here before 1C sees it.

    Export list: the CommerceML template row with File, Last export and In stock columns
    1File
    2Last export
    3In stock
    1. File — name and size of the last run's file.
    2. Last export — date of the run and how long it took; a failed run does not change the date.
    3. In stock — how many exported products were in stock and the change from last time; an empty or shrunken file shows up here.

    Elbuz gets no confirmation from 1C: “Data export completed” means the file was built and placed where you set it to go. Whether the processor accepted it, you can only see in 1C.

    Schedule, file name and link

    Manual and scheduled runs, stopping, stop rules and schedule conflicts work as in all templates: manual and scheduled runs, stop rules. Below is what's different in CommerceML.

    Without a custom name, the file is called export_1c_commerceml2.xml. You can use {DATE}, {DATETIME} and {TIME} in the name; a slash becomes a dot, and .php is replaced with .xml.

    The cloud keeps no archive: after a successful run, the link points only to the new file. The account's temporary folder keeps the last three files; older ones are deleted at the start of a run. You get an archive of “how it was last week” only when the name contains {DATE} and the file goes to your FTP (scenario).

    “Only export new data” narrows the selection to products not yet marked as exported, but the catalog is still marked as complete. There's one mark for all templates — keep this checkbox on in no more than one (why a product didn't make it into the file).

    If a run broke off or was stopped

    Delivery to FTP and the cloud is the last step, so after “Stop” or a break-off:

    • the unfinished file stays in the temporary folder and goes nowhere;
    • the link and last export date don't update — a half-built catalog won't reach 1C;
    • the “Exported” flags aren't set, and the next run takes the same set;
    • a repeat is safe: the file is created from scratch, and 1C recognizes products by ID.

    If the offers are a separate file, the cloud rejected only the price file, and the name has no date, the catalog at the old link is already new. Run the export again so both files come from the same run. On FTP, the new file has already gone out by then: FTP delivery happens before the cloud.

    Turn off a template or delete it

    The “Active” / “Disabled” switch in the card header controls only automatic runs: a disabled template skips the schedule and “Export all templates”, but you can still run it manually. Settings, schedule, last file and link stay, and 1C can keep picking up the old file. Deleting erases the CommerceML settings, FTP, quantity by status, selected categories and schedule.

    The catalog ID is created once, together with the template, and goes into every file: the classifier, the catalog and the offer package. A new template in place of a deleted one gets a different ID, and to 1C it's a different catalog. A channel that already works with your accounting is turned off, not deleted and recreated.

    If the wrong data went to 1C

    The export changes nothing in Elbuz itself: prices, names, stock and statuses stay the same after a run. A run records only the file link, size, date and duration, plus the “Exported” flags with “Only export new data”.

    You can't undo a completed import on the 1C side from Elbuz: the file has no undo commands. You fix it with the next file:

    1. Fix the cause in Elbuz — the price, price type, quantity for a stock status, or the template's filtering conditions.
    2. Click the “Check” flask button and see on one product what now goes into the file.
    3. Run the export again and import the new file into 1C. Products are recognized by the same IDs, and the new values overwrite the wrong ones.

    Items that shouldn't have appeared in 1C won't disappear with a new file: delete them in 1C itself, and remove them from the template's filtering in Elbuz.

    A product dropped out of the file: what 1C gets

    Elbuz sends no “this product is gone” signal — neither for deleted products nor for those that didn't pass filtering. Their nodes are simply missing from the file: no price, no quantity, no zero. What the exchange processor does with such items is up to 1C.

    For 1C to get a zero, the product must stay in the export. Don't remove it with filtering — set zero as the quantity for its stock status in the “Stock-based update setup” window.

    Scenarios

    First connection of accounting in 1C

    Goal: 1C has no items yet, and you need to send both product cards and prices.

    What to turn on: in a new CommerceML template, “Export product “Catalog””, “Export “Offer Package”” and “Export “Offer Package” as a separate file” are already selected — keep them if the processor expects two files. Open “Stock-based update setup” and replace 1000 and 500 in “Quantity” with your numbers. Then click the flask button — “Check” on one product.

    Result: the run produces two files — without a custom name, export_1c_commerceml2.xml with the catalog and export_1c_commerceml2_offers.xml with prices. Nothing appears in 1C until the file import is started there.

    Update only prices and quantity every day

    Goal: the items already exist in 1C, and only fresh prices and quantity should come from Elbuz.

    What to turn on: clear “Export product “Catalog””, keep “Export “Offer Package”” and give the template a schedule.

    Result: the file gets the group tree and the offer package — price types, prices and quantity. There are no descriptions, photos or properties, so a product added in Elbuz after the last run with the catalog arrives without them. To send new items to 1C in full, run the export with the catalog on.

    Send the actual stock, not 1000 or 500

    Goal: 1C should get the quantity from the product card, not a placeholder number by stock status.

    What to turn on: in the “Stock-based update setup” window, clear the “Active” checkbox in the rows of the statuses that need the actual stock.

    Result: products with those statuses go out with the quantity from the card; the other statuses still give the number from the “Quantity” column. There's one quantity per product, with no per-warehouse breakdown.

    Keep a copy of every file sent

    Goal: be able to open a file that went to 1C a few days ago and see what was in it.

    What to turn on: put {DATE} in the template's file name, or {DATETIME} if there are several runs a day; fill in the server and user in “FTP Setup”.

    Result: each run puts a file with its own name on FTP. With {DATE}, two runs on the same day give the same name. Elbuz itself keeps no history — the account folder holds the three latest files, shared by all CommerceML templates.

    What to do when 1C doesn't get what you expected

    Empty selection, stop rules, schedule conflicts and FTP codes are in the general troubleshooting table.

    Troubleshooting common CommerceML problems
    What you seeWhyWhat to do
    1C accepted the file, but there are no prices The “Export “Offer Package”” checkbox is off — the file has only the catalog Turn it on in the template settings
    The 1C processor asks for two files, but one arrived The documents are in one file Turn on “Export “Offer Package” as a separate file”
    No properties The “Export product attributes” checkbox is off Turn it on
    Photos don't open on the receiving side The “Product Image Link” field has no address beginning, or it points to the wrong place Open a link from the file in a browser and check that the image loads (about photos)
    Products arrived with a zero price The price in the catalog is empty, and the export writes zero as is Exclude such products with filtering in the template
    Prices arrived in the wrong currency There's one currency — the store's main currency Check which currency is the store's main one
    “Data export NOT completed: the file was not generated” or “The file was not uploaded to cloud storage…” The file wasn't built, or cloud storage didn't accept it The link still has the previous complete file; run the export again (a repeat doesn't duplicate anything)
    The log is green, but the file isn't on FTP The server address or user name is empty in “FTP Setup” — delivery is silently skipped Fill in the fields and click “Check Connection”
    All products in 1C have a quantity of 1000 or 500 Quantity is taken by stock status, and the defaults are still there Set your own numbers in “Stock-based update setup” (details)
    After a new template, 1C created a second catalog The new template has a different catalog ID Don't delete a working template — turn it off (turn off or delete)

    FAQ

    Which CommerceML version does the program generate?

    Schema version 2.07 in UTF-8 — the edition that the standard 1C exchange processors work with.

    One file or two — which is right?

    Whatever your 1C processor expects. Out of the box, the template produces two files: the catalog and the offers with the _offers suffix. For one file, clear “Export “Offer Package” as a separate file”.

    Why weren't the photos embedded in the file?

    That's by design: the document gets a link to the image. Set the address beginning in the “Product Image Link” field and check that the photos load from it.

    Can I send stock separately for each warehouse?

    No. There's one quantity per product: the number for the stock status or the stock from the card (where quantity comes from).

    Will Elbuz know that 1C accepted the file?

    No, the channel is one-way. Whether the file was imported and which rows the processor accepted, you can only see in 1C.

    What happens if I turn off a template?

    It drops out of the schedule and “Export all templates”, but you can still run it manually. Settings, the last file and the link stay. Deleting, however, changes the catalog ID for 1C.

    How do I send data from 1C to Elbuz or get orders from it?

    That's the reverse direction. Export files with the standard 1C processors «Вивантаження даних у форматі CommerceML» (Data export in CommerceML format) or «Обмін з WEB-сайтом» (Exchange with a website) and import them with CommerceML import. This export doesn't take orders back.

    Where to find it and who has access

    Menu
    Directories → Operations → Data export
    Set up
    template card, “Data export setup” section
    Access right
    “Data export” window; card — “Export Template Setup”
    Prepare
    the CommerceML exchange processor in 1C; , if 1C will pick up the file from there
    CommerceML export settings: catalog and offer package checkboxes, catalog name and product image link
    1Export product “Catalog”
    2Export “Offer Package”
    3Export “Offer Package” as a separate file
    4Product image link
    1. Export product “Catalog” — what the product is: name, SKU, attributes; no prices here.
    2. Export “Offer Package” — prices and stock quantities, a separate standard document.
    3. Export “Offer Package” as a separate file — needed by 1C processors that expect two files.
    4. Product image link — the document carries the picture address, not the picture itself, and the start of that address is set here.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free