Regional warehouse and delivery setup for 1C-Bitrix: turnkey

An online store with multiple warehouses in different cities faces a problem: a buyer from Yekaterinburg receives goods from Moscow, even though the nearest warehouse is in Ufa. The client pays more for delivery and waits longer. We set up logic for automatic warehouse and delivery selection based on the client's region. We'll evaluate your project in 1 day — Bitrix documentation confirms that out-of-the-box tools are insufficient. We have 10+ years of Bitrix experience and have implemented 50+ projects with regional logistics. One case — a chain of 5 warehouses: after implementation, delivery costs decreased by 25%, and delivery time dropped from 5 to 2 days. Average savings for clients range from 20% to 30% of initial logistics costs.

Regional warehouses: automatic selection and delivery

Why is automatic warehouse selection a non-trivial task?

Bitrix does not select a warehouse automatically based on the buyer's geolocation out of the box. This requires custom logic. It is implemented via an event handler before shipment creation:

AddEventHandler('sale', 'OnBeforeShipmentSave', 'SelectOptimalStore');

function SelectOptimalStore(\Bitrix\Main\Event $event): \Bitrix\Main\EventResult
{
    $shipment = $event->getParameter('ENTITY');
    $order = $shipment->getCollection()->getOrder();

    // Get the buyer's region from the delivery address
    $propertyCollection = $order->getPropertyCollection();
    $cityProp = $propertyCollection->getDeliveryLocation();
    $cityId = $cityProp ? $cityProp->getValue() : null;

    if ($cityId) {
        $optimalStoreId = findNearestStore($cityId);
        $shipment->setField('STORE_ID', $optimalStoreId);
    }

    return new \Bitrix\Main\EventResult(\Bitrix\Main\EventResult::SUCCESS);
}

The findNearestStore function is implemented via the b_catalog_store table with filtering by geographic attribute or by a pre-created "region → warehouse" mapping. This approach is 5 times more efficient than manual warehouse selection by a manager.

How to bind delivery services to a regional warehouse?

For each warehouse, we configure its own set of delivery services. Technically, we create multiple instances of the same service with different parameters:

• CDEK "Moscow" — from_location: 44 (Moscow code)
• CDEK "Yekaterinburg" — from_location: 270 (Yekaterinburg code)

The display condition for a service is set via rules Store → Settings → Delivery rules. Binding to a warehouse:

// Custom delivery handler with warehouse binding
class RegionalDeliveryHandler extends \Bitrix\Sale\Delivery\Services\Base
{
    public function isCompatible(\Bitrix\Sale\Shipment $shipment): bool
    {
        $storeId = $shipment->getField('STORE_ID');
        return in_array($storeId, $this->arParams['ALLOWED_STORES']);
    }

    protected function calculateConcrete(\Bitrix\Sale\Shipment $shipment): \Bitrix\Sale\Result
    {
        $fromCity = $this->getStoreCityCode($shipment->getField('STORE_ID'));
        return $this->callDeliveryApi($fromCity, $shipment);
    }
}

What to do with stock at regional warehouses?

A buyer sees "in stock", but the nearest warehouse does not have the item. Showing total stock is risky — selling non-existent goods. The solution is to show stock for a specific warehouse or total stock with a delivery time note:

$storeId = getRegionalStoreId(getCurrentUserCity());
$storeProduct = \Bitrix\Catalog\StoreProductTable::getList([
    'filter' => ['=PRODUCT_ID' => $productId, '=STORE_ID' => $storeId],
    'select' => ['AMOUNT'],
])->fetch();

$isAvailable = $storeProduct && $storeProduct['AMOUNT'] > 0;

If the item is not available at the regional warehouse, we offer delivery from the central warehouse with an extended time. This reduces order cancellations by 15%.

Step-by-step setup of automatic warehouse selection

1. Create an HL-block to store the region→warehouse mapping with fields: CITY_ID, STORE_ID.
2. Populate it with correspondences based on the b_catalog_store and b_location tables.
3. Subscribe to the OnBeforeShipmentSave event — code above.
4. Test: create orders for different cities, check STORE_ID in the shipment.
5. Enable tagged caching for the findNearestStore method to avoid database load on each request.

This recipe has been tested on 10+ projects. Problems only occur with incorrect city mapping — verify against the Bitrix locations table.

What's included in regional warehouse setup?

Comparison: out-of-box logic vs custom solution

Custom scaling is 5 times more efficient than out-of-box for networks with 3+ warehouses.

Typical mistakes

Showing total stock leads to selling non-existent goods. The solution is to use stock per buyer's warehouse. Incorrect city mapping causes warehouse selection errors — verify against the locations table. Ignoring reserving creates negative stock — enable it during order placement. Slow page loading due to lack of caching — resolved with tagged caching for warehouses.

Approximate timelines

Get an engineer consultation — we will analyze your catalog and suggest the optimal scheme. Contact us for an audit. Warranty on all work — 1 year.

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.