In our data we have a transactions table. This table contains the information about the purchased items by different users. However, according to the discussion in the thread for this post :
\n\n\nQ: Hello @fridarimark , thanks a lot for hosting and for the explanations!
\nI have a question to the data:
\n
\n In the data we have a table of transactions. Those are in principle sold items. However, this article from 2019 shows that that up to 30% - 40% of cloths and shoes bought online are being returned.Is the transactions table already cleaned from the returns?
\nAnswer: The transaction table holds all transactions that happened whether returned later or not.
\n
The transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.
\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.
", "messages": [ { "id": "1699813", "postDate": "02/21/2022 13:12:03", "content": "In our data we have a transactions table. This table contains the information about the purchased items by different users. However, according to the discussion in the thread for this post :
\n\n\nQ: Hello @fridarimark , thanks a lot for hosting and for the explanations!
\nI have a question to the data:
\n
\n In the data we have a table of transactions. Those are in principle sold items. However, this article from 2019 shows that that up to 30% - 40% of cloths and shoes bought online are being returned.Is the transactions table already cleaned from the returns?
\nAnswer: The transaction table holds all transactions that happened whether returned later or not.
\n
The transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.
\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.
", "rawMarkdown": "In our data we have a transactions table. This table contains the information about the purchased items by different users. However, according to the discussion in the thread for [this post](https://www.kaggle.com/c/h-and-m-personalized-fashion-recommendations/discussion/305952) :\n\n> Q: Hello @fridarimark , thanks a lot for hosting and for the explanations!\n>\n> I have a question to the data:\n> In the data we have a table of transactions. Those are in principle sold items. However, [this article](https://www.cnbc.com/2019/01/10/growing-online-sales-means-more-returns-and-trash-for-landfills.html#:~:text=Average%20return%20rates%20vary%20by,30%20to%2040%20percent%20returned.) from 2019 shows that that up to 30% - 40% of cloths and shoes bought online are being returned.\n> \n> Is the transactions table already cleaned from the returns?\n>\n> Answer: The transaction table holds all transactions that happened whether returned later or not.\n\nThe transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.\n\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.", "votes": null }, { "id": "1700735", "postDate": "02/22/2022 07:45:25", "content": "\n\nThe transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.
\n
Does that mean the transaction table lists a returned item twice, once when it was originally bought and once when it is returned?
", "rawMarkdown": "> The transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.\n\nDoes that mean the transaction table lists a returned item twice, once when it was originally bought and once when it is returned?", "votes": null }, { "id": "1701639", "postDate": "02/23/2022 00:38:10", "content": "Hallo @melanie7744, As I have understood, it is listed only once but you don't know if this item was later returned or not.
", "rawMarkdown": "Hallo @melanie7744, As I have understood, it is listed only once but you don't know if this item was later returned or not.", "votes": null }, { "id": "1712644", "postDate": "03/05/2022 06:23:36", "content": "*
\n\n\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.*
\n
If the return is for any reason other than size, another user may still buy it. Also, as others have shown with customers making repeat purchases it may work even if for purchased for a better size.
\nYes, in real life, this might be something H&M might look into if a particle article or those belonging to a category are having unusual returns.
", "rawMarkdown": "*\n> That means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.*\n\nIf the return is for any reason other than size, another user may still buy it. Also, as others have shown with customers making repeat purchases it may work even if for purchased for a better size.\n\nYes, in real life, this might be something H&M might look into if a particle article or those belonging to a category are having unusual returns.", "votes": null } ], "comments": [ { "id": 1700735, "author_name": "melanie7744", "author_url": "", "post_date": "02/22/2022 07:45:25", "content": "\n\nThe transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.
\n
Does that mean the transaction table lists a returned item twice, once when it was originally bought and once when it is returned?
", "votes": null, "replies": [ { "id": 1701639, "author_name": "ikorol", "author_url": "", "post_date": "02/23/2022 00:38:10", "content": "Hallo @melanie7744, As I have understood, it is listed only once but you don't know if this item was later returned or not.
", "votes": null, "replies": [] } ] }, { "id": 1712644, "author_name": "atulverma", "author_url": "", "post_date": "03/05/2022 06:23:36", "content": "*
\n\n\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.*
\n
If the return is for any reason other than size, another user may still buy it. Also, as others have shown with customers making repeat purchases it may work even if for purchased for a better size.
\nYes, in real life, this might be something H&M might look into if a particle article or those belonging to a category are having unusual returns.
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "1699813": "In our data we have a transactions table. This table contains the information about the purchased items by different users. However, according to the discussion in the thread for [this post](https://www.kaggle.com/c/h-and-m-personalized-fashion-recommendations/discussion/305952) :\n\n> Q: Hello @fridarimark , thanks a lot for hosting and for the explanations!\n>\n> I have a question to the data:\n> In the data we have a table of transactions. Those are in principle sold items. However, [this article](https://www.cnbc.com/2019/01/10/growing-online-sales-means-more-returns-and-trash-for-landfills.html#:~:text=Average%20return%20rates%20vary%20by,30%20to%2040%20percent%20returned.) from 2019 shows that that up to 30% - 40% of cloths and shoes bought online are being returned.\n> \n> Is the transactions table already cleaned from the returns?\n>\n> Answer: The transaction table holds all transactions that happened whether returned later or not.\n\nThe transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.\n\nThat means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.", "1700735": "> The transactions also contain returns. Meaning, if a user has ordered some article and then returned it back, it is not deleted from transactions and not marked as a refund.\n\nDoes that mean the transaction table lists a returned item twice, once when it was originally bought and once when it is returned?", "1701639": "Hallo @melanie7744, As I have understood, it is listed only once but you don't know if this item was later returned or not.", "1712644": "*\n> That means, that if one user has bought an item, it might not be the best idea to recommend exactly the same item to another similar users, as quite some part of them was returned. The other similar user might have a better knowledge of own size and style and not order the articles from the beginning.*\n\nIf the return is for any reason other than size, another user may still buy it. Also, as others have shown with customers making repeat purchases it may work even if for purchased for a better size.\n\nYes, in real life, this might be something H&M might look into if a particle article or those belonging to a category are having unusual returns." }, "source": "meta" }