> For the complete documentation index, see [llms.txt](https://docs.powerall.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerall.app/en/parts/items.md).

# Items

An item is the most important building block of Powerall. Whether it is a physical part in the warehouse, the hourly rate of a mechanic, or the call-out charge for a job; everything you buy or sell, you record as an item. It is the basis for your stock, your planning, and your Administration.

#### Revenue groups

For each item, you set a revenue group. This is a smart setting that handles the financial side in one go. It saves a lot of figuring out: with every purchase or sale, Powerall places the amounts directly in the right place in the accounting. This prevents mistakes, lets you finish invoicing faster, and ensures the profit and loss statement is always correct without you having to worry about it.

Besides the basic details such as item code, brand, and description, you can enrich items with [characteristics and Tags](/en/general/features-and-tags.md).

#### Types and units

Each item has a specific type. This determines how Powerall handles it:

* **Standard**: For physical goods in the warehouse where you want to keep track of stock.
* **Hours** & Services: To easily record worked time or service visits.
* **Trips**: Specifically for charging travel costs.
* **Costs**: For other items you want to charge.
* **Text**: A handy tool for adding extra explanation to a work receipt or invoice, without price or stock.

In addition, you determine the sales unit (per piece, meter, or set). Do you buy by the box but sell by the piece? No problem, you can easily arrange that with the alternative units.

#### Prices and agreements

For each item, you set a standard selling price. You choose whether to enter this *including* or *excluding* VAT. Powerall calculates this automatically for you.

* **Purchase price:** The basis for your margin, possibly different per supplier.
* **Selling price**: The standard price for the end customer.
* **Promotional price**: A temporary price that takes precedence over the standard selling price.
* **Sales price agreements**: With[ selling price agreements](/en/crm/sales-price-agreements.md) you can deviate from the standard price for specific customers or customer groups.
* **Supplier linkage**: You can link an item to one or more [suppliers](/en/parts/suppliers.md). Here you record the supplier code and purchase price, so that when purchasing you always apply the correct conditions.

#### Delete, archive and block

Not every item remains in use forever. You have three options for managing your item list:

* **Archive**: No longer using the item? Archive it. It will disappear from the search lists, but the history is retained for your reports.
* **Block**: Is there a supply stop or a defect? Temporarily block the item so no one can accidentally sell it.
* **Delete**: This is only possible if an item has never been used on an order or work receipt.

These [action buttons ](/en/general/interface.md#actieknoppen)can be found directly in the item details.

#### Tabs

On the detail page of an item, you will find useful [tabs ](/en/general/interface.md#menu)that give you immediate insight and control. For example, you can instantly see on which sales orders or work receipts the item has been used. In addition, you can take action directly here: set specific characteristics, link the right suppliers, or manage the price agreements for this item. Everything you need is neatly organized in one place.


---

# 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://docs.powerall.app/en/parts/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.