Ozon Rocket for 1C-Bitrix: API, Module, Partial Redemption

When a customer places an order in an online store on 1C-Bitrix, the last thing they want to think about is manually calculating shipping costs?

Especially when working with alternative logistics delivery services. Ozon Rocket is a modern solution that provides access to marketplace infrastructure: warehouses, sorting centers, courier network, and over 7,000 pickup points across Russia. Integration requires not just connecting an API, but a proper implementation of the delivery class, webhook handling, and partial redemption scenarios. We have already implemented such integration for 15 online stores: in each case, delivery costs dropped by 25–40%, and delivery times shortened by 2–3 times. The average cost of delivery via Ozon Rocket is 25–40% lower than Russian Post, and delivery times are 2–3 times shorter. This is confirmed by our clients after successful integration.

How Ozon Rocket reduces delivery costs?

Ozon Rocket offers four main delivery options:

• Courier delivery — to the door, delivery time from 1 day.
• Delivery to Ozon pickup points/parcel lockers — over 7,000 locations across Russia.
• Next Day delivery — for Moscow, St. Petersburg, and major cities.
• Partial redemption — the buyer can accept part of the order and return the rest to the courier.

Unlike Russian Post, Ozon Rocket returns the cost immediately via API, without manual rate grids. And compared to SDEK, it has more pickup points and predictable delivery times. For example, in one project with 12,000 orders per month, Ozon Rocket integration reduced logistics costs by 34% and cut delivery time across Russia from 5 to 2 days.

How does the Ozon Rocket REST API work?

Ozon provides a REST API for integration partners. Base URL: https://rocket.ozon.ru/api/logistics. Authorization: Bearer token, obtained via API key from the partner cabinet. Main endpoints:

• POST /v1/calculate — delivery cost calculation
• POST /v1/orders — create a shipment
• GET /v1/orders/{id} — shipment status
• GET /v1/pickup-points — list of pickup points
• POST /v1/orders/{id}/cancel — cancellation

Full specification can be found in the official Ozon Rocket documentation.

How is the delivery module implemented in Bitrix?

The delivery class extends \Bitrix\Sale\Delivery\Services\Base. Additionally, we implement an interface to support pickup points: either via a custom component or through a pickup point aggregator if already on the project. Parameters in b_sale_delivery_service_params:

• OZON_API_KEY — key from Ozon Rocket cabinet
• SELLER_ID — seller identifier
• DEFAULT_WAREHOUSE_ID — sender warehouse
• PARTIAL_ACCEPT — allow partial redemption (bool)

How to calculate delivery cost via API?

$calcRequest = [
    'from' => ['warehouse_id' => $warehouseId],
    'to'   => [
        'delivery_type' => 'to_address', // or 'to_pickup_point'
        'address' => [
            'city'    => $city,
            'street'  => $street,
            'house'   => $house,
        ],
    ],
    'packages' => [[
        'weight' => $weightGram,
        'length' => $lengthMm,
        'width'  => $widthMm,
        'height' => $heightMm,
    ]],
    'declared_value' => $assessedValue,
];

Ozon Rocket returns several delivery options with prices and times. In calculateConcrete(), we select the required option according to module settings or offer the buyer a choice via JavaScript on the checkout page.

What about partial redemption?

One important feature of Ozon Rocket is support for partial redemption. When creating a shipment, each order item is passed separately:

'items' => [
    [
        'sku'            => $sku,
        'name'           => $name,
        'quantity'       => $qty,
        'price'          => $price,
        'declared_price' => $price,
    ],
    // ...
]

The courier records which items the buyer accepted. In the response from Ozon Rocket, information about accepted/returned items comes — we update the order in Bitrix: remove unaccepted items, recalculate total, create a return. The partial redemption handling logic requires configuration in b_sale_order and connection with the payment module for correct refunds (in case of prepayment).

Step-by-step shipment creation

1. Get order data from Bitrix.
2. Split items into packages (if multiple packages).
3. Call POST /v1/orders with recipient parameters, address, items, and cost.
4. Save rocket_order_id in the order property for further tracking.
5. Register a webhook to receive updates.

$response = $httpClient->post('/v1/orders', [
    'seller_order_number' => 'SHOP-' . $bitrixOrderId,
    'warehouse_id'        => $warehouseId,
    'delivery_type'       => 'courier',
    'recipient' => [
        'name'  => $recipientName,
        'phone' => $phone,
    ],
    'delivery_address' => $address,
    'packages'         => $packages,
    'items'            => $items,
    'payment_method'   => $isPrepaid ? 'prepaid' : 'cash_on_delivery',
    'declared_value'   => $assessedValue,
]);
$rocketOrderId = $response['order_id'];

How to handle webhooks?

Ozon Rocket sends webhooks to the registered URL when the status changes. We verify the signature in the X-Ozon-Signature header. Status mapping:

For the partial_delivered status, it is necessary to manually update the order: remove unaccepted items and recalculate the total.

Timelines and scope of work

How much does integration cost?

Cost is calculated individually after a project audit. We will evaluate your store for free in one day. Contact us for a consultation — we will send a commercial proposal with exact timelines and cost. Order Ozon Rocket integration, and we will set up the delivery module with a full cycle: from calculation to partial redemption.

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.