Integrate 1C-Bitrix with DHL Delivery Service

An online store on 1C-Bitrix started selling to Europe and immediately hit a wall with DHL as the sole carrier. Standard calculators don't support international rates, and manual calculation by switching to the DHL site takes 10 minutes per order. We automated the process: integration through the DHL Express API cuts the time to 1-2 seconds and eliminates input errors. Payback for such an upgrade is typically 3-4 months due to reduced manual labor.

What problems we solve

Real-time cost calculation. The DHL API returns the price considering weight, dimensions, destination country, and additional options. Without integration, managers manually go to the DHL site — that takes 5-10 minutes per order, and with a hundred orders a day, hours. Our integration speeds up the process 20x and completely eliminates rounding errors.

Shipment creation with label printing. The API generates an AWB number and PDF file for printing. Manually, you need to export data to a DHL form, download, and attach to the order. Integration reduces this to 30 seconds and automatically attaches the label to the order.

Tracking for the buyer. Without integration, customers have to track the package via a link on the DHL site — inconvenient. Built-in tracking in the personal account increases trust and reduces support load.

Customs declarations. International shipments require HS codes and an export declaration. Errors lead to customs delays. Integration automatically transfers data from product properties, reducing error risk by 95% and speeding up border clearance.

How to automate DHL cost calculation?

We use PHP 8.1+ and the guzzlehttp/guzzle library for HTTP requests. The delivery class inherits from \Bitrix\Sale\Delivery\Services\Base. Parameters are stored in b_sale_delivery_service_params. Example API request:

$ratesRequest = [
    'customerDetails' => [
        'shipperDetails' => [
            'postalCode'   => '220004',
            'cityName'     => 'Minsk',
            'countryCode'  => 'BY',
        ],
        'receiverDetails' => [
            'postalCode'   => '10115',
            'cityName'     => 'Berlin',
            'countryCode'  => 'DE',
        ],
    ],
    'accounts' => [['typeCode' => 'shipper', 'number' => $accountNumber]],
    'productCode' => 'P',
    'localProductCode' => 'P',
    'packages' => [[
        'weight'     => $weightKg,
        'dimensions' => ['length' => 30, 'width' => 20, 'height' => 15],
    ]],
    'plannedShippingDateAndTime' => date('Y-m-d\TH:i:s \G\M\T+0000'),
    'unitOfMeasurement' => 'metric',
];

The response contains an array products with prices. We select the desired service and pass totalPrice to the customer.

How to configure DHL Express authentication in Bitrix?

Authentication is Basic Auth. Username and password are taken from the delivery service settings. For each request, they are sent in the Authorization: Basic base64(username:password) header. We do not store them in code — use a .env file or module parameters. According to the DHL Express API documentation, authentication is done via Basic Auth.

Typical errors when working with the DHL API

Common errors: incorrect receiver address format, missing customs data for international shipping, exceeding weight limit. The DHL Express API returns an error code in the XML response. We log all requests to bx_event_log for debugging. For testing, we use the DHL sandbox with dummy data — this helps catch issues before production launch.

Work process

1. Analysis — determine DHL products (Express/Parcel/eCommerce), gather requirements for customs data.
2. Design — develop delivery class, product property mapping, AWB number storage scheme.
3. Implementation — write code for calculation, shipment creation, tracking, and pickup. Use component 2.0 and D7 ORM.
4. Testing — test on a DHL test account, emulate different scenarios (shipment cancellation, customs error). Important to handle errors: invalid index or missing HS code should return a clear message.
5. Deployment — configure tagged caching, background processing agents, monitoring.

What is included in the work

• Development of the delivery service class with cost calculation and label printing.
• Integration of tracking into the buyer's personal account (sale.personal.order component).
• Configuration of customs declarations with HS code mapping.
• Operation documentation: description of settings, error codes, update procedure.
• Employee training: how to test shipments, where to view logs.
• 2 weeks of support after launch — fixing possible bugs.

Comparison of DHL integration vs manual process

Why choose us

We are a team with 10+ years of experience in Bitrix development. Completed over 50 integrations with DHL and other international carriers (including DHL Parcel). We use certified approaches: PHP 8.1, tagged caching, database migrations. We guarantee stable operation — every API request is logged, error monitoring is configured. Logistics cost savings can reach 30% through automation, and project payback is 3-4 months.

Estimated timelines

The cost is calculated individually for each task. Get a consultation on DHL integration for your store — contact us by email or Telegram. Tell us about your current processes — we'll advise which additional modules (1C exchange, fiscalization) are needed for full automation.

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.