Multi-store feed

Bloomreach consumers can create a multi-store feed file to contain products linked to two or more stores. The multi-store feed enables you to use one file to contain all product attributes from all of your stores in a single language. If you have more than one langugage, each language has its own file. For example, a product attribute with values for English and Spanish are surfaced in their respective language files.

Each multi-store feed file contains a view_id column, which is a file format to support the multi-store feed. The view_id column enables one row to represent an item and the item can be present in multiple stores. For example, a large company owns store ABC, DEF, and GHI. The company sells lawnmowers in each store. The multi-store feed file enables one file for all three stores. The view_id format specifies in a delimited format which allows for multiple values to be written in a column, such as storeA|storeB.

Store Configuration

important

Before you begin, ensure that your products are associated with a virtual catalog which is associated to a store. Without the product and category association, an offer will not be generated, and the multi-store feed file will not be generated. For more information on offer projections, see the Build Projection Catalog Syndication documentation.

Implementing the multi-store feed

Implement the multi-store feed by preparing your store data.

1. Add a store in Commerce Manager.

   For more information about adding a store, see Creating a store.

2. Add the catalog to a virtual catalog and master catalog.

   For more information about catalogs, see Managing catalog in Elastic Path Commerce.

3. Define the required product attributes and assign them to the product types in each catalog. For more information, see Mapping.

4. Add the locale to the store.

5. Add the currency to the store.

   For example, if you have one locale with two currencies, such as English with USD and CAD currencies, you require only one feed file with the ViewID entry. All localized fields will pull from the English language. In the file, the currency fields show as price_USD and price_CAD.

6. Add the product. Ensure that you associate the product with a catalog, and associate it with a store.

7. Within each product:

   1. Specify the required product attribute values.

   2. Add pricing to the product, associated to the appropriate price list for each store and currency

Preparing store data

Within the Bloomreach console, configure the multi-store feed with the following attributes:

view_id

Contains all of the store Id’s for the file. Each store is separated by a |.For example abc|def|ghi.

This attribute is populated automatically based on the number of stores that you have configured in your system. For example, if you configure one store with the name Sporting Goods store, the view_id value is Sporting Goods store. If you configure another store with the name Grocery store, the view_id value is Sporting Goods store|Grocery store.

SKU_ID

Contains the SKU identifier.

PID

Contains the product identification number. This value is mandatory for every product.

BRAND

Contains the brand name. This value is mandatory for every product.

CATALOG_CODE

Contains the catalog Id’s for the file. Each catalog is separated by a |.For example abc|def|ghi. This value is mandatory for every product.

TITLE

Contains the name of the product, such as ABCGasFurnace. Ensure that you have a title for each product. This value is mandatory.

CRUMBS

Contains the product category association, such as Category_ABC_Equipment|Category_DEF_Equipment_GasFurnace. CRUMBS are built from a category path and are always available for each product. This attribute is populated automatically.

AVAILABILITY

Contains data if the product is available or not. AVAILABILITY is built from a category path and are always available for each product. This attribute is populated automatically.

PRICE_<currency-code>

Contains the price for the product. Elastic Path Commerce uses the sale price, if available, otherwise, it falls back on the list price. The number of price columns in the file depends on the number of currencies. For example, if your store has two currencies assigned to it, you will see two price columns for each. Within each column, prices are delimited by the number of view_id, such as 100.00|199.00|299.00. The price must be assigned to a product. This attribute is populated automatically.

thumb_image

Contains the product image URLs. This image might vary by store and is delimited by view_id, such as http://abc.com/product/image|http://def.com/product/image|http://ghi.com/product/image). Ensure that you configure this attribute for each product. You can also use a global attribute. The value for this attribute must be the correct URL address or a URL address with a placeholder.

url

Contains the product image URLs. This image might vary by store and is delimited by view_id, such as http://abc.com/product/image|http://def.com/product/image|http://ghi.com/product/image). Ensure that you configure this attribute for each product. You can also use a global attribute. The value for this attribute must be the correct URL address or a URL address with a placeholder.

Using localized content

Use the multi-store feed file to enable localization in the same language file. You can create a price per locale, such as 99.00CAD and 89.00USD. The Bloomreach Feed plugin consumes the data and looks at multiple currencies within the file.

For more information about catalogs, see Managing Catalog in Elastic Path Commerce.