The catalog is maintained in 1C, while the website runs on 1C-Bitrix. You need to receive products, offers, prices, stock, and images from 1C, assemble them into a working Eofferix catalog, and send the prepared data to the Eofferix module on the website.
In 1C, use the standard Site exchange flow or the 1C-Bitrix module for the client configuration. In Eofferix, create a 1C / CommerceML source, copy its URL, login, and password into 1C exchange settings, enable unified catalog assembly, then create a 1C-Bitrix profile, verify the website module connection, choose the iblock, and set identification fields.
How to do it in Eofferix
Create or open an Eofferix source and choose
1C / CommerceML. This source type receives CommerceML exchange traffic; it is not a normal manual file upload.
The 1C / CommerceMLcard should be active in the source type step.Save the source and copy the data from the
Import from 1Cblock: exchange URL, login, and password. The screenshot masks the password, but the full source password must be copied into 1C.
The /onec_exchange.php?source_id=...URL is pasted into 1C exchange settings together with the source login and password.In the same block, choose
Automatically assemble a single catalog file from 1C files. Eofferix will mergeimport.xml,offers.xml, price documents, stock documents, and image archives into one working catalog. If offers are needed only for products with variants, keep the nested-offers mode.
For 1C-Bitrix export, it is usually easier to work with the assembled catalog, where products, offers, prices, and stock are already linked. In 1C, open the site exchange settings. The path depends on the client configuration: it can be the standard
Site exchangefeature or an installed1C-Bitrixmodule for that configuration. Paste the Eofferix source URL, login, and password, then run the exchange.Create an interpreter profile and choose the existing
1C / CommerceMLsource. The profile will then use the latest working catalog after every 1C exchange run instead of waiting for a manual upload. In the profile schedule, use an event trigger after this source is successfully received or updated. Then the1C-Bitrixexport starts right after the new 1C exchange instead of running on a separate time schedule.
The profile uses the existing 1C source, so repeated 1C exports can be picked up automatically. In
What format to export?, openApplicationsand choose1C-Bitrix. This is the target profile for a 1C-Bitrix website.
The 1C-Bitrixcard enables batched transfer of sections, products, and offers into the Eofferix module on the website.Install the Eofferix module on the 1C-Bitrix website, enter the website URL and admin login, then click
Check connection. After a successful check, Eofferix receives the catalog manifest and shows the export iblock. Without this check, iblock and identification settings stay hidden.
After connection verification, Eofferix sees the product iblock, SKU iblock, properties, and directories from the website. In
1C-Bitrix element identification, choose the fields used to find existing data. For products, useXML_IDand article/SKU; for offers, use offerXML_IDand offer article; for sections, use sectionXML_ID.
Identification makes repeated exchange runs update existing products and offers instead of creating duplicates.
What the service receives
In 1C
CommerceML<CommerceML>
<import file="import.xml">
<Product>
<Id>1c-1001</Id>
<Sku>LMP-2201</Sku>
<Name>Onyx desk lamp</Name>
</Product>
</import>
<offers file="offers.xml">
<Offer>
<Id>1c-1001#main</Id>
<Price>129.00</Price>
<Stock>12</Stock>
</Offer>
</offers>
</CommerceML>In Eofferix
1C-Bitrix profile<onec_catalog assembly_mode="grouped">
<items>
<item>
<Id>1c-1001</Id>
<Sku>LMP-2201</Sku>
<Name>Onyx desk lamp</Name>
<Offers>
<Offer>
<Id>1c-1001#main</Id>
<Price>129.00</Price>
<Stock>12</Stock>
</Offer>
</Offers>
</item>
</items>
</onec_catalog>