> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/main-cart.md).

# Cart page

The classic `/cart` page — for visitors who navigate there directly or arrive from an app link. It lists each line item with image, title, variant, a − / + quantity stepper, a Remove link, and line price; alongside sits a summary with an optional order note, subtotal, taxes note, and the checkout button.

This section has **no settings of its own**. Two things control it from elsewhere:

* **Theme settings → Cart → Show order note on the cart page** — toggles the "Add an order note" field.
* Your global colors and typography style it.

💡 Day to day, most buyers never see this page — the header's cart icon opens the [cart drawer](/sitesbyseth-docs/showcase/sections/cart-drawer.md), which carries the milestone bar, free gift, and upsells. Treat the cart page as a reliable fallback, and put your conversion effort into the drawer.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/main-cart.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.