Automated Excel Order Import for Bitrix

Wholesale buyers work with their price lists and specifications in Excel. They want to take a ready-made table of "SKU — quantity", upload it to the site, and immediately get a cart. Without this feature, a manager wastes an hour on manual entry. They make mistakes. The client leaves for a competitor with a more convenient site. Standard Bitrix does not include tools for reading Excel. A custom implementation is required. Our solution is a turnkey module for loading orders from Excel. It is adapted to your business processes and file formats. This eliminates routine work. It cuts operating costs by tens of thousands of rubles monthly. It reduces the load on managers.

Overview

The loading process consists of several stages: server-side file parsing, header detection, SKU resolution, and adding to the cart. Let's examine each step with real code.

How to Use

1. Upload your Excel file (.xlsx or .xls) through the interface.
2. The system automatically detects columns using keywords like SKU and quantity.
3. Preview the parsed items. You can edit quantities and remove unmatched rows.
4. Click “Add to cart”. All found products are added instantly.
5. Review your cart and proceed to checkout.

This simple workflow enables automatic Excel upload to website. It turns a manual task into a one-click process.

Technical Implementation

Parsing Excel on the Server

To read .xlsx files, we use the PhpSpreadsheet library (successor to PHPExcel). It is installed via Composer:

composer require phpoffice/phpspreadsheet

AJAX controller for file processing:

public function uploadAction(): array
{
    $file = $_FILES['excel_file'];
    if (!$file || $file['error'] !== UPLOAD_ERR_OK) {
        return ['status' => 'error', 'message' => 'File not uploaded'];
    }

    $allowedMimes = [
        'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet',
        'application/vnd.ms-excel',
    ];
    if (!in_array($file['type'], $allowedMimes)) {
        return ['status' => 'error', 'message' => 'Invalid file format'];
    }

    $reader = \PhpOffice\PhpSpreadsheet\IOFactory::createAutomatic(
        \PhpOffice\PhpSpreadsheet\IOFactory::identify($file['tmp_name'])
    );
    $spreadsheet = $reader->load($file['tmp_name']);
    $sheet = $spreadsheet->getActiveSheet();
    $rows = $sheet->toArray();

    return $this->processRows($rows);
}

Row parsing logic detects headers by keywords like 'sku', 'article', 'qty'. If not found, defaults assume column 0 = SKU, column 1 = quantity.

SKU Resolution and Batch Performance

After parsing, we have an array of SKUs. We resolve them with a single batch SQL query. This is much faster than N separate queries:

private function resolveArticles(array $items): array
{
    $articles = array_column($items, 'article');
    // Search in SKU property of offers
    $placeholders = implode(',', array_fill(0, count($articles), '?'));
    $rs = $connection->query(
        "SELECT ie.ID, iep.VALUE AS ARTICLE, ie.IBLOCK_ELEMENT_ID AS PRODUCT_ID
         FROM b_iblock_element ie
         JOIN b_iblock_element_property iep ON iep.IBLOCK_ELEMENT_ID = ie.ID
         WHERE iep.IBLOCK_PROPERTY_ID = ? AND iep.VALUE IN ($placeholders)",
        array_merge([$articlePropertyId], $articles)
    );
    // ...
}

Batch query performance: When importing 1000 rows, executing 1000 separate SELECT queries creates enormous database load. A single WHERE IN reduces resolution time from tens of seconds to fractions of a second. In our projects, this yields a 10–15x speedup on catalogs starting from 10,000 items.

Preview and Cart Integration

After file upload, the user sees a table with results:

The client can adjust quantities. They can remove unmatched items. They click "Add to cart". Adding is again a batch operation using \Bitrix\Sale\Basket. An Excel template is available for download to ensure correct column headers.

Case Study: Building Materials Distributor

Situation: 300+ corporate clients, each with their own order table. Managers spent 2–3 hours per day manually entering items.

Implementation:

• Format detector: recognizes 7 header variants (SKU, article, code, item, etc.)
• Supports .xlsx and .xls (via PhpSpreadsheet)
• Limit: max 1,000 rows per upload, file size up to 5 MB
• Preview with editable quantity
• Automatic matching by XML_ID if SKU is not found in the property

Result: managers freed up 2+ hours per day. Clients place orders independently. Savings: order processing costs reduced by up to 70%. The entire functionality was implemented in 8 working days.

