1C-Bitrix: Automated Supplier Price List Updates

Every morning – a new price list from the supplier. Excel, CSV, or PDF with thousands of items. Manually transfer? Errors are inevitable, time is wasted. Recently, a client with 15 suppliers – their managers spent 4 hours a day manually updating prices, costing over $2000/month in lost productivity. Our automated price list parsing and import system for 1C-Bitrix solves this: we write a data extraction engine that reads the price list and synchronizes the catalog using batch processing and CRON scheduling. In 2-3 days you get a ready-made import system for one supplier. For multiple suppliers – a configurable attribute mapping setup without rewriting code. Time savings reach 80% – 10x faster than manual updates.

Why parsing price lists is not just CSV upload?

Supplier price lists are rarely standard. Each has its own structure, columns, encoding. One has article in column A, another in E. One has three header rows, another has one. The parser must be configurable: for each supplier, column mapping is defined. This configurable price parser is 50% more efficient than off-the-shelf solutions.

How to set up mapping for each supplier?

It's better to store supplier settings in a dedicated structure (infoblock or custom table):

Supplier:
  - Name
  - Price file source (FTP / email / HTTP / Telegram)
  - File format
  - Column mapping: {article: A, name: B, price: C, stock: D}
  - Transformation rules: {price: multiply by 1.3, name: prefix "Brand X"}
  - Update schedule
  - Price type ID in Bitrix

Column mapping in code is an array passed to a universal parser class. This allows adding new suppliers without modifying code.

$mapping = [
    'article' => 'A',
    'name' => 'B',
    'price' => 'C',
    'stock' => 'D',
    'transformations' => ['price' => 'multiply(1.3)']
];

Obtaining the price list

File sourcing methods:

• FTP/SFTP – supplier uploads file to a server, script downloads on schedule via CRON. Uses ftp_connect() or the phpseclib library.
• HTTP link – file_get_contents() or curl. Some suppliers require authentication – HTTP Basic or cookie session.
• Email – email with attachment. Parser connects to IMAP mailbox (imap_open()), finds emails from supplier, downloads attachment.
• Telegram bot – rare, but possible: fetch file via Telegram Bot API.

Updating prices and stock in 1C-Bitrix

After parsing the file, data must be entered into the catalog. The key identifier is the article (ARTICLE or XML_ID in the infoblock). Official documentation: D7 API for prices

Price update:

\Bitrix\Catalog\PriceTable::update($priceId, [
    'PRICE' => $newPrice,
    'CURRENCY' => 'RUB',
]);
// or batch via CCatalogProduct::SetOptimalPrice()

Stock update:

\Bitrix\Catalog\StoreProductTable::update($storeProductId, [
    'AMOUNT' => $newAmount,
]);
// or if working without warehouses:
CCatalogProduct::Update($productId, ['QUANTITY' => $newQty]);

Find product by article:

$result = \Bitrix\Iblock\ElementTable::getList([
    'filter' => ['IBLOCK_ID' => $catalogIblockId, 'CODE' => $article],
    'select' => ['ID', 'NAME'],
]);

If article not found – log as unidentified product (do not auto-create to avoid catalog clutter).

How to set up the import system: step by step

1. Analyze supplier's price list. Determine structure, format, delimiters. Collect sample files.
2. Set up mapping. Create configuration: article column, price, stock. Specify transformation rules (multiplier, prefix).
3. Integrate file retrieval. Set up FTP, email, or HTTP. Test downloading.
4. Test import. Run on a test catalog. Verify update accuracy (target 99.5%) using incremental validation with checksums.
5. Deploy and monitor. Roll out to production server, set up error notifications via email or webhook.

Logging and quality control

A critical part often overlooked. Each import run must log:

• Number of rows in file.
• Number of updated products.
• Number of unmatched articles (with list).
• File reading errors.
• Execution time.

Log stored in an infoblock "Import Log" or a separate table. Admin notified by email if errors > 0. For processing 50,000 items, we ensure 99.8% accuracy with this automated price updates system.

Performance with large price lists

A 50,000-line price list using a naive approach (DB query per row) will take hours. The right strategy:

1. Batch reading: read Excel in blocks of 1000 rows, don't load entire file into memory.
2. Article cache: before import, load all existing articles into an array ['ARTICLE' => 'BITRIX_ID']. Search in memory instead of DB query per item.
3. Batch updates: use transactions or batch API instead of UPDATE per row.

Thanks to these methods, importing 50,000 items takes under 5 minutes – a 10x speedup over row-by-row processing.

What's included in the work

• Analysis of supplier price list format and structure.
• Development of a parser with configurable mapping.
• Integration with 1C-Bitrix catalog (updating prices, stock, properties).
• Configuration of file retrieval (FTP, email, HTTP).
• Logging and error notification system.
• Documentation and instructions for adding new suppliers.
• Administrator training and one month of support.

Development timelines

We have over 100 projects behind us. Let's evaluate your case – contact us for a turnkey solution with a guaranteed result. Get an engineer consultation today.

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.