> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/rules-and-customizations/rules-overview/keeping-add-ons-in-sync.md).

# Keeping Add-ons in Sync with Plan Dependencies

A **Plan Dependency** keeps one charge's quantity (or included units) automatically in step with another. Link an add-on to your base plan's seats once, and it scales with every change — so an add-on never drifts out of sync, and you never quietly under-bill.

{% embed url="<https://youtu.be/QB8MS21LfQw>" %}

**Where to find it**

Go to **Rules & Automation → Plan Dependencies**. Each dependency ties a **source** charge to one or more **targets**, and keeps them in step whenever the source changes.

**Build a dependency**

1. Select **New Dependency**.
2. **When this changes** — pick the source: the charge whose quantity drives the rule (for example, your Premium plan's **Seats**).
3. **Keep these in sync** — add the target charge that should follow (for example, an add-on's compute or storage blocks).
4. Choose how the target is calculated:
   * **Match exactly (1:1)** — target equals source (5 seats → 5 units).
   * **Multiply by a factor** — target = source × factor (factor 2, 5 seats → 10 units).
5. Set the **direction** (one-way, source → targets) and **activation** (always, or only when the target is present).
6. Save. The plain-English preview and worked example show exactly what will happen — try a value to see the math.

**What it looks like**

The **worked example** calculates a sample for you: with a two-to-one ratio, 25 seats becomes 50 blocks. Because the rule runs automatically, the add-on stays correct the instant seats change — no spreadsheets, no manual updates.

> **Tip:** Dependencies are one-way by default (the source drives the targets). Use **two-way** only when editing either side should update the other.

**Learn more:** [Rules Overview](/product/rules-and-customizations/rules-overview.md) · [Creating and Managing Rule Sets](/product/rules-and-customizations/rules-overview/creating-and-managing-rule-sets.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/rules-and-customizations/rules-overview/keeping-add-ons-in-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.