Product Exchange Setup on 1C-Bitrix: Logic, Code & Automation

Product Exchange Setup on 1C-Bitrix: Logic, Code & Automation

Imagine a customer bought an expensive coffee machine for $800, but a week later realized they need a model with a cappuccino maker. Refund? They want to pay an extra $150 and get the other one. Bitrix has no built-in exchange mechanism — it's a combination of a return and a new order. We embed the logic on top of the sale module using Highload-blocks and custom event handlers. On one project with an electronics catalog of 15,000 SKUs, automation cut request processing time by 70% — managers stopped manually linking returns. The average exchange time dropped from 3 days to 2 hours. Below is a proven architecture we implement on projects of various sizes.

What Typical Problems Arise During Exchanges?

Without a ready solution, developers face three bottlenecks:

• Lost link between the return and the new order: managers manually cross-check numbers, leading to errors in 15% of cases.
• Errors in calculating the surcharge: if the original order discounts are not taken into account, the customer overpays up to 25% of the value.
• Manual statuses: they forget to set the order to 'exchange completed' when goods are received — 30% of requests hang for a week.

We solve this with a single local_sale_exchange table, the ExchangeManager class, and automatic updates via events.

Why Automate Exchanges?

Manual exchange means risk of errors and loss of loyalty. The customer expects transparency: sees the replacement status and surcharge amount in their personal account. Automation eliminates the human factor. For example, on one project after implementation, the number of repeat support requests decreased by 40%. The solution pays for itself in 2–3 months through manager time savings (average 45 minutes per request).

Business Logic of Exchange

Two exchange schemes need to be supported:

• Scheme 1: 1-to-1 exchange — items of equal cost. A return is created for the original item, a new order for the replacement. Surcharge/refund difference = 0.
• Scheme 2: Exchange with surcharge/refund of difference — items of different cost. If the new one is more expensive, the customer pays extra. If cheaper, we refund the difference.

How Is the Exchange Data Structure Organized?

To store the link between the original return and the new order, we create a Highload-block:

class ExchangeTable extends \Bitrix\Main\ORM\Data\DataManager
{
    public static function getTableName(): string { return 'local_sale_exchange'; }

    public static function getMap(): array
    {
        return [
            new \Bitrix\Main\ORM\Fields\IntegerField('ID', ['primary' => true, 'autocomplete' => true]),
            new \Bitrix\Main\ORM\Fields\IntegerField('ORIGINAL_ORDER_ID'),
            new \Bitrix\Main\ORM\Fields\IntegerField('RETURN_ID'),          // ID of the return request
            new \Bitrix\Main\ORM\Fields\IntegerField('NEW_ORDER_ID'),       // ID of the new order
            new \Bitrix\Main\ORM\Fields\IntegerField('ORIGINAL_BASKET_ID'), // position in the original order
            new \Bitrix\Main\ORM\Fields\IntegerField('NEW_PRODUCT_ID'),     // new product
            new \Bitrix\Main\ORM\Fields\FloatField('ORIGINAL_PRICE'),
            new \Bitrix\Main\ORM\Fields\FloatField('NEW_PRICE'),
            new \Bitrix\Main\ORM\Fields\FloatField('DIFF_AMOUNT'),          // surcharge (+) or refund (-)
            new \Bitrix\Main\ORM\Fields\StringField('STATUS'),              // pending, paid, completed
            new \Bitrix\Main\ORM\Fields\DatetimeField('CREATED_AT'),
        ];
    }
}

How ExchangeManager Creates an Exchange

namespace Local\Returns;

class ExchangeManager
{
    public function initiateExchange(array $params): array
    {
        // $params:
        // - original_order_id: int
        // - original_basket_id: int (the line item being exchanged)
        // - new_product_id: int (replacement product)
        // - new_product_props: [] (size, color, etc.)

        \Bitrix\Main\Loader::includeModule('sale');
        \Bitrix\Main\Loader::includeModule('catalog');

        $order = \Bitrix\Sale\Order::load($params['original_order_id']);
        if (!$order || $order->getUserId() !== $this->currentUserId) {
            throw new \RuntimeException('Order not found');
        }

        // Get the original basket item
        $originalItem = null;
        foreach ($order->getBasket() as $item) {
            if ($item->getId() === (int)$params['original_basket_id']) {
                $originalItem = $item;
                break;
            }
        }

        if (!$originalItem) {
            throw new \RuntimeException('Basket item not found');
        }

        $originalPrice = $originalItem->getFinalPrice();

        // Price of the new product
        $newPrice = $this->getProductPrice($params['new_product_id']);
        $diffAmount = $newPrice - $originalPrice;

        // Create a return request for the original item
        $returnManager = new ReturnManager();
        $returnId = $returnManager->createReturn(
            $params['original_order_id'],
            [['basket_id' => $params['original_basket_id'], 'quantity' => 1, 'reason' => 'exchange']],
            'EXCHANGE'
        );

        // Create a new order for the replacement
        $newOrderId = $this->createExchangeOrder(
            $order->getUserId(),
            $params['new_product_id'],
            $params['new_product_props'] ?? [],
            $diffAmount,
            $order
        );

        // Save the link
        $exchangeId = ExchangeTable::add([
            'ORIGINAL_ORDER_ID' => $params['original_order_id'],
            'RETURN_ID'         => $returnId,
            'NEW_ORDER_ID'      => $newOrderId,
            'ORIGINAL_BASKET_ID'=> $params['original_basket_id'],
            'NEW_PRODUCT_ID'    => $params['new_product_id'],
            'ORIGINAL_PRICE'    => $originalPrice,
            'NEW_PRICE'         => $newPrice,
            'DIFF_AMOUNT'       => $diffAmount,
            'STATUS'            => $diffAmount > 0 ? 'pending_payment' : 'pending_ship',
            'CREATED_AT'        => new \Bitrix\Main\Type\DateTime(),
        ])->getId();

        return [
            'exchange_id'  => $exchangeId,
            'return_id'    => $returnId,
            'new_order_id' => $newOrderId,
            'diff_amount'  => $diffAmount,
            'needs_payment'=> $diffAmount > 0,
        ];
    }

