Configuring Courier Delivery in 1C-Bitrix: Complete Guide
Imagine a customer placing an order on your site, selecting courier delivery, but it doesn't appear in the cart. Or the shipping cost is calculated with a fixed rate instead of a formula—and you lose profit on small orders. Most often the problem lies in misconfigured restrictions: location, weight, or sum constraints set incorrectly, and payment systems not bound to the delivery service. As a result, the driver arrives in the wrong city or the customer can't pay. We fix such bugs regularly: over 30 projects in configuring 1C-Bitrix shipping—from simple urban deliveries to multi-warehouse setups with dozens of zones and dynamic cost calculation. In this article, we'll break down how to configure courier delivery correctly, avoiding typical pitfalls.
We'll guide you through the process step by step: from creating the service to binding payment systems and setting schedules. We'll cover the most common hidden issues and how to bypass them with minimal effort. If you already have a store on 1C-Bitrix, you can apply this knowledge immediately. If not, after reading you'll know exactly what to demand from a developer.
Creating a Courier Delivery Service
- Go to
Store → Settings → Delivery services and click "Add service".
- Select "Own delivery service".
- Fill in the parameters:
- Name: e.g., "City Courier Delivery".
- Code:
courier_city (unique identifier).
- Cost: fixed or formula (see example below).
- Currency: ruble.
- Configure restrictions (next section).
- Bind payment systems.
Basic setup can be done in 15–20 minutes if the delivery zones and tariffs are known in advance. This quick configuration saves up to 30% on initial costs compared to hiring a developer.
For formula-based calculation, use PHP expressions:
[PRICE] >= 3000 ? 0 : 350
[PRICE] is the order total, [WEIGHT] is weight in grams. A custom delivery handler is about 5 times more flexible than the standard formula: it can account for address distance, courier service tariffs, promo codes, and other parameters. Using the standard formula is 3 times faster for simple cases, but for complex logic, coding a custom handler from the start is best.
Setting Restrictions
Restrictions define the conditions under which the delivery service is available. They are set on the "Restrictions" tab in the service card. Incorrect restrictions cause 90% of delivery display errors.
| Restriction type |
Parameters |
Example |
| Location |
Selection of cities/regions, zones |
Only Moscow and Moscow region |
| Minimum amount |
Number in currency |
500 rubles |
| Maximum weight |
Number in grams |
30000 g |
| User groups |
Group IDs |
Authorized users |
When configuring delivery zones, note: if a city is not added to the list, the service won't show. Also, restrictions are stored in the b_sale_delivery_restriction table and apply immediately — no caching. So set them correctly the first time. For example, specifying a minimum amount of 500 rubles ensures the shipping option only appears for orders above that threshold.
Why Payment System Binding Is Critical
Without binding to payment systems, delivery may not work: the customer selects card payment, but the courier delivery is incompatible with that method. In 80% of cases, the error "no shipping services compatible with the payment system" occurs precisely due to missing binding.
To avoid this, go to Store → Settings → Payment systems, select the needed payment system, and on the "Delivery services" tab, check which services it works with. For example, cash on delivery only for courier shipping, while e-wallets for all. Without binding—100% error on incompatibility; with binding—correct calculation. This step cannot be skipped.
Setting Dynamic Scheduling and Deadlines
The "Settings" tab of the delivery service allows you to set:
- Delivery period: "from 1 to 3 days".
- Delivery condition: text description, e.g., "Delivery on the day of order if placed before 2 PM".
But that's just text. For actual time checking, you need a custom handler. It analyzes the current time and date, and accordingly enables or disables delivery. Developing such a handler takes 1–2 days and requires knowledge of the Bitrix API. The result is real scheduling, not a static label.
What's Included in Courier Delivery Setup?
| Stage |
Duration |
| Basic setup (service, restrictions, payments) |
3–5 hours |
| With custom formula and schedule |
1 business day |
| Complex integration (multiple zones, logistics) |
2–3 days |
| Custom handler development |
1–2 days |
As a result, you get:
- Working courier delivery with specified rules.
- Payment system binding.
- Brief documentation of settings.
- Testing on a test order.
- Functionality guarantee and 14 days of support.
Results and Guarantees
For over 5 years, we have been implementing and refining 1C-Bitrix. We've completed 30+ delivery projects, including complex integrations with 1C, CDEK, and proprietary courier services. Our experienced engineers handle any task—from simple courier shipping to multi-warehouse with dynamic calculation. Contact us to discuss your situation—we'll offer the best solution without unnecessary extras. Order courier delivery setup and get a smoothly running store without headaches.
For more details, see the official documentation.
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.
