> 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/offer-management/service-portfolio.md). # Service portfolio Create your own services, products and add-ons in the service portfolio: offers, options, descriptions, categories, responsibilities, status, import and bulk update. **Path:** sidebar → **"Offer management" → "Service portfolio"** In the service portfolio, you maintain your company's internal offering. Whatever you create and activate here appears in the Marketplace marked **"Internal"**. ## Tabs | Tab | Content | | ---------------- | -------------------------------------------------------------------------------------------------------------------- | | **"Services"** | Your own products and services | | **"Add-ons"** | Additional services for services | | **"Categories"** | The Marketplace category tree | | **"Inventory"** | Products created when [recording existing inventory](/dokumentation/assets/inventory/record-and-import-inventory.md) | ## The list Columns include: "Id", "Active", "Category", "Name", **"Configuration type"** ("Product"/"Service"), "Fulfillment type", "One-time price", "Monthly price", "Currency", "Archived", "EAN / GTIN", "Internal comment", "External ID", "Features", "Created" as well as the responsibilities **"Management"**, **"Fulfillment"** and **"Service owner"**. Archived entries are hidden by default. Right-clicking a row offers "Edit", "Create offer", "Manage product features" and "Edit availability". ## Creating a service **"Add"** → **"Product"** (simple, exactly one offer) or **"Service"** (with options, multiple offers). The wizard has the following steps: ### 1. "Service details" * **"Name"** and **"Category"** (required; create new categories by typing, max. 3 levels). * For products: "EAN / GTIN", "External ID". * **"Marketplace highlight"** (rank 1 to 20). * **Responsibilities**: "Management", "Fulfillment", "Service owner" (see below). * "Brief description". * **"Activate (offer in the marketplace)"**. Your own services can be assigned to employees (optional) and locations. ### 2. "Pricing model" (first offer) * "Offer name" (optional). * **"Offer type"**: "Purchase" (preselected), "Rent", "Mobile contract" or "Leasing". A mobile contract behaves like a rental: monthly price, term and term extension. * **"Supplier (optional)"**: the offline supplier from whom you procure this offer. The supplier applies **to this offer only**: each offer has no or exactly one supplier, and other offers of the same service can be with other suppliers. With a supplier, ordering creates a separate order for it (see [Suppliers](/dokumentation/offer-management/suppliers.md#assigning-offers-to-a-supplier)); without a supplier, you provide the offer yourself. * **"One-time price"** and **"Monthly price"**; "Currency" is your default currency. * **"Term"** and **"Term extension"** in months. * Countries: for all countries or restricted to individual countries. ### 3. "Target services" (add-ons only) * **"Add-on availability"**: "Always", "New services" (only when ordering) or "Active services" (only afterwards). * The services for which the add-on can be booked. ### 4. "Images" Add images and sort them via drag & drop. ## The service detail page Use the language menu in the header to describe the service in multiple languages. When you edit the service details, **"Approve automatically"** also appears. This default is meant for suppliers that offer the service to their customers. For requests in your company, the setting of the same name in the self-service activation in the Marketplace applies (see [Configuring approvals](/dokumentation/procurement/approval-settings.md)). | Tab | Content | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **"Service details"** | Images, **"Show in marketplace"** (active/inactive), "Archive"/"Restore", category, base service dependency, **"Availability"** ("Available", "Available soon", "Not available", with a custom message), "Features" and "Responsibilities" | | **"Offers"** | All offers, grouped by term. "Set as default" determines which offer is shown first in the Marketplace. Simple products have exactly one offer. | | **"Options"** | Services only: options with variants and surcharges | | **"Description"** | "Detailed description" and "Service agreement" (formatted text) | | **"Add-ons"** | Assigned add-ons; use "Create" to create a new add-on directly | | **"Linked services"** | Services that are requested together with this one ("Mandatory" or optional) | ### Options **"Add option"** with a name, description and at least one **variant**. For each variant, you define a **"Surcharge for this variant"** (one-time and/or monthly). | Setting | Meaning | | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Mapping configuration type"** | **"Variant combination"** (variants together form one configuration, e.g. color × storage) or **"Additive"** (independent extras, e.g. accessories) | | **"Mandatory"** | Must be selected when ordering | | **"Can be booked later"** / **"Can be cancelled later"** / **"Variant can be changed retrospectively"** | What users may change on the service's detail page after ordering | | **"Active"** | The option is offered | ### Description * **Brief description**: appears in lists and on the product card. * **"Detailed description"**: longer text, accessible in the Marketplace via "Show detailed description". * **"Service agreement"**: service description or SLA. ## Responsibilities Each service can be assigned three groups ([organizational units](/dokumentation/organization/groups.md)): | Responsibility | Effect | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **"Management"** | Members with the **"Restricted portfolio manager"** permission only see and maintain services of their groups. | | **"Fulfillment"** | Members with the **"Restricted fulfillment user"** permission only see and process orders for services of their groups in [order processing](/dokumentation/offer-management/order-processing.md). | | **"Service owner"** | Assigned to every ordered service as the responsible unit. Members with the "Business owner" role see these services in their inventory. | This way, IT, facility management and HR, for example, can each maintain and process their own offering. To change multiple services, use **"Actions" → "Update responsibilities"**. {% hint style="info" %} Restricted portfolio managers must belong to at least one group to be able to create services. "Management" and "Fulfillment" are required fields for them. {% endhint %} ## Status: activate, deactivate, archive **Actions → "Status":** | Status | Effect | | ---------------- | ------------------------------------------------------------------------------------------------ | | **"Activate"** | Visible and orderable in the Marketplace | | **"Deactivate"** | No longer orderable, remains in the portfolio; existing services remain unchanged | | **"Archive"** | Removed from the active portfolio; existing services remain active. Can be restored at any time. | ## Further actions Under **"Actions"** (after selecting entries): "Copy", "Update categories", "Set as highlight", "Update product features" or "Remove product features" and "Delete" (up to 500 at once; dependencies on this service are removed). ## Categories **"Categories"** tab: the tree on the left, the details on the right. * New category: "Display name" (required), "Description", "Display order". Move categories via drag & drop. * Details: "Parent category", **"Image"** (tile in the Marketplace) and **"Translations"** per language. Without a translation, the default name is displayed. * **"Standard features"**: features such as serial number, IMEI or internal reference that every service in the category receives. They are inherited by subcategories. The value is later maintained on each individual device. * Deleting a category also deletes its subcategories. ## Import and bulk update * **"Import"**: create services or add-ons via .xlsx. Download the sample file; optionally preselect a category to include its standard features in the file. * **Required columns for services:** name, category, configuration type, context, offer type, one-time price, monthly price, currency, term, term extension. * **Required columns for add-ons:** name, category, one-time price, currency. * Specify images as permanently accessible URLs. * **"Bulk update"**: change existing services in bulk. Download them with **"Export data"**, edit them and upload them again via **"Load XLSX"**. Columns marked "(unchangeable)" are ignored. ## Frequently asked questions **Can I change the currency of an offer?** Offers use your company's default currency. You can only change it in the [portal settings](/dokumentation/settings/portal-settings.md) as long as no active assets exist. **How do I offer the same service for purchase and for rent?** Create a **service** (not a "Product") and add a second offer in the "Offers" tab. **I only see an information page instead of the portfolio.** The module is not enabled for your company. --- # 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/offer-management/service-portfolio.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.