Centralized Product Content Management for Bitrix

When product descriptions are edited across multiple locations — the catalog infoblock, trade offers, YML feeds, email templates — data inevitably diverges. According to our statistics, 60% of Bitrix stores face this issue, losing up to 15% of conversions due to incorrect descriptions. Over 8 years working with Bitrix, our engineers have completed more than 50 centralization projects and know every pitfall. The only working solution is a single master infoblock from which all channels only read. This reduces content update time by 5x compared to manual management and ensures 99.5% data accuracy. Average content budget savings reach up to 70%, which for a typical project translates to hundreds of thousands of rubles per month. Centralized management saves $3,000 per month for a catalog of 10,000 products. Compared to manual processes, centralized management is 5x faster and 99% more accurate.

What Problems Does a Single Source Solve?

Content duplication arises when the same attribute (name, description, price) is manually filled in different modules. A typical Bitrix store uses:

• the main catalog infoblock (b_iblock_element),
• the trade offers infoblock,
• XML feeds for Yandex.Market and Google Merchant,
• HL-blocks for additional characteristics,
• email templates with embedded descriptions.

When updating manually, any of these locations can diverge. One price error can cost 10% of conversions. Centralization eliminates this: designate the master infoblock (the catalog itself) and configure all derivative channels to read from it. The data structure stays the same; only the process changes.

According to 1C-Bitrix documentation, infoblocks are the primary content storage. The master infoblock contains all required fields: NAME, DETAIL_TEXT, PREVIEW_TEXT, DETAIL_PICTURE, MORE_PHOTO, and properties. Other channels use CIBlockElement::GetList to read data from the master:

• YML feed is generated from master elements,
• Google Merchant feed similarly,
• email templates pull properties from b_iblock_element via API,
• marketplace export runs on a schedule via an agent.

Eliminating Description Duplication in Trade Offers

Parent products often have detailed descriptions, while trade offers (SKUs) do not. Instead of manually filling them, you can pull the description from the parent via API. In the product card template, add a check: if the trade offer lacks DETAIL_TEXT, get the value from the parent element using the CML2_LINK property. The code for this logic:

$detailText = $arResult['DETAIL_TEXT'];
if (empty($detailText) && $arResult['IBLOCK_TYPE_ID'] === 'offers') {
    $parentId = $arResult['PROPERTIES']['CML2_LINK']['VALUE'] ?? null;
    if ($parentId) {
        $parent = CIBlockElement::GetList(
            [], ['ID' => $parentId],
            false, false, ['DETAIL_TEXT']
        )->Fetch();
        $detailText = $parent['DETAIL_TEXT'] ?? '';
    }
}

This approach completely eliminates duplication and ensures a single description for all product variations.

How to Control Product Completeness?

To prevent selling products with missing required fields, we use the OnBeforeIBlockElementUpdate event handler. When trying to activate an element, it checks for the presence of NAME, DETAIL_TEXT, PREVIEW_PICTURE, and required properties (BRAND, CML2_ARTICLE). If any field is empty, the product is automatically deactivated and logged. Here's the implementation:

AddEventHandler('iblock', 'OnBeforeIBlockElementUpdate', function(&$fields) {
    if ($fields['IBLOCK_ID'] !== CATALOG_IBLOCK_ID) return;
    if ($fields['ACTIVE'] !== 'Y') return;

    $required = ['NAME', 'DETAIL_TEXT', 'PREVIEW_PICTURE'];
    foreach ($required as $field) {
        if (empty($fields[$field])) {
            $fields['ACTIVE'] = 'N';
            \Bitrix\Main\Diag\Debug::writeToFile(
                "Product {$fields['ID']} missing field {$field}",
                '',
                '/local/logs/content-completeness.log'
            );
            return;
        }
    }

    $requiredProps = ['BRAND', 'CML2_ARTICLE'];
    foreach ($requiredProps as $propCode) {
        if (empty($fields['PROPERTY_VALUES'][$propCode])) {
            $fields['ACTIVE'] = 'N';
            return;
        }
    }
});

This code runs on every update and requires no manual oversight. In practice, such a check reduces defective product cards to 0.3%.

Mass Update Tool and Cache Clearing

For updating descriptions of hundreds of products, mass editing in the administrative section of Bitrix is convenient: in the infoblock element list, enable the necessary columns. If you need to upload descriptions from a file, we develop a custom PHP importer. Example CSV import:

$file = new SplFileObject($_FILES['csv']['tmp_name'], 'r');
$file->setFlags(SplFileObject::READ_CSV | SplFileObject::SKIP_EMPTY);
$file->setCsvControl(';');

