This page contains more frequently asked questions to the module support and answers to them.
- First name
- Last name
- Middle name
- Additional phone
- Delivery address
- Delivery type
- Delivery cost
- Order list (shopping cart content)
- Order custom fields
- Promocode and its discount value
- Cookie values
- Payment method and status
- Order method
- Order number (ID)
Errors can appear because of incorrect API key permissions. Check the key on the Settings page.
If you are sure that you specified a correct API key, but you still see the error message "Check url and API key", make sure you've created at least one store. RetailCRM may return an API error if there are no shops in the CRM account.
Please read the instruction carefully. Very likely you made a mistake during module setup. Also, the orders processing stops when the module is unpaid.
You can integrate as many websites as you want. It doesn't affect the final module cost. Details of setting up multiple sites in on Multiple sites page.
All product options sends to the CRM automatically. Using the Tilda's product catalog it is possible to pass product modifications as a separate trade offers to RetailCRM. The setup process is detailed on the Passing product options section.
It's not possible yet. Some technical restrictions of both Tilda and RetailCRM prevent us from implementing this feature right now as we see it. If you need the synchronization, please contact us for discussion of possible solutions.
Most likely you've forgotten to enable shopping cart content sending in the webhook settings (the Transfer data for goods in the order - as array checkbox). Refer to the instruction to fix this.
Very likely you incorrectly specified Tilda product SKUs and RetailCRM trade offers external codes. Details on how to do this are on the Cart content page.
Delivery calculators are available only when you use the Delivery services Tilda feature. This feature is fully supported by the module and does not require any configuration. All delivery information will be automatically sent to the RetailCRM.
Most likely you have made a mistake during form fields setup. Setting up sending of delivery information to the CRM is described on the Forms setup page.
Most likely you've forgotten to enable cookies sending in the webhook settings (the Send Cookies checkbox). Refer to the instruction to fix this.
The module supports sending promocodes and its discount values to the RetailCRM. Refer to the Promo codes and discounts page of the current instruction.
The instruction of payment method and status sending is on the Payment status page.
UTMs are automatically attached to each order. No special setup required. Details are on the UTM page.
Any cookie value can be sent to the CRM, just like site forms values. The setup process is described on the Cookies page.
Order method is passed to the RetailCRM automatically, but your site form names should match symbolic codes of the Order types data book. More details are on the Order channel page.
No, we do not provide any individual customizations.