> ## Documentation Index
> Fetch the complete documentation index at: https://help.kenekt.app/llms.txt
> Use this file to discover all available pages before exploring further.

# How Inclusions Cascade

> Where a package's inclusion packages come from, which items are featured on its flyer, and in what order.

Inclusion packages are added at different levels, and each package (a build on a lot) picks up everything above it. Changes at a level show on every package below it straight away; there is nothing to sync.

## Where a package's inclusions come from

```mermaid theme={null}
flowchart TD
  L[Library] -.offers packages to.-> P[Project]
  L -.-> Lt[Lot]
  L -.-> D[Design]
  P --> Lt
  Lt --> B[Package]
  D --> B
  A[Agent upgrades] -.added for that agent.-> B
```

| Added on | Shows on |
| - | - |
| A project | Every lot and package in the project |
| A lot | Every package on that lot |
| A design | Every package that uses the design |
| A package | That package only |
| An agent | Every package that agent sees: their prices, brochures and portal include them |

A package always shows its inclusions grouped by where they come from: **On this build**, **From the design**, **From the lot**, **From the project** and **From the BDM**. Packages that come from above are changed where they were added, not on the package.

<Tip>
  Each package is counted once in the price, even if it is added at more than one level.
</Tip>

## Featured items

Featured items are the inclusions listed on the flyer, brochure and portal. They follow four rules:

1. **The library decides.** An item ticked as featured in the library is featured on every package that includes it.
2. **Choices flow down, never up.** Featuring or unfeaturing an item on a design, lot or project applies to every package below it. A change on a package stays on that package.
3. **The nearest choice wins.** A package's own choice beats its design or lot, and theirs beat the library.
4. **When a design and a lot disagree, hidden wins.**

### Example

The "Standard Inclusions" package in your library features *2,440mm ceilings* and *Stone benchtops*. It is added to the *Acacia* design.

* Every Acacia package features both items.
* On the package at Lot 12, you untick *2,440mm ceilings* and tick *2,590mm ceilings* from your "Upgrade List" package. Only Lot 12 changes.
* Later you untick *Stone benchtops* in the library. It disappears from every Acacia package, including Lot 12.

## Featured order

Featured items follow the library's order unless you change it.

* **Designs, packages and agents** can be re-ordered by dragging, in **Featured order**. A new package starts in its design's order.
* **Lots and projects** can't be re-ordered; re-order on each package instead.
* **Your own picks go to the top.** Items a package features that its library doesn't (like *2,590mm ceilings* above) and items from its custom packages go first, newest on top, so you don't have to drag them up. Once you drag an item into place, it stays there.
* **Reset to library order** drops a package's own order and follows its design again.

## Agent upgrades

An agent's upgrade packages are added to every package that agent sees: their prices, brochures and portal include them. On a package's Inclusions page, the BDM's upgrades show under **From the BDM**.

On the agent's Inclusions page, choose how their featured items mix with each package's:

* **Combine**: the agent's featured items come first, then the package's.
* **Replace**: only the agent's featured items show, unless the agent has none.

The choice applies on the brochure and in the portal.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.