Feed Business Logic Review

This document is in Beta stage and we have try to cover all topics in right hierarchy yet indepth. To make this document better, we need your help. Please give your feedback by rating the stars at the end of each topic. For more updates join slack channel #unbxd-knowledgebase

Use this document for internal purpose only. It is not suppose to be shared with customers

In this stage of feed review, we try to understand if any business logic customer has suggested for fields like inventory, out of stock, segment pricing, etc. In this phase, our goal is to make sure we have enough information to implement any special logic the customer has asked for.

Usecase

Usecase 1

Requirement from the customer could be to have 3 types of pricing (of a product ) based on the segment to a user belongs.

Pricing segments could be

• Super Users
• Regular Users
• Guest Users

Consider following sample feed

productId,size,title,description,image,categoriesids,price
"098ABD","small","Black Tshirt","Black tshirt made up of cotton", "https://dummyurl.com/black-t-shirt/img.jpg", "home|womens,home|womens|topwear", 100
"4321ANC","small","Pink Tshirt","Pink tshirt made up of cotton", "https://dummyurl.com/pink-t-shirt/img.jpg", "home|insale,home|newproducts", 200
"654AMIT","small","Green Tshirt","Green tshirt made up of cotton", "https://dummyurl.com/green-t-shirt/img.jpg", "home|newproducts",300
"876BCVF","small","Red Tshirt","Red tshirt made up of cotton", "https://dummyurl.com/red-t-shirt/img.jpg", "home|heavydiscounts",400

If you take a closer look at the feed then this feed contains only one price attribute which is not suffice for implementing pricing segmentation. To implement pricing segmenation in the feed we are suppose to have 3 type of pricing for each segmentation of users.

Feed Review Question

How do we determine segmented pricing given just one price information. Feed should be three pricing for each segment of customers.

So sample feed should look like this

productId,size,title,description,image,categoriesids,price_super,price_regular, price_guest
"098ABD","small","Black Tshirt","Black tshirt made up of cotton", "https://dummyurl.com/black-t-shirt/img.jpg", "home|womens,home|womens|topwear", 100,120,150
"4321ANC","small","Pink Tshirt","Pink tshirt made up of cotton", "https://dummyurl.com/pink-t-shirt/img.jpg", "home|insale,home|newproducts", 200,220,250
"654AMIT","small","Green Tshirt","Green tshirt made up of cotton", "https://dummyurl.com/green-t-shirt/img.jpg", "home|newproducts",300,320,350
"876BCVF","small","Red Tshirt","Red tshirt made up of cotton", "https://dummyurl.com/red-t-shirt/img.jpg", "home|heavydiscounts",400,420,450

Usecase 2

Customer want to show discount % across each product on the website.

Following is the feed given by the customer

productId,size,title,description,image,categoriesids,price
"098ABD","small","Black Tshirt","Black tshirt made up of cotton", "https://dummyurl.com/black-t-shirt/img.jpg", "home|womens,home|womens|topwear", 100
"4321ANC","small","Pink Tshirt","Pink tshirt made up of cotton", "https://dummyurl.com/pink-t-shirt/img.jpg", "home|insale,home|newproducts", 200
"654AMIT","small","Green Tshirt","Green tshirt made up of cotton", "https://dummyurl.com/green-t-shirt/img.jpg", "home|newproducts",300
"876BCVF","small","Red Tshirt","Red tshirt made up of cotton", "https://dummyurl.com/red-t-shirt/img.jpg", "home|heavydiscounts",400

As you can see, we just have price across each product and we can not derive %discount just by this. Here we need either selling price so that we can calculate discount or %discount attribute itself. Hence we have a feed review question to ask from the customer

Feed Review Question

To calculate %discount we need either product's selling price or we need this field itself.

Exercise

Exercise 1

Did you find it useful? Rate it