1C → JSON

Convertisseur de 1C vers JSON

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

S’inscrire et configurer → Comment le lancer

Профильin accountquick file structure check

До 2 ГБafter signupfor production catalogs and price lists

Mappingfieldsconfigure output structure

Profilesfor repeat jobssave rules and run on schedule

converter

Converter 1C → JSON

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

disponible après inscription

Configurez la conversion 1C vers JSON

Le traitement 1C nécessite une structure enregistrée, des types de champs et des règles d’export. Il se lance donc dans le compte, pas dans le convertisseur rapide.

S’inscrire et configurer →

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 → JSON

import d’un export 1C
mapping des champs vers JSON
validation et relance du profil

Besoin de transformations, pas seulement d’un changement de format ?

Inscrivez-vous si vous devez modifier des valeurs, redimensionner et convertir des images, ou filtrer l’export uniquement sur certains éléments.

Augmenter le prix d’un fournisseur ou d’un groupe de produits de 7% et arrondir. Composer le nom produit à partir du SKU, fabricant, modèle et caractéristiques Convertir les images en JPG/PNG/WebP, les redimensionner et ajouter un filigrane Planifier des transformations automatiques et envoyer le résultat au bon canal.

S’inscrire →

format guide

What is a 1C to JSON converter

A 1C to JSON 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 JSON example

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

Before

Код=SKU-001
Наименование=iPhone 15
Цена=999
Остаток=12

Код=SKU-002
Наименование=Samsung S24
Цена=899
Остаток=8

After

JSON

[
  {
    "category": "Smartphones",
    "images": ["front.jpg", "back.jpg"],
    "name": "iPhone 15",
    "price": 999,
    "sku": "SKU-001",
    "stock": 12
  },
  {
    "category": "Smartphones",
    "images": ["s24.jpg"],
    "name": "Samsung S24",
    "price": 899,
    "sku": "SKU-002",
    "stock": 8
  }
]

A profile can save mapping, filters, value transformations and result delivery.

After signup and profile setup

configured output

[
  {
    "category": "Smartphones",
    "images": ["front.jpg", "back.jpg"],
    "name": "iPhone 15",
    "price": 999,
    "sku": "SKU-001",
    "stock": 12
  },
  {
    "category": "Smartphones",
    "images": ["s24.jpg"],
    "name": "Samsung S24",
    "price": 899,
    "sku": "SKU-002",
    "stock": 8
  }
]

use cases

When you need a 1C to JSON 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 JSON 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 JSON 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