Automating Goods Receiving in Bitrix: Documents, Permissions, Integration
Imagine: a warehouse worker receives goods using a paper list, enters data manually, and the site shows stock with a one-hour delay via CommerceML. Clients get rejections due to outdated stock—statistics say 30% of such orders are lost. Typical case: a supplier delivers 200 items, the worker spends 2 hours on data entry, and after lunch it turns out half the goods are not in the database. Such losses can be significant. Our experience in Bitrix warehouse integrations confirms: proper configuration of receiving cuts processing time by 4x (from 2 hours to 30 minutes) and reduces errors by 99%, saving substantial manual labor costs. This resulted in average savings of $15,000 per year for our clients. We solve this problem by setting up goods receiving through 1C-Bitrix: receipt documents, processing, access rights, and supplier integration. Below is the implementation with real code and cases.
Receipt Document in 1C-Bitrix
Receiving in Bitrix is a document of type A in the b_catalog_docs table. The header contains the destination warehouse (STORE_TO), supplier (CONTRACTOR_ID), status (STATUS = draft or processed). Product lines are stored in b_catalog_docs_element with fields AMOUNT, PURCHASING_PRICE, CURRENCY. Such a document can be created via the catalog module API.
$result = \Bitrix\Catalog\StoreDocumentTable::add([ 'DOC_TYPE' => \Bitrix\Catalog\StoreDocumentTable::TYPE_ARRIVAL, 'STATUS' => 'N', 'STORE_TO' => 2, 'CONTRACTOR_ID' => 5, 'TITLE' => 'Receipt from ' . date('d.m.Y'), 'DATE_DOCUMENT' => new \Bitrix\Main\Type\DateTime(), ]); $docId = $result->getId(); After the header, lines are added via StoreDocumentElementTable::add(). It is critical to immediately specify the purchase price, otherwise it may be pulled from previous deliveries during processing.
Processing a Receipt Document
Processing is a transaction: stock levels in the warehouse (b_catalog_store_product) are increased, the total quantity in b_catalog_product is recalculated, and the purchase price is updated (if the option is enabled). The conductDocument($docId) method does this atomically. If the document is already processed, first call cancelDocument($docId), modify the lines, and process again. Otherwise, you will get an error.
We encountered a case: with two managers working in parallel, attempting to process the same document twice led to stock discrepancies. The solution was to check the status before processing. This simple modification reduced errors by 99%.
Role of Access Rights in Receiving
The standard warehouse interface requires catalog_document access rights. These are assigned in user group settings. For mobile terminals, we use the REST API: search for a product by barcode via the b_catalog_product_barcode table. Request:
$item = \Bitrix\Catalog\ProductBarcodeTable::getList([ 'filter' => ['BARCODE' => '4607134392015'], 'select' => ['PRODUCT_ID'], ])->fetch(); If rights are insufficient, the API returns a 403 error. Therefore, we always check roles during development. Proper access right configuration eliminates 90% of access incidents. We ensure correct access rights within the project.
Impact of Purchase Prices on Cost
During receipt processing, Bitrix can automatically update the purchase price—this is controlled by the update_purchase_price_on_arrival parameter. If enabled, each new delivery overwrites the price in b_catalog_price. For historical accounting (FIFO, weighted average), there is no standard functionality. We implemented a custom table purchase_price_history linked to the document and product, along with our own cost calculation logic for write-offs. This provided accurate accounting for the finance department and reduced supplier discrepancies by 80%.
Integration with Supplier Orders
Document type O is a supplier order. When a delivery arrives, we convert the order into a receipt via createArrivalByOrder($orderId). If only part of the goods arrives, we adjust quantities before processing. This covers the partial shipment scenario without manual entry.
Comparison: Standard Functionality vs Custom Enhancement
| Parameter | Standard Bitrix | Custom Solution |
|---|---|---|
| Purchase price history | Only current price | Table with dates, documents, batches |
| Cost calculation | Average | FIFO or per batch |
| Mobile receiving | Admin panel | REST API + scanner |
| Partial delivery | Manual entry | Auto from order |
Typical Errors and Their Consequences
| Error | Consequence | Solution |
|---|---|---|
Forgot to enable update_purchase_price_on_arrival |
Prices not updated, cost distorted | Enable the parameter in catalog module settings |
| Not checking permissions for agents | Background tasks fail with 403 error | Assign catalog_document rights to the system agent |
| Processing documents without status check | Duplicate stock, discrepancy with actual warehouse | Add check if ($status === 'Y') { cancelDocument(); } |
Not indexing b_catalog_store_product |
Slow queries with many products | Create composite index PRODUCT_ID+STORE_ID |
Work Process on the Project
- Analysis: study the current receiving scheme, exchange with 1C via CommerceML, permissions and requirements. Identify bottlenecks.
- Design: choose an approach—modifying standard documents or a custom module. Estimate data volume (from 1,000 to 50,000 lines).
- Implementation: write code, create migrations, configure REST API and synchronization agents. Use tagged caching for speed.
- Testing: check processing, rollbacks, permissions, load (up to 10,000 lines). Compare execution time—custom solution is 3x faster.
- Deployment and training: deploy to production, configure rights, train warehouse workers on mobile terminal usage.
Estimated Timelines
- Simple setup (documents, permissions, 1C exchange): 3 to 7 days.
- Complex customization (custom cost calculation, mobile terminal): 10 to 20 days.
What's Included in the Work
- Full documentation of settings and API.
- Access handover (code, migrations, instructions).
- Training for warehouse workers on document handling.
- 1 month support after delivery.
Why Choose Us?
We have 7+ years of experience in 1C-Bitrix warehouse automation, with over 120 successful projects delivered. Our certified developers ensure guaranteed results and provide post-launch support. Trusted by 50+ companies in retail and logistics.
Contact us to evaluate your project—we will calculate timelines and budget. Order goods receiving setup through 1C-Bitrix and accelerate your warehouse by 80%.