Recover up to 15% of abandoned carts in Bitrix: a complete guide

Problem: Every third order is lost

The average shopping cart abandonment rate in e-commerce is 65–70%. Out of 1000 sessions with added items, 650–700 orders are not completed. With an average cart value of $40, that's up to $28,000 in lost revenue. The good news: up to 15% of these can be recovered with proper tracking and automated notifications. We set up the full cycle: from server-side detection to conversion reports. Based on our experience, the solution pays for itself within 2–3 months. We guarantee recovery of up to 15% of lost orders if our recommendations are followed.

Why customers abandon carts?

The main reasons are unexpected shipping costs, a complicated checkout form, or lack of a convenient payment method. Without data, you won't know the cause. Abandoned cart tracking gives you exact numbers: who, when, and with which product left. We use a combination of server-side methods and client-side events for complete data. Additionally, we analyze drop-off points through UX events.

How to set up server-side tracking in Bitrix?

Cart data resides in the b_sale_fuser (virtual user) and b_sale_basket (items) tables. To find abandoned carts, query \Bitrix\Sale\BasketTable. The code below checks carts not updated for more than an hour and, if an authorized user exists, pushes a task to the notification queue. According to the Sale module documentation, this approach is recommended for minimal load.

<?php
$cutoffTime = new \Bitrix\Main\Type\DateTime();
$cutoffTime->add('-1 hour');

$abandonedFusers = \Bitrix\Sale\BasketTable::getList([
    'filter' => [
        '<DATE_UPDATE' => $cutoffTime,
        '=ORDER_ID'    => false,
    ],
    'group'  => ['FUSER_ID'],
    'select' => ['FUSER_ID'],
])->fetchAll();

foreach ($abandonedFusers as $row) {
    $fuser = \Bitrix\Sale\FuserTable::getList([
        'filter' => ['=ID' => $row['FUSER_ID']],
        'select' => ['USER_ID', 'DATE_UPDATE'],
    ])->fetch();

    if (!$fuser || !$fuser['USER_ID']) continue;

    $user = \Bitrix\Main\UserTable::getById($fuser['USER_ID'])->fetch();
    $email = $user['EMAIL'] ?? '';
    if (!$email) continue;

    AbandonedCartQueue::push($fuser['USER_ID'], $row['FUSER_ID']);
}

After getting the FUSER_ID, we check if the user is authorized (USER_ID not null). If so, get the email and push the task to the queue.

// Agent (Settings -> Agents)
function checkAbandonedCarts(): string
{
    AbandonedCartService::processNew();
    return __FUNCTION__ . '();';
}

For performance optimization, use indexes on DATE_UPDATE and ORDER_ID in b_sale_basket, and on FUSER_ID in b_sale_basket. This reduces load when dealing with large catalogs.

What data to analyze in the report?

After a few weeks, you'll have data: number of detected carts, communications sent, and recovered orders. A simple SQL query shows the trend.

SELECT
    DATE(detected_at) AS date,
    COUNT(*) AS detected,
    SUM(CASE WHEN status = 'recovered' THEN 1 ELSE 0 END) AS recovered,
    ROUND(SUM(CASE WHEN status = 'recovered' THEN 1 ELSE 0 END) * 100.0 / COUNT(*), 1) AS recovery_rate
FROM local_abandoned_cart
GROUP BY DATE(detected_at)
ORDER BY date DESC;

For example, with 1000 detected carts and 150 recovered orders at an average order value of $40, additional revenue is $6,000.

Comparison of server-side and client-side tracking

Server-side detection finds 1.2–1.3 times more abandoned carts than client-side, as confirmed by our projects. But client-side events help analyze UX and drop-off points.

What's included

Implementation process: how we work

1. Audit current cart implementation and identify bottlenecks.
2. Set up server-side tracking: queries, agent, status table.
3. Integrate client-side events (GA4, Yandex Metrica).
4. Develop abandoned cart conversion report.
5. Hand over documentation and train your administrator.

Estimated timeline

Full implementation cycle takes up to 3 days. You'll receive the first report a week after start. Contact us for a preliminary assessment of your project. Order the implementation and see the system pay for itself by recovering up to 15% of lost orders.

Our approach

Each task requires individual analysis and careful planning. We don't use template solutions — every project is adapted to specific requirements and existing infrastructure. Our team has experience with projects of various scales: from small shops to high-load platforms with millions of operations per day.

Guarantees and support

We provide a 12-month warranty on completed work. During this period, we fix any issues free of charge. After project completion, we deliver full documentation and training for your team. Technical support is available for 30 days after launch — we'll help resolve any questions.

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.