Integrating Yandex Delivery with 1C-Bitrix: Automate Shipping

An online store on 1C-Bitrix loses orders due to non-automated delivery: managers spend up to 15 minutes manually calculating costs and tracking statuses. Input errors reach 5%, and customers complain about lack of information. Connecting Yandex Delivery via Delivery API v2 solves these problems, but implementation requires attention to details: two-step claim creation, discrepancy between preliminary and actual cost, correct webhook handling. We are a team with 10+ years of Bitrix experience and perform such turnkey integrations in 3-5 days. Contact us to assess your project. On average, the integration pays for itself in 2-3 months by reducing manual labor: with 100 orders per month, savings reach 7500 rubles on manager salary, as shown in typical project calculations.

How to Integrate Yandex Delivery with 1C-Bitrix?

Built-in delivery methods in Bitrix do not support dynamic cost calculation from Yandex Delivery, automatic claim creation, and real-time status tracking. You have to manually transfer orders to the Yandex personal account, which is fraught with typical errors: incorrect pickup point coordinates, skipping the confirmation step, or lack of webhook processing. Unlike manual exchange, API v2 speeds up order processing by 60 times and completely eliminates input errors. As stated in the official documentation: two-step claim creation is critical for courier assignment.

How Two-Step Claim Creation Works

Yandex Delivery requires explicit confirmation after creation. A single-step approach leaves the claim in new status, and the courier is not assigned. Two-step creation reduces the risk of unfulfilled orders by half compared to single-step. Let's look at an example:

public function createAndAcceptClaim(\Bitrix\Sale\Shipment $shipment): string
{
    $order = $shipment->getOrder();

    $claim = $this->apiPost('/claims?request_id=' . uniqid(), [
        'items'               => $this->buildItems($shipment),
        'route_points'        => $this->buildRoutePoints($shipment),
        'comment'             => 'Order #' . $order->getId(),
        'callback_properties' => ['callback_url' => $this->getOption('WEBHOOK_URL')],
    ]);
    $claimId = $claim['id'];

    // Without this call, the courier will not be assigned
    $this->apiPost('/claims/accept?claim_id=' . $claimId, [
        'version' => $claim['version'],
    ]);

    return $claimId;
}

request_id is an idempotent key: a repeat request with the same value returns the existing claim. This is critical for integration reliability.

Typical Errors When Integrating Yandex Delivery

• Skipping the accept step: the claim remains in new, courier not assigned.
• Incorrect pickup point coordinates: cost is calculated incorrectly.
• Missing webhook handling for cancellation: the order stays "in transit".
• Ignoring the version field on confirmation: API returns 409 error.

Step-by-Step Integration Guide

1. Obtain an OAuth token from Yandex Passport.
2. Create a delivery handler that extends \Bitrix\Sale\Delivery\Services\Base.
3. Implement the calculateConcrete method for cost calculation.
4. Implement methods for claim creation and confirmation.
5. Set up the callback_url for webhooks.
6. Test all scenarios in a test environment.

Configuring Status Webhooks

Yandex Delivery supports push notifications to the callback_url. Lifecycle statuses:

Webhooks arrive at the callback URL specified during claim creation. We recommend implementing an endpoint that accepts a POST request with a JSON body and updates the order status in Bitrix. This allows automatic customer notification.

Comparison of API v2 vs Manual Exchange

API v2 speeds up order processing by 60 times and completely eliminates input errors.

Case: Express Delivery in Moscow

Our client is a cosmetics store; the goal was to show "deliver within 2 hours" for orders before 15:00. We implemented two methods: standard (next day) and express (2-3 hours, with additional fee). Express is available when ordering before 15:00 MSK and order amount from 1500 rubles. Check implemented in the handler's isCompatible() method. On cancelled status webhook, we notify the manager and offer the nearest available slot. Result: conversion increased by 18% in a month.

What's Included

• Development of delivery handler with cost calculation and claim creation methods
• Webhook setup for automatic status updates
• Testing of all scenarios (success, error, cancellation)
• Integration documentation and manager instructions
• Employee training on delivery operations
• Post-release support for 30 days

Timeframes

Request a consultation on integration from our engineers. Get a proposal for your project. We guarantee quality and adherence to deadlines.

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.