> 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/estimating/line-items-and-options.md). # Line Items & Options Add line items for fixed-price work, create options for customers, and manage change orders. Not all work fits neatly into dimension-based rates. Use line items for fixed-price or custom-scoped work, options for upsells and alternate scope, and additional work for approved changes after acceptance. ## In This Section * [Add & Edit Line Items](/support/estimating/line-items-and-options/how-to-add-and-edit-a-line-item.md) — Add saved or custom line items with pricing, materials, hours, photos, notes, and visibility controls * [Customer Accepted Options](/support/estimating/line-items-and-options/customer-accepted-options.md) — Let customers add optional items themselves before they accept the estimate * [Additional Work/Change Orders](/support/estimating/line-items-and-options/additional-work-change-orders.md) — Convert items into approved additional work on invoices --- # 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/estimating/line-items-and-options.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.