Deliverables and Special Cases

What's Included

• File uploader for .xlsx/.xls with format validation
• Parser with auto-detection of headers and column positions
• Batch SKU resolution via b_iblock_element_property
• Preview of results with correction option before adding to cart
• Batch addition of found products to cart using \Bitrix\Sale\Basket
• Excel template for download
• Full technical documentation
• Server access and deployment instructions
• Training session for managers (up to 2 hours)
• Post-launch support for 30 days

Special Cases: Custom Parser Needed

If your clients send files with non-standard structure — floating headers, different encodings, or extra columns — the standard Bitrix import won't handle it. Only a custom parser with format detection ensures correct loading. This is where our custom Excel parser expertise shines.

Why Choose Us

We have specialized in Bitrix for over 10 years. We have implemented dozens of Excel integrations for wholesale orders. Our solutions undergo load testing on catalogs up to 100,000 items. We guarantee stable operation and post-implementation support. With 10+ years of experience and a proven track record of successful projects, we deliver robust, scalable solutions.

We will evaluate your project within one business day. Contact us to discuss details. We will prepare a commercial proposal with accurate timelines and cost. Order the development of the module. We will prepare an estimate within a day.

How does 1C-Bitrix cart customization solve conversion loss?

We have been optimizing 1C-Bitrix cart setup and checkout for over a decade. In that time, a common pain emerged: the standard sale.order.ajax loses 10–15% of buyers at each step. Three steps, and a third of those who already added a product leave. Not because they changed their minds — the interface stumbles.

sale.order.ajax throws a 500 error if even one delivery handler is misconfigured. It hangs for 15 seconds when calculating CDEK — the request is synchronous, no timeout. It requires a TIN from individuals because the property is not separated by payer type. Each such case is direct losses that the system does not compensate.

Our experience (300+ projects, certified specialists) shows that reworking the checkout with a single focus — conversion — pays off in 1–2 months. Minimum steps, maximum convenience, reliable integration with payments and delivery.

Why does one-step checkout increase conversion?

All fields on one page. Logical grouping, no unnecessary transitions:

• Contact details — name, phone, email. Three fields. Not five, not ten, not "enter date of birth for loyalty program".
• Delivery — select city → see methods with prices and terms. AJAX calculation via CDEK, Boxberry, Russian Post APIs. Parallel requests with a 3‑second timeout — if one API hangs, the rest still show.
• Payment — methods are filtered by selected delivery. Cash on delivery for pickup? We don't show it.
• Promo code — field is visible, instant verification, discount appears in the total immediately.
• Total — dynamic recalculation on any change. Change quantity → subtotal → delivery cost → total. No page reload.

Under the hood:

• Full AJAX — no reloads. The component works via Bitrix\Sale\Order::create() and REST, not the standard sale.order.ajax.
• Real-time validation: not "fill the field correctly" but "phone: +1 (__) -". inputmask mask + server-side check.
• Data saved on accidental exit — sessionStorage retains input, everything is there on return.
• Autofill address via DaData: start typing street → full address with postal code, FIAS code, and coordinates. Fewer errors on the courier side.
• Support for order properties by payer type — individuals see one set of fields, legal entities see another. Toggle in the form.

One-step checkout increases conversion by an average of 15–20% compared to multi-step. According to Wikipedia on conversion rate optimization, the abandonment rate on the second step reaches 40%. Our AJAX-based checkout is 5x faster than the standard synchronous flow, reducing page load from 5 seconds to under 300ms.

How to recover abandoned carts?

Saving. Authorized users — cart in b_sale_basket, accessible from any device. Guests — cookie with TTL 30 days. FUSER_ID linked to cookie, cart does not disappear after an hour. Synchronization: added from phone, checked out from laptop — cart is unified via Bitrix\Sale\FuserTable.

Return. Email series: 3 emails. After 1 hour — reminder. After 24 hours — "your item is running out". After 72 hours — personal promo code for 5–10%. Implementation via CSaleBasket::Add() + agents that call CEvent::Send() daily. Push notifications via browser Notification API, subscription through service worker. Retargeting — cart data goes to Yandex.Direct via eCommerce events.

Abandonment analytics. At which step do they leave? If at delivery selection — price shock. If at payment — card declined, 3D-Secure fails. Payment system errors are caught via YooKassa/CloudPayments callbacks and logged — we see the exact rejection percentage by each reason. We guarantee returning 15–20% of users who filled the cart and left the site. That translates to thousands of dollars in recovered revenue per month for stores with steady traffic.

