> 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/sa-request-a-quote/storefront-quote-pages/edit-page-text.md).

# Edit quote page text

Retitle your quote pages, add your own introduction, and find where the app's own wording is changed.

Your two quote pages sit in your Shopify admin like any other page, so you can retitle them and add your own wording — a note on lead times, minimum order quantities, or what happens after someone sends a request.

The wording inside the quote form itself is different: that belongs to the app, and you change it in the app. This page covers both.

## The two pages, and what is inside them

The app creates both pages for you when you install it, each holding a single empty `<div>` that the app fills in on the storefront. Everything else in the page is yours.

<table><thead><tr><th width="210">Page title</th><th width="230">Storefront address</th><th>The app's block inside it</th></tr></thead><tbody><tr><td><strong>Request for quote</strong></td><td><code>/pages/request-for-quote</code></td><td><code>&#x3C;div class="rfq_form_page">&#x3C;/div></code></td></tr><tr><td><strong>Quote history</strong></td><td><code>/pages/quotes-history</code></td><td><code>&#x3C;div class="rfq_history_page">&#x3C;/div></code></td></tr></tbody></table>

{% hint style="danger" %}
**That `<div>` is the page.** It is empty in the editor and looks like nothing worth keeping, which is exactly why people delete it. Delete it and the page still loads on your storefront — it just loads with no quote form and no quote history in it. Everything below is written to stop that happening to you.
{% endhint %}

## Edit the Shopify page

{% stepper %}
{% step %}

### Open the page in Shopify

In your Shopify admin, go to **Online Store** > **Pages**, then open **Request for quote** or **Quote history**.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-0ebe78225312450e0179954140884f6410792802%2Fscreenshot-shopify-pages-list.png?alt=media" alt="Online Store > Pages in the Shopify admin with the quote pages visible in the list"><figcaption><p>Both quote pages live under <strong>Online Store</strong> > <strong>Pages</strong>.</p></figcaption></figure>
{% endstep %}

{% step %}

### Make your edits

Change the title and add the content you want — an introduction, your lead times, a note on minimums. Write it above or below the app's block, never on top of it.
{% endstep %}

{% step %}

### Check the app's block is still there, before you save

Click the **`<>`** icon in the page editor toolbar to open the **HTML viewer**, and look for the app's block in the code.

* On **Request for quote** you should see `<div class="rfq_form_page"></div>`.
* On **Quote history** you should see `<div class="rfq_history_page"></div>`.

If it is there, everything is fine. If it is gone, paste the matching line back in and carry on.

Copy from here — for the **Request for quote** page:

```html
<div class="rfq_form_page"></div>
```

And for the **Quote history** page:

```html
<div class="rfq_history_page"></div>
```

{% hint style="warning" %}
Paste it in the **HTML viewer**, not the rich text editor. Typed into the rich text editor it is saved as visible text, so the page prints the code to your customers instead of showing the quote form.
{% endhint %}

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-071121ac743b7295a6603a2c572f8bd2539dd119%2FScreenshot%202026-09-30%20at%2000-40-06.png?alt=media" alt="The Shopify page editor for the Request for quote page with the HTML view open and the app&#x27;s div outlined in red"><figcaption><p>The <strong>&#x3C;></strong> view — the app's div must survive your edit.</p></figcaption></figure>
{% endstep %}

{% step %}

### Save and check the storefront

Click **Save**, then open `/pages/request-for-quote` or `/pages/quotes-history` on your storefront and look at the result.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Doing the `<>` check *before* you save takes five seconds. Finding out afterwards means a customer got there first. If a page has already lost its quote content, the full repair — including the older `{rfq_content}` and `{rfq_history}` tokens — is in [troubleshooting.md](/sa-request-a-quote/help/troubleshooting.md).
{% endhint %}

{% hint style="warning" %}
**Retitle freely, but leave the web address alone.** Renaming the page is safe. Changing its URL handle away from `request-for-quote` or `quotes-history` moves the page out from under the links the app and your menu point at.
{% endhint %}

