> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/manage-items/serialized-items/understanding-serialized-items.md). # About serialized items **Serialized items** are items that have a unique serial number associated with them. Examples of serialized items include cell phones, laptops, tablets, modems, TV streaming devices, and certain types of cards (e.g., SIM cards, phone cards). Most items will only have one serial number. Other items, such as cell phones, may have two or three serial numbers. RMH can record up to three serial numbers for serialized items. You can configure RMH to require serial numbers to be recorded when receiving serialized items into inventory. This may be necessary to establish chain of custody in the shipping and receiving process for controlled items such as firearms or pharmaceuticals. However, requiring serial numbers to be recorded when receiving serialized items may be too time-consuming in a high-volume retail store that receives hundreds of serialized items in a single shipment, such as a large cell phone store or a big box technology store. For this reason, requiring serial numbers when receiving serialized items is an option that you can enable or disable in the store rules. If serial numbers are recorded when receiving serialized items into inventory, the serial numbers are automatically added on the **Serial** tab in the **Item** window when the purchase order is received and the changes are committed to the store database. If the store does not record serial numbers when receiving serialized items, the store can record serial numbers on the **Serial** tab in the **Item** window after the items have been received, or they can enable a store rule that allows cashiers or salespeople to enter serial numbers in POS when serialized items are sold. --- # 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.rmhpos.com/store-manager/manage-items/serialized-items/understanding-serialized-items.md?ask=&goal= ``` `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.