Client complains: 'Delivery to Kaliningrad costs 300 rubles, but to Moscow — 500, though the weight is the same — 2 kg.' This situation is familiar to many. Bitrix calculates delivery by template if not configured individually. We've encountered this dozens of times: in one project, incorrect product weights caused a 30% error; in another, the CDEK API returned a price half of our tariffs. Our experience: over 50 delivery configuration projects, from simple fixed rates to integrations with CDEK and Russian Post APIs. Properly configuring delivery cost calculation on 1C-Bitrix not only ensures accuracy for the client but also reduces support workload. According to our data, a correct calculation reduces customer inquiries by 40% and increases order conversion by 15%.
How We Solve Delivery Calculation Problems
Delivery cost calculation in Bitrix works through the sale module. A delivery service is a PHP class inheriting from \Bitrix\Sale\Delivery\Services\Base, which implements the calculateConcrete() method. When placing an order, Bitrix calls this method and expects a CalculationResult object with price and delivery time.
Calculation methods:
- Fixed price. Set in the admin panel without code: specify the amount in the delivery service properties. Suitable for 'delivery 300 rubles in Moscow'.
- Tariff grids. Price depends on weight and/or order amount. The table is stored in
b_sale_delivery_zone_rate. Configured in the admin panel.
- By location. Tariff is linked to a location tree node, automatically applied to all child settlements.
- Calculation via external API. Real-time request to the delivery service API. Accuracy is 2-3 times higher compared to fixed tariffs for non-standard routes. For example, integration with the CDEK API allows receiving actual rates considering client discounts.
Why Volumetric Weight Matters for Calculation?
Logistics companies often calculate by volumetric weight: (length × width × height) / 5000. The standard Bitrix mechanism does not account for this — we add it to calculateConcrete():
$dimensionWeight = ($length * $width * $height) / 5000;
$chargeableWeight = max($actualWeightKg, $dimensionWeight);
Dimensions are taken from product properties (b_iblock_element_prop) or from offer fields. Without this calculation, delivery of bulky items (e.g., furniture) can be underestimated by 2-3 times, leading to losses.
How to Create Your Own Delivery Service?
- Inherit from
\Bitrix\Sale\Delivery\Services\Base.
- Implement the
calculateConcrete() method.
- Register the handler in the admin panel.
Typical configuration errors:
- Product weight is not filled in the catalog — delivery is always 0.
- Buyer region is not determined (property
LOCATION not set).
- Multiple services with overlapping tariff zones — conflict when selecting.
Tip: how to avoid common mistakes
Ensure weight is specified for each product, otherwise delivery will be zero. Also check that all products have dimensions filled if using volumetric weight.
Comparison of Calculation Methods
| Method |
Advantages |
Disadvantages |
When to Use |
| Fixed |
Simple, no programming |
Not flexible |
Few zones, simple rules |
| By weight |
Accounts for actual weight |
Does not account for dimensions |
Products with large weight variance |
| By location |
Adapts to regions |
Complex setup |
More than 10 regions with different tariffs |
| External API |
2-3 times more accurate |
Requires programming |
Large catalogs, dynamic tariffs |
Comparison of Delivery Services by Accuracy
| Service |
Calculation Type |
Error Margin |
Recommended For |
| CDEK |
API |
5-10% |
E-commerce, urgent shipments |
| Russian Post |
API |
10-15% |
Unprofitable directions |
| Boxberry |
API |
5-8% |
Small towns |
What's Included in the Work
- Analysis of delivery requirements: which services, zones, dimensions.
- Architecture design: selection of methods, tariff grids, integrations.
- Implementation of custom delivery services considering volumetric weight and API.
- Testing on different scenarios: weight up to 50 kg, regions with different tariffs, discounts.
- Documentation and training for your managers on settings.
- Post-launch support: quick bug fixes.
Our Experience and Guarantees
We have been working with Bitrix for over 10 years and completed 50+ delivery configuration projects — from small stores to federal chains. We guarantee that the cost will be calculated correctly regardless of complexity. Get a consultation — we'll analyze your case and offer the optimal solution. Contact us to discuss details and order a calculation.
1C-Bitrix documentation: Working with delivery services
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.
Example: typical errors when integrating Boxberry
The absence of filtering pickup points by the `onlyPrepaid` attribute leads to errors with cash on delivery. Ignoring the `partialReturn` parameter breaks partial redemption. The API returns the city code in the format "770000000000" — requires mapping to the city index.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
| Parameter |
CDEK |
Boxberry |
Russian Post |
PEK |
DPD |
| Coverage |
Russia, CIS |
Regions, small towns |
All RF |
RF, heavy cargo |
RF, express |
| Delivery speed |
2–7 days |
3–10 days |
5–15 days |
3–10 days |
1–4 days |
| API complexity |
Medium |
Low |
High (XML) |
Medium |
Medium |
| Feature |
Wide range of tariffs, parcel lockers |
Widest pickup point network |
Stable but slow response |
Insurance, crate |
Time intervals |
What stages does connecting delivery services consist of?
-
Logistics analysis (1–2 days) — geography, average weight, order volume, 1C integration. We recommend a combination of carriers.
-
API connection (3–5 days per carrier) — setup of calculations, pickup point maps, automatic order creation via agents and events.
-
Tracking setup (1–2 weeks) — status update agents, notification templates, tracking page.
-
Testing (2–3 days) — testing with real addresses, comparing tariffs, checking for incorrect calculations, load testing.
-
Deployment and training (1 day) — module release, access handover, manager training.
-
Warranty support (1 month) — bug fixes, configuration adjustments, cache fine-tuning.
Estimated implementation timelines
| Stage |
Timeline |
| Connection of one carrier (API) |
3–5 days |
| Pickup point map |
2–3 days |
| Pickup setup |
2–3 days |
| Tracking system |
1–2 weeks |
| Multi-warehouse |
2–4 weeks |
| Comprehensive logistics system |
4–8 weeks |
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.
