retailCRM + amoCRM |
![]() |
Integration of amoCRM and retailCRM | ||||
- Synchronization of contractors - amoCRM and retailCRM have different contact entities - The reference data is amoCRM (from where the initial creation of contacts comes from) - If a contact in amoCRM does not have an associated company, then it is created as a company in MoiSklad - The script uses a database to link identifiers |
retailCRM + |
Integration retailCRM + Yandex.Kassa | ||||
Integration will be available if at least one of the following countries is active in the system settings: Russia, Ukraine, Belarus, and Kazakhstan. One of the currencies should also be chosen: the Russian ruble, dollar, euro, Kazakhstani tenge, hryvnia, Belarusian ruble. The currency in the Yandex.Case should match the currency specified in the system settings. For other currencies, integration is not available. Integration deadline: up to 7 business days |
retailCRM + 1C-Bitrix |
![]() |
Integration of retailCRM and 1C-Bitrix | ||||
After installation, the module will be: - To unload new orders from 1C-Bitrix to retailCRM - Update data on existing orders with changes made to 1C-Bitrix - To unload new orders and customers from retailCRM to 1C-Bitrix - Update the data on existing orders with the changes made in retailCRM (for example, the order status, the quantity of goods in the order, etc., were changed in retailCRM, these changes will also be reflected in 1C-Bitrix) - Send to retailCRM information about online payment of the order by the user. There is also the possibility of finalizing the functionality of the plug-in for the client's business processes. Integration deadline: up to 15 business days |
retailCRM + Poster |
![]() |
Integration of retailCRM and Poster | ||||
- Import goods from Poster to retailCRM - Synchronization of prices of goods from Poster to retailCRM and back - Upload and synchronization of balances in both directions - Write off balances in Poster after placing the order in retailCRM - Refinement for your business processes and requirements. Integration deadline: up to 15 business days |
retailCRM + Ecwid |
![]() |
retailCRM and Ecwid integration | ||||
- Uploading orders from Ecwid - Setting up regular receipt of order changes from retailCRM to Ecwid - Updating information on price and balances in Ecwid based on information in retailCRM As well as additional flexible settings for the requirements of your business. Integration deadline: up to 16 business days |
retailCRM + Zadarma |
![]() |
retailCRM and Zadarma integration | ||||
Integration functions: - Calls to customers from retailCRM in one click. - Pop-up client card for incoming call. - Integration of call statistics and call recordings. Ability to listen to recordings of conversations directly from retailCRM. Integration deadline: up to 12 business days |
retailCRM + |
Integration retailCRM + Shiptor | ||||
Shiptor integration options: - Calculate the preliminary cost of delivery - Make a request for delivery - Edit delivery request in certain statuses - To print labels from the system interface - Display the current status of deliveries in the system and set the status of delivery of the delivery status of the order Integration deadline: up to 7 business days |
retailCRM + Ebay |
![]() |
retailCRM and Ebay integration | ||||
- Uploading orders from Ebay - Set up regular receipt of order changes from retailCRM to Ebay - Update information on price and balances in Ebay based on information in retailCRM As well as additional flexible settings for the requirements of your business. Integration deadline: up to 16 business days |
retailCRM + Sipuni |
![]() |
Configuring Sipuni Telephony for retailCRM | ||||
This service involves setting up the telephony scheme you need, a bundle with retailCRM and one workplace. Integration deadline: up to 10 business days |
retailCRM + Etsy |
![]() |
retailCRM and Etsy integration | ||||
- Uploading orders from Etsy - Setting up regular receipt of order changes from retailCRM to Etsy - Updating information on price and balances in Etsy based on information in retailCRM As well as additional flexible settings for the requirements of your business. Integration deadline: up to 16 business days |
retailCRM + Wordpress |
![]() |
retailCRM and WordPress Integration | ||||
1. Install an existing plug-in from a Woocommerce store that allows you to: - Generate a catalog of goods for uploading to retailCRM - Set up two-way exchange orders for Woocommerce and retailCRM - Send and accept changes on orders - Unload residues from retailCRM to the store. When you enable the function of unloading balances every 15 minutes, balances on goods will be unloaded into the store 2. Refinement of the standard plug-in for your functional requirements. Integration deadline: up to 15 business days |
retailCRM + |
Integration of Prestashop (1.5 / 2.0) with retailCRM + Bonus | ||||
- Set up a regular generation and upload of the catalog from PrestaShop - Uploading orders from Prestashop - Setting up regular receipt of order changes from retailCRM to PrestaShop The bonus is additional unloading to the goods: Supplier Block v1.2.0 - by PrestaShop Manufacturers Block v1.4.0 - by PrestaShop Product Characteristics Integration deadline: up to 15 business days |