# Log and track customer complaints in Breww **URL:** \ **Category:** Breww announcements\ **Created:** [14 September 2026 09:15 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365 "2026-09-14T09:15:47Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\ **Post date:** [14 September 2026 09:15 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/1 "2026-09-14T09:15:47Z")
You can now record customer complaints against the order, product and batch involved, work them through to a resolution, and raise credit notes or ullage the affected stock without leaving the complaint. Categorise your complaints and the report builder will show you what goes wrong most often. [Learn more](https://breww.com/docs/customer-complaints/). ---
**Author:** ![barry-labendz](https://community.breww.com/letter_avatar_proxy/v4/letter/b/82dd89/32.png) [@barry-labendz](https://community.breww.com/u/barry-labendz)\ **Post date:** [14 September 2026 23:50 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/2 "2026-09-14T23:50:11Z")
Is it feasible to have complaints able to be generated/viewed from the delivery screen as well? ---
**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\ **Post date:** [15 September 2026 08:10 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/3 "2026-09-15T08:10:32Z")
There should already be a **Log complaint** button in the top-right of the main delivery page. If this what you’re looking for? ![image](https://breww-community.fra1.digitaloceanspaces.com/original/2X/d/d3e546fb2a2bee160f1e4152e430fe3db055a94c.png) If not, where did you have in mind? ---
**Author:** ![greg-pritchard](https://community.breww.com/user_avatar/community.breww.com/greg-pritchard/32/141_2.png) [@greg-pritchard](https://community.breww.com/u/greg-pritchard)\ **Post date:** [17 September 2026 10:52 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/4 "2026-09-17T10:52:13Z")
This is great! Would it be possible to add the option to have certain specified users notified when a complaint record is logged? This is a fairly essential step in our current QC process, to ensure that the relevant departments and team members are able to action the required next steps promptly. ---
**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\ **Post date:** [17 September 2026 16:18 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/5 "2026-09-17T16:18:26Z")
I’m sure that would be possible, Greg, and it’s a great idea. Would you mind posting this in #Ideas & feature requests so we can keep track of it properly? I don’t want this to get lost in the comments here on the announcement. Cheers ---
**Author:** ![tom-goodingham](https://community.breww.com/user_avatar/community.breww.com/tom-goodingham/32/1772_2.png) [@tom-goodingham](https://community.breww.com/u/tom-goodingham)\ **Post date:** [23 September 2026 13:38 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/6 "2026-09-23T13:38:22Z")
Hello, I think there are a couple bits slightly needing a tweek. - If a mistake is made with generating a log, there is no way to go back or delete once in progress. - Service Complaint - you should **NOT** have to choose a product/SKU when this type has been selected. There potentially is multiple Order items affected by a service failure. We’re very happy this has been implemented, will help centralise our processes. Cheers, Tom p.s. I did think about whether multiple products should be chosen per log, but makes sense to assume an issue is unique within an order. Two line items may have faults within a single order, but they’re independent when considered as a product/batch fault. Therefore require 2 logs. ---
**Author:** ![luke](https://community.breww.com/user_avatar/community.breww.com/luke/32/3636_2.png) [@luke](https://community.breww.com/u/luke)\ **Post date:** [24 September 2026 12:45 UTC](https://community.breww.com/t/log-and-track-customer-complaints-in-breww/7365/7 "2026-09-24T12:45:26Z")
Thanks for the feedback, Tom. It’s great to hear this has been helpful. Regarding your suggestions: > [@tom-goodingham](#): > > If a mistake is made with generating a log, there is no way to go back or delete once in progress. This is intentional. We did this to ensure there is an immutable log on complaints for auditability. If you’d like this to change, can you please open a feature request? > [@tom-goodingham](#): > > Service Complaint - you should **NOT** have to choose a product/SKU when this type has been selected. There potentially is multiple Order items affected by a service failure. This is already the case. For service complaints you can optionally associate it with an invoice/product/batch but you don’t have to. Those three fields are optional for service complaints. > [@tom-goodingham](#): > > p.s. I did think about whether multiple products should be chosen per log, but makes sense to assume an issue is unique within an order. Two line items may have faults within a single order, but they’re independent when considered as a product/batch fault. Therefore require 2 logs. This was exactly our thought too. Thanks again for the feedback.