Parsing for 1C and ERP: How to Configure Data Exchange, Schedules, and Export Formats for Procurement and Nomenclature

Manually transferring supplier price data and updating item master records consumes hours and creates errors. Modern 1С and ERP systems can accept external data automatically — if proper parsing is set up and data exchange is configured. In this article, we'll explore how to build continuous procurement and item master integration through parsing, what formats and schedules to choose, and how ESK Solutions' offerings help eliminate routine tasks.

Why businesses need data parsing for 1С and ERP systems

Without reliable and timely data on prices, stock levels, and product characteristics, procurement becomes guesswork. An ERP system lacking up-to-date external content operates with a delay. Parsing websites and marketplaces solves this problem by turning scattered web resources into structured sources for 1С.

Automating procurement activities

The procurement department monitors dozens of websites and price lists daily. Without automation, employees manually copy numbers, leading to outdated prices and missed deadlines. A parser configured for a specific 1С configuration plays the role of a "digital supply agent": it collects data on a schedule, filters duplicates, and immediately transfers it to the ERP. This speeds up ordering decisions and reduces procurement costs through timely comparisons.

Item master management and directory synchronization

The item master directory is a critical element of any accounting system. When a supplier updates their assortment, your 1С must know about it without delay. Parsing allows exporting not only prices but also complete product cards: names, SKUs, barcodes, units of measure, category hierarchies. This keeps the directory mirror-accurate, and inventory and sales operate with correct analytics.

Data exchange formats — what 1С and modern ERPs support

Any parsing is useless without a properly chosen format that the receiving system "understands." 1С:Enterprise and ERP platforms (SAP, Microsoft Dynamics, Odoo) can load data through common formats, but a reliable integration often requires an adapter.

Comparison of formats for procurement and item master integration

• XML / CommerceML — standard for 1С. Suitable for complex hierarchical directories, transferring product properties and images. Ideal for item master data.
• JSON — lightweight format, convenient for cloud ERPs and REST API. We recommend for fast price list updates via web development of custom connectors.
• CSV / Excel — common language of procurement. Most suppliers publish price lists in these formats. Requires strict field mapping before loading into 1С.
• API (SOAP/REST) — for direct interaction with marketplaces and supplier portals. Allows real-time data retrieval.

At ESK Solutions, we don't just parse data; we immediately prepare output in a format compatible with standard and non-standard configurations. For non-standard ERPs, we develop intermediate conversion services, leveraging cloud solutions that handle all transformation logic before import.

Schedule configuration and automatic loading

A one-time export quickly loses value. The success of procurement and item master integration is determined by update regularity. Prices for exchange-traded goods can change hourly, while the item master directory only needs synchronization once a day. A flexible schedule prevents blockages and resource overuse.

Scheduling tools

• Built-in 1С processing and scheduled jobs — allow launching imports on a calendar without external utilities, if files are already in a network folder.
• Server schedulers (Cron, Task Scheduler) — a reliable way for periodic parser launches and data transfer to cloud storage. We deploy such mechanisms as part of cloud development services.
• External SaaS schedulers — provide a visual interface and logging, reducing the load on in-house administrators.

A well-designed schedule takes into account not only the interval but also the "windows" of availability of source sites, request limits, and the time needed to run the update inside the ERP. We design fault-tolerant chains: if a site is unavailable, data is taken from the last successful iteration, and the administrator receives a notification.

Procurement and Nomenclature Integration: An End-to-End Process

Disconnected steps — parsing, transformation, loading — will have no effect unless they are combined into a single automated pipeline. That is exactly what we build at ESK Solutions, linking data sources directly to procurement processes.

Example Chain: From Price Monitoring to Creating a Purchase Order to a Supplier

Example without specific numbers, illustrating the logic. Suppose a company purchases hardware from ten suppliers. The parser runs overnight, visits their websites, and collects current price lists in XML. The transformation module matches items with internal SKUs and loads the prices into the "Supplier Prices" information register in 1C:Trade Management. In the morning, the manager sees a report with highlighted items whose prices have dropped below a target threshold. The system automatically creates a purchase order to the supplier, using developments in CRM integration to preserve interaction history and contract terms.

For nomenclature management, the process is similar: all new products, their descriptions and photos are imported into directories, checked for duplicates, and immediately become available for sale or purchase. No SKU is lost.

Why You Should Trust ESK Solutions to Develop Your Parser

Writing scripts for parsing on your own often ends up with bans, broken formats, and constant rework. We create industrial solutions focused on long-term, uninterrupted operation:

• analyze sources and select the appropriate data collection technology (requests, headless browsers, APIs);
• configure data structure mirroring for full compatibility with your ERP — whether 1C, SAP, or Dynamics;
• provide monitoring, logging, and protection against blocking;
• deliver a documented product with technical support.

If your goal is procurement automation and seamless nomenclature updates, start with the basic parsing of sites and marketplaces service and get an integration that truly works with 1C.

Frequently Asked Questions

Can I parse dynamic content (JavaScript) for 1C?

Yes, for such tasks we use browser automation (Puppeteer, Playwright) or integrate via API if available. The obtained data is converted into a stable format suitable for import into 1C.

How often can data be updated without getting blocked?

Frequency depends on the source site's policy. We configure a schedule with dynamic delay and request masking to avoid triggering blocks. A typical scenario is updating every 2–4 hours.

Does ESK support integration with SAP / Oracle ERP?

Yes. We prepare exchange files (XML, CSV, JSON) in the specification required by the specific ERP, and if necessary, we develop intermediate data buses. The approach is consistent: the client receives a ready-to-load archive or an API request.

Do I need to modify the standard 1C configuration?

As a rule, it is enough to set up an external processing for loading from a file without touching the configuration core. If the logic requires special checks or distribution, we develop an extension that does not break when the platform is updated.