Parse Product Descriptions into 1C-Bitrix Catalogs Automatically

A trade catalog with 100,000 items—empty descriptions or copies from supplier sites. Manual writing would take a year for a copywriting team, and regular updates make it endless. Duplicate content guarantees search engine penalties: Yandex and Google demote such pages. SEO specialists see traffic drops, managers spend hours manually editing each card. We solve this with automatic parsing: extract, clean, rewrite, and write into infoblocks. The result is unique descriptions without manual work—filling takes days, not years.

Our engineers connect a parser to your 1C-Bitrix project. We use infoblocks v2.0, HL-blocks, and ORM. We write in PHP 8.1+ with Composer and strict typing. Filling speed is up to 20 times faster than manual entry. With AI rewriting via GPT, budget savings reach 70%—three times cheaper than an in-house copywriter. Get a consultation on automating your catalog: we will analyze your sources and propose a solution.

Description Sources

Source selection determines quality and legal risks. Consider the main options:

• Manufacturer website—most relevant content, but often hard to parse and contains copyright. Use as a basis for rewriting, not as final text.
• Aggregators (Yandex.Market, OZON, Wildberries)—large volume, standardized format. Same legal caveats.
• Official distributors—more lenient about content use, often interested in distribution.
• Manufacturer databases (Icecat, Synccentric)—legal option with an API, paid, but gives clean data with license.

Parsing from manufacturer websites often violates copyright. To avoid claims, we focus on legal databases or use rewriting after extraction. The contract defines content responsibility.

How to Automate Rewriting with AI?

After parsing, raw descriptions need uniqueness. We use the GPT API to generate rewritten text. The process:

1. Parse the source content.
2. Clean junk, leave pure text.
3. Send to GPT with prompt: 'Rewrite the product description, keep characteristics and keywords, change phrase structure.'
4. Write the result to the infoblock: PREVIEW_TEXT (first paragraph) and DETAIL_TEXT (full).
5. Set DESCRIPTION_SOURCE = 'parsed' to track the source.

This approach yields unique content, does not violate copyright, and saves up to 70% of the copywriting budget—tens of thousands of rubles monthly. With AI rewriting, you get descriptions that search engines do not consider duplicates—uniqueness compared to the source reaches 80%. Parsing with AI rewriting pays off in 2–3 months.

Why Protect Manual Edits?

Managers may manually improve descriptions. Do not blindly overwrite—add logic:

1. If DETAIL_TEXT is empty—write the parsed text with DESCRIPTION_SOURCE flag.
2. If filled—skip the element when updating. Flag absent? Means description was edited manually—leave untouched.

if (empty($arFields['DETAIL_TEXT']) || $arFields['DESCRIPTION_SOURCE'] === 'parsed') {
    $el->Update($elementId, ['DETAIL_TEXT' => $newText, 'DESCRIPTION_SOURCE' => 'parsed']);
}

Eliminating Content Duplicates

Duplication is the main SEO issue. Solution—rewrite after parsing. Use GPT API for uniqueness: send text with prompt 'rewrite in your own words, preserving meaning and keywords.' Or hire copywriters for selective processing of top items. Another option—use multiple sources and mix descriptions via a template engine.

Writing to Bitrix Fields

Bitrix splits description into two fields:

• PREVIEW_TEXT—short description (for listing)
• DETAIL_TEXT—full description (for product card)

When parsing a long description: first paragraph → PREVIEW_TEXT, full text → DETAIL_TEXT. Text type is set by PREVIEW_TEXT_TYPE and DETAIL_TEXT_TYPE (values: text or html).

Updating an element:

$el = new CIBlockElement();
$el->Update($elementId, [
    'PREVIEW_TEXT' => $shortDesc,
    'PREVIEW_TEXT_TYPE' => 'html',
    'DETAIL_TEXT' => $fullDesc,
    'DETAIL_TEXT_TYPE' => 'html',
]);

Documentation CIBlockElement helps with other methods.

Comparison of Parsing Sources

What's Included

• Source analysis and extraction structure selection
• Parser development with anti-blocking measures
• Text cleaning and normalization (HTMLPurifier, regex)
• Infoblock integration: PREVIEW_TEXT and DETAIL_TEXT
• Manual edit protection via DESCRIPTION_SOURCE flag
• Testing on 100–200 items
• Documentation and manager training

Timeline and Cost

Total: 4–6 working days. If AI rewriting after parsing is needed, add 1–2 days for GPT API integration. Cost is calculated individually for your project.

Contact us for an assessment of your project—we will fill the catalog in 4–6 days and save up to 70% of your text writing budget. Get a consultation on catalog automation: we will analyze sources, choose the optimal solution, and propose implementation.

Parser Development for 1C-Bitrix: Where to Start?

XMLReader, not SimpleXML — the choice of tool determines the project's fate. SimpleXML loads the entire XML into memory, and with an 800 MB supplier file, PHP will crash with a fatal error on a 512 MB limit. XMLReader processes streamingly, node by node, consuming 20–30 MB — 30 times more efficient. This detail starts any parser development for Bitrix. With over 10 years of Bitrix development and 50+ parser projects delivered, we know the pitfalls. Contact us to start your parser development today.

