> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/purchase-order.md). # Purchase Order ## Overview A Purchase Order (PO) is an official document issued to a vendor to authorize the purchase of materials, products, or services for a project. It records the agreed items, quantities, pricing, and vendor details, creating a clear reference for both your team and the vendor. In BuilderTek, the Purchase Order connects purchasing, vendor management, project budgets, and financial tracking. It can be created from multiple modules depending on your workflow, allowing your team to create and manage purchasing activity from the point where it is most relevant. ### Purchase Orders and the RFQ Process In the general BuilderTek configuration, a Purchase Order is automatically created when a vendor is awarded through the RFQ process. You can access the Purchase Order directly from the RFQ through the Quick Links section. However, the Purchase Order workflow is fully configurable to match your company's operational requirements. Depending on your preferred process, BuilderTek can be configured to: * Create a Purchase Order immediately when a vendor is awarded. * Create a Purchase Order only after the vendor accepts the award. * Automatically send the Purchase Order to the vendor when the RFQ is awarded. * Require additional internal approvals before issuing the Purchase Order. ### Purchase Orders Across BuilderTek A Purchase Order does not have to originate only from the RFQ module. Depending on your workflow and configuration, you can create or access POs from other relevant areas of BuilderTek, including Projects, Budgets, RFQs, and other connected modules. This flexibility allows your team to create a PO based on the actual workflow you follow rather than forcing every purchase through a single process. Once created, the Purchase Order becomes the official record authorizing the transaction and communicating the approved project requirements to the vendor. It also becomes the foundation for the next stages of the financial workflow, including Contractor Invoices and payment processing. --- # 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.buildertek.com/purchase-order.md?ask=&goal= ``` `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.