Cross-Docking on Bitrix: Automating Transit Logistics
When an e‑commerce store operates on a drop‑shipping model, every order demands instant transmission to the supplier?
Without automation, operators manually create orders, verify statuses, and control shipments. On a standard Bitrix, such a process becomes a bottleneck: the system knows nothing about suppliers, doesn't create counter‑orders, and doesn't track the transit warehouse. The result: delays, errors, and lost customers. We solve this problem with custom statuses, events, and integrations. Our specialists have been working with Bitrix for 5+ years and have implemented over 50 cross‑docking projects.
What problems we solve
The first problem is the lack of a unified status model. Standard statuses (NEW, PAID, ALLOW_DELIVERY) do not reflect the stages of working with a supplier. The second problem is manual creation of supplier orders. With 200 orders per day, an operator spends up to 4 hours on data entry. The third problem is loss of control over the transit warehouse: goods arrive but the system does not initiate shipment to the customer. We eliminate these issues with custom statuses, automation, and integrations.
How cross‑docking works in an online store on Bitrix
The scheme is simple: a customer places an order, the system automatically creates a supplier order, the supplier sends the goods to a transit warehouse, from where they are immediately shipped to the customer. In Bitrix, this uses a custom status chain:
-
CROSS_WAITING— awaiting supplier (ID: CW) -
CROSS_IN_TRANSIT— goods in transit (ID: CI) -
CROSS_ARRIVED— arrived at transit warehouse (ID: CA) -
CROSS_SHIPPED— shipped to customer (ID: CS)
The difference from a regular order lies in the intermediate waiting and transit statuses. This provides transparency and control.
Why standard Bitrix statuses are not suitable
Bitrix provides predefined statuses (N, P, F, D), which do not include "awaiting supplier" or "in transit". Using standard statuses, you cannot distinguish an order waiting for a supplier from a paid one. We create custom statuses via \Bitrix\Sale\OrderStatus::add() and link them to events.
Table of custom statuses
| Status | ID | Description | Used in cross‑docking |
|---|---|---|---|
| NEW | N | New order | No |
| CROSS_WAITING | CW | Awaiting supplier | Yes |
| CROSS_IN_TRANSIT | CI | Goods in transit from supplier | Yes |
| CROSS_ARRIVED | CA | Arrived at transit warehouse | Yes |
| CROSS_SHIPPED | CS | Shipped to customer | Yes |
| ALLOW_DELIVERY | D | Delivery allowed | No (replaced by CS) |
How to automatically create a supplier order?
When the order transitions to status CW, the OnSaleStatusOrder event fires. We add a handler that loads the order and, for each item, determines the supplier via a custom class SupplierCatalog. Then SupplierOrderService creates a supplier order via API or EDI. Example code:
AddEventHandler('sale', 'OnSaleStatusOrder', function($orderId, $newStatus) { if ($newStatus === 'CW') { $order = \Bitrix\Sale\Order::load($orderId); $basket = $order->getBasket(); foreach ($basket as $item) { $productId = $item->getProductId(); $supplier = SupplierCatalog::getSupplierByProduct($productId); if ($supplier) { SupplierOrderService::create($supplier, [ 'PRODUCT_ID' => $productId, 'QUANTITY' => $item->getQuantity(), 'ORDER_REF' => $orderId, ]); } } } }); Bitrix documentation on the OnSaleStatusOrder event
Additional: monitoring the transit warehouse
For transit storage, create a separate warehouse in b_catalog_store with type "Transit". Receipt from the supplier is registered via \Bitrix\Catalog\StoreDocumentTable with type A (arrival). After increasing the stock at the transit warehouse, an agent immediately creates a shipment to the customer.
What is included in the setup
Our engineers carry out the work in stages:
| Stage | Details |
|---|---|
| Analysis | Define cross‑docking scheme, supplier list, integration types |
| Design | Design status model, product‑supplier mapping tables |
| Development | Custom statuses, event handlers, supplier integration (API/EDI) |
| Testing | Verify order chains, error handling, load testing |
| Launch | Configure transit warehouse, train operators, documentation |
Timeline: from 5 to 15 business days, depending on the number of suppliers and integration complexity. Cost is calculated individually.
How to choose the supplier integration method?
For cross‑docking, data exchange speed is critical. Best options:
- API — direct order transmission in JSON/XML. Requires the supplier to provide an API.
- EDI — electronic document exchange (order, confirmation, invoice). Suitable for large suppliers.
- Email — sending PDF order via email. Simple but unreliable: delays possible.
For stores with 2‑3 suppliers, API is enough. For 10 or more suppliers, it is better to implement an EDI gateway.
Typical mistakes during setup
- Agent for processing arrivals not configured — order hangs in "Arrived" status.
- No mechanism to cancel supplier order — if the customer changes their mind, the order is already created.
- Supplier stock not considered — order may be accepted when goods are unavailable.
- Incorrect handling of partial shipments — if the supplier ships in parts.
These problems are solved at the design stage. Our team has experience integrating with dozens of suppliers via various protocols. Get a consultation for your project — we will assess the complexity and propose the optimal solution. Savings on warehouse costs reach up to 40%, and order processing time is reduced by 60%.