What Problems Does Parsing Solve?

• Primary catalog filling — 15,000 cards with descriptions, characteristics, photos. Manually, that's three months of content manager work; a parser takes a week with debugging.
• Competitor price monitoring — collecting data from Ozon, Wildberries, competitor sites. A competitor drops the price on a hot item — you find out in two hours, not two weeks.
• Supplier aggregation — five price lists in different formats (CSV with CP1251, XML in CommerceML, Excel with merged cells) become a single catalog with a unified property system.
• Card enrichment — pulling characteristics, instructions, 3D models from manufacturer sites. Without this, a product card is an SEO empty shell.
• Assortment update — products missing from the supplier feed are deactivated via CIBlockElement::Update($ID, ['ACTIVE' => 'N']). New ones are created. The catalog stays synchronized.

What Tools Do We Use in Parser Development?

Static websites — PHP (Goutte, Symfony DomCrawler) or Python (Scrapy, lxml). Speed: 50–100 pages/sec. Sufficient for catalogs without JS rendering.

SPA and dynamic websites — Puppeteer or Playwright. Infinite scroll, AJAX filters, lazy-load images — headless browser handles it all. Speed drops to 1–10 pages/sec, but there is no alternative: data exists only after JavaScript execution.

Supplier files:

• Excel (XLS, XLSX) — PhpSpreadsheet. Beware of merged cells and formulas — they break automatic mapping.
• CSV — fgetcsv() with correct encoding. Suppliers love CP1251, BOM in UTF-8, and semicolons instead of commas. All need detection and handling.
• XML/YML — XMLReader for large files, SimpleXML for feeds up to 50 MB.
• CommerceML — standard exchange format with 1C. We parse import.xml and offers.xml, map to information block structure.

API — Supplier REST endpoints, marketplace APIs (Ozon Seller API, Wildberries API). We work within rate limits, handle pagination.

How Is the Auto-Population Pipeline Structured?

Four stages. Each can break in its own way.

1. Collection. Parser crawls sources via cron schedule. Raw data goes to an intermediate table — not directly into b_iblock_element. Log everything: pages visited, elements parsed, where we got 403 or timeout. Without logs, debugging a parser is like fortune-telling.

2. Normalization. Main work here:

   • Clean HTML tags, extra spaces, Unicode garbage
   • Units: "mm" → "mm", "millimeters" → "mm", "миллиметр" → "mm"
   • Map supplier categories to Bitrix information block sections. One supplier has "Notebooks", another "Notebooks and tablets", third "Laptops" — all into one section
   • Deduplication by SKU, EAN/GTIN. One product from three suppliers should not appear three times

3. Load into Bitrix. Via CIBlockElement::Add() for new elements, CIBlockElement::Update() for existing. Images: download, resize via CFile::ResizeImageGet(), convert to WebP. Properties via CIBlockElement::SetPropertyValuesEx(). SEO meta via \Bitrix\Iblock\InheritedProperty\ElementValues. SEF URLs generated from name transliteration.

4. Update. Key point — not overwrite manual edits by content manager. Update only price, stock, activity. Description and photos manually edited are flagged with UF_MANUAL_EDIT property and skipped during import. Products missing from feed are deactivated, not deleted.

Why Is Competitor Price Monitoring Necessary?

A separate subsystem with its own specifics:

Result — dashboard: your product vs competitors, price history, trends. The manager sees where to raise price without losing position, and where to react.

CSV/XML Import Module: Customization for Your Format

For supplier files — custom module with admin panel:

• Configurable mapping: "column B in file → BRAND property of information block"
• Auto-detect encoding (CP1251, UTF-8, UTF-16) via mb_detect_encoding() with validation
• Download images from URL with queue — to avoid channel saturation
• Incremental update by row hash: row changed — update, no — skip
• Cron schedule, report: created 145, updated 892, errors 3 (with details)

Large files: CSV processed in batches of 1000 rows via fgetcsv() (10 times faster than row-by-row), XML streamed via XMLReader, background execution via Bitrix agent queue — no PHP timeouts.

Legal Aspects to Consider

• robots.txt — respect it. Crawl-delay — comply.
• Request frequency — 1–2 per second, no more. Don't DDoS someone else's site.
• Manufacturer content — use it. Unique author texts — don't copy.
• Personal data — don't collect.

What Is Included in a Turnkey Parser Development?

How We Work and Deadlines

1. Prototype — parser for 1–2 sources in 2–3 days. Assess data quality, pitfalls (Cloudflare protection, captcha, dynamic loading).
2. Development — full pipeline: parser → normalization → import into Bitrix → admin panel for management.
3. Testing — run on full catalog volume, check edge cases (empty fields, malformed HTML, broken images).
4. Launch — configure cron, error monitoring via Telegram bot.
5. Support — competitor changed layout? Update CSS selectors in parser.

Get in touch for a free consultation — we will analyze your data sources and propose the optimal parser architecture. Request a project assessment today and get a fixed deadline. We guarantee stable parser operation and full support throughout the usage period.