> For the complete documentation index, see [llms.txt](https://kbase.whitelabel-loyalty.com/product/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kbase.whitelabel-loyalty.com/product/modules/receipts-and-products.md).

# Receipts & Products

{% hint style="info" %}
Modules are sold separately and **not included** in the Loyalty Engine core platform licence. For pricing and details, contact your account manager.&#x20;
{% endhint %}

## About the Receipts module

The **Receipts module** streamlines loyalty program engagement by automating receipt submission and validation. With custom receipt rules, you can verify claims, ensure authenticity, and flag invalid claims for manual review in the Loyalty Console. You can also predefine merchant information and receipt formats within the Loyalty Console to accelerate the validation process, reduce errors, and enhance efficiency through automation.

***

## About the Products module

The **Products module** enables you to define a curated list of products directly in the Loyalty Console. These products can act as triggers for campaigns, awarding bonuses to end-users for purchasing specific items. Additionally, the module offers detailed reporting on product sales and quantities, allowing you to optimise promotions and create tailored loyalty incentives based on customer purchasing behaviour.


---

# 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://kbase.whitelabel-loyalty.com/product/modules/receipts-and-products.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.
