Feed Generation Module for 1C-Bitrix: Automating Export

A marketer discovers that the product feed for Yandex.Market updates once a day through a manual export, while prices in the catalog change several times a day due to imports from 1C. The result: marketplaces show outdated prices — customers click, see a different price, and leave. The standard Bitrix export module (catalog.export) handles basic cases, but encounters limitations with non-standard requirements (multiple warehouses, custom properties, regional conditions). On a project with a catalog of 50,000 products, the price discrepancy hit 15%, causing a 30% abandonment rate. Only after implementing a custom module with incremental updates was the problem resolved. Our experience spans over 30 successful projects. We guarantee correct stock handling and no duplicates. Contact us for a module tailored to your specifics.

Why Standard Export Falls Short for Feed Generation

The standard catalog.export module does not support:

• Multiple warehouses with separate stock levels.
• Custom properties for different channels (e.g., condition for Google Merchant).
• Regional prices and discounts.
• Incremental updates — full feed regeneration each time, which on 50,000 products takes 5–10 minutes and loads the server.

These limitations lead to manual exports, errors, and outdated data. A custom module solves it all.

How the Feed Generation Module Works

The core task is to make generation fast, flexible, and automatic. The module is built around three components: a feed template engine, an update scheduler, and a format registry.

The format registry stores configurations for each channel: Yandex.Market (YML), Google Merchant (XML/CSV), VK, Avito, Ozon, custom client formats. Each format is described by a PHP class implementing the FeedFormatInterface:

interface FeedFormatInterface {
    public function getHeader(): string;
    public function renderOffer(array $element, array $prices): string;
    public function getFooter(): string;
    public function getMimeType(): string;
}

This allows adding new formats without touching the generator core. More about YML format on Wikipedia.

The generator works in a streaming mode: data is read from b_iblock_element, b_catalog_price, b_catalog_product via DataManager::getList with pagination (batches of 500 elements) and immediately written to a file using fwrite. Generating a feed of 50,000 products does not require 512 MB of RAM. The final file is atomically replaced (rename), so a crawler never receives a partially written document.

How Price and Stock Resolvers Work

This is the most variable part. One project needs prices for unregistered users, another for special prices with promotions, yet another for the minimum price across all warehouses.

The module implements a price resolver — a strategy that selects the final price based on a set of rules:

$priceResolver = new PriceResolver([
    new DiscountRule($userId),           // apply discounts via Sale\Discount
    new RegionPriceRule($regionCode),    // regional markup
    new MinPriceRule(),                   // take minimum among price types
]);
$finalPrice = $priceResolver->resolve($productId);

Stock by warehouses. For Ozon and other platforms, you need to specify stocks for specific warehouses (b_catalog_store_product). The module aggregates stocks from multiple warehouses (up to 50), applies reserves from b_sale_basket, and outputs the correct available quantity.

Product filtering. Through the module interface, you define conditions: only products with non-zero stock, specific sections, exclude by property CML2_EXPORT = N. Conditions are compiled into a filter for CIBlockElement::GetList.

What Is Incremental Update?

Full regeneration of a feed with 50,000 items takes 3–5 minutes. For frequent price changes, this is unacceptable. The module supports incremental mode: via the OnAfterCatalogPriceUpdate event, changed products are recorded, and an agent regenerates only their lines in the feed every 15 minutes using a partial update (temporary file and patching). This update is 10 times faster than full regeneration. The event is described in the Bitrix documentation.

How Monitoring Helps Module Operation

The module maintains a table myvendor_feed_log with generation history: start/end time, element count, file size, errors. The admin interface shows a dashboard: when each feed was last updated, how many products were exported, which were filtered out and why. This enables quick detection of data or configuration issues.

Development Process

1. Audit of current catalog and feed requirements.
2. Architecture design (resolvers, formats, caching).
3. Module development and integration on your project.
4. Configuration of agents and scheduler for automatic generation.
5. Testing on real data and adjustments.
6. Documentation handover and admin training.
7. 1-month warranty support.

What's Included in the Deliverable

• Full module source code with installation instructions.
• Configuration and integration of all required feed formats (up to 5 in standard package).
• Price resolver and stock logic tailored to your catalog.
• Incremental update mechanism with agent setup.
• Monitoring dashboard and logging system.
• Administrator training (2 sessions) and written documentation.
• 1-month priority support after launch.

Comparison: Standard vs. Custom Module

Timeline

Timelines can be adjusted after analyzing your catalog. For an accurate estimate, contact us for a consultation on your project. The trade catalog configuration (prices, warehouse structure, presence of SKUs) must be finalized before development begins. Typical investment starts at $3,000 and pays back within 2 months through reduced abandonment and manual work.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.