> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/bound-products.md).
# Bound products
## Bound products - linked products, sets and deposits
**Menu path:** `Administration -> Dictionaries -> Products`
Bound products describe relationships between product records.
They can be used for sets, packaging, process-dependent products or deposits, if such a mechanism is used in the implementation.
### Bound products
The `Bound products` tab shows products linked to the current record. For each relationship, the product index, name, quantity and price are visible, if price is used in the given process. Example uses:
* a product of type `Set`, which consists of several other products,
* a product sold together with packaging,
* a product requiring an additional dependent item,
* a relationship used by a POS process or integration.
### Deposits
A deposit can be handled as a separate product record or as a product linked to the main product. The exact configuration method depends on implementation arrangements, country, POS integration and reporting requirements. If deposits are used in the organization, before changing the configuration check:
* whether the deposit has a separate product record,
* whether the deposit is linked to the main product in the `Bound products` tab,
* whether the deposit has the correct VAT rate and sales settings,
* whether the deposit should be visible on POS as a separate item,
* whether the change affects reports, receipts or integrations.
### When to use
Use this section when the product is part of a set, requires packaging, has a deposit or should automatically work together with another product record.
### What to watch out for
* Do not add relationships without knowing the process in which they will be used.
* Do not change deposit relationships without confirming the implementation rules.
* After changes, check the product behavior on POS if the relationship affects sales.
* For sets, check whether all components have correct availability and sales configuration.
### Related pages
* [Product types](/aquila-store-user-manual/products-and-product-records/product-types.md)
* [PLU codes](/aquila-store-user-manual/products-and-product-records/plu-codes.md)
* [Availability](/aquila-store-user-manual/products-and-product-records/availability.md)
* [Product card navigation](/aquila-store-user-manual/products-and-product-records/product-card-navigation.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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.aquiladynamics.com/aquila-store-user-manual/products-and-product-records/bound-products.md?ask=&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.
