> For the complete documentation index, see [llms.txt](https://docs.silkline.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.silkline.ai/profile-and-settings/organization-settings/quality-clauses.md).

# Quality Clauses

Create reusable quality clauses (e.g. C of C, DFARS, DPAS) that flow down to suppliers on RFQs and POs based on category and item matches

Quality Clauses define the quality and compliance requirements that apply to RFQs and purchase orders. Each clause includes a unique code, title, and description, and can be tailored to your organization's standards.

* **Relevant clauses automatically appear on both RFQs and POs**, ensuring suppliers see all applicable requirements up front—no surprises after award.
* Clauses can include inspection requirements, documentation needs (e.g. Certificate of Conformance), or other quality instructions.
* A clause is the requirement text on the RFQ or PO, not the certificate itself. Silkline does not store certificate files on the clause or the part, and does not package certificates across a BOM.

{% hint style="info" %}
Quality clauses are part of **Quality Controls**, an Advanced capability that Silkline turns on for your organization. See [Pedigree Management](https://docs.silkline.ai/profile-and-settings/organization-settings/pedigree.md#quality-controls).
{% endhint %}

## Managing Clauses

* Click **Create Quality Clause** to add a new clause, or click the vertical three dots on a quality clause to edit that quality clause. Clauses are created only on this page; the quality clause pickers on requests select existing clauses.
* Each clause must have a **unique code** (e.g. QC-001) and title.
* Clauses can be **edited or archived** as your requirements evolve.
* Set **Required shipping documents** on a clause when you create or edit it. See [Required shipping documents](https://docs.silkline.ai/orders/shipments.md#required-shipping-documents).

### Viewing clauses

The **All Quality Clauses** table lists every clause:

* Columns show each clause's **Number**, **Title**, **Content**, and **Status** (Active or Archived), plus one column per integration that syncs quality clauses
* **Orders**, **Requests**, and **Parts** count the order lines, request lines, and parts that carry the clause. Click a count's header to sort by it
* **Required Shipping Documents** lists the document types each shipment line needs for an order line with the clause
* Search matches a clause's number, title, or integration ID
* The **Status** filter shows only active or only archived clauses
* The row menu offers **Edit** and **Delete**

### Bulk editing and merging clauses

With [data cleaning mode](https://docs.silkline.ai/administration-tools/data-cleaning-mode.md) on, the clauses table shows a checkbox on every row:

* Select clauses, click **Edit**, and set **Archived** to archive or unarchive them all at once
* Select clauses and click **Delete** to remove them permanently
* Select exactly two clauses and click **Merge** to combine duplicates — see [Merging Duplicate Records](https://docs.silkline.ai/administration-tools/merging-records.md)

{% hint style="info" %}
Quality Clauses can also be used to flow down end-customer requirements to suppliers, such as DFARS requirements or DPAS ratings.
{% endhint %}

{% hint style="info" %}
Quality clauses can be made **mandatory for specific pedigrees** (e.g. T1 – Flight). When a pedigree requires quality clauses, order line items using that pedigree must include at least one. See [Pedigree Management](https://docs.silkline.ai/profile-and-settings/organization-settings/pedigree.md#require-quality-clauses).
{% endhint %}

## Pulling Clauses from an Integration

When your organization has an integration that syncs quality clauses into Silkline (for example, First Resonance ION), a **Pull** button with the integration's logo appears next to **Create Quality Clause**. Click it to fetch all quality clauses from the connected system. The sync runs in the background and new clauses appear shortly after it finishes. Pulling requires permission to edit integrations.

<figure><img src="https://2684497859-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwPsevXC0g5kNMF7GTyPN%2Fuploads%2Fgit-blob-0c90be735b536ed2462d9807414253d3b31ec604%2Fquality-clauses-pull-button.png?alt=media" alt="Quality Clauses settings page with the ION Pull button next to Create Quality Clause"><figcaption><p>Pull quality clauses from a connected integration</p></figcaption></figure>
