Magento 2 BaseLinker Stock Export
Magento 2 BaseLinker Stock Export was designed for stores that need more control over stock synchronization than the standard integration offers. The module retrieves quantities from Magento 2 and saves them to the selected catalog and warehouse in BaseLinker, helping keep product availability data consistent between systems.
The solution supports both the classic Magento inventory model and MSI. The administrator can select one or multiple stock sources, decide whether the quantity should be calculated as a simple sum or as a sum reduced by reservations, and set minimum and maximum limits for the exported stock level. This gives the module control over the final value sent to BaseLinker.
Synchronization works by SKU and can be run automatically via CRON or manually from the CLI. This simplifies both day-to-day store operations and diagnostics during implementation. The module stores synchronization history, logs warnings and errors, and maintains product mapping, reducing unnecessary requests to the BaseLinker API during subsequent runs.
If a product does not yet exist in the BaseLinker catalog, the module can operate in two modes. In safe mode, it updates only existing records and skips missing products with an entry in the log. In extended mode, it can automatically create the missing product in BaseLinker, assign it to the selected category, and immediately send its stock level.
A major advantage of the module is its ability to work in environments where inventory logic does not follow the standard Magento scenario. If stock levels are supplied from an ERP system and the store operates with inventory management disabled on the standard BaseLinker integration side, the module can still retrieve quantities from Magento and pass them on to BaseLinker. This closes an integration gap that often blocks multichannel sales in practice.
Key benefits
- export stock levels from Magento 2 to BaseLinker via API,
- support for MSI and the classic single-stock model,
- saving to one or multiple BaseLinker warehouses,
- automatic or manual synchronization launch,
- optional creation of missing products in BaseLinker,
- product filtering by status, visibility, and export attribute,
- operational logs and synchronization history,
- secure configuration in the Magento panel.
Who this module is for
- Magento 2 stores using BaseLinker,
- implementations where an ERP supplies Magento with inventory data,
- installations with MSI and multiple stock sources,
- projects where the standard integration does not support the actual inventory model.
Questions and Answers
Problem
In the VITCAS store, stock levels were delivered to Magento from an external ERP. At the same time, the standard stock management on the Magento side was not used in the model expected by the standard BaseLinker integration. As a result, BaseLinker was unable to correctly import the stock levels, even though quantity data was available in Magento.
Challenge
The problem was not the lack of inventory data, but the way it was read. The standard integration was too rigid for the project's architecture. A solution was needed that would retrieve stock levels directly from Magento, in line with the actual implementation logic, and then save them to the appropriate catalog and warehouse in BaseLinker.
Solution
For VITCAS, the Magento 2 BaseLinker Stock Export module was implemented. The module:
- retrieved stock levels from Magento despite the non-standard inventory management model,
- synchronized them to the designated inventory in BaseLinker,
- saved quantities in the target BaseLinker warehouse,
- enabled cyclical data refresh via CRON,
- provided error logging and control over the synchronization process.
Result
The store regained the ability to reliably transfer stock levels to BaseLinker without rebuilding the entire inventory logic in Magento. As a result, the ERP remained the main source of inventory data, Magento retained its role as the integration intermediary, and BaseLinker received up-to-date stock levels in a format it could continue to handle in sales channels.
Business conclusion
This implementation shows that a stock synchronization problem does not always require replacing the ERP or rebuilding the store. Often, a dedicated module is enough to adapt the integration to the actual architecture of the project.























