The Seller.Tools ManyChat native integration now utilizes arrays to store all of the ASIN(s) and SKU(s) that a customer purchased in one order.

Arrays are a new custom field type in ManyChat that allow you to store multiple values in one custom user field.

ManyChat has a fantastic and very extensive resource on using arrays. This resource can be found in ManyChat's Knowledge Base here. This resource has been adapted and customized here for Seller.Tools use cases.

This resource talks extensively about response mapping in ManyChat. Response mapping is simply the process of saving the output from the Seller.Tools API to a custom field in ManyChat, so you can use it in your messaging and next steps with your customer.


When you check the status of an Amazon order, you will now be able to pull all of the ASIN(s) and SKU(s) purchased into a singular field, an array.

Example of what Array CUFs look like in your audience tab when they contain more than one value.

The array field will then be 'scanned' by a condition step to see if the CUF contains the ASIN you are running a promotion for.

In most cases, your customer will purchase only one ASIN — your product — and this will not make any difference from normal response mapping to a text custom field.

However, in the event that your customer has a few other items in their cart or purchased other items from your storefront, this field type will enable us to find all the products they purchased and separate out ASIN information for the specific ASIN you are promoting, and want to verify that they purchased.

Sean is covering all you need to know about arrays and how to use them with Seller.Tools in this video:

Note: Previously, our response mapping only mapped the first product that a customer purchased (the first row of data).

If you are using an existing flow and mapping ASIN and SKU fields to text custom fields, your flows will still be functional. Any arrays mapped to a text custom field will simply pull the first row of data and map as normal. However, we would strongly recommend updating your mapping to map to an array field type, then modify your condition step to check the array field.

When you import a new Seller.Tools template, you will automatically import the array fields that the app uses and the recommended setup for using these fields.

Did this answer your question?