> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/space/guides/products/replacing-add-to-cart.md).

# Replace “Add to cart”

The “Add to cart” text can be customized for each product using metafields. This is useful if you want to change the wording for specific products. For example, you could use this to display “Pre-order” for one product.

{% stepper %}
{% step %}
**Create metafield definition**

1. Navigate to **Settings** > **Custom** **data** > **Products**
2. Click **Add definition**
3. In the name field type “**Button text**”
4. Ensure the namespace and key field is `custom.button_text`
   {% endstep %}

{% step %}
**Update metafield**

1. Navigate to the product you’d like to update
2. Scroll to the bottom and enter in text for the “Button text” metafield
3. Click **Save**
   {% endstep %}
   {% endstepper %}

{% hint style="info" %}
Metafields can also be updated using the bulk editor
{% endhint %}


---

# 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://help.brickspacelab.com/space/guides/products/replacing-add-to-cart.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.