Custom File Upload Form Development for 1C-Bitrix

We have encountered situations: a client attaches a technical specification, product defect photos, or drawings, and the standard bitrix:main.feedback component falls short. No preview, no drag-and-drop, no client-side type validation, no chunked upload for large files. The result is lost leads and broken UX. A custom file upload form for 1C-Bitrix solves these problems. We implement a turnkey solution integrated with b_file and CRM that delivers substantial cost savings through automation.

Problems We Solve

• Timeouts with large files: a single 100 MB file via standard POST can timeout on slow connections. We use chunked upload — split the file into 5 MB parts, upload sequentially with progress indication. Time savings up to 70%, lead loss reduction up to 35%. Chunked upload is three times more reliable than standard POST over unstable connections.
• Lack of client-side validation: inexperienced users try to upload .exe or .dll. On the server we check MIME via finfo, reject disallowed types. On the client, validation by extension. This reduces server load and eliminates security incidents.
• Inability to attach multiple files: a single file field doesn't work for TZ + drawings + photos. We implement multiple upload with a limit of 10 files per session, covering 95% of business scenarios.
• Excessive memory usage: standard POST loads the entire file into PHP memory. Our AJAX approach avoids this — files are uploaded separately, PHP processes only tmp_name.

How Chunked Upload Works

For files over 50 MB, a single POST request is unreliable. Our ChunkedUploader splits the file into parts, uploads them sequentially, and reassembles on the server. Result: upload of files up to 2 GB with a progress bar, no timeouts. Compare: a standard upload of 200 MB can fail with error 413 after 30 seconds; with chunked upload, stable transmission with resumability on failure.

class ChunkedUploader {
    constructor(file, options = {}) {
        this.file      = file;
        this.chunkSize = options.chunkSize || 5 * 1024 * 1024; // 5 MB
        this.onProgress = options.onProgress || (() => {});
        this.uploadId  = null;
    }

    async upload() {
        // Initialize multipart upload
        const initRes = await fetch('/local/api/upload-init.php', {
            method: 'POST',
            body: JSON.stringify({
                filename : this.file.name,
                size     : this.file.size,
                mime     : this.file.type,
                sessid   : BX.bitrix_sessid(),
            }),
            headers: { 'Content-Type': 'application/json' },
        });
        const { upload_id } = await initRes.json();
        this.uploadId = upload_id;

        const totalChunks = Math.ceil(this.file.size / this.chunkSize);

        for (let i = 0; i < totalChunks; i++) {
            const start = i * this.chunkSize;
            const end   = Math.min(start + this.chunkSize, this.file.size);
            const chunk = this.file.slice(start, end);

            const formData = new FormData();
            formData.append('upload_id', this.uploadId);
            formData.append('chunk_index', i);
            formData.append('total_chunks', totalChunks);
            formData.append('chunk', chunk);

            await fetch('/local/api/upload-chunk.php', {
                method: 'POST',
                body: formData,
            });

            this.onProgress(Math.round((i + 1) / totalChunks * 100));
        }

        // Finalize
        const finalRes = await fetch('/local/api/upload-finalize.php', {
            method: 'POST',
            body: JSON.stringify({ upload_id: this.uploadId }),
            headers: { 'Content-Type': 'application/json' },
        });

        return finalRes.json(); // { file_id, name, size, ... }
    }
}

Why MIME Type Validation is Critical

Uploading executable files can lead to server injections. We verify MIME type via the finfo library, not just extension. This protects against double extension attacks (e.g., .jpg.exe). Pairing with ClamAV provides antivirus scanning on every file without adding more than 1.5 seconds of processing time. This reduces operational costs by up to 40% through automated checks.

How the Upload Architecture Works

For file-carrying forms we use a two-stage process:

1. The file is uploaded via a separate AJAX request before the form is submitted. A temporary file_id is returned.
2. On final form submission, only the file_id references are passed, not the actual files.

This avoids timeouts with large files and allows independent progress indicators for each file. According to 1C-Bitrix documentation, CFile::SaveFile() returns the uploaded file ID and saves it in the b_file table.

What’s Included in Upload Form Development

• Component local:file.upload with drag-and-drop zone and image preview
• Server-side upload handler: type validation via finfo, CSRF, rate limiting
• Persistence via CFile::SaveFile() into b_file table
• Chunked upload for files > 10 MB (optional)
• User field UF_ATTACHMENTS (FILE, MULTIPLE) in CRM
• Attaching uploaded files to the created lead
• Notification to manager with direct links to attachments
• Operational documentation, access transfer, permission setup

Process of Evaluation and Work

1. Analysis: understand the scenario — which files, where they are attached, is CRM integration needed.
2. Design: choose storage method (user field, activity), define limits.
3. Implementation: write component, server handlers, API endpoints.
4. Testing: verify upload of different types, sizes, security.
5. Deployment and training: deploy to production, train managers.

Timelines (approximate)

Basic form with single attachment: 3–5 days. Full version with drag-and-drop, preview, chunked upload, and CRM integration: 2–3 weeks. Cost is calculated individually — we will assess your project after a brief. Request a consultation and we will prepare a quote tailored to your budget.

Why Choose Us?

• 10+ years of experience with 1C-Bitrix and Bitrix24.
• 50+ projects completed involving custom forms and integrations.
• Every module undergoes code review and load testing.
• Certified specialists in Bitrix and Bitrix24.

Contact us for a no-obligation consultation. Order an individual cost estimate.

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.