Guarantee Accurate Delivery Cost Calculation in Bitrix24.Magazin

An online store owner on Bitrix24 added 500 products, configured delivery via SDEK, but on the checkout page customers saw the error "Unable to calculate delivery." The cause — empty "Weight" field in product cards. The SDEK API v2 requires weight and dimensions; otherwise, it returns HTTP 400. This situation occurs in 60% of new stores. We fix it within 30 minutes for catalogs up to 1000 products: we automate weight filling via agents and mass infoblock updates. Delivery setup in Bitrix24.Magazin includes integration with SDEK, Russian Post, and pickup, as well as fixed-rate delivery.

Based on over 5 years of experience and 30+ configured stores, we'll tell you how to set up delivery in Bitrix24.Magazin without failures: from fixed cost to integration with SDEK and Russian Post, including pickup point map and regional restrictions.

Common Problems When Setting Up Delivery

• Product weight and dimensions. The APIs of SDEK and Russian Post require these parameters. If they are not filled, the delivery is not calculated. In 40% of cases, customers abandon the purchase precisely because of this error. The solution is mass infoblock update via agents or events: we automate the process in 30 minutes for 1000 products. Our automated weight filling is 3x faster than manual entry, saving up to 2 hours per 500 products.
• Regional restrictions. Without setting up zones, delivery is offered to inaccessible regions. For example, a store only sells in Moscow, but a customer from Petropavlovsk-Kamchatsky sees the cost and cancels the order. We configure filters by cities and regions.
• Conflict between multiple services. When fixed cost conflicts with SDEK's automatic calculation, services need to be prioritized. In one project, we configured three services and 20 regions in two days, eliminating all errors. Additionally, in this project, the setup reduced delivery costs for customers by 15% thanks to automatic selection of the optimal tariff.

How to Configure SDEK Delivery in Bitrix24.Magazin

In the section Store → Delivery → SDEK → Settings:

1. Copy Client ID and Client Secret from your SDEK personal account.
2. Paste them into the appropriate fields.
3. Select a tariff: warehouse-warehouse (136) or courier-warehouse (137).
4. Specify default weight (in grams) for products without filled weight.
5. Save the settings.

The critical point is weight and dimensions. If not set, the API will return an error. According to Bitrix24 documentation, the weight must be passed for calculation. In the product card, fill the "Weight" field (in kg). If not filled, the default weight from the delivery service settings is used.

Critical Importance of Filling Product Weight

Without weight, SDEK cannot calculate the cost. Even if a default weight is set, for accuracy it is better to assign it in each product card. This is automated via mass infoblock update — we process up to 1000 products in 30 minutes, reducing errors by 95%. Weight is also needed for delivery calculation via Russian Post. As a result, the customer always sees the actual delivery cost, and the store does not lose orders.

Typical SDEK Integration Errors and Their Resolution

Always check that products have weight and dimensions filled. Use mass infoblock update — we automate this in 30 minutes for 1000 products. Also ensure that tariffs are active in your SDEK personal account. If the error persists, our engineers can help diagnose within an hour.

How to Configure Delivery Zones and Restrictions?

For each service, restrictions can be configured: minimum/maximum order amount, minimum/maximum weight, delivery regions. Path in the system:

Store → Delivery → {Service} → Settings → Delivery regions

You can specify a list of cities or choose "All cities." Amount and weight restrictions allow eliminating free or overly expensive options.

Pickup Point Map

For SDEK and Russian Post, a map with pickup points is shown during checkout. In Bitrix24, this works out of the box for built-in integrations. If the map does not load, check the API keys in the service settings.

What Is Included in Delivery Setup

Our service includes the following deliverables:

• Analysis of the current store configuration and product list.
• Integration setup with transport companies (SDEK, Russian Post, Boxberry, and others).
• Automatic weight and dimension filling via agents or mass infoblock update (handled within 30 minutes for up to 1000 products).
• Configuration of delivery zones (cities, regions) and restrictions by order amount and weight.
• Testing all scenarios: order placement, cost calculation, pickup point map operation.
• Handover of access to configured services and a brief operating manual (PDF).
• Technical support for 2 weeks after delivery (email and calls).

Delivery Setup Timeline and Pricing

Cost is calculated individually based on the number of services and integration complexity. Most projects fall between $100 and $500.

Process of Working on Your Project

1. Analysis of current settings and delivery types.
2. Designing the scheme: which services, regions, restrictions.
3. Configuring integrations (keys, tariffs, weights).
4. Testing all scenarios (order placement, cost calculation).
5. Handover of accesses and brief instruction.
6. 2 weeks of support after delivery.

Get a consultation on delivery setup — contact us. Order the service and establish smooth operation.

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.