1C-Bitrix Integration with IML Delivery Service

We frequently handle the integration of the IML delivery service with 1C-Bitrix stores. IML is a Russian delivery service with its own network of pickup points and courier delivery. Coverage spans over 5,000 settlements, with a focus on e-commerce. For online stores, three scenarios are relevant: courier delivery to the door, delivery to a pickup point, and self-pickup from a pickup point with fitting. Each requires correct cost calculation, order placement, and status synchronization. This article covers the technical implementation—from the IML API to final deployment on a production server. Our company has specialized in Bitrix integrations for over 10 years, and IML is a frequent request. We guarantee transparent pricing and fixed timelines: a basic integration takes 4–5 days, an extended one up to 7 days. Contact us for a free project evaluation.

How the IML API Works

IML provides a REST API. Base URL: https://api.iml.ru. Authentication is Basic Auth (login and password from your IML account). All requests are POST with a JSON body, responses are also JSON.

Key endpoints:

• POST /api/v2/auto-zones — calculate delivery zone and cost by address/zip
• POST /api/v2/orders — create a delivery order
• GET /api/v2/orders/{orderNumber} — order status
• GET /api/v1/delivery-points — list of pickup points (can be large—cache it)
• GET /api/v2/tracking/{barcode} — detailed tracking

According to the IML API documentation, delivery zone calculation requires sender and recipient region codes.

Why IML Is Beneficial for E-commerce

Based on our data, IML is on average 15% cheaper than traditional courier services for distances up to 300 km, and pickup points save up to 40% on last-mile costs. Thanks to the extensive pickup point network (over 5,000 settlements), stores reduce delivery times and decrease rejection rates. Our experience: implementing IML increased checkout conversion by 12% for one client.

Delivery Module in Bitrix

The delivery class inherits \Bitrix\Sale\Delivery\Services\Base. To display pickup points on a map, we also implement a separate component or integrate with an existing pickup point selection widget, if one is already on the project.

Parameters in b_sale_delivery_service_params:

• IML_LOGIN, IML_PASSWORD
• SENDER_CODE — sender code (provided by IML when connecting)
• DELIVERY_TYPE — default delivery type (courier / pickup)

Cost and Zone Calculation

IML calculates cost by zone: first, the delivery zone is determined by locality, then the cost is calculated based on weight and dimensions using a tariff grid.

$response = $httpClient->post(
    'https://api.iml.ru/api/v2/auto-zones',
    [
        'RegionCodeFrom' => $senderRegionCode,
        'RegionCodeTo'   => $deliveryRegionCode,
        'Weight'         => $weightGram,
        'Volume'         => $volumeCm3,
        'AssessedValue'  => $assessedValue,
        'DeliveryType'   => 'CurierDelivery', // or 'PickupPoint'
    ]
);
$deliveryPrice = $response['Price'];
$deliveryDays  = $response['DeliveryTime'];

IML region codes are their own classification. On first run, we load the region reference GET /api/v2/regions and store it in b_option (or a separate table) for fast lookups.

How Orders Are Created

When an order is confirmed and the delivery method is selected, we create an order in IML:

$orderData = [
    'SenderCode'    => $senderCode,
    'OrderNumber'   => 'SHOP-' . $bitrixOrderId,
    'ReceiverName'  => $receiverName,
    'Phone'         => $phone,
    'RegionCode'    => $regionCode,
    'AddressString' => $address,
    'Weight'        => $weightGram,
    'GoodsDescription' => 'Online store goods',
    'AssessedValue' => $assessedValue,
    'CashOnDelivery'=> $codAmount, // cash on delivery, 0 if prepaid
    'DeliveryType'  => 'CurierDelivery',
];

The response contains BarCode—the IML shipment barcode. We save it in b_sale_order_props as IML_BARCODE.

Pickup Points and Map Selection

The list of pickup points is returned by GET /api/v1/delivery-points — a large array (thousands of objects). We load it once a day via a Bitrix agent and cache it in a highload block or b_iblock_element (infoblock "IML Pickup Points").

On the checkout page, we display a map with pickup points: Yandex.Maps or Google Maps with markers. When a pickup point is selected, we save its code in the order property IML_PICKUP_POINT. When creating an order, we pass PickupPointCode instead of an address.

Statuses and Tracking

Status synchronization via a Bitrix agent: every 30–60 minutes, we poll GET /api/v2/orders/{orderNumber} for active orders. IML also supports webhooks (sending notifications to the merchant's URL)—preferable for high order volumes.

Cash on Delivery

IML supports cash on delivery (COD). The CashOnDelivery amount equals the order total if the buyer pays upon receipt. When configuring two payment methods (prepaid / upon receipt) in Bitrix, the COD selection logic is implemented in calculateConcrete().

Timelines

What the Work Includes

• Documentation: integration description, data schemes, settings
• Access: to server, IML API, personal account
• Training: instructions for managers and operators
• Support: 2 weeks post-launch with 99.9% SLA guarantee

We are a certified Bitrix Partner with over 10 years of integration experience and have completed over 100 projects connecting delivery services to 1C-Bitrix. Reach out—we'll evaluate your project within one business day.

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.