> 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/managing-quotes/export-csv.md).

# Export quotes to CSV

Export your quotes to a CSV file for reporting, or to move the data into another system.

Exporting gives you your quote data as a spreadsheet — useful for reporting on what customers keep asking for, and for getting the information into a CRM or accounts system.

{% hint style="info" %}
**Export quotes to CSV** is a PRO plan feature. See [Plan comparison](/sa-request-a-quote/reference/plan-comparison.md), or open **Pricing plans** in the app navigation.

If **Export** is greyed out with a padlock line — "🔐 This feature is available on …" — that is your plan, not a fault. Nothing is broken.
{% endhint %}

## Export

{% stepper %}
{% step %}

### Open Quote list

Go to **Quote list** in the app navigation. The page is headed **Quotes**.
{% endstep %}

{% step %}

### Narrow the list, if you are exporting the current page

The status tabs — **All**, **Read**, **Unread**, **Order created** and **Purchased** — split the queue up, and the search and filter control beside them narrows it further. There is a sort control and an **Items per page** setting too.

This only matters if you are going to pick **Current page** in the next step, because that option exports exactly the rows on screen. **All quotes** and the date range ignore what you have filtered.

If instead you want a specific handful, tick their checkboxes now — that is what the **Quotes selected** option exports.
{% endstep %}

{% step %}

### Click Export

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2FNglQLUZGuCNnHtKPhED0%2Fimage.png?alt=media&amp;token=d8b11fb2-1f72-4bc1-b246-debff0a678cc" alt=""><figcaption></figcaption></figure>

**Export** sits at the top right, next to **Create quote**.

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2FMnFRyfkP2cjCAf7YslQl%2Fimage.png?alt=media&amp;token=ea0bfab8-ec41-4da5-9c81-8b9a6508d00d" alt=""><figcaption><p>The dialog decides how much of the list you take away.</p></figcaption></figure>
{% endstep %}

{% step %}

### Choose what goes in the file

A dialog opens, headed **Export quotes to CSV file**. Make your choice under **Export:** before you do anything else — nothing is exported until you press the button in the next step.

<table><thead><tr><th width="220">Option</th><th>What it exports</th></tr></thead><tbody><tr><td><strong>Current page</strong></td><td>Exactly the rows showing on screen right now — so this is the one your tab, search, filter and <strong>Items per page</strong> setting decide.</td></tr><tr><td><strong>All quotes</strong></td><td>Everything, whatever is filtered. Choosing it reveals a list of quote-number ranges — <strong>#1 -> #20</strong> and so on — so a large store can take one block at a time.</td></tr><tr><td><strong>By condition</strong></td><td>Opens a second set of choices: <strong>Quotes selected</strong> exports the rows you ticked on the list, and <strong>Date range</strong> gives you <strong>Start date</strong> and <strong>End date</strong> boxes in YYYY-MM-DD format.</td></tr></tbody></table>

Above the options sits one checkbox, **Without quote list items**. Leave it clear for a full export. Tick it when you only want one row per quote — the customer, the dates and the status, without the products — which is the shape you want for a contact list or a simple count.

{% hint style="info" %}
**Split into multiple files**, under **By condition**, appears greyed out. It is not selectable, so use the ranges under **All quotes** when an export is too big to handle in one piece.
{% endhint %}
{% endstep %}

{% step %}

### Click Export quotes

**Export quotes** is the blue button at the bottom of the dialog — **Cancel** beside it closes without exporting.

The app confirms with "Quotes exported successfully." and the file downloads as **quotes.csv**, ready to open in Excel, Google Sheets or Numbers.
{% endstep %}
{% endstepper %}

## What one quote actually holds

<figure><img src="https://2993310686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIvNtDAMNVIdy5nl9kiOU%2Fuploads%2F3jAZ1pjxcQhrilOAkQAI%2Fimage.png?alt=media&amp;token=7a403c69-375a-4974-8897-765f58879cc5" alt=""><figcaption></figcaption></figure>

An export is only as useful as the quotes behind it, so it is worth knowing what one quote carries. Open any row on the **Quotes** page and you will see the lot.

