Imagine: 60% of orders in your online store are handled manually – managers call customers to confirm the city and choose a carrier. Sounds familiar? We configure flexible delivery routing on 1C-Bitrix: automatic warehouse selection, prioritized delivery services per region, weight and time considerations. As a result, order processing time drops by 35% and manual errors fall to 2%. Our engineers are certified 1C-Bitrix specialists with 7+ years of experience and 50+ logistics automation projects.
How to set up warehouse selection by delivery address?
Standard Bitrix cannot automatically assign a shipping warehouse based on the buyer's address. We implement this through custom handlers. We create a bl_store_zones table with location_id -> store_id mapping. When a shipment is created, the region from the delivery address is identified and the warehouse is assigned. Example code:
$locationId = $order->getPropertyCollection()->getItemByOrderPropertyCode('LOCATION')?->getValue();
$storeId = StoreZoneTable::getStoreByLocation($locationId) ?? DEFAULT_STORE_ID;
$shipment->setField('DELIVERY_DOC_NUM', $storeId);
This enables selection of the nearest distribution center, reducing shipping cost for the customer and processing time.
Why is Bitrix's standard functionality insufficient?
Bitrix provides basic delivery zones and service binding via b_sale_delivery_location. But multi-warehouse setups, carrier prioritization by weight and region, and custom warehouse integrations require custom development. We use events, agents, and admin interfaces to flexibly manage logistics without code changes each time.
How we configure routing: a case with 5 warehouses
One of our clients is a retail chain with 5 warehouses across Russia and 10 delivery methods. Before integration, 40% of orders were processed manually. After our upgrade, the system automatically determines the nearest warehouse to the delivery address and suggests the cheapest available service. Order processing time decreased by 30%, errors dropped to 2%.
Key elements we improve:
Delivery zones in Bitrix
Delivery zones are stored in the b_sale_location table – a hierarchical directory of regions. Delivery services (b_sale_delivery_service) are linked to zones via b_sale_delivery_location. When a customer selects a city, Bitrix shows only those services that operate in that zone. Standard binding:
\Bitrix\Sale\Delivery\Services\Manager::save([
'ID' => $deliveryServiceId,
'ACTIVE' => 'Y',
'RESTRICTED_LOCATION' => [$locationId1, $locationId2],
]);
But for complex scenarios (multiple warehouses, weight/size restrictions) this is insufficient.
Selecting the shipping warehouse by address
The logic "which warehouse is closest to the delivery address" is absent in standard Bitrix. We implement it via the OnSaleShipmentBeforeSave event or a custom order handler. We create a bl_store_zones table with location_id → store_id mapping. When a shipment is created, we determine the region from the delivery address and assign the warehouse.
Carrier prioritization
When multiple delivery services are active, we can automatically suggest the optimal one by cost or speed. Create prioritization rules in bl_delivery_rules:
| Field |
Description |
location_group |
Region or group of regions |
order_weight_from / to |
Weight range |
delivery_service_id |
Preferred delivery service |
priority |
Order of suggestion |
An agent or basket component sorts available services by these rules during delivery calculation.
Comparison: standard setup vs. our custom solution
| Criteria |
Standard Setup |
Our Development |
| Warehouse selection by address |
Not supported |
Custom handler, bl_store_zones table |
| Carrier prioritization |
Manual sorting only |
Rules by weight, region, cost |
| 1C integration |
Basic via CommerceML |
Custom handlers, REST API |
| Admin interface |
Standard |
Extended interface for rules |
| Warranty |
None |
12 months |
Official documentation: Delivery zones in Bitrix
What our work includes
- Analysis of current delivery scheme and requirements gathering.
- Configuring delivery zones in
b_sale_location and binding services to zones.
- Developing
bl_store_zones table with region-to-warehouse mapping.
- Implementing warehouse selection logic during shipment creation.
- Carrier prioritization rules by weight, region, cost.
- Admin interface for managing routing rules.
- Documentation and training for your managers.
Timeline and warranty
Timelines depend on complexity: from 3 to 14 business days. We provide a 12-month warranty on all customizations. Our engineers are certified 1C-Bitrix specialists with 7+ years of experience. We'll assess your project free of charge in 1 day – just contact us.
Typical mistakes when doing it yourself
- Incorrect location binding: regions don't match addresses, delivery doesn't show.
- Lack of priorities: with multiple carriers, the customer sees all but doesn't know which to choose.
- Ignoring product weight: lightweight orders aren't offered postal services even when cheaper.
We account for these nuances and configure routing to work seamlessly. Order our setup – and your customers will stop getting confused about delivery. Get a consultation: we'll evaluate your project in one 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.
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.
