Setting Up Gift Promotions in 1C-Bitrix: From Simple to Custom

Automating Gift Promotions in the Bitrix Cart

Typical situation: a customer adds a product, but the gift does not appear. Or it appears with a non-zero price. Or it is only visible after recalculating the cart. All of this results from incorrect marketing rule configuration. The gift mechanism in Bitrix is based on the AddGift action, but the nuances are hidden. Our engineers have over 5 years of experience, 1C-Bitrix certification, and more than 50 implementations for online stores of varying complexity. In 80% of cases, problems are solved by adjusting conditions and stock.

How Does a Gift Work Technically in Bitrix?

A gift is a marketing rule action with type AddGift. When the conditions are met, the system adds the specified product to the cart with a price of 0. The product physically exists in the catalog — it is a regular information block element with regular stock. Data is stored in b_sale_discount (the rule itself), b_sale_discount_action (action type = gift, gift product ID). In the cart, the gift goes into b_sale_basket with PRODUCT_PRICE_ID = 0 and a gift marker. More details on the rule type are in the official 1C-Bitrix documentation.

Setting Up a Marketing Rule with a Gift

The sequence of actions in the admin panel: Store → Marketing → Discounts and promotions → Add.

1. Condition: e.g., above a certain order sum
2. Action: select Add gift type
3. Gift product selection: specify a specific catalog item
4. Quantity: how many units of the gift to add
5. Settings: priority, promotion period, user group restrictions

Why Is It Important to Properly Configure Gift Stock?

The gift product must have stock. If stock is zero, the gift will not be added to the cart. For promotions with a limited number of gifts, create a separate product with limited stock and set up a notification for the manager when stock reaches a minimum. Alternatively, use the OnSaleBasketItemAdd event handler to control the issue limit — this allows flexible management of the number of gifts without creating many products.

Customer Selection of a Gift

The standard mechanism adds a specific product automatically. If the customer needs to choose from several gifts, that is custom development: a gift selection component in the cart, a handler that adds the chosen product and marks it as a gift via b_sale_basket.CUSTOM_PRICE = Y and zero price. In our projects, such functionality increased conversion by 15–20% and average order value by 12%.

Successful case example. A cosmetics store wanted to give a gift for orders above a certain amount, but the customer could choose one of three mini-products. We implemented a custom selection component in the cart, configured stock, and integration with 1C. As a result, the promotion attracted 30% new customers and increased repeat orders by 25% over the quarter.

Display in Cart and Order

In standard cart templates, the gift is displayed with price 0 and a "Gift" label. In custom components, you need to check the gift flag and format the markup accordingly so the customer understands it is a bonus product, not a system error.

Typical Problems and Their Solutions

Comparison of Standard and Custom Approaches

The standard approach is 10 times faster, but the custom one gives 5 times more flexibility. Choose based on your needs.

What Is Included in Our Work

• Audit of the current configuration and identification of bottlenecks
• Designing the promotion logic (conditions, quantity, period)
• Creating a gift product and configuring stock
• Implementing the marketing rule in the admin panel
• Custom development (if gift selection, cart integration is needed)
• Testing all scenarios (adding, removing, recalculating the cart)
• Integration with 1C (excluding gifts from export)
• Documentation and training for your managers

Timelines and Guarantees

Standard setup of a single gift promotion takes from 3 to 5 hours, including product creation and verification of display in the cart. Complex scenarios (choice from multiple gifts, 1C integration) take from 2 days. We guarantee correct operation of the mechanism and provide support for one month after implementation. Contact us — we will evaluate your scenario free of charge. Order a turnkey gift setup and get a ready-made solution without hidden costs. Our certified specialists with over 5 years of experience and 100+ Bitrix projects will help you quickly launch a promotion.

Additional resources: official 1C-Bitrix documentation on marketing rules. We also recommend reading the Wikipedia article on sales promotion.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.