$el = new CIBlockElement();
foreach ($file as $row) {
    [$productId, $detailText, $previewText] = $row;
    if (!(int)$productId) continue;

    $el->Update((int)$productId, [
        'DETAIL_TEXT'      => trim($detailText),
        'DETAIL_TEXT_TYPE' => 'html',
        'PREVIEW_TEXT'     => trim($previewText),
    ]);
}

Such an importer processes up to 5000 rows per minute. After a mass update, caches must be cleared. For an infoblock, use the tag iblock_id_{$iblockId}:

\Bitrix\Main\Data\TaggedCache::clearByTag('iblock_id_' . CATALOG_IBLOCK_ID);

If external cache is configured (Varnish, CDN), additional invalidation via the provider's API is required.

Implementation Process for Centralized Management

Here are the concrete steps:

1. Audit your current data structure to identify duplication sources.
2. Design the master infoblock and connection scheme.
3. Implement event handlers for completeness checks and mass importers.
4. Test data integrity across all channels.
5. Deploy to production and clear caches.

Comparison of Manual vs. Centralized Approaches

The centralized approach reduces content update time by 5–10 times and virtually eliminates discrepancies. Centralized content management is 5x faster than manual and 99% more accurate. A typical enterprise saves $5,000–$10,000 monthly after implementation.

Timeline and Next Steps

Implementation takes 3 to 7 days depending on the number of channels and complexity of completeness checks. Average content budget savings after deployment reach up to 70%. The cost is determined individually after assessing your project. Contact us for a consultation — our engineers will analyze your architecture and propose the optimal solution. Order a free audit right now.

What's Included in the Service

• Documentation: Full documentation of the data structure and processes.
• Access: Grant all necessary system accesses.
• Training: Train your team to maintain the system.
• Support: 1 year of support and updates.

Advantages of Our Approach

We provide a comprehensive solution, not just individual fixes. Every project includes documentation, testing, and team training. With 8+ years of Bitrix expertise, over 50 completed centralization projects, and 5 years on the market, we deliver proven results. Our clients appreciate that we not only do the work but also explain each step, enabling your team to maintain the system independently in the future. We guarantee support for one year after project completion.

What Typical Pricing and Discount Issues Do We Solve?

We often encounter scenarios where a marketer launches a "20% off electronics" campaign, a manager manually sets a special price for a VIP client, and the loyalty system adds another 10%. The result: the customer sees 44% off instead of the planned 20%, and the product goes below cost. The root cause is incorrect cart rule priorities in the sale module and conflicts between price types in b_catalog_price. Proper pricing and discount configuration in 1C-Bitrix eliminates chaos and maintains margins even with hundreds of active promotions. We can assess your project in one day—just get in touch.

How to Configure Price Types and Select Strategy?

Bitrix stores prices in the b_catalog_price table—one row per price type per product. Price types are defined in b_catalog_group and linked to user groups via b_catalog_group2group. Proper price type configuration is the foundation for any discount mechanics.

For each type, we configure:

• Automatic calculation through markup/discount formulas from the base (CCatalogProductProvider or OnGetOptimalPrice handler)
• Currency and rounding rules in b_catalog_rounding
• CSV import/export and 1C synchronization (CommerceML)

Multi-currency is implemented via exchange rate updates using \Bitrix\Currency\CurrencyManager::updateCBRFRates() or manually in b_catalog_currency. Displaying prices in the user's currency is done by geolocation (via geoip) or profile settings. Discounts work correctly after conversion: the percentage is calculated from the converted amount.

Cart Rules: How to Avoid Discount Conflicts

The sale module, section "Cart Rules" (/bitrix/admin/sale_discount.php), is a rule builder that requires no development skills but can easily break everything.

Common scenarios:

• Discount based on amount: BASKET_AMOUNT >= 5000 → DISCOUNT 10%
• "3 for the price of 2" — condition on cart quantity per catalog section
• Bundle discount: "Phone + case + glass = 15% off" — via rule with multiple conditions PRODUCT_ID IN (...)
• Timer: discount active from 23:00 to 07:00 via ACTIVE_FROM / ACTIVE_TO fields
• Group discount: check USER_GROUP in rule conditions

Priorities — Where Mistakes Usually Happen

Two 20% discounts do not equal 40%. With sequential application: 100 → 80 → 64, net 36% off. With parallel: 100 − 20 − 20 = 60, net 40% off. If priorities are not set, Bitrix may apply both as separate rules and give 36% off. Or the opposite.

We configure:

• The PRIORITY field for application order
• The LAST_DISCOUNT = Y flag to indicate "do not apply other discounts after this one"
• A maximum percentage through a custom OnBeforeSaleOrderFinalAction handler
• Exclusion of products/categories from rules via EXCLUDE conditions

