> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/how-tos/placing-orders/shopping-cart.md).

# Shopping cart

How to add a shopping cart to your website

When building ecommerce, the shopping cart management is one of the key steps, as it bridges the gap between browsing and buying, driving the customer to the checkout process.

![A sample product page with shopping cart summary](https://2610849379-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lk-ezuDClaMavTqnRi0%2Fuploads%2F0yXm4nU8gw4lEHsifgyw%2Fproduct-page-cart-summary.jpg?alt=media\&token=c780ddae-3725-4c01-b14b-d12bea263c5e)

This guide will walk you through all the actions that you typically want to implement on your shopping cart, like adding a new line item, updating quantities, or displaying a cart summary to the customer.

{% hint style="info" %}
We will assume all the example requests to be authenticated through a valid access token for a **sales channel**. See the [Authentication](/core/authentication.md) and [Applications](/core/api-credentials.md) sections of our documentation if you need more information on how to get an access token for your client or about the different types of credentials you can get.
{% endhint %}


---

# 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.commercelayer.io/how-tos/placing-orders/shopping-cart.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.