> For the complete documentation index, see [llms.txt](https://broadcast.presidiocreative.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://broadcast.presidiocreative.com/broadcast-v3/products/pre-order-products.md).

# Pre-order products using tags

Replace the add-to-cart button with a pre-order button using tags

If you have a product that is not yet ready to be shipped to customers, you can set it up as a pre-order product. Broadcast can replace the add-to-cart button with a pre-order button by using a `_preorder` tag.

![Convert the Add to cart button to Pre-order](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/57PwBtgiN51Qkegpv1WU/preorder-button.gif)

### How to use

* From your Shopify admin, choose "Products"
* Choose the product you want to change into a preorder
* Add the tag `_preorder`
* Save the product

![](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/vPNiFVByvajFLXF3OE7F/file-HdiMXmam3G.png)

When Broadcast sees a product with this tag, the Add to cart button will automatically be changed to Pre-order. 

### Customize the button text

Use the language editor to customize the button text for pre-order.

![Choose Edit languages from the Actions button](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/cEGS7XU8ZbWRtzTlSWJB/Screen%20Shot%202021-08-19%20at%209.35.20%20AM.png)

Search for `pre-order` in the Filter bar:

![Update value to change button text for any language](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/T5B7lHb2Z6KM4I1eueAf/Screen%20Shot%202021-08-19%20at%209.31.20%20AM.png)

### Manually capture payment

Pre-orders require that you set up payment options to manually capture payments instead of automatic. 

From your Shopify admin, click **Settings** (bottom left), and then click **Payments**:

![](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/BwIGRzFNZnc43snvQBle/Screen%20Shot%202021-08-30%20at%209.39.10%20PM.png)

Scroll down to find the **Payment capture** section, choose to **Manage** for Payment capture set to Manual:

![](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/1ycJB09utzFlkIPGp3eg/Screen%20Shot%202021-08-30%20at%209.41.07%20PM.png)

Choose **Manually** capture payment for orders:

![](https://content.gitbook.com/content/gPVWISoa427RKoZWt1y6/blobs/x6I3zPQG9cJrEB1MuIaE/Screen%20Shot%202021-08-30%20at%209.43.32%20PM.png)

Learn more about Capturing payments from Shopify:

{% embed url="<https://help.shopify.com/en/manual/orders/get-paid>" %}


---

# 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://broadcast.presidiocreative.com/broadcast-v3/products/pre-order-products.md?ask=<question>&goal=<user_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.