Automated Price and Stock Updates from Supplier Price Lists

When you have 10,000 products in your catalog and your supplier sends a daily Excel price list, updating manually wastes time and invites errors.

We automate this process: fetch the file, parse it, update prices and stocks without human intervention. A full integration takes 4 to 6 business days per supplier. Manually updating 1,000 items takes hours—and typos and missed rows are common. Automation eliminates human error and frees resources for higher-value tasks.

How automation reduces costs

Manual update of 1,000 items takes 2–3 hours, with inevitable errors. Automation cuts time to zero and reduces errors by 95%. Once configured, the process runs for years. Our client with 15,000 SKUs saves 40 hours per month—tens of thousands of rubles monthly. Payback period is 2–3 months. For a store with 50,000 products, benefits scale: time savings can exceed 100 hours per month.

How we fetch price lists from different sources

Email with attachment is the most common scenario. We connect to the mailbox via IMAP, search for emails from the supplier by subject or sender, and download the attachment. For security, we use a separate mailbox or folder.

$imap = imap_open('{mail.imap.example.com:993/imap/ssl}INBOX', $user, $pass);
$emails = imap_search($imap, 'FROM "[email protected]" UNSEEN');
foreach ($emails as $num) {
    $structure = imap_fetchstructure($imap, $num);
    // extract attachment
}

FTP/SFTP—we download the file daily on a schedule, compare the modification date with the previous run. If unchanged, we skip. HTTP URL—supplier publishes a price list via a link with Basic Auth. All options are supported out of the box.

How to set up column mapping for any format

Problem: each supplier has a different format—SKU sometimes in column B, sometimes in D; header rows range from 2 to 5. Solution—configurable mapping stored in a Highload-block:

supplier_id: 42
sku_column: B       # SKU in column B
price_column: D     # price in column D
qty_column: F       # stock in column F
header_rows: 3      # first 3 rows are header

To read Excel files, we use PhpSpreadsheet (successor of PHPExcel):

$spreadsheet = \PhpOffice\PhpSpreadsheet\IOFactory::load($filePath);
$sheet = $spreadsheet->getActiveSheet();
$rows = $sheet->toArray();

If the supplier changes the format, edit the mapping. For 50,000+ SKUs, we build a reverse index in memory when the worker starts: load all SKU mappings once to avoid DB hits.

How to update prices and stocks via Bitrix API

Prices in Bitrix are stored in the b_catalog_price table. Each price type is a separate record. We update them via API:

$priceType = CCatalogPriceType::GetList([], ['NAME' => 'Purchase price'])->Fetch();
CCatalogProduct::SetPrice($elementId, $priceType['ID'], $price, 'RUB');
// markup for retail price
$retailPrice = $supplierPrice * $supplier->getMarkupCoefficient();

Stocks are in b_catalog_store_product. If warehouses are not used, we update QUANTITY directly:

CCatalogStoreProduct::Update($storeProductId, ['AMOUNT' => $qty]);

Identification of products by SKU: we store correspondences in an infoblock property SUPPLIER_SKU or in a Highload-block SupplierMapping. For 50,000+ SKUs, we use in-memory cache.

Comparison of manual vs automated import

Automation is 50 times faster and 100 times more accurate than manual work.

What's included in the integration setup

• Analysis of data sources and current price list format
• Development of column mapping configuration for each supplier
• Setup of file retrieval (email/FTP/HTTP) and the agent for processing
• Implementation of price and stock updates via Bitrix API, accounting for trade catalogs and warehouses
• Creation of error logging and notification system (Telegram, Email)
• Delivery of documentation: architecture description, instructions for adding a new supplier, support contacts
• Operator training: how to recognize a failure and what to do when the format changes
• Integration support for one month after launch

Typical import errors and how to avoid them

File format change. Supplier didn't warn and the parser fails. Logging records errors, we get a notification and quickly fix the mapping. For critical suppliers, we set up a fallback parser.

Duplicate SKUs. One SKU can appear in two products. Solution: check SKU uniqueness before import. If duplicate, stop the process and send an alert.

Incorrect prices. Sometimes the supplier makes a mistake in the file. We check for a valid price range: if the price changes by more than 30%, the process pauses and requires confirmation.

For stores with frequent price changes and large assortments, automation is the only way to stay current. Contact us to evaluate your project. We will analyze your suppliers' price lists and propose the optimal architecture. Get a consultation on import automation—we'll show you how to speed up catalog updates tenfold.

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.