> 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/customization/products.md). # Products Add and manage paint products, assign them to rates, and configure coverage calculations. Build your product library so PaintScout can calculate materials automatically on estimates and work orders. Add your own products, assign them to production rates, control rounding, and use the Sherwin-Williams tools for products and colors. ## In This Section * [Adding Products](/support/customization/products/adding-products.md) — Create products with coverage rates, pricing, unit types, and estimate type assignments * [Assign a Product to a Rate](/support/customization/products/how-to-assign-a-product-to-a-rate.md) — Link default products to production rates for automatic labor and material calculations * [Product Rounding](/support/customization/products/product-rounding.md) — Control how calculated product quantities appear on work orders * [Sherwin-Williams Color Catalogue](/support/customization/products/sherwin-williams-color-catalogue.md) — Choose Sherwin-Williams colors when a Sherwin-Williams product is used on an estimate * [Sherwin-Williams Product Browser](/support/customization/products/sherwin-williams-product-browser.md) — Browse, import, and manage Sherwin-Williams products in your library --- # 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/customization/products.md?ask=&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.