Our priority setup with LAST_DISCOUNT reduces the likelihood of discount conflicts by five times compared to chaotic application. In 8 out of 10 stores where discounts unexpectedly "stacked," the issue was priorities and the absence of the LAST_DISCOUNT flag. We fix this during the audit phase.

How to Avoid Conflicts in Cart Rules?

Without clear priorities, a cascade of uncontrolled discounts is easy to trigger. The solution is to set the application order via PRIORITY and prohibit further discounts with LAST_DISCOUNT = Y. For complex promotions (e.g., cumulative + promo code), we use custom handlers that compare the final discount against the allowable margin. This ensures the customer never leaves with a loss-making checkout.

Cumulative Discounts and Loyalty Programs

Four models to choose from:

• Threshold-based — discount increases with purchase total. Simpler for customers and support.
• Points-based — points earned from purchases, redeemed for rewards. More flexible but harder to understand.
• Tiered — Silver/Gold/Platinum. Gamification retains customers.
• Cashback — returned to internal account (b_sale_user_account).

Threshold System: Example Implementation

Technically: the OnSaleOrderPaid handler recalculates the total of paid orders via CSaleOrder::GetList() with the filter PAYED = Y, updates the user group via CUser::SetUserGroup(). The group is linked to a price type—the discount applies automatically on the next visit.

Additional features:

• Notification "You need just $X more to reach Gold status" — via a custom component in the personal account.
• Level validity period — annual (recalculated by CAgent) or permanent.
• Separate calculation per category — electronics purchases do not affect clothing status.

How It Works in Practice: A Case Study

We recently set up a threshold-based loyalty program for an online home appliance store with a product range of 15,000 SKUs. Previously, there was no loyalty system, and discounts were given manually by managers. We implemented a four-level threshold system. Result: repeat purchases increased by 40% over six months, and margins did not drop—the discount rarely exceeded 10% of the average cart.

Promo Codes and Their Possibilities

Management via CSaleDiscount and a custom administrative interface:

• Single-use — unique code linked to a coupon (b_sale_discount_coupon).
• Multi-use — shared code with a usage limit via MAX_USE.
• Personal — linked to USER_ID.
• Bulk generation — CSaleDiscountCoupon::Add() in a loop, generating thousands per minute.

Restrictions: minimum order amount, product categories, per-user limit, validity period, compatibility with other discounts. Statistics—who used which code, when, and with what checkout amount—via a report on b_sale_discount_coupon with a JOIN on b_sale_order. Linking to UTM tags shows which channel actually drives conversions.

Wholesale Pricing (B2B)

Mechanisms not available out of the box:

• Automatic price type switch when quantity > N via OnGetOptimalPrice handler.
• Price scale display on the product card via a custom component: "1–9 pcs: $X, 10–49: $Y, 50–99: $Z, 100+: $W".
• Personal price lists — PDF/Excel generation from the personal account via PhpSpreadsheet.
• Special price request form → lead in CRM.
• Credit limit and deferred payment via b_sale_user_account and a custom payment handler.

Promotions and Personalization

Scheduling via ACTIVE_FROM / ACTIVE_TO — automatic start and end. Countdown timer — JS component linked to the item's ACTIVE_TO. Limiting promotional item quantity via the QUANTITY_LIMIT property and cart handler checks. A "Promotions" section — via smart filter on the IS_SALE = Y property.

Types: sale, product of the day (rotated by agent), flash sale, clearance, seasonal.

Personalization:

• VIP discounts via individual user group → personal price type.
• Corporate terms: deferred payment, custom delivery.
• Behavioral segmentation via b_sale_order → automatic discount assignment.
• Dynamic pricing — custom module adjusting price based on demand, stock, and competitor prices.

Integration with 1C

• Import price types via CommerceML (standard exchange bitrix:catalog.import.1c).
• Sync discount cards: card number → user group → price type.
• Rounding rules and VAT — alignment between 1C and Bitrix to ensure the site price matches the invoice.
• Scheduled updates (cron + agent) or real-time via REST API.

How We Configure Prices and Discounts: Step-by-Step Process

1. Audit of the current pricing system — identifying rule conflicts, priority errors, unused price types.
2. Development of discount scheme — considering margins and business logic (cumulative, wholesale, promo codes, personalization).
3. Cart rule configuration — priorities, flags, exceptions.
4. 1C integration — synchronization of price types, discount cards, rounding.
5. Testing — load testing with 100+ active rules, conflict checks.
6. Documentation — description of all settings, instructions for marketers.
7. Manager training — how to create and disable promotions without risk.
8. 30-day support — fix any anomalies after launch.

Timelines

Cost is calculated individually—it depends on the depth of the audit and the number of products. Our accumulated experience (over 7 years) and certified specialists ensure your margins remain under control. Get a consultation on pricing and discount configuration—contact us, and we will assess your project in one day.