Shopping cart content

To pass the shopping cart content to the CRM make sure you've enabled this feature during the webhook setup.

Enabling shopping cart content sending

All shopping cart positions along with its prices and quantities are adding to the RetailCRM order. Without any additional settings the positions are adding by its name as-is (without binding to products from the CRM catalog). Probably it is not what you need, and you may want to connect the products from your website with products from your CRM warehouse.

First, if you haven't done it before, enable catalog editing in CRM settings (Settings > System > Warehouse > Allow catalogue editing).

Catalog editing settings

Each item in the RetailCRM catalog must contain one or more trade offer. For example, the Backpack item may have the following trade offers:

  • Blue backpack
  • Red backpack
  • Black backpack
  • And so on...

Thus, using trade offers you can add different modifications to one product. One trade offer must exist even if the product has no modifications. In that case the trade offer can have the same name as the product.

Each trade offer has an editable External code field. If you fill it with the same value as in the Subtitle or SKU Tilda product field, then this trade offer will be adder to the CRM order.

Using our backpacks example, the steps will be:

  1. Find (or create) a Backpack product with a Red backpack trade offer in the CRM catalog.
  2. In the External code field of the trade offer type in some value (letters and/or digits), e.g. 42.
  3. Find (or create) a Red backpack product and type 42 in the Subtitle or SKU field.
  4. Re-publish the website.

RetailCRM trade offer external code Tilda product subtitle or SKU

If you can't se the Subtitle or SKU field, press the Show more: button, label, options button in the bottom of the product settings window.

Additional Tilda product settings

Now each red backpack order from the website will have the red backpack trade offer from the CRM warehouse in its positions. The same procedure of binding website products with the CRM trade offers should be done for each product.

Passing product options

Product properties are sent to the order card and displayed in the Properties column of the positions list. For example, instead of creating a dedicated product item for each of backpack color, you decided to create one Backpack product item with the color option that has Red, Blue, Black values.

Product with options

On the website it'll be shown as:

Product with options

In that case the 42 external code will be passed to the CRM order, no matter what color the customer has chosen. The selected color will be displayed in the positions list.

Product properties in the positions list

Product catalog

In order to pass different product modifications to the CRM when a customer selects differrent properties, a separate Subtitle or SKU value should be set for each backpack color (e.g.: red - 42, blue - 43, black - 44). It is possible only by using Tilda product catalog. After enabling this feature, you don't need to manually add products to the site page anymore. All products will be added/updated/deleted automatically from the catalog.

To enable the catalog go to the site settings, find a Product catalog item in the More section of the left-side menu and press Connect.

Enabling Tilda product catalog

Add a new catalog item with a name Backpack. In the item settings add a Color property in the Product variants section. Additionally, when you work with the catalog, there is one more field called External ID. It is ment to be used for matching Tilda's catalog item with the corresponding RetailCRM trade offer. Just like the Subtitle or SKU field we used earlier.

When the module sends orders to the crm, it checks the External ID first. If it's not present, the module fallbacks to the Subtitle or SKU field. Sending the external id must be enabled in the webhook settings.

Important: if you decided to use the external id, be careful with its format. The ids are set for the catalog item and for all its variants individually. Tilda contatenates the product id and its variant id using a # symbol while sending a webhook. For example, if the customer orders the Backpack with id backpack and specifies Red with id red as its color, a backpack#red string will be sent to the crm. So, the Red backpack crm trade offer must have the backpack#red external code. External ID in Tilda catalog External code in RetailCRM trade offer

Let's get back the unique-sku-per-variant example. Create three product variants (Red, Blue and Black) with SKU 42, 43, 44 accordingly. You can also add a photo and price for each variant.

Product variants in Tilda catalog

Find a Show products from catalog dropdown list in the product cards block on the website and select the All products option. You can also split your catalog into categories and use them on different site pages.

Connecting product catalog to website

Save and re-publish the website. Now, the product cart for the customer will look like this:

Product with variants

When a site visitor selects the backpack color, the SKU (and photo, price if you specified it) will be updated, and on form submit the CRM will add precisely the backpack modification the customer selected.

The product catalog feature usage makes working with products much more convenient and functional.