1C-Bitrix Price List Generation Setup – Automatic Export

A manager spends an hour assembling a price list in Excel — and still makes a mistake in the price for a regular customer. With a catalog of 15,000 items, manual export takes a whole day, and pricing errors lead to lost profit or customers. Each error costs the company an average of 5,000 rubles; with 2,000 errors annually, that's 10 million rubles lost. Our price list generation setup from 1C-Bitrix ensures data is always up-to-date and role-based. Automation eliminates manual errors and gives managers ready documents in seconds. The client gets an up-to-date pricing sheet in minutes, not hours. Setting up automatic export with access control and updates is the foundation for an efficient sales department.

Problems We Solve

Manual price updates—when items or prices change, you need to manually edit files, risking outdated data and client dissatisfaction. On one project with 50,000 products, managers spent 3 days updating Excel. Calculation errors: different price types (wholesale, retail, special offers) are easily mixed up. Our system automatically substitutes the correct price for the user, eliminating confusion. Access to confidential information: retail clients must not see wholesale prices. Segregation via user groups and price types solves this.

How We Do It

We use PhpSpreadsheet (phpoffice/phpspreadsheet) PhpSpreadsheet — a modern library for working with Excel. The generator is written in PHP 8.1+, uses Bitrix ORM and tagged caching for faster queries. All queries are optimized: price selection via CCatalogProduct::GetOptimalPrice, stock via CCatalogStoreProduct, section caching.

Here's an example of generating an Excel price list with formatting and auto-width columns:

use PhpOffice\PhpSpreadsheet\Spreadsheet;
use PhpOffice\PhpSpreadsheet\Writer\Xlsx;
use PhpOffice\PhpSpreadsheet\Style\NumberFormat;

class BitrixPriceListGenerator
{
    public function generate(int $priceTypeId, array $userGroups): string
    {
        $spreadsheet = new Spreadsheet();
        $sheet = $spreadsheet->getActiveSheet();
        $sheet->setTitle('Price list');

        // Headers
        $headers = ['SKU', 'Name', 'Section', 'Price', 'Currency', 'Stock'];
        foreach ($headers as $col => $header) {
            $sheet->setCellValueByColumnAndRow($col + 1, 1, $header);
        }

        // Header style
        $sheet->getStyle('A1:F1')->getFont()->setBold(true);
        $sheet->getStyle('A1:F1')->getFill()
            ->setFillType(\PhpOffice\PhpSpreadsheet\Style\Fill::FILL_SOLID)
            ->getStartColor()->setARGB('FFE0E0E0');

        $row = 2;
        $res = $this->getProductsWithPrices($priceTypeId, $userGroups);

        foreach ($res as $product) {
            $sheet->setCellValueByColumnAndRow(1, $row, $product['ARTICLE']);
            $sheet->setCellValueByColumnAndRow(2, $row, $product['NAME']);
            $sheet->setCellValueByColumnAndRow(3, $row, $product['SECTION']);
            $sheet->setCellValueByColumnAndRow(4, $row, $product['PRICE']);
            $sheet->setCellValueByColumnAndRow(5, $row, $product['CURRENCY']);
            $sheet->setCellValueByColumnAndRow(6, $row, $product['QUANTITY']);

            // Price number format
            $sheet->getStyleByColumnAndRow(4, $row)
                ->getNumberFormat()
                ->setFormatCode(NumberFormat::FORMAT_NUMBER_COMMA_SEPARATED2);
            $row++;
        }

        // Auto-width columns
        foreach (range('A', 'F') as $col) {
            $sheet->getColumnDimension($col)->setAutoSize(true);
        }

        // Add generation date
        $sheet->setCellValue('A' . ($row + 1), 'Generated: ' . date('d.m.Y H:i'));

        $writer = new Xlsx($spreadsheet);
        $tempFile = tempnam(sys_get_temp_dir(), 'pricelist_');
        $writer->save($tempFile);

        return $tempFile;
    }

