> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/beta-guides/multiple-products-on-rates.md).

# Multiple Products on Rates

Add more than one default product to a production rate and set the number of coats for each product.

{% hint style="info" %}

#### Important Information:

* This feature is in active development. You may encounter bugs or missing functionality as we improve the experience.
* You can enable this feature by going to Account Settings > Beta Features section
* Please send questions or feedback to <product@paintscout.com>.
  {% endhint %}

By default, a production rate uses one product. Multiple Products lets you add more than one default product to a single rate instead, so a rate like "Walls" can automatically include both a primer and a topcoat, for example. You can also set a different number of coats for each product on the rate.

This guide covers how to set it up from scratch, and how it carries through to your estimates. If you've used Multiple Products before, the coats and swapping behavior described below is new, see the note near the bottom for what's changed.

***

### Why this is useful

A common setup is a primer plus a topcoat on the same rate. The primer usually only goes on once, no matter what, while the topcoat follows however many coats you've set for that rate, 2, 3, sometimes more. Without setting up multiple products, you'd need to add these as separate line items or handle it manually. With multiple products on one rate, both are built in, and each one can follow its own rules.

***

### Adding products to a production rate

{% embed url="<https://share.zight.com/01a0c4cc-3192-70b4-a647-deea526c4fcd>" %}

1. Go to your production rate in Settings, and find the **Default Products** section.
2. For each product row, you'll see:
   * **Name**: pick the product from the dropdown.
   * **Coverage (sqft/gal)**: you can override the product's default coverage here.
   * **# Coats**: choose how many coats this specific product should use (see below).
3. Click **+ Add Product** to add another product to the same rate. Each product row is independent, with its own name, coverage, and coat count.

***

### Choosing coats per product

Each product's **# Coats** dropdown gives you two ways to set it:

* **Use rate default**: this product's coat count always matches whatever the rate itself is set to. If you change the rate from 2 coats to 3, this product updates automatically, no need to touch it.
* **A fixed number (1, 2, 3, or 4 coats)**: this product always uses that exact number, no matter what the rate's overall coat count is set to.

**Example:** on a Walls rate, you might set your primer to a fixed **1 coat**, since primer rarely needs more than one pass, while your topcoat stays on **Use rate default**, so it automatically follows however many coats you set on the rate for that job.

***

### How this shows up on an estimate

When you build an estimate and use a rate with multiple default products, each product on that rate shows its own **# Coats** dropdown right there in the estimate.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2F2wRwvyFMUYKuU9e3njuG%2FScreenshot%202026-09-21%20at%2010.34.13%E2%80%AFAM.png?alt=media&amp;token=bd5e6c28-ba58-4264-beea-1e3707b72a1a" alt=""><figcaption></figcaption></figure>

* It starts out matching whatever you set in your rate's settings.
* You can change it for this one estimate without affecting your saved rate settings anywhere else.
* If a product is set to **Use rate default**, it stays connected to the rate's coat count for that estimate too. So if you bump the rate from 2 coats to 3 while building the estimate, any product still set to "Use rate default" updates right along with it. Products set to a fixed number stay put.

***

### What happens to your existing rates

If you already had multiple products set up on a rate before this update, nothing changes automatically. Every existing product on your rates has been set to **Use rate default**, which is exactly how they already behaved, so your estimates will look and calculate the same as before. From here, it's up to you to switch any product to a fixed coat count if you want it to stop following the rate.

***

### Quick tips

* Use **Use rate default** for products that should scale with the job, like a topcoat that varies by how many coats a customer wants.
* Use a **fixed number** for products that should always stay the same, like a single-coat primer or a specialty product that never changes regardless of the rate.

***

## Thanks for Trying the Beta! <a href="#h_a1cb63cea7" id="h_a1cb63cea7"></a>

Your feedback helps us improve this feature. Tell us what works well and where you get stuck.

For questions, issues, or feedback, email <product@paintscout.com>.

&#x20;&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.paintscout.com/support/beta-guides/multiple-products-on-rates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
