A report on defective goods can cross member, structure and supplier. The route should retain the elements necessary to recognize the product, problem and actions already carried out. Security obligations and specific procedures require appropriate expertise; the organisation must allow for a timely response.
I propose to distinguish the essential data from the additional descriptions. The report must arrive at the responsible team without unnecessary steps. The person who sent it should know the status of the verification and the relevant instructions, avoiding local initiatives based on incomplete information.
In a hypothetical example, multiple stores detect similar damage on the same supply. Connecting reports can help you understand the perimeter of the problem. A total aggregate lacking references to the goods could, on the other hand, hinder verification and subsequent actions.
The review of the process observes timing, requests for additional information, and problems that remain open. Information must be treated according to its nature. A common path is useful when it allows to act on recognizable facts and keeps clear who must provide indications to the members involved.