    private function getProductsWithPrices(int $priceTypeId, array $userGroups): array
    {
        $result = [];
        $dbRes = \CIBlockElement::GetList(
            ['SECTION_ID' => 'ASC', 'SORT' => 'ASC'],
            ['IBLOCK_ID' => CATALOG_IBLOCK_ID, 'ACTIVE' => 'Y'],
            false,
            false,
            ['ID', 'NAME', 'IBLOCK_SECTION_ID', 'PROPERTY_ARTICLE']
        );

        $sectionCache = [];

        while ($el = $dbRes->GetNextElement()) {
            $fields = $el->GetFields();
            $productId = $fields['ID'];

            // Get price for type
            $priceRes = \CCatalogProduct::GetOptimalPrice($productId, 1, $userGroups);
            $price = $priceRes['PRICE']['PRICE'] ?? 0;

            // Cache section names
            $sectionId = $fields['IBLOCK_SECTION_ID'];
            if (!isset($sectionCache[$sectionId])) {
                $sectionCache[$sectionId] = \CIBlockSection::GetByID($sectionId)->GetNext()['NAME'] ?? '';
            }

            // Stock
            $storeData = \CCatalogStoreProduct::GetList(
                [], ['PRODUCT_ID' => $productId]
            )->Fetch();
            $quantity = $storeData['AMOUNT'] ?? 0;

            $result[] = [
                'ARTICLE' => $fields['PROPERTY_ARTICLE_VALUE'],
                'NAME'    => $fields['NAME'],
                'SECTION' => $sectionCache[$sectionId],
                'PRICE'   => $price,
                'CURRENCY' => $priceRes['PRICE']['CURRENCY'] ?? 'RUB',
                'QUANTITY' => $quantity,
            ];
        }

        return $result;
    }
}

Access Control is built on Bitrix user groups and price types. Example of determining the price type:

$userId = \Bitrix\Main\Context::getCurrent()->getUser()->getId();
$userGroups = \CUser::GetUserGroup($userId);

$priceTypeId = 1; // base
if (in_array(WHOLESALE_GROUP_ID, $userGroups)) {
    $priceTypeId = 2; // wholesale
} elseif (in_array(VIP_GROUP_ID, $userGroups)) {
    $priceTypeId = 3; // VIP
}

This approach allows generating a separate pricing sheet for each price type, accessible only to the corresponding group. We also configure file access rights via the web server or .htaccess.

Benefits of Automating Generation Automation via Bitrix agents is especially beneficial for catalogs from 10,000 items. The agent runs at night, generates pricing sheets for all price types, and saves them on the server:

function GeneratePriceLists(): string
{
    $generator = new BitrixPriceListGenerator();
    foreach (getPriceTypes() as $type) {
        $file = $generator->generate($type['ID'], $type['USER_GROUPS']);
        $targetPath = '/upload/pricelists/pricelist_' . $type['CODE'] . '.xlsx';
        rename($file, $_SERVER['DOCUMENT_ROOT'] . $targetPath);
    }
    return __FUNCTION__ . '();';
}

Time savings for a catalog of 10,000 items: manual export — 4 hours, automatic — 2 minutes for generating all pricing sheets. Human error is eliminated. Each price error costs the company an average of 5,000 rubles. Automation reduces errors by 95%, from 8% to 0.5%. Our clients generate over 100 pricing sheets daily with zero errors. Setup cost starts from 50,000 rubles, payback within 2 months. Clients typically save over 500,000 rubles annually by eliminating manual errors.

Price List Format Comparison

The format choice depends on the audience: managers prefer Excel, for automatic upload to ERP — CSV, for clients — PDF.

Work Process

1. Analysis. We study your catalog structure, price types, format requirements. Identify bottlenecks in the current export.
2. Design. Agree on pricing sheet layout, permission logic, generation frequency. Create a prototype.
3. Implementation. Write a PHP module with caching and query optimization. We implement a complete price list generation setup with caching and optimization. Code is commented.
4. Testing. Check on real data, fix nuances. Test all price types and user groups.
5. Deployment. Install on the server, configure agents, grant access. Train responsible employees.

require_once($_SERVER['DOCUMENT_ROOT'].'/bitrix/modules/main/include/prolog_before.php');
$GLOBALS['DB']->StartTransaction();
if (CAgent::CheckAgentName('GeneratePriceLists();')) {
    CAgent::AddAgent('GeneratePriceLists();', 'main', 'N', 86400, '', 'Y', date('d.m.Y H:i:s', strtotime('+1 day')), 30);
}
$GLOBALS['DB']->Commit();

What's Included

• Setting up price list generation in required formats
• Access control for different price types
• Development and configuration of auto-generation agents
• Integration with 1C (CommerceML) if needed
• Operation documentation
• Training of responsible employees
• 12-month code warranty. Our experience: 5+ years on the market, over 50 successful Bitrix projects. We are certified 1C-Bitrix specialists. Contact us to evaluate your project — we will calculate the timeframe and cost within one business day. Get a consultation on setting up automatic pricing automation today.

Estimated Timeframes

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.