Commerce Quality - Manage Inspections, NCRs, and Quality Holds

Can Quality Management Really Be This Automated?

Those of us working in supply chain or production management all share the same feeling: quality inspection, while seemingly simple, is incredibly tedious in practice. Every time a shipment arrives, inspection results must be manually recorded. When defective items are found, a Non-Conformance Report (NCR) has to be issued, then it goes to leadership for approval, and finally a decision is made on whether to rework or return the goods. The entire process relies on Excel and email, which is not only inefficient but also prone to errors. I recently discovered a skill called Commerce Quality, which is practically a lifesaver for quality professionals. Today, let's talk about what it can actually do.

What Does This Skill Do?

In simple terms, it's a tool specifically designed to manage the quality inspection process. You can use it to create inspection orders—whether it's incoming inspection, in-process checks during production, or inspections of customer returns, all of these can be created. Then, you can record the inspection results for each material item one by one, marking them as pass or fail, and even attaching defect codes if there are any issues. Once the inspection is complete, if non-conformances are found, it can automatically generate an NCR for you, documenting the problem. Even better, it can implement a quality hold on inventory to prevent those problematic goods from being shipped out by mistake.

Let me give you a practical example. Suppose we receive a shipment, PO-100, which contains a material with the SKU WIDGET-BLK. I just need to enter the following command in the command line:

stateset --db ./store.db "create inspection type=Receiving po_id=PO-100 sku=WIDGET-BLK" --apply

An inspection order is created right away. Next, after inspecting the batch and finding a few cosmetic defects, I can record that with:

stateset --db ./store.db "record inspection result inspection_id=INS-001 result=Fail defect=Cosmetic" --apply

The system will automatically mark this inspection as failed and link the defect type to it. Then, I can directly create a quality hold to prevent this batch from being moved:

stateset --db ./store.db "create quality hold sku=WIDGET-BLK reason='Pending re-inspection'" --apply

The whole process flows seamlessly without the need to manually fill out any more forms.

Status Workflows and Disposition Options

In my opinion, the most valuable part of this skill is that it standardizes the various states in quality management. For example, inspection statuses include: Pending, InProgress, and the final results can be Pass, Fail, or ConditionalPass. The NCR statuses are also very detailed: Open → UnderReview → PendingDisposition → CorrectiveAction → PreventiveAction → Verification → Closed, and of course, it can also be Cancelled. Quality hold statuses include: Placed → UnderReview → Released or Escalated.

The benefit of this standardization is that everyone on the team can clearly understand what stage they're currently in and what the next step should be. Furthermore, it supports severity levels: Critical, Major, Minor, and Observation, along with corresponding disposition options: UseAsIs, Rework, Repair, Scrap, ReturnToVendor, Downgrade, and SortAndScreen. These are all common terms in quality management, making the tool very intuitive to use.

A Few Practical Tips

When using this skill, there are a few small details to keep in mind. First, write operations (such as creating inspections, recording results, or creating quality holds) all require the --apply parameter to actually take effect. If you're just testing, you can omit it, which prevents accidental changes. Second, if you want to see which inspections have failed, you can simply use stateset --db ./store.db "list inspections status=Fail", which is very convenient. Third, if you encounter issues—for example, an inspection cannot be completed, it might be because there are still materials that haven't been inspected; if a quality hold is blocking shipments, you'll need to release the hold or move the goods to a quarantine area; if an NCR seems stuck, check whether the corrective action and verification steps have all been completed.

An Overview of Common Error Codes

The error code handling is also thoughtfully designed. For example:

• INSPECTION_INCOMPLETE: All materials must be inspected before the inspection order can be finalized.
• HOLD_BLOCKING_SHIPMENT: A quality hold is preventing inventory movement; it needs to be released or rerouted first.
• NCR_DISPOSITION_INVALID: The current severity level of the NCR does not permit the use of this disposition option.

When you see these error codes, you can quickly pinpoint the problem instead of guessing blindly.

How to Install It?

Installation is also straightforward. If you already have npx installed, simply run the following command:

npx skills add github.com/stateset/ic...