POET is not designed to serve as the system of record for regulated processes, therefore not subject to GxP requirements. It is designed to enable cross-organizational collaboration and process orchestration, while the system of record for each process remains within the respective enterprise systems.
Type = Troubleshooting,; Topic = Multienterprise Information Network Tower (MINT),;Persona = TraceLink Administrator, User,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = Supply Chain, IT, Procurement,
Product Complaint
Product complaint includes issues reported by customers, healthcare providers, distributors, or internal stakeholders about a pharmaceutical product.
What is product complaint handling
Product Complaint Handling is a regulated quality and pharmacovigilance process where issues reported by customers, healthcare providers, distributors, or internal stakeholders about a pharmaceutical product are logged, investigated, and resolved. These complaints may involve product quality defects, packaging errors, labeling mistakes, adverse drug reactions (ADRs), or distribution failures.
Types of product complaints
-
Product Quality: Covers defects that affect the physical characteristics of the drug product.
-
Packaging Defect: Encompasses issues with the external or protective packaging.
-
Labeling Error: Applies to inaccuracies or omissions in printed or affixed labels.
-
Adverse Drug Reaction: Refers to unexpected or harmful responses experienced after using the drug as prescribed.
-
Distribution Issues: Concerns linked to the supply chain and product delivery.
-
Counterfeit or Fraud: Suspicion or confirmation of falsified products in the supply chain.
-
Other: Covers all complaints that do not fit into the standard categories. Examples include user or operator error, duplicate complaint submissions, or issues that fall outside the defined scope of product, packaging, labeling, ADR, distribution, or fraud.
How to use the product complaint marketplace solution
Before using the product complaint marketplace solution, Solution Designers must first configure the solution in Opus Solution Environment (OSE) by following the steps listed below:
Solution Designers must first save the latest version of the marketplace solution from the marketplace catalog as a company solution.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select .
- On the Search Solutions page, Filter the list of solutions to find the required solution.
- Find the latest version of the solution and select the to open the solution.
- On the Solution Details page, select .
- On the Save As panel, fill in the following fields:
- field – The name of the solution that will be saved as a company solution.
- field – (Optional) The description of the solution.
- Select .
The marketplace will be saved as a company solution in the Available tab on the left menu.
After saving the solution to Company Solutions, Solution designers must create a network for the solution from OPUS Administration.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select the New
button. - In the Network Information section, fill in the following fields:
- drop-down – Select the application for which you want to configure the marketplace solution. For e.g. Process Orchestration for Empowered Teams.
- field – The name of the network being created.
- field – (Optional) The description of the network being created.
- In the Solution section, fill in the following fields:
- toggle – This value must be no as the solution for which the network is being created is a marketplace solution.
- field – Select the solution that you saved as a company solution in the previous procedure.
- Select the Save
button.
The new network is created and the solution is ready for use.
After creating a network for the solution, Solution Designers must define roles for accessing the network.
- Select the Main Menu
icon. - Select .
- Select from the left menu.
- Select from the left menu.
- On the Search Network Members page, filter the list of network members by the network created in the previous procedure.
- Select the user email of the user who created the network.
- Select the Edit
button. - In the Roles section, select the role required to access the network.
- Select the Save
button.
The role to access the new network is configured.
For more information about configuring or customizing marketplace solutions as per your business needs, see OPUS Solution Environment Help Center.
Add a product complaint
By default, a product complaint is created by a set of basic fields, which are widely used. However, depending on your business needs, you may need to include additional fields in the product complaint. To include additional fields, edit the product complaint to view all available fields and update the required fields.
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the (e.g. your entire company or a Link to a specific Partner or internal location) drop-down in the header.
- Select .
- Select from the left menu.
- Select the New
button. - In the General section fill in the following fields:
- field – The title of the new product complaint.
- field – The description of the product complaint.
- Select the Save
button.
The product complaint is created in the Draft state. - To move the product complaint to To Do state, select the Move to
button.
Modify a product complaint
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the (e.g. your entire company or a Link to a specific Partner or internal location) drop-down in the header.
- Select .
- Select from the left menu.
- Select the Display Identifier of the product complaint to edit.
- Select the Edit
button.
In addition to the fields updated when creating the product complaint, additional fields will be displayed which can be updated if required. - In the General section update the following fields:
- field – The display identifier of the product complaint.
- field – The title of the product complaint.
- field – The level of priority for the product complaint. Select from Low, Medium, High, and Critical.
- field – The source of the product complaint. For example: Company Websites, Email, Regulatory Authority Portals, etc.
- field – Indicates if this been submitted to PV authorities.
- field – The type of the product complaint. For example: Product Quality, Packaging Defect, Labeling Error, etc.
- If you selected Product Quality in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Physical Appearance Issue, Contamination (Particulate/Microbial), etc.
- field – The batch involved in the complaint.
- field – Indicates if a physical sample is available.
- field – Observations from physical inspection.
- field – Indicates whether lab analysis is needed.
- If you selected Packaging Defect in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Damaged Packaging, Improper Sealing, etc.
- field – The type of packaging which is defective.
- field – The batch or lot involved in the complaint.
- field – Indicates if the defect affects label clarity.
- field – Indicates if the product insert was included.
- If you selected Labeling Error in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Incorrect Product Name, Incorrect Strength / Dosage, Mismatched Batch or Expiry Info, etc.
- field – The correct label that was intended for the product.
- field – The type of label.
- field – Indicates if the complaint requires regulatory notification.
- If you selected Adverse Drug Reaction (ADR) in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Unexpected Side Effect, Lack of Efficacy, Allergic Reaction, etc.
- field – The age of the affected patient.
- field – The gender of the affected patient.
- field – The description of the adverse event.
- field – Indicates whether hospitalization or treatment was needed.
- field – Indicates if this been submitted to PV authorities.
- If you selected Distribution/Delivery Issue in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Cold Chain Violation, Shipment Delay, Damaged During Transport, etc.
- field – The name of the logistics provider.
- field – The shipment tracking ID.
- field – The date the shipment was received.
- field – Indicates if temperature log is available.
- field – Description of product state upon delivery.
- If you selected Counterfeit/Suspected Fraud in the Category drop-down, add the required sub-category information:
- field – The sub-category of the selected category. For example: Falsified Product Appearance, Suspected Tampering, Product Not Matching Label Claims, etc.
- field – Indicates where the product was obtained.
- field – The description of why the product is suspicious
- field – Indicates if this been reported to a health authority.
- field – Indicates if a verification test was performed.
- If you selected Product Quality in the Category drop-down, add the required sub-category information:
- field – The date when the issue was observed.
- field – The due date of the product complaint.
- field – The detailed description of the product complaint.
- field – Indicates if a physical sample is available.
- field – Supporting documents or images if any.
- If you require to collaborate with an external partner, enter the details under the Participants section:
- field – The name of the company that created the product complaint. This field is automatically populated with the logged-in user.
- field – The name of the Partner company that is assigned to take action on the product complaint.
- In the Product Information section, add information about the impacted product in the following fields:
- field – The name of the impacted product.
- field – The item code type of the impacted product.
- field – The item code value of the impacted product.
- field – The GTIN of the impacted product.
- field – (Optional) The batch or lot number of the impacted product.
- Select the Save
button.
The product complaint is updated.
Owners can edit the Assignee Details section while the batch record review is in the Draft state. Once the work item moves to the To Do state, the Assignee Details section can be edited only once.Monitor product complaint
A high level understanding of the state of all product complaints that you have access to.
- Select the Main Menu
icon. - Select .
- Select a [POET Network] from the drop-down in the header.
- Select a Partner or location from the (e.g. your entire company or a Link to a specific Partner or internal location) drop-down in the header.
- Select .
- Select from the left menu.
- Select the Filter
button. -
In the Filters panel, fill in one or more of the following fields to filter the results:
- field – The status of the product complaint.
- field – The user who is assigned the complaint.
- field – The user who created the product complaint.
- field – The name of the affected product.
- drop-down – The batch or lot affected.
- drop-down – The severity of the product complaint.
- field – The type of complaint.
- field – The person who filed the complaint.
- field – The date when the complaint was created.
- field – The date when the complaint was last modified.
-
Select .
All product complaints matching the filter criteria are displayed.
Tag end


