Product Catalog File Use Cases
A client does not need to provide the product file in order to use the most basic TIBCO Reward functionality. The file is required, however, if you want the following capabilities:
- Targeting based on past purchases of certain products within certain categories.
- Offers valid only on purchases of certain products or categories.
- Ability to collect category preferences from customers and target based on preferences.
Detailed Use Cases
Use Case 1. The client wants to target customers based on past purchases. The client has launched a cross-sell campaign to convince customers who bought an HDTV in the last year to purchase a new model. Using the TIBCO Reward CRMS, the client sends an email presenting the new HDTV models to all customers who have bought a product in the flat screen TV category in the last year. In order to complete this scenario, the following data integration is required:
Use Case 2. The client wants to create an offer that awards 50 bonus points to all purchases in the “Cashmere” category. Using the TIBCO Reward CRMS, the client sets up a new offer that awards 50 bonus points to all customers who buy any product in the “Cashmere” category. In order to complete this scenario, the following data integration is required:
Use Case 3. The client wants to quickly move some additional inventory of a given product. The client creates an offer to give 100 additional points for purchasing selected products and associates a SKU image with the offer. The client includes the offer in an email communication sent to customers who have bought similar products in the past. In order to complete this scenario, the following data integration is required:
Use Case 4. The client wants to collect category preferences from customers so that the client can target email communications and offers based on each customer’s self-expressed interests. Customers can select their preferred categories in the microsite, which lists the available product categories, and the client can then create offers and email communications tailored to customers based on their preferences. In order to complete this scenario, the following data integration is required:
Use Case 5. The client wants to create a new Product custom attribute that is called "Seasonal Collections." This product attribute will allow clients to search for selected seasonal items, which will be useful when creating offers or segmenting customers by purchase history. SKUs that are part of a seasonal collection, such as the items labeled as "Winter Collection," can include items from different categories and brands, so this custom attribute provides a means of searching for and selecting items that are not addressed by other existing product category or brand criteria.
To implement this product custom attribute, the client:
- Defines a set of lookup values for this custom attribute by creating a simple file containing a list of values for the Seasonal Collections custom attribute.
- Defines a product custom attribute using the CRMS (under the Admin>Custom Attributes menu). The custom attribute is a lookup type attribute that is named "Seasonal Collections."
- Modifies the Product Catalog file, assigning selected products a custom attribute of the Lookup type called Seasonal Collections, and assigning the product a Seasonal Collection attribute value from the list of lookup values. One of these is Winter Collection.