Integrating 1C-Bitrix with the 5Post Delivery Service

Pickup points are the main channel for customers to receive goods in the regions. 5Post, a subsidiary of X5 Retail, manages a network of over 15,000 pickup points in "Pyaterochka" and "Perekrestok" stores. However, integration with 1C-Bitrix often causes difficulties: incorrect token handling, unaccounted dimension restrictions, lost webhooks. We offer a ready-made solution — we connect 5Post via REST API from scratch or refine an existing integration. Our team's experience — 5+ years of Bitrix development, 100+ delivery integration projects — ensures you get a stable result and a performance guarantee.

Why Integrate 5Post into 1C-Bitrix?

5Post outperforms many alternatives: its pickup point network is the largest among Russian delivery services, and delivery costs are below market average. For an online store, this means more loyal customers and lower logistics costs. Integration via REST API provides full control — from cost calculation to real-time status tracking.

How to Configure OAuth 2.0 for 5Post?

5Post provides a REST API. Authorization is via OAuth 2.0 (client_credentials). Base production URL: https://api.5post.ru. A test environment is provided upon connection through your 5Post personal account. Getting a token:

$tokenResponse = $httpClient->post('https://api.5post.ru/api/v1/auth/token', [
    'grant_type'    => 'client_credentials',
    'client_id'     => $clientId,
    'client_secret' => $clientSecret,
]);
$accessToken = $tokenResponse['access_token'];
// token valid for 1 hour — cache in b_option

The token is valid for 60 minutes, so we cache it in module options and refresh it 5 minutes before expiration. On a 401 error, we automatically request a new token and retry the request. 5Post API documentation details request parameters.

Main API methods:

• POST /api/v1/orders — create a delivery request
• GET /api/v1/orders/{orderUUID} — get request status
• DELETE /api/v1/orders/{orderUUID} — cancel
• GET /api/v1/pvz — list pickup points with region/city filtering
• POST /api/v1/orders/calc — calculate delivery cost

What to Do When Webhooks Fail?

5Post sends webhooks on status changes. Register the URL in your personal account. Status mapping:

On receiving a webhook, check the X-Signature header (HMAC signature) — 5Post signs requests with the partner's secret key. If the signature does not match, the webhook is ignored and an error is logged.

$signature = $_SERVER['HTTP_X_SIGNATURE'];
$payload = file_get_contents('php://input');
$expectedSignature = hash_hmac('sha256', $payload, $secretKey);
if (hash_equals($expectedSignature, $signature)) {
    // process webhook
} else {
    // ignore and log
}

Module in Bitrix

The delivery class inherits from \Bitrix\Sale\Delivery\Services\Base. Parameters are stored in b_sale_delivery_service_params: CLIENT_ID, CLIENT_SECRET, PARTNER_CODE (5Post partner code).

Cost Calculation

$calcResult = $httpClient->post('/api/v1/orders/calc', [
    'partnerOrder' => [
        'partnerOrderId' => 'SHOP-' . $orderId,
        'pvzCode'        => $selectedPvzCode,
        'dimensions'     => [
            'length' => $lengthCm,
            'width'  => $widthCm,
            'height' => $heightCm,
            'weight' => $weightGram,
        ],
        'assessedValue' => $assessedValue,
    ],
]);
$deliveryCost = $calcResult['deliveryCost'];

For a preliminary calculation (before selecting a specific pickup point), you can pass the locality code instead of the pickup point code — the API will return the base cost by zone.

Loading and Displaying Pickup Points

The list of pickup points is large: over 15,000 objects. Loading strategy:

1. Once daily (Bitrix agent) request the current list via GET /api/v1/pvz.
2. Save to an HL-block "5Post Pickup Points" with fields: code, name, address, coordinates, working hours, allowed dimensions.
3. On the checkout page, filter pickup points by selected city and display on a map.

An important nuance: 5Post pickup points have dimension restrictions. maxDimensionCm and maxWeightGram must be considered during filtering to avoid showing pickup points where the parcel physically cannot fit.

Creating a Request

After selecting a pickup point and placing the order, create a request:

$orderPayload = [
    'partnerOrder' => [
        'partnerOrderId'  => 'SHOP-' . $bitrixOrderId,
        'pvzCode'         => $pvzCode,
        'recipientName'   => $fullName,
        'recipientPhone'  => $phone,
        'recipientEmail'  => $email,
        'assessedValue'   => $assessedValue,
        'cashOnDelivery'  => $codAmount,
        'dimensions'      => $dimensions,
        'places'          => [
            ['barcode' => 'SHOP-' . $bitrixOrderId . '-1', 'description' => 'Place 1']
        ],
    ],
];

The response contains orderUUID — saved in b_sale_order_props. It also returns a label for printing (labelUrl): a PDF with a barcode for the parcel sticker.

Operational Features

5Post does not automatically refund money for unclaimed orders — return conditions must be set in the contract. Shelf life at pickup points is 7 days, after which the parcel is returned. On return, the status in b_sale_order is updated via the same webhook mechanism.

What's Included in the Integration

• OAuth 2.0 setup and token caching
• Development of a delivery class with cost calculation
• Loading and storing pickup points in an HL-block
• Filtering pickup points by city and dimensions
• Webhook processing with HMAC signature verification
• Creating requests and printing labels
• Testing in the 5Post sandbox
• Documentation and training for your manager

Timelines

Contact us — we will assess your project and provide accurate timelines. We guarantee stable integration: monitoring, error handling, and post-launch support. Get a consultation on integration — we will help configure 5Post for your business.

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.