-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Filter free products from reports #5596
Comments
@kloon what do you think? Are free products an annoyance for woo.com? |
@mikejolley Not really, however we do not use the built in product reports that much, we use Google analytics for tracking sales data per product which allows us better filtering. I would not say remove them altogether, perhaps a filter rather if there is not one already? |
@mikejolley been thinking about this now, what about we do it like this http://cld.wthms.co/HkDL, so have top sellers only list paid products and add a separate tab for the top sellers of free products? |
What I like about the screenshot @kloon posted is that it's easy to see stats on both paid and free items. Both are important depending on what someone is looking for at the time. There is probably little value in having them combined so that separation works well. |
I have tested the patch in my store and can confirm that it is working well. |
I have a WC store with both for sale products and free downloadable items. The free products throw off the reports because there are many more "purchases" so they’re always shown as top sellers. For example, looking my product sales for this month, only two of the twelve top sellers are not free items.
It would be helpful to have the ability to filter out the free stuff to better see what is truly a top seller. It may also be that a more general solution allowing filtering by price, category, or status would be the way to go.
What do you think, is this core or plugin territory? I'm willing to attempt a solution but any pointers for the best way to tackle it are welcome.
The text was updated successfully, but these errors were encountered: