> For the complete documentation index, see [llms.txt](https://manual.firstresonance.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.firstresonance.io/plans-and-autoplan/autoplan-suggested-suppliers-and-procedures.md).
# Autoplan suggested suppliers and procedures
Based on data in ION, Autoplan will infer the supplier or procedure that should be used
### Overview
Autoplan will suggest which suppliers and procedures should be used on unlinked plan items. These appear as columns within the results shown on a plan (you may need to adjust which columns you have visible via the column picker).
Additionally, you can group by supplier to see all plan items that must go to a specific supplier.
### Logic
* **Procedure**: Autoplan will use the procedures associated with the part on the part library record. It only uses the first procedure if many are defined for a single part.
* **Supplier**: Autoplan will use the part <> supplier relationship defined on the part library record. Once again, it will use the first supplier if there are many defined for a single part.
---
# 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://manual.firstresonance.io/plans-and-autoplan/autoplan-suggested-suppliers-and-procedures.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.
