The Eofferix integration with Bitrix moves a catalog from external sources into a site running the 1C-Bitrix CMS. The source can be a file, link, FTP/SFTP, Google Sheet, 1C / CommerceML exchange, XML, JSON, CSV, XLSX, YML, or a supplier export downloaded from a supplier account. A source can run manually or by schedule when this is configured in Eofferix.
Eofferix does not just send a file to the site. It converts the original format, applies value transformations such as rounding prices, adding values, changing text, and many other operations, then applies loading conditions that let you import only selected items instead of the whole source.
This article follows the main first-import path. Details are covered separately: module installation, profile settings, running the export, 1C and Bitrix integration through Eofferix, profile schedule, and source schedule.
Short Path
- Install the Eofferix module on the 1C-Bitrix site.
- Create or choose a source.
- On Template, choose 1C-Bitrix, check the site connection, choose the catalog, and set loading rules.
- On the source structure step, mark sections, products, offers, and fields.
- Run a test export.
- Run the full exchange.
- Use stop, continue, or rollback if needed.
- Enable the profile schedule if the exchange should run by itself.
1. Prepare The Site
Install the module first: installing the Eofferix module for 1C-Bitrix. After that, all export settings are handled in Eofferix.
2. Create A Source And Profile
A source is the place where Eofferix receives the catalog. In the profile, upload a new file or choose an existing source, then select 1C-Bitrix in Applications.

3. Connecting Eofferix To Bitrix
Enter the site address, the login and password of a user with administrator rights, and click Check connection. After a successful check, choose the catalog block in Bitrix where products should be loaded, then set the loading rules. Details: 1C-Bitrix export settings.

Typical Bitrix Exchange Scenarios
In the profile settings, choose a ready exchange scenario. It defines what happens with new products, already found products, offers, and objects that disappeared from the source.
| Scenario | When to use it |
|---|---|
| Safe exchange | Eofferix creates new products and updates found ones, but does not delete missing products automatically. It also does not bind products and offers to a specific profile. |
| Full source sync | The profile binds all imported products to itself. A repeated profile run removes products and offers that disappeared from the source and adds new ones that appeared with the next update. |
| Update found | Use this scenario when you need to change prices, stock, names, or properties only for already found products and offers. New products are not created. |
| Add new only | Use this when missing products and offers should be added, but existing site data should stay unchanged. |
| Full catalog rewrite | This scenario removes missing products, offers, and sections within the selected scope, then creates or updates objects from the current source. Properties and dictionary values are retained. |
You can also configure exchange behavior manually for products, offers, and product categories.
4. Mark The Source Structure
On the source structure step, mark what is a product, what is an offer, and which values should become names, prices, stock, section paths, images, and matching IDs. If the source comes from 1C, read the 1C and Bitrix integration article before the first run.

5. Run A Test Export
Send a small sample first. Then check the Bitrix admin panel: products, offers, properties, sections, and images. If something is wrong, return to the source structure or Bitrix settings.

6. Run The Full Exchange
After the test looks correct, click Run. Eofferix sends a large catalog in parts and lets you stop or continue the task without creating already processed products again.

7. Stop, Continue, And Roll Back
During a full exchange, you can stop the task. The service does not stop it instantly, so wait a little. After a stop or an error, the import can continue from the last confirmed point, so already processed products, offers, and sections should not be created again.
The result screen shows only a confirmed, currently available rollback point for the same physical 1C-Bitrix destination. Rolling back to it can undo the selected run and later imports to that same destination; data in another destination must not be affected. Check the point time and scope before confirming.
Automatic missing-data cleanup does not delete or unlink properties or dictionary values used by the profile. If they are temporarily absent from a later source, they remain in the catalog; when they appear again, Eofferix reuses the retained mapping when one compatible object can be identified unambiguously. Rules for missing products, offers, sections, and images work separately.
8. Enable Regular Exchange
Open the profile block Load schedule, choose By schedule, set the time, and save the profile. If the source must refresh first, configure the source schedule separately, then set the catalog import to By event and select running the exchange after the needed source is updated.