## What is worth adding

<table><thead><tr><th width="250">Add</th><th>Why</th></tr></thead><tbody><tr><td>How soon you reply</td><td>Sets expectations and cuts chasing emails. "We reply within one business day" is enough.</td></tr><tr><td>Minimum order quantity</td><td>Saves you quoting requests you cannot fulfil.</td></tr><tr><td>What to include</td><td>Asking for dimensions or a deadline up front avoids a round trip.</td></tr></tbody></table>

{% hint style="info" %}
Keep it short. A long paragraph customers have to scroll past is a paragraph they will not read.
{% endhint %}

## Wording the app controls

These strings are not page content. Change them in the app instead.

<table><thead><tr><th width="270">Wording</th><th>Where you change it</th></tr></thead><tbody><tr><td><strong>Button text</strong> on your quote button, default <code>Add to Quote</code></td><td><strong>Quote settings</strong> > <strong>Customize</strong> > <strong>Button &#x26; widget</strong></td></tr><tr><td>The confirmation popup: <strong>Message</strong>, <strong>Primary button</strong> (<code>View Quote</code>) and <strong>Secondary button</strong> (<code>Continue Shopping</code>)</td><td><strong>Quote settings</strong> > <strong>Customize</strong> > <strong>Button &#x26; widget</strong></td></tr><tr><td>Field labels on the quote form</td><td><strong>Quote settings</strong> > <strong>Customize</strong> > <strong>Quote form</strong>, in <strong>Form builder</strong></td></tr><tr><td>The success message customers see after submitting — <strong>Thank you</strong> and "Thank you for submitting a request a quote!"</td><td><strong>Quote settings</strong> > <strong>Customize</strong> > <strong>Success message</strong></td></tr><tr><td>The wording on the floating quote widget — its <strong>Text</strong></td><td><strong>Quote settings</strong> > <strong>Customize</strong> > <strong>Quote cart page</strong>, under <strong>Enable Quote Cart Widget</strong></td></tr><tr><td>The rest of the storefront wording, in the other languages you sell in</td><td><strong>Advanced settings</strong> > <strong>Translations</strong></td></tr><tr><td>The Quote List section inside Shopify's new customer accounts</td><td><strong>Customer account</strong> > <strong>Translation</strong> — see <a href="/sa-request-a-quote/storefront-quote-pages/customer-account-quotes.md">customer-account-quotes.md</a></td></tr></tbody></table>

{% hint style="info" %}
A quick way to tell the two apart: if you can select the text in the Shopify page editor, it is page content and you edit it here. If it only appears once the quote form has loaded, it belongs to the app.
{% endhint %}

## Translate the rest

On the **Translations** tab, **Translations AI** will "Translate everything your customers see — quote form, storefront text and both quote emails."

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2Fgit-blob-2079f0906ed03974c2a733d332764370d5db38aa%2Fscreenshot-advanced-settings-translations.png?alt=media" alt="The Translations tab of Advanced settings, with the language table showing English as the default source language"><figcaption><p>The language table lists each language with its <strong>Status</strong> and a <strong>Translate</strong> action.</p></figcaption></figure>

{% hint style="info" %}
The languages listed there come from **Settings** > **Languages** in your Shopify admin, and the list mirrors the languages published there. To add or remove one, change it in Shopify first.
{% endhint %}

Your own page content is not covered by that, because it is Shopify page content rather than app text. Translate it the way you translate your other Shopify pages.

## Next steps

* [Translate storefront text](/sa-request-a-quote/settings/translations.md) — change the wording inside the quote form
* [Request a Quote page](/sa-request-a-quote/storefront-quote-pages/request-a-quote-page.md) — set up the quote cart page itself
* [Troubleshooting](/sa-request-a-quote/help/troubleshooting.md) — if a page loads without its quote content


---

# 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/sa-request-a-quote/storefront-quote-pages/edit-page-text.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.