Integration through Eofferix significantly expands the exchange settings between 1C and the site. You can configure rules that a direct exchange usually does not cover without custom work: adjust names and descriptions, round or recalculate prices, add markup, remove unwanted items, and much more.
For example, Eofferix can take the base price from 1C, add a percentage for selected groups, rename size 46-48 into a site-friendly variant, build a value for a new field from several fields, such as META Title from "Buy + name + SKU", and convert the size, quality, and format of an image from the export archive. After these rules, Eofferix sends the prepared catalog to the site: sections, products, offers, properties, prices, stock, images, and files.
What Moves From 1C To Bitrix
| Data from 1C | Result in Bitrix |
|---|---|
| Product groups | Catalog sections. If no separate matching field is selected, sections are matched by the full name path. |
| Product items | Products in the selected catalog information block. |
| Product, offer, and section characteristics | Product, offer, and section characteristics: sizes, colors, bundles, separate prices, stock, and catalog group properties. |
| Attributes and properties | Product, offer, or section properties, depending on where you bind the field in the source structure. |
| Prices and stock | Values of the product or of a specific offer. |
| Images and files | Images and files for cards when they exist in the source or export archive. |
How To Set Up Catalog Exchange
- Create or choose the source with the 1C export.
Upload a new file or choose an existing source that can be refreshed manually or by schedule. - In the profile, choose the 1C-Bitrix template and check the site connection.
After the connection check, Eofferix sees the installed module and the selected catalog settings. - Choose the Bitrix catalog where products should be loaded.
Choose the product information block here. Eofferix detects the offer block from the Bitrix commercial catalog settings. - In the source structure, mark where sections, products, offers, and properties are located.
- Bind fields: name, price, stock, images, section path, external ID, SKUs, and needed properties.
In the source structure, choose which 1C data becomes a product, offer, section, price, stock, image, or property. - Choose an exchange scenario: safe update, full source sync, update found items, or another suitable preset.
The scenario defines what happens with new products, found products, empty values, and objects that disappeared from the source. - Run a test export, check the result in the Bitrix admin panel, then run the full exchange.
Use a test export for the first check. Run the full exchange after checking products, offers, properties, and images in the Bitrix admin panel.
Products And Offers
In Bitrix, products and offers are usually stored in different information blocks: parent products are in the product catalog block, and product variants are in the linked offers block. That means the main product card data and the specific variant data must be bound separately.
You usually do not need to choose the offers block separately in Eofferix. After you choose the product catalog, the service reads the linked offers block from the Bitrix commercial catalog settings. If this link is not configured in Bitrix, offers will not be loaded as product variants: configure the link in Bitrix first and run the connection check again.
For example, a T-shirt can be one parent product, while sizes S, M, and L are separate offers. The price, stock, color, size, and SKU of a specific size should go to the offer, not to the parent product.
Order Exchange Between A Bitrix Site And 1C
Eofferix sends the catalog to the site, but does not transfer orders. Order exchange must be configured directly between 1C and Bitrix using the standard 1C and Bitrix tools.
So that 1C can recognize products from site orders after that exchange, keep the original 1C external code in the Bitrix external code field. In Bitrix, this field is usually called External code; older screens may also show it as XML_ID.
The rule is simple: the product external code from 1C must go to the product external code in Bitrix, and the offer external code from 1C must go to the offer external code in Bitrix. Do not use service values such as eofferix-* as the 1C external code.
If the external code is empty, saved only on the parent product, or replaced by a service value, 1C may not match the order line to the needed product or product variant.
If The Catalog Is Already Loaded On The Site
If products already exist on the site and you need to match them with the 1C catalog, choose a reliable identification key that definitely exists both in the 1C catalog and in the site catalog: external ID, SKU, name + SKU, or another combination that exactly matches the old catalog.
Then Eofferix can update existing cards in place and fill the 1C external code without creating duplicates.
More about matching fields: Bitrix export settings. More about test and full runs: running the export.