> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/b2b-customer-portal/my-quotes.md).

# My Quotes

The **My Quotes** section of the portal (`/apps/orbit-boost-wholesale/portal/quotes`) lists every quote request the logged-in buyer has submitted, embedded inside the portal sidebar shell.

This is the **canonical "all quotes" entry** for logged-in buyers. The standalone routes are kept for the cases the portal can't cover:

| Route            | When it's used                                                                                |
| ---------------- | --------------------------------------------------------------------------------------------- |
| `/portal/quotes` | Logged-in buyer browsing all their quotes (inside the shell)                                  |
| `/quotes/:id`    | A single quote opened from an email deep link, or by a buyer who isn't logged into the portal |

## What the buyer sees

* A list of their quotes with status badges — **Pending**, **Replied**, **Negotiating**, **Accepted**, **Rejected**, **Expired**
* Each row opens the quote detail, where (once your team has replied) they can **Accept**, **Decline**, or **Send a reply**

The list reuses the same `quote-storefront.js` bundle that powers the Request-a-Quote modal, so status labels and copy follow your [Storefront Text translations](/orbit-b2b-docs/quotes-rfq/storefront-text.md).

## Relationship to the Quotes feature

My Quotes is the customer-facing read side of the [Quotes (RFQ)](/orbit-b2b-docs/quotes-rfq/overview.md) workflow:

* Buyers **create** quotes from the Request-a-Quote app block on product pages — see [How a buyer requests a quote](/orbit-b2b-docs/quotes-rfq/request-flow.md)
* You **reply** with prices from the admin inbox — see [How you reply with prices](/orbit-b2b-docs/quotes-rfq/reply-flow.md)
* Accepted quotes with Net / Prepay terms appear in the buyer's [Invoices](/orbit-b2b-docs/b2b-customer-portal/invoices.md)

## Note on quote detail

Opening a quote from `/portal/quotes` currently navigates to the standalone `/quotes/:id` detail page (it leaves the sidebar shell). The list, status, and accept/decline actions all work — only the visual shell differs on the detail view.

## Next

* [Invoices](/orbit-b2b-docs/b2b-customer-portal/invoices.md)
* [Quotes (RFQ) overview](/orbit-b2b-docs/quotes-rfq/overview.md)
* [Payment terms — Net 30 / PDF invoice](/orbit-b2b-docs/quotes-rfq/payment-terms.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://orbit-b2b.gitbook.io/orbit-b2b-docs/b2b-customer-portal/my-quotes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.