Integration with CRM SalesDrive for UTP, UPP, UT, 2.3, and other configurations on standard forms. Bidirectional exchange with SalesDrive

Implemented for configurations:

• UTP. Trade enterprise management;
• UVP. Management of a production enterprise;
• Other configurations on regular forms (to be specified).

Why Choose Our Solution:

• More than 50 integrations over 4 years; 
• We have been working in this area since 2021.
• Ability to change the exchange settings between "SalesDrive" and accounting system in the "Enterprise" operating mode, not via the "Configurator". From "Enterprise," you can configure everything except the algorithms, specifically:
• matching the document type in "SalesDrive" ("Deal"/"Agreement") to the document type in accounting system ("Customer Order" or another);
• matching the requisites (fields) of the "Deal" in "SalesDrive" to the requisites of the selected document type in "accounting system";
• matching the directory/catalogue values in "SalesDrive" to the directory/catalogue values in "accounting system" (For example: you can set correspondences for deal statuses in "SalesDrive" to the corresponding statuses of customer orders in "accounting system", similarly for directories - "Delivery Types", "Payment Types").

 

 








Fig. 1. Scheme of exchange with SalesDrive.





How implemented:

A - Exchange of orders with the site (may not be)

                The order comes from the site. Reverse order/pre-order status changes.

B - Exchange of orders with the accounting system.

                The order comes from SalesDrive to the accounting system. Order/pre-order status changes are sent back.

Based on the exchange scheme (Fig. 1), an order (request) in SalesDrive can be created both manually in SalesDrive and received when exchanging with the site. But part B will work the same in any of these options.




Integration functionality includes

1. Receiving an order/pre-order via WebHook. 

When an order is created or its status changed, SalesDrive sends a message with the order data. On the side of the accounting system, it is accepted by the HTTP service.

Result:

а) An order is created/changed and its status in BAS;

б) Sent (using the API) to SalesDrive the number of the created document (If allowed by the corresponding setting).

2. When the order status changes in the accounting system, the status value is sent to SalesDrive (using the API) (if allowed by the corresponding settings).

3. Since the SalesDrive API does not provide for changing the amount of the order, when changing the amount of the order/pre-order to the accounting system, the line "Attention changed the amount of the order - UAH 0000.00" is added to the comment of the order to the accounting system. and the comment value (via API) is sent to SalesDrive.










Fig. 2. SalesDrive integration settings.




Integration settings specify authorization parameters for working with API (Account and API key).




 




Fig. 3. How to find Account and API Key parameters (1).










Fig. 4. How to find the Account and API Key parameters (2).




To receive a Webhook, you need to publish an HTTP integration service (called SalesDrive) and perform port forwarding.

The result should be a URL like this:

http://<external IP>:<port>/<public name>/hs/SalesDrive/WebHook

It must be specified in the Webhook SalesDrive settings (see Fig. 5).










Fig. 5. Where is the URL for Webhook SalesDrive.




This solution partially uses the functionality of integration with Bitrix24.

In particular, the exchange entity setting mechanism is used. It allows you to add/change the necessary fields in the exchange entity in user mode.







Fig. 6. Exchange Essence (Order/Pre-Order).




To work with the SalesDrive API directories for entity reference values, the ability to identify by ID has been added (this was not required (and was not) in the standard integration with Bitrix24).










Fig. 7. Directories of exchange entities with identification, incl. by ID.




Correspondences of lookup values are specified in the same way as in integration with Bitrix24.










Fig. 8. Configuring SalesDrive Reference Value Correspondences.




The object ID is stored in the same registry as for Bitrix24. To understand that this is a SalesDrive ID, it is written with the prefix "SD_":











Fig. 9. The SalesDrive ID is stored in the same register that was used in the integration with Bitrix24.




To set up the exchange entity, you can use all the fields of the request that come via Webhook (all fields of the data section in JSON Webhook SalesDrive).










Fig. 10. The principle of setting up an exchange entity for integration with SalesDrive.

 

Solution Cost: 

Standard functionality cost		12000.00
Additional functionality cost		Price, UAH
1.	Importing products from CRM "SalesDrive" to the accounting system while maintaining the nomenclature folder structure	4000.00
2.	Exporting products from the accounting system to CRM "SalesDrive"	3000.00
3.	Exporting stock balances to CRM "SalesDrive"	3000.00
4.	Importing payments from CRM "SalesDrive" to the accounting system, linked to customer orders	4000.00
5.	Exporting payment data from the accounting system to CRM "SalesDrive"	4000.00
6.	Uploading payment receipts from CRM "SalesDrive" to the accounting system	3000.00
7.	Importing additional deal characteristics from CRM "SalesDrive" to the accounting system	3000.00
8.	Using item characteristics when loading transactions into the accounting system	8000.00
9.	Exporting prices to CRM "SalesDrive"	3000.00
10.	Exporting cost prices to CRM "SalesDrive"	2000.00
11.	Automatic generation of sales invoices in the accounting system based on customer order/proforma invoice by "Ship" status	3000.00
12.	Formation of the document "Closing the buyer's order" based on the document "Buyer's order", if the order status is "Cancellation"	2000.00
13.	Formation of the document "Invoice for return of goods" in the accounting system, based on the "Outgoing invoice for goods", if the outgoing invoice exists and the status "Cancellation" appears in the buyer's order	3000.00

     

Rights to the module are protected (Certificate No. 139214). We provide favorable cooperation terms for partners.

   

Developer: LLC "NCT" 

www.nct.ua  

info@nct.ua