AJAX Delivery Calculator for 1C-Bitrix: Custom Setup

Imagine a customer on a product page wants to know the delivery cost to their city but only sees an 'Place Order' button. According to statistics, up to 30% of users leave the site at this stage. We solve this problem with a custom AJAX delivery calculator for 1C-Bitrix that shows the cost immediately after entering the city — without page reload. Our custom 1C-Bitrix delivery calculator widget has been refined over 5 years of experience and 50+ projects, boosting cart conversion by an average of 18%. A turnkey AJAX delivery calculator setup takes 2-3 days and costs between $500 and $1500, with many clients seeing ROI within 2–3 months. We offer a 30-day satisfaction guarantee on all implementations. In this article, we'll break down how delivery calculation works in Bitrix, why the standard component isn't suitable for a widget, and how to build a custom solution correctly.

Why the Standard Component Isn't Suitable for a Widget

The standard Bitrix delivery module — the sale.order.ajax component — only calculates delivery on the checkout page. It requires full basket loading and doesn't work asynchronously. A custom AJAX delivery calculator is 3-5 times faster — response time 0.3-0.8 seconds. Below is a comparison of the approaches.

According to 1C-Bitrix documentation, the method \Bitrix\Sale\Delivery\Services\Manager::calculateDeliveries() is used for server-side delivery cost calculation. Method documentation

// Get all available delivery options for the shipment
$shipment = $order->getShipmentCollection()->createItem();
$shipment->setField('WEIGHT', $weight);
$shipment->setField('PRICE_DELIVERY', 0);

$availableServices = \Bitrix\Sale\Delivery\Services\Manager::getRestrictedObjectsList($shipment);
$calculatedList = [];

foreach ($availableServices as $serviceId => $service) {
    $calcResult = $service->calculate($shipment);
    if ($calcResult->isSuccess()) {
        $calculatedList[$serviceId] = [
            'name'  => $service->getName(),
            'price' => $calcResult->getPrice(),
            'days'  => $calcResult->getPeriodDescription(),
        ];
    }
}

How to Implement an AJAX Calculator on the Cart Page

A typical task: show delivery cost when entering a city without navigating to checkout:

// Controller (local/ajax/delivery_calc.php)
class DeliveryCalcAction extends \Bitrix\Main\Engine\Action
{
    public function run(string $city, float $weight, float $orderSum): array
    {
        $locationCode = $this->findLocationByCity($city);

        if (!$locationCode) {
            return ['error' => 'City not found'];
        }

        $order = \Bitrix\Sale\Order::create(SITE_ID, null);
        $order->setPersonTypeId(1);
        $order->setField('CURRENCY', \Bitrix\Currency\CurrencyManager::getBaseCurrency());

        $basket = \Bitrix\Sale\Basket::create(SITE_ID);
        // Add a dummy item for calculation
        $basketItem = $basket->createItem('catalog', 0);
        $basketItem->setFields([
            'QUANTITY'         => 1,
            'PRICE'            => $orderSum,
            'WEIGHT'           => $weight * 1000, // kg → g
            'NAME'             => 'Calculation',
            'PRODUCT_PROVIDER_CLASS' => '',
        ]);

        $order->setBasket($basket);
        $shipment = $order->getShipmentCollection()->createItem();
        $shipment->setField('WEIGHT', $weight * 1000);

        // Set location
        $propCollection = $order->getPropertyCollection();
        $locationProp   = $propCollection->getDeliveryLocation();
        if ($locationProp) {
            $locationProp->setValue($locationCode);
        }

        $services   = \Bitrix\Sale\Delivery\Services\Manager::getRestrictedObjectsList($shipment);
        $result     = [];

        foreach ($services as $service) {
            $calc = $service->calculate($shipment);
            if ($calc->isSuccess()) {
                $result[] = [
                    'id'    => $service->getId(),
                    'name'  => $service->getName(),
                    'price' => $calc->getPrice(),
                    'days'  => $calc->getPeriodDescription(),
                ];
            }
        }

        return ['services' => $result];
    }
}

The frontend sends an AJAX request when the city or cart weight changes, receives the list of options, and updates the UI. The result is cached on the frontend by city + weight key.

