> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/understand-refrigerant-registration.md).

# Understand refrigerant registration

Refrigerant registration is the transaction-level record behind KoudSmart reporting.

It captures what happened, where it happened, and which refrigerant was involved.

### Registration can include

* installation details
* handling date
* refrigerant type and quantity
* fill and recovery reasons
* cylinder information

### Where the data comes from

KoudSmart uses data from work orders, forms, linked objects, and related stock movements.

That makes daily data quality important.

### Frequently asked questions

<details>

<summary>Why is installation-level registration important?</summary>

It creates the foundation for yearly reporting.

</details>

<details>

<summary>Does KoudSmart use work order data here?</summary>

Yes.

That is a key source in the process.

</details>

<details>

<summary>What happens if data is incomplete?</summary>

The report output becomes less reliable.

</details>

### Related topics

* [**Use KoudSmart in work orders**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/use-koudsmart-in-work-orders.md)
* [**Use KoudSmart in forms**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/use-koudsmart-in-forms.md)
* [**Generate KoudSmart reports**](/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/generate-koudsmart-reports.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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/f-gases-forms-koudsmart/understand-refrigerant-registration.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.