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.