jaycmb
commented
3 years ago I think "simply" adding the Code Field to the https://openfoodnetwork.org.uk/admin/orders page could be done as Papercut, but we need to take into account whcih is why I would say needs careful consideration and is not a Papercut
- There is a another Papercut asking for adding a columns for first and last name https://github.com/openfoodfoundation/wishlist/issues/3 -> so 3 more columns will break the page without implementing a column selector
- The Code field would also need to be added to the search options, requiring design
- Understand use case: is using the code field for company name workaround a universal thing that users do across instances?
What is the need / problem?
Hubs selling wholesale sell to businesses not individuals, but at present they can only search for orders by an individual's name. Hubs that sell to businesses often add the business name (restaurant name, institution name...) in the 'code' field in their customer list. But they can't find invoices by business name.
Which type of users does this problem affect (and how many, if known)?
MCFEs - especially those selling wholesale to businesses versus (or in addition to ) individual consumers
e.g. - Shoppers - Hub Managers (MCFEs) - Producers - Instance Managers - Other (Please specify)
Potential solutions that will solve the problem ?[[brainstorming to list feature candidates]
Bring the 'code' field onto the orders search page - so the manager can enter the business name and search for invoices.
Connected wishlist and discovery discussions* [list precedent discussions]
There is another candidate - wishlist #3 that deals with order searching/filtering.
Additional context
Is Papercut or feature candidate?
Add papercut or feature label to answer the question. If you are not sure, don't worry product team will cover :-)