> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/customers-and-sales/credits-refunds-returns-and-replacements/customer-credits.md).

# Customer Credits

From now on, all the flows we talk about will begin with a Customer Credit, so let’s get to know them in detail.

There are a number of basic facts you need to remember:

1. They always impact the customer’s account balance positively. If the customer was on zero, you now owe them money. If they owed you money previously, now they owe you less.
2. They do NOT impact stock - you need to also enter a 'Return' if you want to bring stock back.
3. They are required before a refund can be entered.
4. They can be applied in lieu of payment to Orders that are pending payment.


---

# 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.pakk.io/customers-and-sales/credits-refunds-returns-and-replacements/customer-credits.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.