Quality incident QI-2026-00033 under investigation: an ankle boot in cognac with a structural material defect of medium severity, the customer's description, the resolution notes, an activity log, a repair MTO order in production, and a return shipment in Draft carrying the boot.
The Quality Incidents listing with its filters: five incidents of a leather goods store, with their order, product, category and subcategory such as Functional Defect and Fit/Dimensions, severity, incident date, state from Open to Closed, and the transition buttons of each state.
The Create return shipment dialog for QI-2026-00034 on order 52511: Repair selected, the shipment item Leather tote - Black × 1, the customer's address in Braga, and Free shipping as the shipping method.

Commerce Quality Incident is for Drupal Commerce stores that need to follow a product defect from the customer's complaint to its resolution. Each quality incident is linked to the order, the order item and the product variation, carries a category, a subcategory and a severity, and moves through a workflow from Open to Closed with its own activity log. Its sub-modules open the repair or replacement production order and create the shipment that takes the item back to the customer.

Features

  • 🛒 Incidents linked to the order. Each incident points at a Commerce order, one of its order items and the product variation, chosen in that order on the incident form. An incident type can require the order or allow incidents without one. The order's page lists its incidents.
  • 🏷️ Categories, subcategories and severity. Categories come from a plugin chosen per incident type: generic products (manufacturing, material, functional and other defects) or footwear and bags, each with its own subcategories. Site code adds plugins with a PHP attribute. Severity goes from Low to Critical.
  • ⚙️ A workflow for the quality team. Open, Investigating, Resolved and Closed, with reopening, or any State Machine workflow per incident type. Transitions are buttons on the incident and on the listing, confirmed in a dialog, and closing an incident asks for its resolution notes. Incident numbers come from a Commerce number pattern, QI-2026-00001 by default.
  • 📊 A listing and an activity log. The listing filters incidents by number, state, severity and order. Each incident keeps a timeline of its creation, its transitions and what was done for it.
  • 🧩 QI-MTO Integration sub-module. With Commerce Make-to-Order, opens the repair or replacement production order from the incident, with its priority taken from the severity, and lists the incident's production orders on its page.
  • 🧩 QI-Shipping Integration sub-module. With Commerce Shipping, creates the shipment that takes the repaired or replaced item back to the customer, on the incident's order and carrying its order item, even when that item already traveled on another shipment. An event lets site code fill its own fields on the shipment before it is saved.

 an ankle boot in cognac with a structural material defect of medium severity, the customer's description, the resolution notes, an activity log, a repair MTO order in production, and a return shipment in Draft carrying the boot.

Quick start

composer require drupal/commerce_quality_incident
drush en commerce_quality_incident
  1. At Commerce > Configuration > Quality incident types, edit Default and check its workflow, number pattern, incident category plugin and default severity.
  2. At Commerce > Quality Incidents, click Add quality incident.
  3. Choose the order, the order item and the defect category and subcategory, describe the defect, and save.
  4. The incident opens as QI-2026-00001, in Open, with a Start Investigation button and its creation in the activity log.

 five incidents of a leather goods store, with their order, product, category and subcategory such as Functional Defect and Fit/Dimensions, severity, incident date, state from Open to Closed, and the transition buttons of each state.

The quality team's listing, newest incidents first.

 Repair selected, the shipment item Leather tote - Black × 1, the customer's address in Braga, and Free shipping as the shipping method.

The return shipment of a leather tote whose handle is restitched.

Good to know

  • One return shipment per incident is active at a time. It is created in the first state of the shipment workflow with the first rate of the chosen method, and it is not sent to the carrier: staff check it and send it from the shipment's operations.
  • The return shipment goes to a copy of the order's shipping address, so deleting it never deletes the address the order's other shipments use.
  • Creating a return shipment needs the sub-module's permission, update access to the incident, and permission to manage shipments of the order's shipment type.

Additional requirements

  • Drupal 10.3 or later, or 11, and PHP 8.1 or later.
  • Commerce Core 2.33 or later, or 3, with its Order, Product, Log and Number Pattern modules.
  • State Machine 1.

Recommended modules/libraries

  • Commerce Make-to-Order: production orders for stores that make what they sell, which the QI-MTO Integration sub-module opens from an incident.
  • Commerce Shipping: shipments, which the QI-Shipping Integration sub-module creates for the item going back to the customer.
  • Commerce Order Amend: amends a placed order, for instance to swap the item for another variation, when a resolution changes what is delivered.

Community documentation

  • README: incident types, number patterns, the workflow, category plugins, the API, and the two sub-modules, each with a README of its own.

Supporting this module

Developed and maintained by Bloomidea. Bloomidea offers support and custom development for this module.

Supporting organizations: 
Development and maintenance

Project information

Releases