Integration of 1C-Bitrix with Dostavista Delivery Service

A customer places an order at 18:30, and the courier arrives only the next day by noon? The reason is manual order creation in the delivery service. The manager spends 15 minutes filling in data: address, weight, contacts. An error in the phone number—and the courier can't call. Integration of 1C-Bitrix with Dostavista via REST API eliminates the human factor and speeds up delivery to 1–2 hours. We, a team of certified Bitrix developers with 10+ years of experience and over 50 successful projects, offer turnkey implementation. On average, the project takes 3–6 days depending on complexity.

Why Integrate with Dostavista?

Manual creation of delivery requests leads to delays, errors, and lost customers. Automation via REST API of Dostavista allows you to reduce delivery time—the request goes to the courier within seconds after order confirmation. Eliminate errors—addresses and contacts are transferred automatically. Increase loyalty—the customer sees the status and location of the courier in real time. The Dostavista API is better than SOAP integrations with bulky XML schemas: REST requests are lighter, documentation is transparent, and response time is 2–3 times lower.

How Dostavista API Works

Dostavista provides a REST API. Authorization is done via a token in the X-Authorizationtoken header. Main methods:

• POST /api/business/v1/orders — create a delivery request
• GET /api/business/v1/orders/{id} — get request status
• DELETE /api/business/v1/orders/{id} — cancel request
• GET /api/business/v1/couriers/{id}/location — courier coordinates

The request contains route points (points array): point 0 is the pickup location (warehouse/store), points 1..N are the delivery addresses of customers. One Dostavista order can contain multiple delivery points—this is convenient for batch shipments.

Delivery Module in Bitrix

The delivery service is connected via a class inheriting \Bitrix\Sale\Delivery\Services\Base. Key methods:

• calculateConcrete() — calculates shipping cost. Calls POST /api/business/v1/orders/calculate-price with pickup/delivery address and weight.
• createDelivery() — creates the actual request when the order is confirmed by the manager or automatically on status change.
• Handler OnSaleStatusOrder — hook on order status change in b_sale_order.

Module parameters are stored in b_sale_delivery_service_params: API_TOKEN, SHOP_POINT_ADDRESS (warehouse address), AUTO_CREATE (create request automatically).

Shipping Cost Calculation

$response = $httpClient->post(
    'https://robot.dostavista.ru/api/business/v1/orders/calculate-price',
    [
        'matter'    => 'Товар из магазина',
        'weight_kg' => $weightKg,
        'points'    => [
            ['address' => $shopAddress],
            [
                'address'  => $deliveryAddress,
                'contact_person' => ['phone' => $phone],
            ],
        ],
    ],
    ['X-Authorizationtoken' => $apiToken]
);
$price = $response['order']['payment_amount'];

The response contains payment_amount—the amount to pay (in local currency). If the address is not recognized or falls outside the coverage area, the API returns an error—we handle that as "delivery unavailable".

How to Automate Order Creation in Bitrix

The request is created either automatically when the customer selects the delivery method and order is confirmed, or manually by the manager from the admin panel. The second option is preferable for stores that need to check stock before dispatch.

In b_sale_order_props, we save DOSTAVISTA_ORDER_ID—the request ID in the Dostavista system. It is needed for:

• tracking request status (polling or webhook)
• canceling the request when the order is canceled in Bitrix
• providing the customer with a tracking link for the courier

Statuses and Synchronization

Dostavista supports webhooks: when the status of a request changes, the system sends a POST request to the specified URL. Configure it in your personal account. On the Bitrix side, we create a handler that maps Dostavista statuses to order statuses:

If webhooks are not available (no public IP), we implement polling: a Bitrix agent polls the status of active requests every 5–10 minutes via GET /api/business/v1/orders/{id}.

Courier Tracking

Dostavista returns courier.latitude/courier.longitude in the request when delivery is active. For stores that want to show the courier's position on a map, we implement an AJAX endpoint on the Bitrix side—it forwards the request to the Dostavista API and returns coordinates.

Timelines

What's Included

We provide a full cycle of services: analysis of logistics processes, configuration of API tokens and access rights, development of a custom delivery module tailored to the store's specifics, implementation of status handlers (webhooks or polling), creation of an AJAX tracking widget on a map, production testing, documentation, and manager training. We guarantee stable operation of the integration and prompt support after launch. If you want to automate delivery in your store, contact us. Get a free consultation on your project.

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.