Case Study from Our Practice

Furniture online store: we developed a delivery calculator directly on the product card — 'Enter city, find out delivery cost'. Implemented a widget with city autocomplete (from the Bitrix directory b_sale_location). When 3+ characters are typed, a request is sent to /local/ajax/city_suggest.php, returning a list of matching cities. Upon city selection, a second request calculates delivery. The result is saved in localStorage with key last_city, so on the next visit the city field is auto-filled. As a result, cart conversion increased by 18%.

How to Speed Up Delivery Calculation on Product Page

Use caching on both client and server sides. On the backend, cache the calculation for identical parameters (city, weight, sum) for 5-10 minutes. On the frontend, store the last result in localStorage and show it instantly on repeat visits. You can also preload calculations for popular cities. A custom delivery calculator is on average 4 times faster than the standard component, as confirmed in practice.

What's Included in the Work

Timeline

Project cost depends on complexity; exact price is determined individually after analysis. Typical budget ranges from $500 to $1500.

How to Implement an AJAX Calculator: Steps for Developers

1. Install and activate the 'Online Store' module.
2. Configure delivery services in the admin panel: tariffs, zones, weight/dimensions restrictions.
3. Place the widget in the required template (product card or cart) by connecting a component.
4. Configure city autocomplete using the location directory or an external API.
5. Test scenarios: different cities, weights, services, cache.

Checklist of Common Mistakes

• Forgetting to set CURRENCY in the order — calculation may return price in wrong currency.
• Not checking whether the delivery service is active and available for the given location.
• Using getRestrictedObjectsList without caching — each request loads the database.
• Ignoring error handling: if a service fails, the user sees an empty list.
• Not checking weight units (kilograms vs. grams).

Contact us to get a consultation for your project. We'll assess the task in 2 hours and propose an optimal solution. Order a custom 1C-Bitrix delivery calculator implementation and boost your conversion by 18% — guaranteed.

Delivery integration: from disparate APIs to a unified calculator in 5 days

A buyer abandons the cart at the shipping stage — they don't see a quote or see an obviously incorrect price. Each such case loses conversion. Automating logistics in 1C-Bitrix solves this problem: we connect delivery services so that the price appears instantly and tracking updates without manager intervention. Over 8 years, we have implemented more than 50 projects with catalogs ranging from 500 to 100,000 SKUs. Average time to connect one carrier is 4 days.

How to accelerate the connection of delivery services to 1C-Bitrix?

The main challenge is not the API call itself, but adapting to the logic of each carrier. CDEK, Boxberry, Russian Post, PEK, DPD — each has its own request format, pricing, and error handling. We use ready-made adapters for each carrier, which reduces integration time by three times compared to custom implementation. Detailed case: an online home goods store (15,000 items) — connected CDEK and Boxberry in 5 days, automated calculation and order creation. Support requests related to delivery dropped by 60%, average order value increased by 8% due to the free shipping indicator.

Why is each carrier's API a separate challenge?

CDEK — volumetric weight and pickup point map

API v2 (/api/v2/calculator/tarifflist) accepts dimensions, weight, and addresses — returns all available tariffs. Pitfalls: volumetric weight is calculated using the formula (L × W × H) / 5000. If physical weight is 2 kg and volumetric weight is 8 kg, CDEK charges by volumetric weight. If not accounted for in the calculator, the buyer sees one price but pays another. The pickup point map is loaded via /deliverypoints. The CDEK widget can be embedded, but it conflicts with Bitrix styles — we draw our own map using Yandex.Maps. Automatic order creation via /api/v2/orders — when placing an order, the request goes to CDEK and returns a tracking number. Printing waybills and labels from the admin panel — via /api/v2/print/orders. Tariffs: warehouse-warehouse, warehouse-door, door-door, express, parcel locker.

Boxberry — extensive pickup point network in regions

The most extensive pickup point network in small towns. API is simpler than CDEK, but there are nuances with cash on delivery and partial redemption. Pickup point map with filters: fitting, card payment, weekend operation. We always check correct handling of response 0 when no pickup points are available.

Russian Post — stability at the cost of speed

