> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/portfolio-management/service-portfolio/add-ons-vs.-products.md). # Add Ons vs. Products When adding smaller items or one time extras to your portfolio, the question often comes up:\ **Should this be created as an Add On or as a Product?** The difference mainly lies in how the item is used. **An Add On is always connected to an existing service.**\ **A Product stands on its own as a separate portfolio item.** ### What Add Ons are made for Add Ons are intended for one time actions or small supplementary items that belong to a service, but should not be managed as separate objects in equipme. They are booked directly on the related service, processed once, and then completed. After that, they do not continue through their own lifecycle. An Add On therefore does not create: * recurring costs * a separate inventory entry * an independent lifecycle This makes Add Ons useful for cases such as: * maintenance * reinstalling a device * cleaning a device * a notebook bag * a phone case * a screen protector A screen protector is a good example. It may be relevant when a smartphone is ordered or managed, and you may want to see that it was provided. At the same time, it usually does not need to become its own inventory object. As an Add On, it stays traceable through the related service without making the inventory unnecessarily detailed. ### How Products differ A Product is used when something should be available as an independent entry in the portfolio. Unlike an Add On, it is not attached to another service. It is offered on its own and booked as its own item. That means a Product is the better choice when the item should not depend on an existing service, but should be available separately in the portfolio. ### When should you use Add Ons and when Products? Use an **Add On** when: * it belongs to an existing service * it should only be booked in connection with that service * it is processed once and then completed * it should not create recurring costs * it should not appear as its own inventory item Use a **Product** when: * it should be available as a standalone portfolio item * it should be booked independently * it should not be tied to another service ### A simple example A **notebook bag** can be handled in both ways, depending on how you want to offer it. If it should only be selected together with a notebook service, it is a good fit for an **Add On**. It remains connected to that service and can still be tracked in that context. If you want to offer the bag independently in your portfolio, it should be created as a **Product**. The key question is therefore simple: **Does it belong to another service, or should it stand on its own?** --- # 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: ``` GET https://hub.equipme.io/documentation/portfolio-management/service-portfolio/add-ons-vs.-products.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.