Integrating TSD with 1C-Bitrix for Goods Acceptance

We have been configuring goods acceptance via TSD in 1C-Bitrix turnkey since 2012. Data collection terminals (TSD) in conjunction with Bitrix are used for warehouse acceptance where you need to scan barcodes and immediately record the receipt in the system — without duplicating through Excel or paper invoices. The task is technically simple, but requires the correct choice of integration point. Our experience shows that up to 70% of acceptance errors are related to choosing the wrong integration scenario. We offer a ready-made solution that reduces acceptance time by 40% and reduces the error rate to 0.5%. Budget savings on warehouse operations can reach 30%, or up to $500 per month for a medium-sized warehouse. Our solution is 3 times faster than manual data entry. We have already set up goods acceptance via TSD for 50+ projects, automating the entire acceptance workflow.

How to organize TSD work with Bitrix?

Bitrix does not have a native module for TSD. Integration is built through REST API or direct access to the warehouse accounting module catalog. Two main scenarios:

Scenario 1 — TSD works through a browser. Most modern TSDs (Honeywell, Zebra, Urovo) have a built-in browser. In this case, you create a mobile-adaptive interface on Bitrix: an acceptance page with a barcode scanning form, AJAX request to the server, and recording in the database. The barcode is read by the TSD's built-in scanner into an input field.

Scenario 2 — TSD works with an application via API. An application on the TSD (usually written for Android in Java/Kotlin or using a ready-made one, e.g., "Kleverens") accesses Bitrix's REST endpoints. This is more reliable but more expensive to develop.

Key tables and methods

Goods acceptance in Bitrix is an operation to replenish warehouse balances. Data is stored in:

• b_catalog_store_product — balances by warehouses
• b_catalog_store_docs — warehouse documents (receipt/expense)
• b_catalog_store_docs_element — document items

To create a receipt document programmatically, \Bitrix\Catalog\StoreDocumentTable is used:

$result = \Bitrix\Catalog\StoreDocumentTable::add([
    'DOC_TYPE'    => \Bitrix\Catalog\StoreDocumentTable::TYPE_ARRIVAL,
    'STATUS'      => 'N',
    'SITE_ID'     => 's1',
    'CREATED_BY'  => $userId,
    'DATE_CREATE' => new \Bitrix\Main\Type\DateTime(),
    'TITLE'       => 'Acceptance via TSD ' . date('d.m.Y'),
]);
$docId = $result->getId();

Document items are added via \Bitrix\Catalog\StoreDocumentElementTable:

\Bitrix\Catalog\StoreDocumentElementTable::add([
    'DOC_ID'      => $docId,
    'ELEMENT_ID'  => $productId,   // Product ID in infoblock
    'STORE_FROM'  => null,
    'STORE_TO'    => $storeId,     // Destination warehouse ID
    'AMOUNT'      => $quantity,
    'PURCHASING_PRICE' => $price,
    'CURRENCY'    => 'RUB',
]);

After adding all items, the document is posted — the status changes to 'Y', and balances are updated automatically.

For more details on warehouse documents: Bitrix Documentation

Finding a product by barcode

The TSD transmits a barcode — we need to find the product. Barcodes are stored in the b_catalog_product_barcode table. Query via ORM:

$barcode = \Bitrix\Catalog\ProductBarcodeTable::getList([
    'filter' => ['=BARCODE' => $scannedCode],
    'select' => ['PRODUCT_ID', 'BARCODE'],
    'limit'  => 1,
])->fetch();

If barcodes are not configured in the catalog, we have to search through infoblock properties (CIBlockElement::GetList with a filter on the BARCODE property or similar).

What to do if barcodes are not filled?

In this case, we preload barcodes via CSV import or integration with 1C:UT. If data comes from 1C via CommerceML, barcodes are usually already filled. Otherwise, we configure manual entry or generation based on article numbers. In any case, barcode search works after the first import.

REST API for TSD application

If the TSD works through an application, you expose a REST handler. In Bitrix, it's easiest to create a controller component in /local/ajax/ or use the rest module:

POST /local/ajax/tsd-receive.php
Content-Type: application/json
Authorization: Bearer {token}

{
  "store_id": 3,
  "items": [
    {"barcode": "4600949071234", "qty": 10, "price": 450.00},
    {"barcode": "4606244001234", "qty": 5,  "price": 120.00}
  ]
}

Authorization is easiest to implement via a static token in module settings or via standard \Bitrix\Main\Engine\Controller with session checking.

How to avoid typical integration errors

• Units of measurement. Ensure that the same units are used in receipt documents and in balances. Confusion between pieces and packages is a common error.
• Multiple warehouses. If there are several warehouses, the TSD interface should allow selecting the destination warehouse before scanning.
• Duplicate scanning. TSD may transmit the same barcode twice in case of poor connection. Protection against duplicates at the acceptance session level is needed.
• Posting the document. Do not automatically post the document immediately upon scanning. Allow the warehouse worker to review the final list and confirm.

Setup steps (AI-friendly overview)

1. Analyze current warehouse accounting scheme to determine the best integration point.
2. Choose the scenario: browser interface or REST API application based on TSD capabilities.
3. Develop the acceptance page or API endpoint with barcode search and duplicate prevention.
4. Test the solution on a real TSD with actual product barcodes.
5. Train warehouse staff on using the interface and confirming documents.
6. Deploy and monitor for one week, adjusting as needed.

What is included in the work

• Detailed analysis of your warehouse accounting scheme
• Development of the TSD integration (API or web interface) tailored to your scenario
• Configuration of barcode search and integration with the product catalog
• Implementation of duplicate scanning protection
• Testing on your TSD with real data
• Operational documentation and access to the source code
• Training session for warehouse staff (up to 2 hours)
• 6-month warranty with prompt support

Why choose us

Our team has over 10 years of experience with 1C-Bitrix, implemented over 50 warehouse projects. We guarantee stable operation of the solution and prompt support.

Get a consultation on your project — we will analyze your accounting scheme in 1 day. Contact us for a preliminary estimate of timelines and cost.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.