> For the complete documentation index, see [llms.txt](https://help.takulabs.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.takulabs.io/pos/sales-and-returns/commitments-recurring-orders/managing-commitments.md).

# Managing Commitments

Once a Commitment has been created, your customer will receive an email confirming that a saved payment method will be used for future recurring orders.

{% hint style="info" %}
Note that PCI Compliance rules require that customers have the ability to cancel recurring payments on their own. With TAKU, customers can do this by clicking the link at the bottom of Confirmation Emails and confirming that they wish to cancel.
{% endhint %}

At the same time, the new Commitment will be added to the list of all active commitments which can be viewed by going to **Sell** > **Commitments** in the main navigation menu. 

<figure><img src="/files/Qo8mC3CAc4tSjCfdAKUA" alt=""><figcaption></figcaption></figure>

To view the details of any existing Commitment #, click the link in the first column.

## Day-to-Day Management of Commitments

Now that you have commitments from your customers, you will need to remember to check the Commitments list so that you can:

1. [Generate the next Recurring Order by the Next Charge Date](/pos/sales-and-returns/commitments-recurring-orders/managing-commitments/generating-recurring-orders-from-commitments.md)
2. [Skip, Pause or Void a Commitment as required](/pos/sales-and-returns/commitments-recurring-orders/managing-commitments/skipping-pausing-or-voiding-commitments.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://help.takulabs.io/pos/sales-and-returns/commitments-recurring-orders/managing-commitments.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.