> For the complete documentation index, see [llms.txt](https://docs.plummerindustries.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plummerindustries.com/website/catalog-and-checkout/purchase-order-process.md). # Purchase Order Process ## School systems work differently. There are a wide range of ways that schools require to use a purchase order. We try our best to accommodate them. ## If you need a Quote before purchase order. Checkout normally on the website and choose **Quote only** as the payment method. This will create an "order" and you will receive an email with your quote attached as a PDF. When you get the PO from your school Email it to **** We will then send you an updated order with **Purchase Order** on the invoice. Quotes that are not turned into PO orders within 30 Days will be Canceled. ## If you have a purchase order already Checkout normally on the website and choose **Purchase order** as the payment method. You can add the PO number in the comments of the order. Email **** or respond to the order confirmation with an attached copy of your PO. Standard payment terms are NET 30. Failure to pay or late payment may affect the usage of future PO's from your school. ## Plummer Industries - W9 {% file src="/files/kvl0M1ZNDJHzokM33UR4" %} --- # 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://docs.plummerindustries.com/website/catalog-and-checkout/purchase-order-process.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.