> 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/coverage-segmentation.md).

# Coverage Segmentation

Keep supply matched to the right demand using fields such as project.

Use Coverage Segmentation to keep supply for one project from counting toward another project's demand. Choose a configurable field, such as **Project**, and Silkline counts supply toward a demand line only when their field values match. Each field you add is called a **segment**.

For example, demand for **Project A** can be covered by supply tagged **Project A**. Supply tagged **Project B** does not count, even for the same part and quantity.

**Need date** is a segment for every organization. It sits at the top of the table alongside the fields you add. See [Need date](#need-date) below.

## Need date

Supply counts toward a demand line only when the supply is needed on or before the date the demand needs it. A blank need date counts as the far future: a demand line with no need date accepts any supply, and supply with no need date covers only demand that also has none. Need date is always a segment: it appears first in the Coverage Segmentation table and has no remove action.

Its **Bin** sets which demand lines merge into one line when you promote demand to a request or order. Lines whose need dates fall in the same bin raise a single line, dated the earliest of them.

Its bin starts at **Day**, so each date raises its own line. Widen the bin to raise fewer, larger lines:

1. Go to **Organization Settings** → **Plans** → **Coverage Segmentation**.
2. In the **Need date** row, open the **Bin** list.
3. Choose **Day**, **Week (Mon-Sun)**, or **Month**.

The new bin applies as soon as you choose it and takes effect immediately. Changing it requires the same permission as adding a segmentation field.

Grouping demand does not widen coverage: supply still has to be needed on or before the demand it covers. Under a **Month** bin, demand needed 7 October and demand needed 30 October raise one line, and supply needed 21 October covers the demand needed 30 October but not the demand needed 7 October.

## Add a segmentation field

Coverage Segmentation is under **Organization Settings** → **Plans** and appears when **Enable Plans** is on. Enabling Plans requires administrator permissions.

Use a [Configurable Field](/profile-and-settings/organization-settings/configurable-fields.md) with type **Text**, **Select**, **Labeled Select**, or **Date**. Other field types are not available for segmentation. **Select** is recommended to keep values consistent across your team. A **Date** field also takes a **Bin** size, which sets which demand lines merge into one line when you promote demand.

1. Go to **Organization Settings** → **Plans** → **Coverage Segmentation**.
2. Click **Add Segmentation Field**.
3. Choose a field attached to **Demand Lines**, **Request Items**, and **Order Items**. If a field is missing any of these attachments, click **Attach & add** in the second list to attach it and add it as a segment in one step.
4. For a **Date** field, choose a **Bin**: **Day**, **Week (Mon-Sun)**, or **Month**. **Attach & add** stays unavailable until a bin is chosen.

The field takes effect immediately. A date field's bin is fixed once the field is a segment. To change it, remove the segmentation field and add it again. The **Need date** bin is the one you can change in place.

Each segment appears by default as a marked column in the [Demand](/demand.md) table. Use the column selector to hide it for your view.

{% hint style="warning" %}
**Review existing coverage when you add a segment.** Supply already counted toward a demand line continues to count, even if the segment values differ. Silkline does not recheck or flag these mismatches.

Review these demand lines and re-promote any whose existing supply should not count. There is no bulk action for this review.

Segmentation is checked when a request converts to an order, using the fields and bins in place at that moment. Adding, removing, or rebinning a field changes how requests that have not yet converted move their coverage to order lines.
{% endhint %}

## What always matches

Segmentation narrows which supply counts. Two requirements hold regardless of the fields you add:

* **Same part.** Supply for a different part does not count.
* **Same pedigree.** A different pedigree is a different part as far as coverage is concerned.

When several demand lines compete for the same supply, the demand line with the tightest need date is filled first.

## How values match

Supply and demand must match on every segmentation field.

* **Blank matches blank only.** Supply with no project value cannot cover demand tagged for a project.
* **Text is case-sensitive.** `Project A` and `project a` do not match. Spaces at the start and end of a value are ignored.
* **Select fields use a fixed list.** Everyone chooses from the same options, helping avoid differences in spelling or capitalization.
* **Dates match on the date itself.** Supply shares the segment with a demand line when the supply's date falls on or before the demand's. For a configurable date field, a blank date is its own value and matches only blank. For need date, a blank date counts as the far future (see [Need date](#need-date)).
* **A date bin groups demand; it does not widen coverage.** Bins follow the ordinary calendar: weeks run Monday to Sunday, and months are calendar months. Under a **Month** bin, supply dated 21 October covers demand dated 30 October, and does not cover demand dated 7 October. Need date bins the same way.

## Keep values aligned across your workflow

**Promoting demand to a request or order** copies the demand line's segment values to the new line automatically. Above the form, **Coverage plan** summarizes how many demand lines become how many new lines, and how many are not included. Expand it to see each preloaded line with the demand lines and quantities feeding it, any skipped demand with the reason it is skipped, and **Learn more** for grouping rules, coverage guidance, and examples. Once you save, it reports which demand the new lines cover and names any selected demand left open, along with the reason - a part or need date you edited, a segment value that differs, or a line you removed from the form.

For these workflows, check the values yourself:

* **Build plan runs:** Configure Build Plan Item custom fields and set values on each build plan item. A run copies values for matching Demand Line fields into generated demand, including segmentation fields.
* **Linking an existing order to a request:** Orders created separately or imported by an integration keep their own segment values. Coverage transfers from the request line to the order line only when the values match.
* **Read-only fields populated by an integration:** You can use these fields for segmentation, but corrections must be made in the source system. Manufacturo can populate a **Project** field on demand and request lines this way; see [Project configurable field](https://docs.silkline.ai/configuration/integrations/manufacturo#project-configurable-field).

## Remove a segmentation field

Click the trash icon next to the field and confirm. That field's values are then ignored when matching supply to demand. All other matching requirements still apply, and existing coverage stays in place. **Need date** has no trash icon; widen its bin instead.

Removing segmentation leaves the field attached to Demand Lines, Request Items, and Order Items. To remove any of those attachments, remove the field from Coverage Segmentation first.