> For the complete documentation index, see [llms.txt](https://info.whitepoppypreservation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://info.whitepoppypreservation.com/before-you-purchase/why-are-your-frames-so-expensive.md). # Why Are Your Frames So Expensive? Preserving your flowers into a beautiful, long-lasting memory is a lengthy process that requires weeks of labor and expensive materials. While we strive to make our frames as affordable as possible, our top priority is compensating our employees fairly and ensuring our customers a high-quality, custom-made product! **Our total cost includes:** * Compensation for our team of talented employees specializing in each step of the process * Materials required for preservation and assembling the final product * Shipping the finished frame to you **We *****do not***** cover:** * Shipping your bouquet to us * Replacing any blooms that arrive to us dead/not healthy enough to press --- # 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://info.whitepoppypreservation.com/before-you-purchase/why-are-your-frames-so-expensive.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.