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.