> 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/dokumentation/procurement/marketplace/products-and-offers.md). # Products, offers, options and add-ons What products, services, offers, offer types, terms, options, add-ons, linked services and base services are. This page explains the building blocks that make up every entry in the Marketplace. ## Product and service | | **Product** | **Service** | | ------------- | ---------------------------- | -------------------------------------------------------------------- | | Configuration | no options | with options and variants | | Offers | exactly one | several (e.g. purchase and rental, different terms) | | Typical for | accessories, simple hardware | configurable devices, software, professional services, subscriptions | In everyday language and in the app, both are often simply called "Service". ## Offers An **offer** is an orderable variant of a service with a price, term, billing and contract type. The offer you choose when ordering is the basis for billing the service. ### Service, offers and supplier ``` Service (or product), e.g. "Notebook 14 inch" ├── Offer "Purchase" → supplier A ├── Offer "Rental 36 months" → supplier B └── Offer "Purchase (stock)" → no supplier, provided in-house ``` * The **service** describes *what* is ordered (name, category, images, options). * The **offers** below it define *on which terms* and *from whom* it is ordered. * For services of **platform suppliers**, all offers come from that supplier. * For **own services** ("Internal"), each offer has no or exactly one offline supplier. Without a supplier, your company provides the offer itself. Details: [Suppliers](/dokumentation/offer-management/suppliers.md#assigning-offers-to-a-supplier). ### Offer types | Offer type | Meaning | | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | | **Purchase** | One-time acquisition. The device belongs to the company. | | **Rental** | Monthly rent over a term; returned at the end. | | **Leasing** | Monthly leasing rate over a term. | | **Mobile contract** | Mobile contract with a monthly price over a term; treated like a rental for renewal, reminders and automatic cancellation. | ### Term and renewal * **Term:** minimum contract duration in months. * **Term extension:** by how many months the contract is automatically extended after it expires, e.g. "Extension: 12 months recurring till cancellation". If it says "No automatic renewal", the service expires at the end of the term. {% hint style="warning" %} Rental, leasing and mobile contract services **without** a term extension cannot be canceled after activation until the end of the term. {% endhint %} ### Prices * **One-time costs**: e.g. purchase price or setup fee. * **Monthly or recurring costs**: billed in the offer's billing cycle (monthly, yearly, etc.). * Your company is billed in **one currency**, its default currency. ### Regions An offer can be restricted to certain countries ("Available in: …") or be "Available globally". equipme only shows offers that deliver to the location or the delivery address. ## Options and variants **Options** are configurable features of a service, e.g. storage, color or software edition. Each option has **variants** (e.g. 256 GB, 512 GB), which may come at an extra charge. * **Mandatory options** must be selected. * Some options can be added, canceled or changed to a different variant after ordering. You do this on the [service detail page](/dokumentation/assets/inventory/asset-details.md#configuration). ## Add-ons **Add-ons** are extra services for a main service, e.g. warranty extension, insurance, setup, pickup, exchange or offboarding services. They are booked when ordering or later on the detail page of the main service. Add-ons purchased once do not appear as a separate row in the inventory. ## Linked services **Linked services** are independent services that are requested together with a main service, e.g. a docking station for a laptop. "Mandatory" links are ordered automatically, optional ones are suggested. They take over the assignment of the main service and are approved together with it. ## Base services **Base services** are company-wide foundations, e.g. a tenant, on which other services build. Each exists only once per company. Dependent services can only be ordered once the base service is present or requested. If a base service is canceled, all dependent services end as well. Overview: [Service catalog](/dokumentation/assets/service-catalog.md). ## Internal services Services from your own [Service Portfolio](/dokumentation/offer-management/service-portfolio.md) are marked as **"Internal"** in the Marketplace. Your company processes their orders itself in [Order processing](/dokumentation/offer-management/order-processing.md). --- # 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://hub.equipme.io/dokumentation/procurement/marketplace/products-and-offers.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.