> 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/pro/portfolio/service-portfolio.md). # Service portfolio In the service portfolio you create the services your customers order: details, options, variants, mapping (bill of materials), add-ons, linked services, basic services, categories. **Path:** "Portfolio Management" → "Service portfolio" The service portfolio is your sales catalog. Every active service with a matching [offer](/pro/portfolio/offers-and-pricing.md) appears in your customers' marketplace. The page has five tabs: | Tab | Content | | -------------------- | --------------------------------------------------------------------------- | | **"Services"** | Your orderable services and products | | **"Add-ons"** | Extras that are booked onto other services | | **"Basic services"** | Prerequisites a customer must have before they can order dependent services | | **"Categories"** | The marketplace category structure with standard features | | **"Blueprints"** | Service templates for you and your partners | ## Product or service? When creating, you choose the **configuration type**: | | **"Product"** | **"Service"** | | --------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------ | | Intended for | Simple items without choices, e.g. a headset | Configurable offerings, e.g. a notebook workstation with sizes and accessories | | Options and variants | – | ✓ | | Offers | Exactly one | Any number, including customer-specific ones | | Context selectable | – (default: employee optional, location) | ✓ | | Assign customers at service level | – | ✓ | ## "Services" tab ### The list Columns include: preview image, "Id", "Active", "Category", "Name", "Configuration type", "Fulfillment type", "One-time price", "Monthly price", "Currency", "System product", "Archived", "EAN / GTIN", "Internal comment", "External ID", "Features", "Customer" and "Created". By default, the list only shows services that are not assigned to a single customer. "Tip: Use the customer detail view to view and edit customer-specific services." ### Buttons and actions * **"Add"** → "Product", "Service" or "From Blueprint" * **"Import"** and **"Bulk update"**: see [Importing products and services](/pro/portfolio/product-import.md) * **"Actions"** (for selected services): * "Copy" (exactly one service) * "Obtain product information" (from a connected distributor catalog) * "Status" → "Activate", "Deactivate", "Archive" * "Update categories" * "Set as highlight" * "Update product features", "Remove product features" * "Delete" Right-clicking a row gives you "Edit", "Create offer", "Manage product features" and "Edit availability". ### Creating a service 1. **"Add"** → **"Service"** (or "Product"). 2. **"Service details"**: * If a distributor catalog is connected, you can search by EAN or manufacturer part number at the top via **"Import product"** and have the fields prefilled. * "Name" (required) and "Category" (required; choose from the tree or type a new name) * **"Context"** (only for "Service"), see below * "EAN / GTIN", "External ID", "Brief description" * "Activate (offer in the marketplace)" 3. **"Pricing model"**: the first offer, see [Offers and pricing](/pro/portfolio/offers-and-pricing.md). 4. **"Images"**: upload images and sort them via drag & drop. 5. Save. The service details open. ### Contexts "You can use contexts to control how your service is assigned within the company." A service needs at least one context: | Context | The customer assigns the service to … | | ------------------- | ---------------------------------------------------------------------------------------------------- | | "Employee" | an employee | | "Location" | a location | | "Global" | the whole company (typical for basic services) | | "Cloud" | a cloud service | | Workstation context | an employee's workstation device (only visible if at least one customer uses workstation management) | With **"Optional"**, assignment becomes voluntary ("When activated, assignment is optional"). A common choice is "Employee (optional), location": the service is always attached to a location and can additionally belong to an employee. In addition, there are **"Subsequent employee change"** and **"Subsequent change of location"**. They define whether the customer may still change the assignment after provisioning. ## The service details At the top, you see the name and labels such as "Product"/"Service", "Exclusive" (only for one customer) or "Add-on"/"Blueprint". To the right: * The ⋮ menu with "Obtain product information", "Delete" and, in the customer view, "To the portfolio view". * The **input language**: "Describe the service in different languages." You maintain texts such as name and description per language. ### "Details" tab * **Images** with "Add images" * **"Set marketplace highlight"** with "Order": highlighted services appear prominently in your customers' marketplace. * **"Active"** ("Display service in the marketplace"): inactive services can't be ordered by customers. * **"Archive"** / **"Restore"**: "The service will no longer be available in the marketplace, but active instances will remain active." * **"Edit"**: name, category, context, EAN, external ID, brief description, automatic approval, highlight. * **"Approve automatically"**: "When enabled, the service is automatically approved for self-service requests on the customer's page. The customer can override this setting later." * Information on "Category", "Context", "Add-on type" and "Basic service" (with link) * **"Customized service"**: Shows "All customers" or the list of customers who see the service. Use the pencil to select specific customers; "Enable service for all customers" makes it visible to everyone again. See also [Offers and pricing](/pro/portfolio/offers-and-pricing.md#two-levels-service-and-offer). * **"Availability"**: "Status" ("Available", "Available soon", "Not available") and a "Message" the customer sees in the marketplace, e.g. supply shortages. * **"Features"**: technical properties such as screen size or storage. They are shown to the customer in the marketplace. {% hint style="info" %} A service with partner offers can't be assigned to an individual customer: "Please delete all partner offers first if you want to assign this service to specific customers." {% endhint %} ### "Offers" tab Prices, terms, offer type and who the offer applies to. Described in detail under [Offers and pricing](/pro/portfolio/offers-and-pricing.md). ### "Options" tab (only for "Service") Options are choices in the marketplace, e.g. "Color" with the variants "Black" and "Silver". **Adding an option:** 1. Click **"Add"**. 2. Enter "Name" (e.g. color), "Description" and the first "Variant" (e.g. black). "You can add more variants later." 3. Choose the **"Mapping configuration type"**: * **"Variant combination"**: Options of this type depend on each other. Each combination (e.g. size × color) gets its own bill of materials in the mapping. * **"Additive"**: The variant adds extra components independently of the rest, e.g. accessories. 4. Set the switches: * **"Mandatory"**: The option is always ordered as well and can't be deselected. * **"Can be cancelled later"**: The option may be removed after provisioning. * **"Can be booked later"**: The option may be added after provisioning. * **"Variant can be changed retrospectively"**: The variant may be switched afterward. * **"Active"**: The option can be ordered. For each option, you can add variants ("Add new variant"), "Set as default" for a variant, store a "Marketing text" and choose the "Display type" ("Standard" or "Compact"). Via "Prices displayed for", you see the variants' prices per offer. You set the surcharges themselves in the offer. A variant without a price isn't available in that offer. ### "Mapping" tab "In Service Mapping, you can define parts lists and processes that are needed to fulfill your customer orders." **Fulfillment type:** "In-house" (you provision yourself, possibly from your warehouse) or "Dropshipping" (the supplier delivers directly to the customer). For dropshipping, you need a bill of materials for all combinations. **Bills of materials** ("Bills of materials" subtab): * **"Base bill of materials"**: components included in every booking. * **"Variant combinations"**: one bill of materials per combination of variants. Each combination is "Valid" or "Combination not allowed". * **"Additional options"**: components that an additive variant brings in addition. You can switch between "Configuration view" and "List view". You add components like this: * "Quick search: Add product to bill of materials..." (search in the [product master data](/pro/portfolio/products.md)) * "Add multiple" (list with filters and multiple selection) * "Add new product" (creates a product and adds it directly) For each item, you set the "Quantity" and optionally a **"Term condition"**. With a term condition, the component is only included in the bill of materials when this term is booked. **"Mapping impact"** shows which fulfillment processes an order goes through: "Purchasing", "Picking", "Production", "Shipping" or "None (the instance is activated directly)". There you also see whether attribute values such as a serial number must be recorded during provisioning. **Release:** Click **"Release"** when the mapping is finished. "The release activates the application of the mapping when a customer order is received." All waiting orders for this service are then processed. As long as the mapping is released, you can't edit it. To make changes, click **"Revoke release"**. {% hint style="warning" %} Without a release, orders remain in fulfillment in the status **"Waiting for mapping approval"**. So release the mapping even for services without components. Orders to which an older mapping has already been applied don't change with a new release. {% endhint %} ### "Description" tab Two texts with an editor: **"Detailed description"** (marketing and product text) and **"Service agreement"** (scope of service). The customer sees both in the detail view in the marketplace. Maintain them per input language if needed. ### "Add-ons" tab (for add-ons: "Services") * For a service: **"Add add-ons"** defines which add-ons fit this service. * For an add-on of type "Standard": **"Add services"** defines which services the add-on can be booked onto. ### "More information" tab Additional key-value pairs for the service, e.g. for integrations and automations. Use "Add" to create an entry. ### "Linked services" tab Here you bundle other services with this service, e.g. a notebook with a setup fee and optional insurance: * **"Add"**: select services. * **"Mandatory"**: Linked mandatory services are automatically ordered along with the main service and take over its assignment (employee, location, cost center). * Without "Mandatory", they are offered to the customer as an addition when ordering. {% hint style="warning" %} If a linked mandatory service has no offer for the customer, the customer can't order the main service. So check the offers of all linked services. {% endhint %} ## "Add-ons" tab Add-ons are additional services that are booked onto another service. You create them with **"Add"**. In the dialog, you additionally choose the **"Add-on type"**: | Add-on type | Use | | ---------------------- | ---------------------------------------------------------------------- | | "Standard" | Any additional service, e.g. insurance or setup | | "Return" | Return of a device. Used when the customer returns a device. | | "Replacement" | Replacement of a device; the delivery address is the device's location | | "Employee offboarding" | Tasks when an employee leaves | For the types "Return", "Replacement" and "Employee offboarding": "Only one global add-on can exist for this type." You create a customer-specific add-on of these types in the customer details in the "Offers" tab. In the additional **"Target services"** step, you define what a standard add-on can be booked onto, and the **"Add-on availability"**: * "Always": regardless of the lifecycle * "New services": only for services in the cart that haven't been ordered yet * "Active services": only for services already provisioned ## "Basic services" tab Basic services are prerequisites. Example: before a customer can order licenses, they must have the basic service "Tenant setup". 1. **"Add"** → enter "Service name" and "Description". 2. In the details: * **"Service details"**: Via "Configure product", you connect the basic service to an orderable service product and its offers. * **"Services"**: the services that depend on this basic service. * **"Service dependencies"**: other basic services that must exist beforehand. **Effect for the customer:** If a customer wants to order a dependent service without having the basic service, the marketplace points this out and leads them to the basic service. A basic service can only be ordered once per customer. In the marketplace, basic services the customer doesn't have yet appear in a separate section. See the customer guide, chapter Marketplace. {% hint style="warning" %} Don't create circular dependencies (A depends on B, B on C, C on A). Equipme Pro only prevents direct circles between two basic services. {% endhint %} ## "Categories" tab On the left you see the category tree, on the right the details of the selected category. You move categories via drag & drop. Use "Create service category" to create a new one. Details of a category: * "Display name", "Parent category", "Display order", "Description", "Image" * **"Standard features"**: "These characteristics are automatically applied when creating a service in this category. They also apply to all subcategories." Features from parent categories appear as "Inherited standard features". * **"Translations"**: category names for further languages. Without a translation, the default value applies. If you delete a category, its subcategories are deleted as well. ## "Blueprints" tab Blueprints are service templates with master data, mapping and offers. They can't be ordered themselves. Real services are created from them: * **Creating blueprints:** "Add" → "Product" or "Service" ("Create product blueprint" or "Create service blueprint"). In the offer, you use **"Offer available internally and to all partners"** to decide whether the blueprint is available only to you ("*Company* (Internal)"), to everyone or only to selected connected partners. * **Creating services from blueprints:** In the "Services" tab → "Add" → **"From Blueprint"**: 1. "Select the blueprints": your own blueprints and those of your connected partners. By default, all offers of a blueprint are taken over; you can deselect individual ones. One offer must remain selected. 2. "Adjust the service information": optionally **"Price increase in percent"** ("The surcharge is added when the blueprints are transferred to the offers.") and **"Override blueprint categories"**. 3. "Processing": the services are created. The price increase is only applied once when taking over. Later changes to the blueprint don't affect services already created. ## Copying a service Select exactly one service → "Actions" → "Copy". In the "Copy service" dialog, you enter the "Service name of the copy" and decide on "Copy options", "Copy images" and "Copy mapping". "The copied service is initially set to inactive." System products and add-ons of the types Return, Replacement and Employee offboarding can't be copied. ## Customer-specific services If you open a service from the [customer details](/pro/customers/customer-details.md) ("Offers" tab), you see the **"Offer view for *****customer*****"**. There you can create exclusive services and individual offers for this customer. If the service isn't exclusive to the customer, information that also affects other customers is locked. Edit it via "To the portfolio view" instead. ## Status of a service | Status | Meaning | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------ | | "Active" | Visible and orderable in the marketplace (provided a matching offer exists) | | "Inactive" | Not in the marketplace; existing instances remain unchanged | | "Archived" | Removed from the marketplace and hidden from day-to-day business; active instances remain active. Can be brought back via "Restore". | | Deleted | Permanently removed; existing dependencies on other services are removed | ## Frequently asked questions **Why is the "Options" tab missing?** The service has the configuration type "Product". Options only exist for "Service". **Why can't I edit the mapping?** It is released. First click "Revoke release". In the customer view of a non-exclusive service, the mapping is also locked. **Archive or deactivate?** Deactivate if the service should only temporarily not be orderable. Archive if you no longer offer it permanently but the running instances continue to exist. **How do I highlight a service in the marketplace?** Via "Set marketplace highlight" in the details or "Set as highlight" in the list. Use "Order" to control the position. --- # 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/pro/portfolio/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.