> For the complete documentation index, see [llms.txt](https://cherrycake.tin.cat/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cherrycake.tin.cat/version-0.x/architecture/items.md).

# Items

Items are Cherrycake's conceptualization of the fundamental objects stored in a database. For example, in an e-commerce site, a product would be an Item, but also would a user, a product category or an invoice.

The most interesting benefits of working with Items in Cherrycake are:

* Items can be easily retrieved, updated or deleted from the database, there's no need to implement your own database access code.
* All security-sensible operations with Items are supervised by the Cherrycake [Security](/version-0.x/architecture/security.md) mechanisms.
* Items get all the [performance](/version-0.x/architecture/performance.md) and caching benefits of Cherrycake right out of the box.
* Items support multi language fields, multi-timezone date-time fields, automatic URL slug generation and much more.

> See the [Items guide](/version-0.x/guide/items-guide.md) to learn how to work with Items in Cherrycake


---

# 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://cherrycake.tin.cat/version-0.x/architecture/items.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.