> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/sales-items/sales-item-setup-item-types.md). # Sales Item Setup - Item Types When creating sales items, each item is given a type. While the most common type used for pretty much any revenue item in Veloce is "Regular", other types are available for various usages, from remarks to discounts. #### 2 for 1 coupon ... #### 2 for 1 item ... #### Admission ... #### By volume ... #### Customer counter ... #### Discount ... #### Discount item ... #### Hotel revenue center ... #### Included item Select this item type for free items that are included with another item. This is useful to create combos, where the main item has a price and a choice of sides and a choice of drinks is offered. #### Linked to client ... #### Message ... #### Message item ... #### Misc. item ... #### Misc. +Message ... #### Misc. +Message item ... #### Modifier ... #### Negative misc. ... #### Negative Paid-in ... #### Negative scale ... #### None This is the default selection when creating a new item. This option can also be selected to disable an item without deleting it. #### Paid-in ... #### Perpetual ... #### Perpetual remark ... #### Quantity discount ... #### Regular Use this type for most revenue items which can be sold at the POS. #### Remark ... #### Remark by quantity ... #### Scale ... #### Shift item ... #### Tare ... --- # 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.payfacto.com/payfacto-knowledge/veloce-pos/veloce/point-of-sales-control/sales-items/sales-item-setup-item-types.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.