> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/avante-themes/templates/cart-page.md).

# Cart page

The cart template in Avante — the items list, the summary blocks, discount code, order note, gift message and shipping calculator.

Even with the cart drawer switched on, every store still has a cart page. Shoppers reach it from a bookmark, from an email, from a link in a support reply, or because they opened `/cart` directly — and some simply prefer a full page before paying. In Avante it is a normal template built from blocks, so the summary column holds exactly what your store needs and nothing else.

{% hint style="info" %}
**Theme Editor → Cart → Cart page**
{% endhint %}

{% hint style="warning" %}
The **cart drawer** is a separate thing with its own settings — see [Theme settings → Cart drawer](https://staylime.com/docs/avante-themes/theme-settings/cart-drawer.md). Turning the drawer on does not replace this page; it only changes where shoppers usually land first.
{% endhint %}

***

### How to set it up

{% stepper %}
{% step %}

#### Open the cart template

In the theme editor use the page selector at the top and choose **Cart**.
{% endstep %}

{% step %}

#### Open the Cart page section

It holds the items list and the summary column. Section-level settings cover the heading size and tag, **Show vendor** on the line items, and the desktop and mobile section paddings.
{% endstep %}

{% step %}

#### Add the blocks you need

Press **Add block** and pick from **Price**, **Checkout button**, **Discount code**, **Order note**, **Gift message** and **Shipping calculator**. Drag them into the order you want in the summary column.
{% endstep %}

{% step %}

#### Check it with a real cart

Add a product on the storefront preview and open `/cart`. An empty cart shows the empty state, not the summary.
{% endstep %}
{% endstepper %}

***

### The blocks

**Price** — the money part of the summary. **Show 'Cart total'** prints the total line and **Show 'You saved'** shows the difference when discounts or compare-at prices apply. The subtotal has its own size setting, so it can be the largest thing in the column.

**Checkout button** — the button itself. It has no settings; its styling comes from the theme's button settings.

**Discount code** — a field for a code on the cart page. It can be shown as a collapsible tab so it does not invite everyone to go hunting for a code, with its own heading and field label.

**Order note** — the standard Shopify order note, with its own heading, field label and placeholder, and the same collapsible-tab option.

**Gift message** — a message field that travels with a gift-wrapped order. Only one can be added.

**Shipping calculator** — a shipping estimate before checkout. **Default country** sets which country is preselected; for a logged-in customer the country from their default shipping address wins instead.

Blocks from installed apps can be added here too.

***

### Good to know

* **Gift message only appears under three conditions at once**: a gift wrapping product is set up, the gift wrapping checkbox is enabled, and the shopper has actually ticked it. Until then the block renders nothing — which is almost always the answer to "I added the block and it is not there".
* **Discount code, Order note, Gift message and Shipping calculator each have a collapsible-tab option.** Collapsed is usually the better default: a visible discount field sends people off to search for a code instead of checking out.
* **Shipping estimates come from your Shopify shipping rates**, not from the theme. If a country returns no rate, check the rates in Shopify admin.
* **The empty cart state is part of the template.** Look at it — for many stores it is the only page a returning visitor sees first.
* **This page and the cart drawer are configured separately.** A block added here does not appear in the drawer.

***

### Customization ideas

* **Add** [**Cart recommendations**](https://staylime.com/docs/avante-themes/sections/products/cart-recommendations.md) under the items — suggestions based on what is already in the cart.
* **Add** [**Recently viewed products**](https://staylime.com/docs/avante-themes/sections/products/recently-viewed-products.md) so the products they looked at but did not add get a second chance.
* **Trust content under the summary** — returns, delivery times, payment icons — placed where the hesitation actually happens.
* **Collapse everything optional** and leave only the subtotal and the checkout button expanded.

***

### Best practices

* Keep the checkout button above the fold on mobile with a one-item cart.
* Do not add every block because it exists. Each extra field is another reason to pause.
* Test with a discount code, with a gift-wrapped order and with an empty cart — all three look different.
* Keep the page consistent with the drawer, so a shopper who sees both does not meet two different carts.

***

### Related

* [Templates overview](https://staylime.com/docs/avante-themes/templates/overview.md)
* [Theme settings → Cart drawer](https://staylime.com/docs/avante-themes/theme-settings/cart-drawer.md)
* [Cart recommendations](https://staylime.com/docs/avante-themes/sections/products/cart-recommendations.md)
* [Recently viewed products](https://staylime.com/docs/avante-themes/sections/products/recently-viewed-products.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/avante-themes/templates/cart-page.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.
