> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-commerce/tutorials/build-a-store/checkout.md).

# Implementing a Checkout Flow

Learn how to implement a checkout flow in Umbraco Commerce.

When it comes to implementing a checkout in Umbraco Commerce, there are two options available to you.

## [Using the Umbraco.Commerce.Checkout Drop-in Checkout Flow](https://docs.umbraco.com/umbraco-commerce-packages/checkout/checkout)

The [Umbraco.Commerce.Checkout](https://docs.umbraco.com/umbraco-commerce-packages/checkout/checkout) add-on is a great starting point for most stores. It provides a ready-to-use checkout experience.

For details on how to install and configure the `Umbraco.Commerce.Checkout` add-on, see the [Umbraco.Commerce.Checkout](https://docs.umbraco.com/umbraco-commerce-packages/checkout/checkout) documentation.

## Creating a Custom Shopping Cart

If you need a more custom checkout experience, you can build your own checkout flow using the Umbraco Commerce API. This approach gives you full control over the checkout experience, allowing you to tailor it to your specific requirements.

For details on how to build a custom checkout flow, see the [Creating a Custom Checkout Flow](/umbraco-commerce/tutorials/build-a-store/checkout/custom-checkout.md) article.


---

# 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.umbraco.com/umbraco-commerce/tutorials/build-a-store/checkout.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.