# Store Mapping

## Possible Entity Keys

Store Mapping import templates supprot keys from entity that you are using mapping for.

{% hint style="warning" %}
Your entity key must be unique. If you have two products with same Name fields, you will not be able to use Name as entity key.
{% endhint %}

## Column Destinations

<table><thead><tr><th width="272">Column destination</th><th>Explanation</th></tr></thead><tbody><tr><td>Key</td><td>The value that you selected as entity key for this template.</td></tr><tr><td>Store '&#x3C;Store Name>'</td><td>TRUE or FALSE value, wether to show this product in this store.</td></tr></tbody></table>

{% hint style="warning" %}
If you don't have Store Mapping set up for this product/category/manufacturer, all stores would show this product. If you set up any restrictions, all, except stores with TRUE value, **will not have access**.
{% endhint %}

## Example table

This is an example table for ACL Mapping of Product

<table><thead><tr><th width="133">SKU</th><th width="220.33333333333331">Store 'My store 1'</th><th>Store 'My store 2'</th></tr></thead><tbody><tr><td>001</td><td>TRUE</td><td>TRUE</td></tr><tr><td>002</td><td>FALSE</td><td>TRUE</td></tr><tr><td>003</td><td>FALSE</td><td>FALSE</td></tr></tbody></table>

{% hint style="info" %}
With the import above being the only Store mapping rules that are set up for products with SKU 001, 002 and 003, the following scenario would be executed. \
1\. Store 1 and 2 would have product 001. No other store would have it.\
2\. Only store 2 would have product 002.\
3\. No store would have product 003.
{% endhint %}