1C → XML

Converter from 1C to XML

1C to XML converter online: configure a processing profile, transform data structure and automate repeat exports.

Profilein accountquick file structure check

Up to 2 GBafter signupfor production catalogs and price lists

Mappingfieldsconfigure output structure

Profilesfor repeat jobssave rules and run on schedule

converter

Converter 1C → XML

1C to XML conversion is configured in your account: upload the source, define output structure, transformations, filters and schedule.

available after signup

Configure 1C to XML conversion

1C processing needs saved structure, field types and export rules. That is why it runs in the account, not in the quick site converter.

01 Add a data source

Upload a file or connect a recurring source.

02 Configure output structure

Choose fields, column or node order, nested-data rules and filters.

03 Save the profile

Check the preview and reuse the profile manually, on schedule or with delivery.

1C → XML

upload a 1C export
map fields to XML
validate and rerun the profile

Need transformations, not just format conversion?

Sign up when you need to change values in cells, resize and convert images, or filter exports to include only selected items.

Increase prices for a supplier or product group by 7% and round them. Build a product name from SKU, manufacturer, model and attributes Convert images to JPG/PNG/WebP, resize them and add a watermark Schedule automatic transformations and deliver the result to the right channel.

format guide

What is a 1C to XML converter

A 1C to XML converter reads data in one format and builds output in another structure. It is useful when a supplier, CMS, ERP, marketplace or internal system expects a different file from the one you have. For simple files Eofferix can move fields automatically. In production workflows, rules matter: which fields are kept, how columns or tags are named, how nested data is handled, how empty values are normalized and which records are excluded.

When you need it

When data exists in one format but the next system expects another format or structure.

What Eofferix does

The service reads the source, detects repeated records and builds output with clear fields.

Why rules matter

The same file can be exported as a flat table, XML nodes, JSON structure or a feed.

example

1C to XML example

This simple example shows the basic conversion. After signup, fields, filters, order and recurring runs can be configured.

Before

<?xml version="1.0" encoding="UTF-8"?>
<КоммерческаяИнформация ВерсияСхемы="2.10" ДатаФормирования="2026-07-19">
  <Классификатор>
    <Группы>
      <Группа><Ид>cat-phone</Ид><Наименование>Смартфоны</Наименование></Группа>
    </Группы>
  </Классификатор>
  <Каталог>
    <Товары>
      <Товар>
        <Ид>product-001</Ид>
        <Артикул>SKU-001</Артикул>
        <Наименование>iPhone 15</Наименование>
        <Группы><Ид>cat-phone</Ид></Группы>
        <Картинка>import_files/front.jpg</Картинка>
        <Картинка>import_files/back.jpg</Картинка>
      </Товар>
      <Товар>
        <Ид>product-002</Ид>
        <Артикул>SKU-002</Артикул>
        <Наименование>Samsung S24</Наименование>
        <Группы><Ид>cat-phone</Ид></Группы>
        <Картинка>import_files/s24.jpg</Картинка>
      </Товар>
    </Товары>
  </Каталог>
  <ПакетПредложений>
    <Предложения>
      <Предложение>
        <Ид>product-001</Ид><ИдТовара>product-001</ИдТовара>
        <Цены><Цена><ЦенаЗаЕдиницу>999</ЦенаЗаЕдиницу><Валюта>USD</Валюта></Цена></Цены>
        <Количество>12</Количество>
      </Предложение>
      <Предложение>
        <Ид>product-002</Ид><ИдТовара>product-002</ИдТовара>
        <Цены><Цена><ЦенаЗаЕдиницу>899</ЦенаЗаЕдиницу><Валюта>USD</Валюта></Цена></Цены>
        <Количество>0</Количество>
      </Предложение>
    </Предложения>
  </ПакетПредложений>
</КоммерческаяИнформация>

After reading the 1C export

XML

<?xml version="1.0" encoding="UTF-8"?>
<root>
  <row>
    <category>Smartphones</category>
    <image>https://storage.eofferix.com/users/42/media/profile_128/files/8f4f7d/front-800.webp</image>
    <image>https://storage.eofferix.com/users/42/media/profile_128/files/8f4f7d/back-800.webp</image>
    <name>iPhone 15</name>
    <price>999</price>
    <sku>SKU-001</sku>
    <stock>12</stock>
  </row>
  <row>
    <category>Smartphones</category>
    <image>https://storage.eofferix.com/users/42/media/profile_128/files/a31c92/s24-800.webp</image>
    <name>Samsung S24</name>
    <price>899</price>
    <sku>SKU-002</sku>
    <stock>0</stock>
  </row>
</root>

After signup and profile setup

configured output

<?xml version="1.0" encoding="UTF-8"?>
<catalog generated="profile">
  <offer id="SKU-001" available="true">
    <title>iPhone 15</title>
    <price currency="USD">1099</price>
    <category>Айфоны</category>
    <image>https://storage.eofferix.com/users/42/media/profile_128/files/8f4f7d/front-800.webp</image>
    <image>https://storage.eofferix.com/users/42/media/profile_128/files/8f4f7d/back-800.webp</image>
  </offer>
</catalog>

What happened: the service joined products with offers from different 1C files, stored images in the cloud so they can be passed to third parties by URL, converted them to .webp and resized them to 800px. For the profile, zero-stock items were removed, prices were recalculated with a markup, attributes were normalized, and the 1C group with id 10 was renamed to Айфоны. The transformation profile is saved and can automatically receive data from 1C, apply the saved template of these settings and send the result to the required channel.

use cases

When you need a 1C to XML converter

These conversions are commonly used for catalogs, price lists, stock data, partner exchange and files prepared for receiving-system requirements.

Supplier catalogs

Bring supplier files to the structure expected by a site, CMS, ERP or PIM.

Price lists and stock

Prepare prices, availability, SKUs and categories for import or checks.

Marketplaces and channels

Build files for channel requirements, required fields and stable IDs.

Internal integrations

Move data between systems that use different exchange formats.

Manual review

Get a readable structure for managers, analysts or content teams.

Recurring exports

Run the same scenario repeatedly without manual setup.

common errors

Common 1C to XML conversion mistakes

Errors usually come from nesting, mixed value types, empty fields and receiver requirements.

Repeated node not selected

Define which records become rows, objects, nodes or offers.

Lost nesting

Arrays and nested objects need a rule: keep, split or move separately.

Different fields

If records have different fields, decide how empty values are handled.

Types not normalized

Prices, dates, true/false and HTML should be normalized.

No filters

Without filters, inactive products or extra categories may be exported.

No validation

Before recurring runs, check preview, encoding and required fields.

comparison

1C to XML online or manual conversion

A one-time check and production exchange need different approaches.

Method	Pros	Cons
Manual code	Maximum flexibility for unique schemas.	Requires developer time, tests and maintenance.
Script	Fast for repeated technical tasks.	Harder to control files, logs, permissions, schedule and delivery.
Eofferix	Preview, profiles, rules, files up to 2 GB and scheduled runs.	Complex structures need a saved profile.

limits and safety

Limits, safety and recurring workflows

Eofferix creates a separate output and does not change the source file. For large catalogs and exact rules, use a saved profile.

Up to 5 MB without signup

Good for quick checks of simple files.

Up to 2 GB after signup

Large catalogs are processed in the account with saved rules.

Source stays unchanged

Output is created as a separate file.

Structure control

When supplier data changes, update only affected rules.

Value transformations

Normalize text, prices, empty values and fields.

Result delivery

Email, FTP/SFTP, webhook and other channels for repeat processes.

other formats