Problem 1:

Originally, a seller can only duplicate all products from a previous store, but they can’t choose what they want to add to the new store.

With Product pool:

Seller can choose any items to add to the new store.

Problem 2:

Same items in different stores can't be recognized as the same items. Therefore, it's impossible for data tracking for this product in multiple store. 

With Product pool:

Since items are choose from the Product pool, they can be recognized as the same item. 

Problem 2 might be a bit confusing. Allow me to explain by using an example.

Below is the original flow. Store 2 is duplicated by store 1, therefore, an identical product - Banana A was copied and pasted to Banana B.

The problem is, in the data base, Banana A and Banana B is not the same item even they are identical. It's like they don't share the same SKU number. The theory is the same as you can't have files with same name and format in a folder in Windows or Mac OS.

Store 1

Store 2

Banana A

Banana B

Duplicate

Let see how Product pool can solve this problem.

Items created in the Product pool can be add to Store 1 and Store 2. What's different is that this time Banana in Store 1 and Banana is store 2's data can be traced back to the one in the Product pool. In other words, they share the same SKU number. So Banana's data from both stores will be saved in the Product pool.

Banana

Banana

Banana

Product pool

Store 1

Store 2

Add product

Add product

Sales data

Sales data

In more simple words, now we know Banana's total history sales = Sales in Store 1 + Sales in Store 2

With all that information, 6 updates are associated with the seller's demand and concerns. The 6 updates are "Redesign Interface,""Batch add,""Filter and search,""Easy selection,""Edit mode,"and "New data tracking."