<table><thead><tr><th width="250">On the quote</th><th>What it is</th></tr></thead><tbody><tr><td>The line items</td><td><strong>Products</strong>, <strong>Price &#x26; quantity</strong> and <strong>Total</strong>, each line with its <strong>SKU</strong> — the prices you agreed, not your list prices.</td></tr><tr><td>The <strong>Payment</strong> panel</td><td><strong>Subtotal</strong>, the amounts behind <strong>Edit discount</strong>, <strong>Edit shipping</strong> and <strong>Edit tax rate</strong>, and <strong>Total</strong>.</td></tr><tr><td>The right-hand column</td><td><strong>Customer</strong> and <strong>Email</strong>, then <strong>Contact information</strong>, <strong>Company information</strong>, <strong>Shipping address</strong>, <strong>Billing address</strong>, <strong>Payment terms</strong>, <strong>Extra info</strong> and <strong>Tags</strong>.</td></tr><tr><td>The <strong>Timeline</strong></td><td>Your own notes on the quote. "Only you and your staff can see comments", so anything you record there with <strong>Post</strong> stays out of the customer's sight.</td></tr></tbody></table>

If a column you were expecting is empty, the usual reason is that your form never asked for it. See [Quote form overview](/sa-request-a-quote/quote-form/overview.md).

Remember that **Without quote list items** strips the product lines out. If your export has no products in it, check that box first before assuming anything is wrong.

## What you can learn from it

<table><thead><tr><th width="270">Question</th><th>What to look at</th></tr></thead><tbody><tr><td>What do people ask for most?</td><td>Group by product to find demand your published pricing is not capturing.</td></tr><tr><td>How many quotes turn into orders?</td><td>Compare the quotes you raised against the ones that reached <strong>Order created</strong> and <strong>Purchased</strong> — that is your quote-to-order rate.</td></tr><tr><td>What sizes are typical?</td><td>Quantities tell you whether your minimum order and pricing tiers are set sensibly.</td></tr><tr><td>Who is buying?</td><td>The <strong>Company</strong> column shows how much of your quoting is business buyers rather than individuals.</td></tr></tbody></table>

The dashboard's **Analytics overview** answers some of this without an export at all: **Quote number**, **Completed orders**, **Total draft orders** and **Order value** over a date range you pick.

{% hint style="success" %}
A quarterly export is a quick way to spot patterns, and **Date range** under **By condition** is built for exactly that — set **Start date** and **End date** to the quarter and take one file per period. If the same product is quoted constantly and always agreed near the same price, that is a candidate for a published tier price, and one fewer quote to handle each week.
{% endhint %}

## Keeping your own copy

If you rely on quote history, take an export periodically. It is also how you keep your records if you ever uninstall the app — see [Permissions and data](/sa-request-a-quote/reference/permissions-and-data.md).

The dashboard's **Pricing plan details** section shows your **Storage size** and **Used storage**, which is worth a glance if you take a lot of file uploads with your quotes.

{% hint style="warning" %}
Exports contain customer contact details. Treat the file the way you would treat any customer data — store it somewhere appropriate and do not email it around.
{% endhint %}

{% hint style="danger" %}
Export before you delete, not after. Deleting a quote also destroys the files customers uploaded to it, "including from previously exported links" — so an old export's attachment links stop working once the quote behind them is gone. See [Duplicate or delete a quote](/sa-request-a-quote/managing-quotes/duplicate-delete.md).
{% endhint %}

## Sending quote data somewhere automatically

If the reason you are exporting is to get quotes into another tool, an integration may save you the round trip. Under **Advanced settings** > **Integrations** the app connects to Mailchimp, Klaviyo, Shopify, HubSpot, Omnisend, GetResponse, Sendinblue, ActiveCampaign, Campaign Monitor and Zapier.

{% hint style="info" %}
Mailchimp, Klaviyo and Shopify are on the FREE plan. The rest need PRO, as does exporting itself.
{% endhint %}

## Next steps

* [Integrations overview](/sa-request-a-quote/integrations/overview.md) — send quote data to your tools automatically
* [Permissions and data](/sa-request-a-quote/reference/permissions-and-data.md) — what is stored, and for how long
* [Duplicate or delete a quote](/sa-request-a-quote/managing-quotes/duplicate-delete.md) — clear out quotes once you have a copy


---

# 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/managing-quotes/export-csv.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.