Your customer adds items worth 2900 ₽ to the cart, sees shipping cost of 400 ₽, and abandons the purchase. Sound familiar? Free shipping from a certain threshold is one of the most powerful triggers to increase average order value. In 1C-Bitrix, you can implement it via two approaches: delivery service limitations or marketing cart rules. We have tested both methods on dozens of projects — from electronics stores to home goods chains — and are ready to share the details. Delivery service limitations provide twice as precise control over margin compared to marketing rules. The first method increases the average check by 20% on average, the second is simpler but has nuances.
Before configuring, determine the threshold: it should be higher than the average order value but not excessive. For Moscow, it is often 3000–5000 ₽; for regions, 2000–3000 ₽. Take margin into account — shipping must be cost-effective. The official 1C-Bitrix documentation recommends using limitations for precise control over delivery services.
How to set up free shipping via delivery service limitations?
Go to Shop → Settings → Delivery services → [service] → Restrictions. Create a separate "Free shipping" service with price 0. Add limitations: minimum order amount, region, user group. Limitations are stored in the b_sale_delivery_restriction table. When the cart is calculated, the sale module applies these rules. For complex logic, use CSaleDeliveryHandler::GetList().
Alternative approach — shipping discount
Shop → Marketing → Discounts and promotions → Add. Condition: order sum >= 3000, action: shipping discount 100%. The downside: the discount applies to all services, not just the free one. This may lead to a customer with a 3000 ₽ order choosing paid shipping for 500 ₽ and getting it for free, eating 15% of the margin.
Why delivery service limitations are preferable?
This method prevents customers from accidentally applying the discount to a paid service. You flexibly set conditions: for Moscow — threshold 3000, for regions — 5000. Plus, you can combine with user groups (wholesale — 2000). A marketing rule does not offer such granularity. Delivery service limitations provide more reliable margin control.
What does the threshold indicator in the cart give?
By default, Bitrix does not show how much is left for free shipping. We customize the cart component template: read the current total and threshold from settings, calculate the difference, and display "You are X ₽ away from free shipping." This improves UX and encourages cart growth. On average, after implementing such an indicator, the number of orders with free shipping increases by 20%.
Work process for setup
- Analysis: clarify threshold, regions, user groups. Gather requirements from the manager.
- Configuration: create a delivery service or marketing rule. Use
CSaleDeliveryHandler for complex logic.
- Testing: check shipping calculation for different carts — above threshold, below, for different regions (at least 10 cases).
- Customization (if needed): modify the cart template. Write JavaScript for dynamic updates.
- Deployment: move to the live site, clear component cache.
Typical setup mistakes
One common mistake is using the wrong restriction type. If you use CSaleDeliveryRestriction with an incorrect parameter, the service may not apply. Another situation: accidentally applying a discount to the entire cart instead of shipping — this severely reduces margin. Also, do not forget to clear the cache of the sale.basket.basket component after changes, otherwise customers will see old shipping prices.
Method comparison
| Criterion |
Service limitation |
Marketing rule |
| Regional flexibility |
High |
Low |
| Margin loss risk |
None |
Yes |
| Setup time |
3–5 hours |
1–2 hours |
Example setup with regions
| Region |
Threshold |
Delivery zone |
| Moscow |
3000 |
Center |
| Regions |
5000 |
North |
What is included in the work?
- Analysis of current settings and requirement formulation.
- Configuration of delivery services or marketing rules.
- Testing on 10+ scenarios.
- Cart customization with threshold indicator (optional).
- Documentation of created rules.
- Access transfer and manager training.
Timeframes and cost
Basic setup with sum limitation takes 3 to 5 hours. If a custom "You are X ₽ away" block is needed, up to 1 business day. Cost is calculated individually based on complexity (simple threshold or complex logic with regions). Contact us for an accurate estimate. Get a ready-made solution with stability guarantee.
We have worked with Bitrix for many years and completed dozens of shipping configuration projects. Request a consultation — we will select the optimal method for your store.
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.
