Testing 1C-Bitrix Delivery Integrations: from Calculation to Tracking

We test delivery integrations in 1C-Bitrix not by checklist, but by diving into business logic. Over our work period, we have conducted more than 50 audits for online stores with revenue from 5 million RUB. Typical picture: cost calculation returns 0, pickup point does not load, tracking number does not arrive. And all this without on-screen errors. Our task is to find such scenarios before they hit customers. We perform load testing of delivery to evaluate API response time.

Integration with delivery services is a chain: cost calculation → order creation in the service account → label printing → tracking. Any link can break silently. We select test scenarios for your project and guarantee on identified errors.

Why does delivery calculation failure go unnoticed?

80% of problems in delivery calculation are related to missing product dimensions or incorrect city code. CDEK API v2 with empty weight returns 400, the Bitrix module silently returns 0. The buyer sees only "delivery not calculated" and leaves. We check raw requests to the API and find such discrepancies before deployment.

Architecture of delivery integration in Bitrix

Delivery services are connected through the sale module as delivery handlers (class \Bitrix\Sale\Delivery\Services\Base). For each service there is a separate class with implementation:

• calculateConcrete() — cost calculation
• createShipment() — creating shipment in an external system (if implemented)
• getTrackingInfo() — getting tracking status

Custom handlers are placed in /local/php_interface/include/sale_delivery/. Standard modules for delivery services (CDEK, DHL, DPD, Boxberry, PickPoint, SDEK) are installed from the Marketplace.

What to test

Delivery cost calculation

The first and most frequent point of failure. They check:

• Correct calculation for different product dimensions (products with filled WEIGHT, WIDTH, HEIGHT, DEPTH in the catalog are needed)
• Operation when some products in the cart lack dimensions
• Correctness of delivery zones — a tariff for Moscow should not apply to Vladivostok
• Calculation caching: repeated request of the same cart should return the result from cache, not calling external API again

// Check delivery calculation cache
$cacheManager = \Bitrix\Main\Data\Cache::createInstance();
$cacheKey = 'delivery_calc_' . md5(serialize($basketItems) . $cityCode);
if ($cacheManager->initCache(3600, $cacheKey, '/sale/delivery/calc')) {
    $cachedResult = $cacheManager->getVars();
} else {
    $result = $deliveryService->calculate($shipmentItemCollection, $extraServices);
    $cacheManager->startDataCache();
    $cacheManager->endDataCache($result);
}

Pickup point selection

Widgets of CDEK, Boxberry, PickPoint load a map via JS. They test:

• Widget loading on all target browsers
• Correct transfer of selected pickup point to the order form
• Saving the selected pickup point on page refresh
• Behavior when JS is unavailable (graceful degradation)

Shipment creation

Checking that the order is correctly registered in the delivery service account when the status changes in Bitrix:

// Handler for order status change event
AddEventHandler('sale', 'OnOrderStatusChange', function(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ORDER');
    $newStatus = $event->getParameter('NEW_STATUS');

    if ($newStatus === 'PROCESSING') {
        foreach ($order->getShipmentCollection() as $shipment) {
            if (!$shipment->isSystem()) {
                $deliveryService = $shipment->getDelivery();
                // Test: check that createShipment returns tracking number
                $result = $deliveryService->createShipment($shipment);
                // result should contain tracking_number
            }
        }
    }
});

Tracking

We test with real tracking numbers (CDEK has test ones in the documentation sandbox) checking the update of UF_TRACKING field in b_sale_shipment.

# Get token
curl -X POST https://api.edu.cdek.ru/v2/oauth/token \
  -d "grant_type=client_credentials&client_id=EMscd6r9JnFiQ3bLoyjJY6eM&client_secret=PjLZkKBHEiLK3YsjtNrt7ZpUWSrTJtp6"

# Calculate delivery
curl -X POST https://api.edu.cdek.ru/v2/calculator/tariff \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{"tariff_code":136,"from_location":{"code":44},"to_location":{"code":270},"packages":[{"weight":1000,"length":20,"width":15,"height":10}]}'

How to automate regression testing of delivery?

For regression testing of delivery calculations, we write unit tests in PHPUnit with HTTP client mocking. Automated testing is 5 times faster than manual regression. It covers 95% of scenarios against 70%.

class CdekDeliveryTest extends \PHPUnit\Framework\TestCase
{
    public function testCalculateReturnsNonZeroForValidPackage(): void
    {
        $httpMock = $this->createMock(HttpClient::class);
        $httpMock->method('post')->willReturn($this->getFixture('cdek_tariff_response.json'));

        $service = new CdekDeliveryService(['http_client' => $httpMock]);
        $result = $service->calculate($this->buildShipment(weight: 1000, city: 'SPB'));

        $this->assertGreaterThan(0, $result->getPrice());
        $this->assertNotEmpty($result->getPeriodMin());
    }
}

Comparison of manual and automated testing

What is included in the work

• Audit of current integration and documentation
• Writing test scenarios for your catalog and services
• Testing calculations, pickup points, shipment creation, tracking
• Compiling a report with found errors and recommendations
• Automation of regression tests (optional)
• Consultation on fixing typical problems

Timelines and cost

Cost is calculated individually after analyzing your terms of reference. We guarantee detection of at least 90% of typical integration errors. Each found error saves the company up to 500,000 RUB on fixing in production. Contact us for a preliminary project estimate — get a consultation on typical problems of your integration. Order testing now.

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.