> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/bulk-price-editor-sami/field-guides/description.md).

# Description

Find and replace text in product descriptions or add text before or after them.

The **Description** field edits the product description (the HTML body of the product).

## Edit methods

| Edit method                    | Inputs                    |
| ------------------------------ | ------------------------- |
| **Find and replace** (default) | Find value, Replace value |
| **Replace entire text**        | Value                     |
| **Add text at beginning**      | Value                     |
| **Add text at end**            | Value                     |

## Working with HTML

Descriptions are stored as HTML. The value you type is inserted as-is, so you can include HTML tags:

* **Add text at end** with `<p>Free shipping on orders over $50.</p>` appends a new paragraph.
* **Find and replace** works on the HTML source. To replace text that Shopify has wrapped in tags, match the exact text between the tags, for example find `Soft 100% cotton` and replace with `Soft organic cotton`.

The **Find value** and **Replace value** boxes are multi-line so you can paste longer snippets.

## Tips

* Use **Replace entire text** carefully. It overwrites the complete description of every matching product.
* [Dynamic variables](/bulk-price-editor-sami/field-guides/dynamic-variables.md) work in all three inputs, for example `<p>Made by {{ product.vendor }}.</p>`.
* Click the eye icon in the preview or in **Product changes** to compare the original and updated descriptions side by side.
* Reverting the task restores the original description of each product.


---

# 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.samita.io/bulk-price-editor-sami/field-guides/description.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.