MoySklad Stocks Synchronization Module
website·Indexed 32 days ago
https://docs.despi.ruDocumentation for the rbs.moyskladstocks module, providing synchronization of products, modifications, kits, and services from MoySklad. Includes guides on importing prices and stocks, configuring web-hooks, setting up cron scripts for agents, and developer events such as [OnSetPropsForItem], [OnSetSkuProps], and [OnBuildImportFilter].
What's inside MoySklad Stocks
- The Moysklad Stocks module uses three recurring configuration blocks across its entity import tabs to manage how data is synchronized and filtered. These blocks are present in almost every import tab, allowing for consistent control over different entities.
Overview of despi-aiconnector for Bitrix
Thedespi.aiconnectormodule automates the generation of content for Bitrix infoblocks, such as product descriptions, section texts, SEO meta-tags, and translations. Instead of manual chat interactions with AI, the module uses 'Rules' (profiles) to apply consistent prompts and processing steps to thousands of elements in the background via the Bitrix agent. It supports custom API keys from providers like Polza.ai, OpenRouter, or any OpenAI-compatible gateway.Overview of Service Import Settings in RBS MoySkladStocks
The Service import settings tab allows users to configure how services are imported from MoySklad. The configuration is divided into several functional areas: General Parameters (infoblock and section selection), Import Logic (field rules and links), Element Filtering (filtering services from MoySklad), Agent (bulk import scheduling), Property Mapping, New Service Import structure, One-time Import execution, and Base Settings.Overview of entity and stock filtering in Moysklad Stocks
Filtering settings are applied across multiple import tabs, including Stocks, Products, Modifications, Kits, Services, and Groups. Note that price imports also utilize the filtering rules defined for the specific entity (Product, Modification, Kit, or Service).Overview of RBS Moysklad module settings tabs
The RBS Moysklad module provides a comprehensive set of configuration tabs to manage the synchronization and data exchange between 1C-Bitrix and Moysklad. The available settings tabs include:
- Settings (Main): Core module parameters, including authorization and general operational settings.
- Webhooks: Configuration for real-time event and change tracking.
- Order Export: Parameters for exporting orders from 1C-Bitrix to Moysklad.
- Order Import: Settings for importing orders from Moysklad to 1C-Bitrix.
- Statuses: Mapping of order statuses between 1C-Bitrix and Moysklad.
- Basket: Management and processing of order baskets during synchronization.
- Properties: Mapping and management of order properties for import/export.
- Counterparty: Rules for searching and creating counterparties in Moysklad.
- Payments: Management of payment document exchange.
- Shipments: Settings for shipment documents and delivery cost export.
- Other: Additional miscellaneous module settings.
- Log: Event log and history of actions performed by the module.
Overview of Order Export Settings from BUS to MoySklad
The 'Sections' (Разделы) settings tab manages the export of orders from the Business Management System (BUS) to MoySklad (MS). It allows developers and administrators to configure how order data is mapped, filtered, and synchronized between the two systems.Overview of Bitrix24 and MoySklad Synchronization
Thedespi.moyskladcrmmodule integrates Bitrix24 CRM (Self-hosted/Box version) with MoySklad warehouse accounting. It automates the creation and updating of customer and supplier orders, ensuring that sales managers in the CRM and accountants/warehouse staff in MoySklad work with synchronized data. The integration is bidirectional and event-driven, meaning changes in one system trigger updates in the other without requiring manual exports or scheduled API polling.Configure payment document exchange in RBS MoySklad
The 'Payments' (Оплаты) tab in the settings allows users to configure how payment documents are exchanged and synchronized with MoySklad. Available configuration areas include:
- Payment method synchronization and mapping to MoySklad orders.
- Default fields for payment documents.
- Exporting payment information into additional order fields.
- Assigning payment owners and departments.
- Mapping payment systems to specific document types and organizations.
- Configuring document synchronization modes.
Use the Despi MoySkladCRM Dashboard for initial diagnostics
The Dashboard provides a high-level overview of the module's health and is the primary starting point for troubleshooting synchronization issues. It contains the following key diagnostic areas:
- Settings State: Shows which document types, counterparty types, and directories are configured and ready for exchange.
- Queue Agent Card: Displays whether the agent is active, inactive, or not installed, along with the last and next run times. Includes options to install or reactivate the agent.
- Module Events Card: Indicates if all CRM handlers are registered and enabled.
- Queue Counters: Displays the number of pending tasks, completed tasks, and tasks that failed with an error.
Access and use the Diagnostics tool in RBS Moyskladstocks
The Diagnostics tool allows users to monitor exchange processes. It supports selecting specific exchange profiles to display in the monitoring view. This diagnostic functionality is largely identical to the one found in the 'Moysklad: Flexible Order Exchange' module, with some module-specific exceptions.Moysklad Flexible Order Exchange via API (rbs-moysklad)
Synchronizes orders between 1C-Bitrix CMS and Moysklad using the recommended modern API exchange method. It provides granular settings for the data exchange process and is compatible with the Moysklad counterparty synchronization module.Understand the MoySklad import process workflow
The import module processes entities (products, modifications, bundles, and services) in three sequential stages. Data is read in batches (multiples of 100, maximum 1000 elements). Each batch is split into two groups: elements found by external code (to be updated) and elements not found (to be created).