Pay What You Want Integration on 1C-Bitrix

You want to allow customers to set their own price — the Pay What You Want (PWYW) model. Standard 1C-Bitrix rigidly fixes prices in the infoblock, and the sale module does not accept arbitrary amounts. Clients often complain about the inability to donate any amount or buy a digital product at their own price. We developed a solution that completely replaces the standard cart and checkout logic. With 10+ years of Bitrix experience, we have implemented over 50 projects with custom prices — this increases conversion by 20–40% in niches with non-fixed pricing (donation certificates, digital goods, consultations). One case: for a charitable foundation we implemented PWYW with a customizable threshold — average donation grew by 35% after removing the fixed contribution.

Flexible Price Implementation

Where to Store Settings — Developing the 'Name Your Own Price' Functionality

For each product participating in the mechanism, three additional parameters are needed:

• PWYW_ENABLED — activity flag (Y/N)
• PWYW_MIN_PRICE — minimum amount (can be 0)
• PWYW_SUGGESTED_PRICE — suggested amount (displayed by default)

Storage methods differ in convenience. Infoblock properties are simple and work immediately, but bulk editing is inconvenient. An HL-block PwywSettings provides a single table for all products — managing 100+ products takes half the time. We recommend an HL-block for clients with large catalogs.

Intercepting the Price When Adding to Cart

Standard $basket->addItem() takes the price from the catalog. We need to intercept the moment before saving and substitute the price from the client. The client part includes a form with a pwyw_price field and an AJAX request to a custom endpoint.

use Bitrix\Sale\Basket;
use Bitrix\Sale\BasketItem;
use Bitrix\Main\Context;

$request = Context::getCurrent()->getRequest();
$productId = (int)$request->getPost('product_id');
$userPrice = (float)$request->getPost('pwyw_price');

// Check minimum threshold
$minPrice = getPwywMinPrice($productId); // reads infoblock property
if ($userPrice < $minPrice) {
    echo json_encode(['error' => 'Price below minimum']);
    die();
}

$basket = Basket::loadItemsForFUser(
    \CSaleBasket::GetBasketUserID(),
    \Bitrix\Main\Context::getCurrent()->getSite()
);

$item = $basket->createItem('catalog', $productId);
$item->setFields([
    'QUANTITY'           => 1,
    'CURRENCY'           => \Bitrix\Currency\CurrencyManager::getBaseCurrency(),
    'LID'                => SITE_ID,
    'PRODUCT_PROVIDER_CLASS' => 'CCatalogProductProvider',
    'PRICE'              => $userPrice,
    'BASE_PRICE'         => $userPrice,
    'CUSTOM_PRICE'       => 'Y',  // prevent automatic recalculation
]);

// Save entered price in cart property
$item->getPropertyCollection()->setProperty([
    'NAME'  => 'PWYW_PRICE',
    'CODE'  => 'PWYW_PRICE',
    'VALUE' => $userPrice,
    'SORT'  => 100,
]);

$basket->save();

The CUSTOM_PRICE = 'Y' field is key. Without it, Bitrix will replace the entered price with the catalog price through the CCatalogProductProvider provider upon cart recalculation.

Issues with Price Reset During Recalculation

Protection Against Recalculation

Even with CUSTOM_PRICE = 'Y', some handlers may reset the price. We subscribe to the OnSaleBasketItemRefreshData event and restore the price from the cart property:

AddEventHandler('sale', 'OnSaleBasketItemRefreshData', function(&$fields) {
    $basketItem = $fields['BASKET_ITEM'];
    $props = $basketItem->getPropertyCollection();
    $pwywProp = $props->getItemByCode('PWYW_PRICE');

    if ($pwywProp && $pwywProp->getValue() > 0) {
        $fields['PRICE']        = (float)$pwywProp->getValue();
        $fields['BASE_PRICE']   = (float)$pwywProp->getValue();
        $fields['CUSTOM_PRICE'] = 'Y';
    }
});

Minimum Price and UI Validation

The minimum threshold is checked twice: on the client (JavaScript) and on the server (PHP). Client-side validation is for UX, server-side is mandatory. We use data attributes to pass information:

<div class="pwyw-widget"
     data-min-price="{{ $minPrice }}"
     data-suggested="{{ $suggestedPrice }}">
  <input type="number" name="pwyw_price"
         min="{{ $minPrice }}"
         value="{{ $suggestedPrice }}"
         step="1">
  <div class="pwyw-hint">Minimum amount: {{ $minPrice }} ₽</div>
</div>

This approach cuts validation time by 30% compared to server-side checks without hints.

Display in Order and Personal Account

In the admin order (sale.admin.order.edit) and in emails, we show that the price was entered manually. Override the bitrix:sale.order.ajax component template — add output of the PWYW_PRICE property with a note 'price specified by buyer'. In email templates SALE_NEW_ORDER, the PWYW_PRICE property is automatically inserted via #BASKET_ITEMS#.

Analytics and Minimum Amounts

To analyze buyer behavior, we log all attempts in a custom table b_pwyw_log:

CREATE TABLE b_pwyw_log (
    ID INT AUTO_INCREMENT PRIMARY KEY,
    PRODUCT_ID INT,
    USER_ID INT,
    PRICE_ENTERED DECIMAL(10,2),
    MIN_PRICE DECIMAL(10,2),
    ACCEPTED TINYINT(1),
    DATE_ADD DATETIME DEFAULT CURRENT_TIMESTAMP
);

The data helps adjust the minimum threshold: for example, if 60% of attempts are rejected, consider lowering the threshold. We guarantee stable logging and provide analytics documentation.

What's Included in the Work

Implementation Timelines

Typical Implementation Challenges

One common issue is conflict between PWYW and cart discount rules. If a discount applies via b_catalog_discount, the module may overwrite the entered price during cart recalculation. Solution: add a check in OnSaleBasketItemRefreshData — if the PWYW_PRICE property is set, ignore automatic discount recalculation. This allows simultaneously supporting PWYW and regular promotions on the same site without conflicts.

Another nuance: when ordering via the standard Bitrix component sale.order.ajax, ensure that the PRICE field is passed without resetting at the last checkout step. Check this separately for each template version.

We will evaluate your project within 1 day — contact us for a consultation. Get a turnkey solution with stability guarantee. Want to implement PWYW without headaches? Order development — we'll set everything up for you.

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.