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%.
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.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
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']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
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?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- 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.
