> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/products/quick-view-and-pre-order-templates.md).
# Quick View & Pre-order templates
Configure Volume Quick View popup and Pre-order template: edit the quick-view template in the Theme Editor and assign pre-order via product settings.
### Quick view template
When customers click the cart icon on a product card, a popup appears showing a simplified product preview. This popup uses a dedicated Quick view template, based on a streamlined version of the standard Product overview template.
To edit this template, go to Online Store → Themes → Customize, then navigate to Products → quick-view using the template selector dropdown.
### Pre-order template
The Pre-order template shares the same structure and settings as the Product overview template.
{% hint style="warning" icon="triangle-exclamation" %}
For pre-orders to function correctly, the product must either have **available inventory or inventory tracking must be disabled**.
{% endhint %}
To assign this template to a product:
1. Open the product in the Shopify admin.
2. In the Theme template dropdown, select preorder.
---
# 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://staylime.com/docs/volume-themes/products/quick-view-and-pre-order-templates.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.
