Setting Up Order Discounts in 1C-Bitrix: Marketing Rules and Promo Codes

Why distinguishing catalog and cart discounts matters

When multiple promotions run simultaneously in your online store, a cart discount can stack with a catalog discount—giving the customer a much larger discount than intended. Over 10 years, we've fine-tuned more than 200 such configurations and know all the typical mistakes. For example, in one store with monthly turnover over 1 million rubles, incorrect priority settings led to regular revenue losses.

Order discounts in Bitrix work through the sale module, in the marketing rules section. Unlike catalog discounts (price reduction at the product level), marketing rules apply to the final cart total considering the order composition, user group, and promo codes. They are three times more flexible in the number of available conditions—this provides more opportunities for complex promotions but also increases the risk of conflicts.

Two levels of discounts

Catalog discounts are managed via Shop → Catalog → Discounts. They apply to product prices before entering the cart. Marketing rules for orders are stored separately and work in the cart context: they see order composition, user group, and promo code.

How to create an order discount with priorities

Go to Shop → Marketing → Discounts and promotions → Add.

Conditions — set of checks:

• Order total greater/less than X
• Cart contains product from category N
• User belongs to group G
• Promo code applied

Actions — what to do when conditions are met:

• Discount on the entire order (percentage or fixed amount)
• Discount on specific products in the cart
• Discount on delivery
• Add a gift product

Application parameters:

• Priority — order of application when multiple rules are active
• "Stop processing" — flag LAST_DISCOUNT = Y, prevents subsequent rules from applying

Example: 10% discount on orders over 5000 rubles

1. Create a rule, condition: Order total >= 5000
2. Action: Order discount 10%
3. Discount type: percentage of order total
4. Priority: set relative to other promotions
5. Validity period: specify dates or leave permanent

Typical mistakes when setting up discounts

The most common is not setting a priority, causing rules to stack unexpectedly. For example, a 20% catalog discount and a 10% cart discount could result in 30% instead of the planned 20%. The second mistake is not using the "Stop processing" flag for main promotions. The third is forgetting about compatibility with promo codes: if the rule doesn't specify the coupon type, any promo code can trigger jointly. We recommend always explicitly setting priorities and testing all combinations.

How to avoid discount conflicts

Use the "Stop processing subsequent rules" field on the priority discount. For mutually exclusive promotions, add the condition "Coupon X not applied". You can also explicitly set priorities so only one discount applies at a time. For complex cases, a compatibility table helps:

We have set up discounts for stores with catalogs up to 50,000 products and 20+ rules. Our experience shows that correct promotion functioning directly impacts customer trust and financial stability. We guarantee that all discounts will apply strictly according to the specified logic.

What's included in the work?

• Audit of current marketing rules and conflict detection
• Development of a technical specification with conditions and actions
• Setup of discounts, promo codes, priorities
• Testing all scenarios: manual and automated
• Training managers to work with the rules
• Transfer of documentation and access

More than 10 years of experience and 50+ successful discount setup projects confirm our expertise.

Timeframes

Basic setup of 3–5 standard order discount rules takes 3 to 5 hours. Complex projects with audit and integrations take up to 3 days. We give an accurate estimate after analyzing your store.

Learn more about marketing rules in the official 1C-Bitrix documentation and Wikipedia on discounts.

Contact us for a consultation on discount setup — get an audit of your current rules and a selection of the optimal solution for your business. Order a primary analysis of your loyalty system.

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.