Integration of Europochta with 1C-Bitrix: Complete Setup

Integration of Europochta with 1C-Bitrix: Complete Setup

When integrating the Europochta delivery service with 1C-Bitrix, problems often arise: non-standard parcel weight calculation (minimum threshold 0.05 kg), confusion with cash on delivery, and lack of automatic tracking. We have been solving these tasks for many years and have implemented over 30 integrations for Belarusian online stores. Our turnkey solution includes everything from API setup to a pickup point map on the website. Europochta is a private postal operator with a wide network of pickup points. The API is provided to partners after registration.

What problems do stores face?

The main technical difficulties: non-standard weight calculation (requires a minimum threshold of 0.05 kg), incorrect transmission of the cash-on-delivery code, and lack of status synchronization. Additionally, low performance due to frequent API requests during delivery calculation. Standard delivery components in Bitrix are not optimized for Europochta — frequent requests slow down the page. Our component uses tagged caching and reduces server load by 2-3 times. Average time savings on processing one order is up to 60%.

Why integrate Europochta through our component?

We use tagged caching for calculation results, reducing server load by 2-3 times. Unlike standard solutions, our component supports automatic cod determination based on the payment method, eliminating manual errors. We transmit cod as a numeric value with two decimal places, as prescribed in the official Europochta API documentation.

How to set up cost calculation without errors?

class EuropachtaHandler extends \Bitrix\Sale\Delivery\Services\Base
{
    protected function calculateConcrete(
        \Bitrix\Sale\Shipment $shipment
    ): \Bitrix\Sale\Delivery\CalculationResult {
        $result = new \Bitrix\Sale\Delivery\CalculationResult();
        $order  = $shipment->getOrder();

        $response = $this->apiPost('/rate/calculate', [
            'from_city'    => $this->getOption('SENDER_CITY'),
            'to_city'      => $this->getOrderCity($shipment),
            'weight'       => max($shipment->getWeight() / 1000, 0.05),
            'declared'     => round($order->getPrice()),
            'delivery_type' => $this->getOption('DELIVERY_TYPE', 'pvz'),
        ]);

        if (!empty($response['price'])) {
            $result->setDeliveryPrice((float)$response['price']);
            $days = $response['days'] ?? '2–5';
            $result->setPeriodDescription("{$days} days");
        }

        return $result;
    }
}

Creating an order with cash on delivery

public function createOrder(\Bitrix\Sale\Shipment $shipment): string
{
    $order = $shipment->getOrder();
    $props = $order->getPropertyCollection();

    $payload = [
        'external_id'   => 'bitrix_' . $order->getId(),
        'delivery_type' => $this->getOption('DELIVERY_TYPE', 'pvz'),
        'weight'        => max($shipment->getWeight() / 1000, 0.05),
        'declared'      => round($order->getPrice()),
        'cod'           => $this->getCodAmount($order),
        'sender'        => [
            'name'    => $this->getOption('SENDER_NAME'),
            'phone'   => $this->getOption('SENDER_PHONE'),
            'address' => $this->getOption('SENDER_ADDRESS'),
        ],
        'recipient'     => [
            'name'    => $props->getItemByOrderPropertyCode('FIO')?->getValue(),
            'phone'   => $props->getItemByOrderPropertyCode('PHONE')?->getValue(),
            'city'    => $this->getOrderCity($shipment),
            'pvz_id'  => $props->getItemByOrderPropertyCode('EUROPOCHTA_PVZ')?->getValue(),
        ],
        'items'         => $this->buildItems($shipment),
    ];

    $response = $this->apiPost('/order/create', $payload);
    return (string)($response['order_id'] ?? '');
}

The cod field is the cash-on-delivery amount. If the order is prepaid, we pass 0. If cash on delivery, we pass the full order amount. We automatically determine cod by payment method, eliminating manual errors.

API error handling and data validation

Robust error handling is critical during integration. The Europochta API can return error codes: 401 (invalid credentials), 400 (invalid request format), 404 (city not found in directory), 500 (server-side error). Each case requires a different strategy: for 401, check API keys in configuration; for 400, validate address and weight data; for 404, suggest the user select an alternative city or delivery district; for 500, retry the request after 10-30 seconds with exponential backoff. All errors should be logged with full request parameter information for debugging. We use Bitrix's built-in logging system and send critical errors as notifications to managers.

Why is it important to implement cash on delivery correctly?

Incorrect cod transmission leads to disputes with buyers and loss of money. Automation by payment method ensures the amount is collected correctly.

How we speed up the delivery service?

For caching the pickup point list, we use Bitrix\Main\Data\Cache with a TTL of 12 hours. An agent checks order statuses every 3-4 hours, as Europochta does not provide webhooks. Our component is optimized so that the checkout page does not slow down even under high loads.

Testing the integration and troubleshooting

Before going into production, test all scenarios: delivery cost calculation for different weights (including the boundary case of 0.05 kg), order creation with different payment methods, status synchronization for delivered and returned parcels. It is recommended to first work with the Europochta sandbox environment (if available), then move to production with low traffic. Regularly check the agent logs in the Bitrix admin panel to identify API failures or incorrect address data. Common errors: incorrect phone format (use international format +375...), city not in Europochta directory, exceeding API rate limit (usually 100 requests per minute — add throttling at the component level).

Security and best practices

API keys and credentials for Europochta should never be stored in code — use environment variables or a secure parameter storage in Bitrix (.env file or local.php option). All requests to the Europochta API must go over HTTPS with SSL certificate verification. When logging, never save the full API key or sensitive user data (passport data, full addresses) in logs — log only order IDs and states. Restrict access to the component admin panel to trusted managers using Bitrix user permissions. It is recommended to regularly rotate API keys (every 90 days) and check access logs for unusual activity.

What's included in the work

• Setting up the delivery service in Bitrix with cost calculation via API
• Automatic order creation upon checkout
• Display pickup point list with caching (dropdown list or map)
• Automatic tracking and status updates (agent with configurable interval)
• Support for cash on delivery with automatic cod determination
• Component source code and operation documentation
• Manager training on working with new statuses

Timeline

Contact us for a consultation on setup. Order a turnkey integration — get a ready-made solution in 3-7 days. We will calculate the cost of your project for free.

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.