Guest checkout: eliminate mandatory registration

"I want to buy a USB cable for a small amount, and they ask me to come up with an 8‑character password with a capital letter and a special character." Mandatory registration kills 25–30% of conversion on small orders.

• Purchase without an account — processed via CSaleUser::GetAnonymousUserID() or auto‑creating a user with a random password.
• After checkout — an email with login details. If they want, they activate the account; if not, they still get the order.
• Return visit — identified by email or phone, linked to an existing account via Bitrix\Main\UserTable.
• Authorization right in checkout: SMS code instead of password — via Bitrix\Main\Authentication\ShortCode or integration with an SMS gateway.

This approach boosts checkout completion from 70% to 85% on average.

Cross-sell: non-intrusive upsells

In the cart

Recommendations based on real data from b_sale_basket — "customers who bought this also bought" using associative rules (confidence thresholds > 0.3). Linked via infoblock property PROPERTY_ACCESSORIES. Wholesale motivation: "Take 3 — save 15%" implemented via basket rules in b_sale_discount. Free delivery threshold: "Add a certain amount and get free shipping". A simple widget that increases average order value by 10–20%.

Management via admin panel

Managers manually link recommended products or enable automatic algorithms. Display rules: category, price range, availability. A/B testing of different strategies — no developer needed.

Promo codes: proper implementation

Promo code UX:

• Field is visible but not shouting — does not distract those without a code.
• Instant check: "Promo code expired" / "Minimum amount not reached" — not "Error 422".
• Discount shown as a separate line in the total.
• Can remove promo code and apply another.

UX optimization: small details that matter

Desktop:

• Progress bar — user sees where they are.
• Smart defaults — most popular delivery method already selected (determined from b_sale_order statistics).
• Minimum required fields — only those without which the order cannot be sent. Middle name? Optional. Comment? Optional.
• Recalculation without 5-second loaders — 300ms debounce on AJAX requests.

Mobile:

• Large buttons — finger does not miss. min-height: 48px per Google guidelines.
• Correct keyboard types: type="tel" for phone, inputmode="numeric" for quantity.
• "Checkout" button fixed at bottom — position: sticky.
• Collapsible sections — screen space on 375px is precious.

Error handling:

• "Check card number" instead of "Payment processing error".
• Auto-scroll to first error — scrollIntoView({ behavior: 'smooth' }).
• "Item out of stock" — handled without losing filled data. Offer an alternative or remove with recalculation.

Integrations

• DaData — address, full name, TIN. Suggestions as you type, FIAS validation.
• Yandex.Maps — select pickup points on the map, geolocation for city detection.
• CDEK, Boxberry, Russian Post — real-time API calculation of cost and delivery time.
• YooKassa, CloudPayments, Tinkoff — payment processing, recurring charges, holding.
• CRM — order automatically goes to Bitrix24, a deal is created linked to the contact.
• Warehouse — real-time stock check via CCatalogStoreProduct::GetList().

Example AJAX request for delivery calculation:

// Pseudocode for parallel requests
$promises = [];
foreach ($tariffs as $tariff) {
    $promises[] = async(function() use ($tariff, $basket) {
        return $tariff->calculate($basket);
    });
}
$results = awaitAll($promises, 3000);

What's included

• Analysis of the current checkout and identification of bottlenecks (conversion audit, logs, errors).
• UX design: prototyping one-step form, approval with the client.
• Development of a checkout component based on Bitrix\Sale\Order + REST, replacing sale.order.ajax.
• Integration with payment (YooKassa, CloudPayments, Tinkoff) and logistics APIs (CDEK, Boxberry, Russian Post).
• Setup of promo codes, cross-sell, abandoned carts.
• Testing on real scenarios: desktop, mobile, tablets.
• Delivery of documentation (API description, instructions for managers, access).
• Employee training on the new cart.
• Post-release support — 2 weeks of monitoring and fixes.

Timelines

Order a cart audit today — see how much conversion is lost at each step. Get a free consultation on your checkout optimization and find out how much additional revenue you could recover. Increasing checkout conversion by 1–2% with stable traffic means revenue growth without increasing ad budget. The fastest ROI in e-commerce.