Hide users that have never purchased from customer reports

+1

Does it really matter when you can sort the columns so customers with no orders are at the bottom?

What if you wanted to find customers who have registered, but never made an order?

In my case it's important. Mine is a site where there are hundreds of regular users who will never become buyers and hundreds of e-commerce customers.

OK, so this is a feature request, although note that #502356: Expand Customer Search Page to Include Users Without Orders is asking for the opposite!

New features should go into 7.x-3.x first.

view is customizable? why would we still need it in 7.x? users should adjust view to their specific needs with views ui....

In 7.x this is already the case according to #1417736: Customers Do not appear until they have an order so back to 6.x for this one. Not convinced we can please everybody, though.

Wait, this is talking about the report, not the customer listing, although perhaps the two should be merged as they basically show the same things..

A customer is different from a site user, but that difference is not reflected in Ubercart. I tried to get that distinction put in during the D5->D6 port but it was rejected. It's necessary if we want true anonymous checkout, which requires creating a customer who does not have a site account. Right now, customers are just site users who have an order, but the schema is such that you have to search the orders table to compile a list of customers - there is no table relating users and orders.

Ubercart admin pages should usually manage customers only, not general users. The exception would be places like creating a new order administratively, where you want to be able to create an order for any existing site user, not just for previous customers. I think that this is the way it works now in 7.x-3.x *except* for the customer reports.

Reports have not yet been replaced by Views in 7.x-3.x, so they cannot be arbitrarily customized. Rather than patching reports to exclude users without orders, I think it makes sense to put the effort into converting the reports to views so they will be more useful.

Regardless, the behavior described by the original poster still exists in both 6.x-2.x and 7.x-3.x, and if any work is going to be put into fixing this it should be put into 7.x-3.x first then backported if desired and if the D6 branch is still open by the time this gets fixed.

New features need to go into 8.x-4.x first, then get backported if there is sufficient interest. Because Drupal 6 is almost obsolete, it is highly unlikely this will be added to Ubercart for D6.