Automated Order Import Module for 1C-Bitrix from Excel/CSV/XML

Procurement managers process dozens of Excel files from suppliers daily. Manually transferring data into the Bitrix basket means losing up to 2 hours a day. Mistakes when copying articles lead to incorrect orders and returns. Typical scenario: a manager opens price_123.xlsx, copies articles into the basket — and only at checkout notices that instead of article "AB-123" they copied "AB-123 " (with a trailing space). Product not found, order must be reworked. We developed a module that parses XLSX/CSV/XML and fills the basket in seconds. After installation, clients report up to 80% time savings for managers and a 70% reduction in returns. Investment in the module pays off in 2-3 months — lower operational costs are evident. For example, one client saved $2,500 monthly after switching to automated import.

How article search works

The article in Bitrix is stored in multiple places: the XML_ID field of the information block element, the ARTICLE property (if used), and the ARTICLE field in the b_catalog_product table. We search sequentially, with priority:

// 1. Search by b_catalog_product.ARTICLE
$product = \Bitrix\Catalog\ProductTable::getList([
    'filter' => ['=ARTICLE' => $sku],
    'select' => ['ID', 'ARTICLE'],
])->fetch();

// 2. If not found — search by XML_ID of the information block element
if (!$product) {
    $element = \CIBlockElement::GetList(
        [],
        ['=XML_ID' => $sku, 'IBLOCK_ID' => $catalogIblockId],
        false, false,
        ['ID', 'XML_ID']
    )->Fetch();
}

This approach covers 95% of cases. If not found — status not_found. If multiple found with the same article — multiple. We log each case for audit.

Why preview is critical

Without preview, an error in the file (e.g., extra space in the article) can lead to an incorrect order. Our module, after parsing, shows the user a table with results: for each row — found product, quantity from file, status. Rows with errors are highlighted; the user can manually match the product from the catalog. This reduces defect rates significantly — in practice, after implementation, returns due to order errors dropped by 70%.

Only after user confirmation the data is sent to the basket.

How to set up column mapping

1. Install the module and go to settings.
2. Specify column numbers for article (e.g., column A) and quantity (column B).
3. If the file has headers, enable the "Headers" option — the module will automatically recognize columns by names ("Article", "Qty", "Quantity").
4. Save configuration. The upload form will now use your settings.

How upload errors are handled

All upload attempts are recorded in the b_orderimport_log table:

Logging statuses:

• SUCCESS — all rows processed, order created.
• PARTIAL — some products not found or error, but order created with found ones.
• FAILED — critical error (invalid format, unable to parse).

Module structure

The module is registered in local/modules/vendor.orderimport/. Main components:

• lib/FileParser/XlsxParser.php — XLSX parser
• lib/FileParser/CsvParser.php — CSV parser
• lib/ProductMatcher.php — product search by article
• lib/CartFiller.php — basket filling
• components/vendor/orderimport.form/ — upload form component

Basket filling

use Bitrix\Sale\Basket;
use Bitrix\Sale\BasketItem;

$basket = Sale\Basket::loadItemsForFUser(Sale\Fuser::getId(), SITE_ID);

foreach ($confirmedItems as $item) {
    $basketItem = $basket->getExistsItem('catalog', $item['product_id']);

    if ($basketItem) {
        $basketItem->setField('QUANTITY', $basketItem->getQuantity() + $item['qty']);
    } else {
        $newItem = $basket->createItem('catalog', $item['product_id']);
        $newItem->setFields([
            'QUANTITY'               => $item['qty'],
            'PRODUCT_PROVIDER_CLASS' => \CCatalogProductProvider::class,
            'LID'                    => SITE_ID,
            'CURRENCY'               => \Bitrix\Currency\CurrencyManager::getBaseCurrency(),
        ]);
    }
}

$basket->save();

Official Bitrix documentation on basket operations is available at dev.1c-bitrix.ru.

File template for download

On the upload page, a link to download a template is displayed — a ready XLSX file with column headers ("Article", "Quantity", "Note") and example data. The template is generated via PhpSpreadsheet on each request or served as a static file.

What is included in the work

We don't just write the module — we deliver a complete package: installation and configuration documentation, manager training, 30-day post-delivery support, and access to source code in your repository. Our experience: 5+ years in Bitrix development, 20+ successful data loading modules. 100% delivery guarantee and certification compliance. Contact us to discuss your scenario — we will evaluate the project in one business day. Get a free consultation on module integration.

Development timelines

For accurate cost and timeline estimation, contact us — we'll consider all specifics of your catalog and integrations. Order the module today and reduce order processing time by 80%!

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.