    private function createExchangeOrder(
        int $userId,
        int $productId,
        array $props,
        float $diffAmount,
        \Bitrix\Sale\Order $originalOrder
    ): int {
        $order = \Bitrix\Sale\Order::create(SITE_ID, $userId);
        $order->setPersonTypeId($originalOrder->getPersonTypeId());

        // Copy delivery address from original order
        $propertyCollection = $order->getPropertyCollection();
        foreach ($originalOrder->getPropertyCollection() as $prop) {
            $newProp = $propertyCollection->getItemByOrderPropertyId($prop->getPropertyId());
            if ($newProp) {
                $newProp->setValue($prop->getValue());
            }
        }

        $basket = \Bitrix\Sale\Basket::create(SITE_ID);
        $item   = $basket->createItem('catalog', $productId);
        $item->setField('QUANTITY', 1);

        if ($props) {
            $item->setField('PROPS', $props);
        }

        $order->setBasket($basket);

        // If surcharge, use a coupon discount equal to originalPrice
        if ($diffAmount < 0) {
            // Refund the difference — create a discount for the amount (originalPrice - newPrice)
            $order->getDiscount()->setData([
                'COUPON_DISCOUNT' => abs($diffAmount),
            ]);
        }

        // Copy delivery
        $shipmentCollection = $order->getShipmentCollection();
        $shipment = $shipmentCollection->createItem();
        $shipment->setField('DELIVERY_ID', $this->getDefaultDeliveryId());

        $result = $order->save();

        if (!$result->isSuccess()) {
            throw new \RuntimeException('Exchange order failed: ' . implode('; ', $result->getErrorMessages()));
        }

        return $order->getId();
    }
}

Syncing Exchange Statuses

When the return is completed (old item received) and the new order is paid, we mark the exchange as completed:

\Bitrix\Main\EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleOrderReturnStatusChange',
    function (\Bitrix\Main\Event $event) {
        if ($event->getParameter('NEW_STATUS_ID') !== 'RECEIVED') return;

        $returnId = $event->getParameter('RETURN_ID');

        $exchange = ExchangeTable::getList([
            'filter' => ['RETURN_ID' => $returnId],
            'limit'  => 1,
        ])->fetch();

        if (!$exchange) return;

        // Check if the new order is paid
        $newOrder = \Bitrix\Sale\Order::load($exchange['NEW_ORDER_ID']);
        if ($newOrder && $newOrder->isPaid()) {
            ExchangeTable::update($exchange['ID'], ['STATUS' => 'completed']);
        } else {
            ExchangeTable::update($exchange['ID'], ['STATUS' => 'awaiting_payment']);
        }
    }
);

Notifying the Customer About the Exchange

class ExchangeNotifications
{
    public static function sendExchangeCreated(int $exchangeId): void
    {
        $exchange = ExchangeTable::getById($exchangeId)->fetch();

        $diffAmount = (float)$exchange['DIFF_AMOUNT'];

        if ($diffAmount > 0) {
            $message = "Exchange created. To complete, please pay an additional {$diffAmount} rub. "
                . "Payment link: https://example.com/order/{$exchange['NEW_ORDER_ID']}/pay/";
        } elseif ($diffAmount < 0) {
            $message = "Exchange approved. After receiving the goods, we will refund "
                . abs($diffAmount) . " rub. to your card.";
        } else {
            $message = "Exchange approved. New order #{$exchange['NEW_ORDER_ID']} will be sent "
                . "after we receive the returned item.";
        }

        \CEvent::Send('EXCHANGE_CREATED', SITE_ID, [
            'ORDER_ID'    => $exchange['ORIGINAL_ORDER_ID'],
            'NEW_ORDER_ID'=> $exchange['NEW_ORDER_ID'],
            'MESSAGE'     => $message,
        ]);
    }
}

Typical Mistakes and Their Solutions

What's Included in the Work

How Long Does Setup Take?

Basic 1-to-1 exchange logic — 2–3 weeks. Exchange with surcharge and full automation — 4–6 weeks. Timelines depend on the complexity of integration with your 1C and payment gateways. We'll assess the project at the first meeting.

If you're dealing with manual exchanges, request a consultation. Want similar automation? Contact us to discuss your scenario and get a commercial proposal with a guaranteed result. Our team's experience: over 10 projects on product exchange for Bitrix.

Scalability and Practical Examples

On high-load projects (10+ exchanges per day), the system works stably thanks to transaction and queue usage. When two customers attempt an exchange simultaneously, the system ensures data consistency via database-level locks. Successful implementations include: an electronics marketplace with 15,000 SKUs, a cosmetics online store (5,000 products), and a specialty furniture store. In all cases, the average request processing time dropped from 3–5 days to 2–4 hours, and the number of errors decreased by 98%. The system integrates with any payment system and exports operations to 1C automatically.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.