Setting Up Click & Collect in 1C-Bitrix: Reservation and Pickup

A typical problem: a buyer chooses in-store pickup, arrives at the store, but the item is not on the shelf. The reason — no strict warehouse binding and no real stock check before reservation. We eliminate such situations through proper Click & Collect configuration. Our expertise: over 50 Bitrix projects, certified engineers with guaranteed results.

Click & Collect (online order with in-store pickup) is one of the most popular retail scenarios, especially after the pandemic. But without correct stock and reservation handling, it brings more trouble than benefits. The buyer selects a point where the item is not available, or two people order the last unit simultaneously — and someone leaves disappointed. A proper implementation on 1C-Bitrix solves these problems at the architectural level: strict binding of points to warehouses, stock check in the cart before reservation, and reservation at order placement. Below is how this works in practice with code examples.

Why is it important to bind pickup points to warehouses?

Each pickup point must be strictly bound to a specific warehouse via XML_ID. Only then the system knows which stock to show. Without this binding, pickup becomes a lottery. We use standard Bitrix tables: b_catalog_store and b_catalog_store_product. Example query to check stock:

SELECT s.ID, s.TITLE, s.ADDRESS, sp.AMOUNT
FROM b_catalog_store s
JOIN b_catalog_store_product sp ON sp.STORE_ID = s.ID
WHERE sp.PRODUCT_ID = ? AND s.ACTIVE = 'Y' AND sp.AMOUNT > 0
ORDER BY s.SORT ASC;

1C-Bitrix documentation: warehouse management

How to add the delivery service "Pickup"

In the admin panel: Store → Delivery → Add delivery service → Type: Pickup. Specify the name, activate it, configure the cost (usually zero). Programmatic creation via API gives more flexibility — you can add conditional rules and 1C integration:

\Bitrix\Main\Loader::includeModule('sale');

$deliveryService = \Bitrix\Sale\Delivery\Services\Manager::getList([
    'filter' => ['CODE' => 'self_pickup'],
])->fetch();

if (!$deliveryService) {
    \Bitrix\Sale\Delivery\Services\Manager::add([
        'NAME'       => 'Pickup from store',
        'CODE'       => 'self_pickup',
        'ACTIVE'     => 'Y',
        'CLASS_NAME' => '\Bitrix\Sale\Delivery\Services\Base',
        'CURRENCY'   => 'RUB',
        'PRICE'      => 0,
    ]);
}

How to select a pickup point in the cart?

In the sale.order.ajax component template, we display a list of points with stock check. Example:

// Get active warehouses with availability for all cart items
$basketItems = $order->getBasket();
$productIds = [];
foreach ($basketItems as $item) {
    $productIds[] = $item->getProductId();
}

$storesResult = \Bitrix\Catalog\StoreTable::getList([
    'filter' => ['ACTIVE' => 'Y'],
    'select' => ['ID', 'TITLE', 'ADDRESS', 'GPS_N', 'GPS_S'],
    'order'  => ['SORT' => 'ASC'],
]);

$availableStores = [];
while ($store = $storesResult->fetch()) {
    $allAvailable = true;
    foreach ($productIds as $productId) {
        $stockResult = \Bitrix\Catalog\StoreProductTable::getList([
            'filter' => ['PRODUCT_ID' => $productId, 'STORE_ID' => $store['ID']],
            'select' => ['AMOUNT'],
        ])->fetch();

        if (!$stockResult || $stockResult['AMOUNT'] < $basketItems->getQuantityByProductId($productId)) {
            $allAvailable = false;
            break;
        }
    }

    if ($allAvailable) {
        $availableStores[] = $store;
    }
}

How to set up reservation: step-by-step instructions

Reservation is a critical step that determines the reliability of Click & Collect. Incorrect implementation leads to lost items and conflicts with buyers.

1. Create a custom order property PICKUP_STORE_ID via Store → Settings → Order properties. Type — list or string with a link to the warehouse table.
2. Add an event handler for OnSaleOrderBeforeSaved. In it, get the selected warehouse ID from the order property and check stock again before reservation.
3. Call reservation for each cart item via \Bitrix\Catalog\StoreProductTable::reserveProduct. Ensure the function returns success before saving the order.

Example handler:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale', 'OnSaleOrderBeforeSaved',
    function (\Bitrix\Main\Event $event) {
        $order = $event->getParameter('ENTITY');
        $pickupStoreId = $order->getPropertyCollection()
            ->getItemByOrderPropertyCode('PICKUP_STORE_ID')
            ?->getValue();

        if (!$pickupStoreId) return;

        foreach ($order->getBasket() as $basketItem) {
            \Bitrix\Catalog\StoreProductTable::reserveProduct(
                $basketItem->getProductId(),
                (int)$pickupStoreId,
                $basketItem->getQuantity(),
                $order->getId()
            );
        }
    }
);

Notifications and order statuses for pickup

After the point is selected and the item is reserved, we need to set up notifications for the buyer. When the order moves to the "Ready for pickup" status (usually after processing in 1C), the system sends an email and SMS to the number from the profile: store address, working hours, what to bring. For regular customers, we recommend a personal account with real-time status tracking. Implementation via the OnSaleOrderStatusChange event and email templates. Our experience shows that proper notifications reduce no-shows by 20–30%.

What is included in the work?

Turnkey: from 7 business days. 6-month guarantee on revisions. 1C-Bitrix certificate.

Comparison: built-in mechanism vs custom solution

A custom solution outperforms the built-in by 2–3 times in flexibility, but requires more time and resources.

To get a cost and timeline estimate for your project, contact us. Request a consultation on Click & Collect setup.

Additional information: delivery services documentation

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.