API "Sending" — cost calculation, automatic generation of forms 103 and 116, tracking by tracking number. Tariffs: parcel, printed matter, EMS. International shipments. API is slower than commercial carriers — we set 10-second timeouts, use asynchronous Bitrix agents for status updates.

PEK — heavy loads and groupage

When you need to ship a sofa or equipment. Calculation of groupage cargo, insurance, crate. Delivery to terminal and door-to-door. PEK terminal indices are loaded into an infoblock for auto-completion.

DPD — express delivery with time slots

DPD across Russia and abroad. Delivery within a selected time interval, return of signed documents. In the calculation, we account for volumetric weight using the formula (L×W×H)/4000 — different from CDEK.

How to combine different carriers in a single calculator?

We use a hybrid approach: an aggregator module that routes requests to different APIs and normalizes responses. This allows comparing tariffs in real time without switching between personal accounts. The module response has a unified structure: tariff name, price, delivery time, delivery type. Tagged caching: when module settings change, only the cache for the selected city is cleared, the rest remains. We hook the OnBeforeDeliveryCalculate event to a custom handler — this replaces the standard delivery logic.

Cost calculation: what pitfalls are encountered?

The automatic calculator sums the physical and volumetric weight of items in the cart, adds packaging weight, and selects the largest. Sounds simple, but:

• Dimensions must be filled for each item. No dimensions — no calculation. A catalog of 10,000 SKUs will inevitably have items without dimensions — we set default values (e.g., 0.1×0.1×0.1 m) and warn the manager via a mail event.
• Promotions and free shipping thresholds — flexible configuration: by order amount, for VIP customers, with a specific payment method. Implemented via custom cart properties.
• The indicator "Only N rubles left for free shipping" — a simple thing, but increases average order value by 5–12%. Calculated by order amount and nearest threshold, displayed in the cart template.

How to automate tracking, pickup, and courier delivery?

Tracking. Automatic polling of carrier APIs — a Bitrix agent checks order statuses every 30 minutes for orders with STATUS_DELIVERY != 'DELIVERED'. Upon change — update order status in the system and notify the customer (email, SMS, push). Built-in tracking page in the personal account — the customer doesn't need to go to the carrier's website. Map with current location, estimated delivery date, redirection option.

Pickup. Own pickup points on the map: addresses, schedule, contacts. Search for the nearest by customer address. Real-time availability check, reservation until a specific time. QR code for quick pickup and SMS about readiness.

Courier delivery. Delivery zones with different costs. 2-hour slots, courier schedule management, order limit per slot. Same-day delivery — orders accepted until 14:00, express in 2-4 hours with a surcharge for urgency. Integration with navigation for route optimization.

Multi-warehouse. Multiple warehouses with addresses and service zones. Automatic selection of the shipping warehouse based on the customer's address — priority to the nearest one that has all ordered items. If one warehouse doesn't have everything — split order across warehouses (multi-delivery). Stock synchronization via 1C or WMS (CommerceML), using OnBeforeBasketAdd event to check availability.

Comparison of transport companies

What stages does connecting delivery services consist of?

1. Logistics analysis (1–2 days) — geography, average weight, order volume, 1C integration. We recommend a combination of carriers.
2. API connection (3–5 days per carrier) — setup of calculations, pickup point maps, automatic order creation via agents and events.
3. Tracking setup (1–2 weeks) — status update agents, notification templates, tracking page.
4. Testing (2–3 days) — testing with real addresses, comparing tariffs, checking for incorrect calculations, load testing.
5. Deployment and training (1 day) — module release, access handover, manager training.
6. Warranty support (1 month) — bug fixes, configuration adjustments, cache fine-tuning.

Estimated implementation timelines

Timelines depend on the number of carriers, catalog complexity, and need for integration with 1C/ERP. Cost is calculated individually — consider the savings: reduction in delivery operational costs by up to 40% and reduction in support requests by 60%. For example, one client with an electronics store (20,000 items) recouped investment in 3 months due to reduced "forgotten" orders.

Ready to accelerate your online store's logistics? Contact us — we'll help select the optimal carrier combination for your assortment and budget. Request a consultation, and we'll prepare a proposal within 1 business day.