> ## 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.

# Managing Status

Update package availability status to reflect current sales pipeline stages.

## Package Statuses

| Status | Description | Cascade Behaviour |
| - | - | - |
| **Prerelease** | Not yet available for sale | New items inherit from Project |
| **Available** | Ready for sale | Default status |
| **On Hold** | Reserved by an agent | Linked packages get "linked hold" |
| **Under Offer** | Contracts being negotiated | Archives other packages on lot |
| **Under Contract** | Contracts exchanged | Archives other packages on lot |
| **Sold** | Sale completed | Archives other packages on lot |
| **Archived** | Hidden from all views | Preserved for sold packages |

## Changing Status

### Single Package

1. Open the package
2. Click the **status button**
3. Select the new status
4. For **On Hold**: Select the agent and duration
5. Confirm the change

### Bulk Status Change

1. Go to **Packages**
2. Select multiple packages using checkboxes
3. Use the bulk actions menu
4. Choose **Change Status**
5. Select the new status

## Status Flow

Typical progression:

```
Prerelease → Available → On Hold → Under Offer → Under Contract → Sold
```

You can move status backwards if a deal falls through.

## Status Cascade Behaviour

Kenekt automatically manages related items when status changes.

### Prerelease Inheritance

Setting a **Project** to Prerelease:

* **New** Lots created under the project inherit Prerelease status
* **New** Packages created under those lots inherit Prerelease status
* Existing lots and packages are **not changed**

### On Hold Cascade

When a package goes **On Hold**:

* The **Lot** status changes to On Hold
* Other packages on the same lot show **"linked hold"** status
* When the hold expires or is released, linked packages return to Available

### Under Offer / Sold Cascade

When a package goes **Under Offer** or **Sold**:

* Other packages on the **same lot are archived**
* Only one package per lot shows the correct sales status
* This ensures accurate reporting and prevents confusion

### Archive Cascade

When archiving a **Project**:

* All Available lots and packages are archived
* **Sold packages are NOT archived**: preserves sales history
* Maintains data integrity for reporting

## On Hold Details

When placing a package On Hold:

1. **Select the agent** who requested the hold
2. **Set the duration** (days)
3. The agent receives an **email notification** with hold details
4. Package **automatically returns to Available** when duration expires

See **Deal Workflow** for full hold management details.

## Portal Visibility

Configure which statuses appear in the agent portal:

1. Go to **Agency Settings** → **Agent Portal**
2. Select which statuses to show
3. Save changes

## Automatic Status Changes

Some status changes happen automatically:

* **Hold created** → Status changes to On Hold
* **Deal progresses** → Status follows deal stage
* **Hold expires** → Status returns to Available
* **Under Offer/Sold** → Other lot packages archived

## Tips

* Archive packages instead of deleting them
* Use Prerelease at Project level to cascade to all stock
* Configure portal visibility based on your sales process
* Only one package per lot can be Under Offer or Sold


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