> 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/help/glossary.md). # Glossary Glossary for Equipme Pro: provider terms from A to Z, e.g. provider, Hosted customer, Standalone customer, partner, Lite access, service, offer, service instance, customer portal. Terms that mainly concern customers (e.g. approval, self-service, cost center) are explained in the customer guide's glossary (see customer guide). | Term | Meaning | | --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Account Manager** | Provider role for looking after all customers; automatically receives access to all customer portals | | **Add-on** | Additional service for a service, e.g. warranty extension, setup, pickup | | **API key** | Key with which other systems and the automation module access Pro; has full administrator rights | | **Automation** | Module requiring a license for workflows and integrations without programming | | **Base service** | Company-wide foundation at the customer (e.g. a tenant) on which other services depend | | **Billing item** | Individual amount that goes into an invoice to a customer, e.g. recurring costs of a service or a fee | | **Blueprint** | Template for products or services including offers that you take over into your service portfolio, e.g. from a partner | | **Call-off** | Delivery of a service from the warehouse or a pre-order to the customer | | **Cancellation** | Termination or cancellation of a service by the customer; you process it under "Fulfillment" → "Cancellations" | | **Change** | Change to an existing service of a customer, e.g. options, add-ons or replacement | | **Client (tenant)** | Separate data area of a company; each customer is its own client | | **Completed position** | Fulfillment position that has been fully processed | | **Customer attribute** | Up to three custom fields per customer, e.g. sales region | | **Customer portal** | The equipme interface your Hosted customers work with (marketplace, orders, assets) | | **Customer warehouse** | Warehouse per customer in which devices are kept for this customer, e.g. after a return for renewed call-off | | **Distributor catalog** | Connected product data catalog of a distributor for product import and price updates | | **Dropshipping** | The supplier delivers directly to the customer, without going through your warehouse | | **Equipme Operate** | equipme's ticket system, used by your customers to make and handle support requests; equipme activates it for Hosted customers → [Ticket system (Equipme Operate)](/pro/operations/tickets.md) | | **Financing agreement** | Agreement with a financing partner (e.g. leasing) to which purchase orders are linked | | **Fulfillment** | Provision of ordered services: from the open position to delivery and activation | | **Fulfillment position** | Single position of a customer order (or of a change, return, cancellation) that is processed in fulfillment | | **Full Pro access** | Access to all areas of Equipme Pro (depending on role) and any number of customers; created by registering as a provider | | **Goods receipt** | Booking delivered goods into the warehouse | | **Hosted customer** | Customer who uses equipme as a customer portal under your license; sub-client of your provider company. Shown as "Direct customer" in the customer list | | **HR sync** | Automatic transfer of organizational data from an HR system | | **Individual permission** | Fine-grained permission in addition to roles, e.g. "Confirm received customer orders" | | **Large license** | "Pro with customer portals" variant: you run customer portals for Hosted customers under your brand and additionally look after Standalone customers and partners | | **Lite access** | Restricted access for a supplier invited by a Standalone customer; looks after exactly this customer, menu only "Sales" → "Customers" | | **Multi-tenancy** | Pro's ability to look after many customers (clients) separately from one interface | | **Offer** | Orderable variant of a service with price, term, billing cycle and offer type; can be released for all customers, selected customers or partners | | **Offer type** | Purchase, rental, leasing or subscription | | **Offline supplier** | Supplier who does not use equipme themselves and is maintained manually | | **Open position** | Fulfillment position that still needs to be processed | | **Operational use** | "Pro in operational use" variant: you use Equipme Pro as a backend and ERP for Standalone customers and partners, without your own customer portals | | **Order authorization** | Your release, as a provider, of a customer to be allowed to order at all | | **Order inbox** | List of new customer orders that you confirm or reject before they go into fulfillment | | **Order proposal** | Proposal for a purchase order with the supplier, e.g. for stock goods or dropshipping | | **Parcel** | Shipment with one or more fulfillment positions, with tracking number and tracking link | | **Partner** | Another Pro provider you are connected with via Partner Connect, e.g. as a supplier or reseller | | **Partner Connect** | Function for connecting with Standalone customers and other partners via the partner directory | | **Partner Connect profile** | Your public presence in the partner directory with logo, banner and description | | **Partner customer** | Customer referred to you by a partner; appears in the customer list as "Partner customer" with a reference to the partner | | **Partner directory** | Directory of all providers who have made themselves visible for Partner Connect | | **Pending activation** | Service instance that has been provided but whose contract has not yet been activated; you schedule the activation date under "Fulfillment" → "Pending activations" | | **Picking** | Assembling goods from the warehouse for a customer order | | **Pro** | Equipme Pro, the service ERP for providers | | **Product** | Item in the product master data, e.g. a hardware model with manufacturer, manufacturer part number and purchasing data | | **Product master data** | Your item base from which you build services for the service portfolio | | **Production** | Fulfillment step in which the production steps from service mapping are carried out, e.g. installation or configuration | | **Provider** | Company that uses Equipme Pro to offer, deliver and bill services for customers – e.g. IT service provider, retailer, lessor or supplier | | **Reseller** | Provider role for sales partners who create their own customers and manage them to a limited extent | | **Service** | Orderable service in the service portfolio: hardware, software, cloud or professional service | | **Service instance** | Specific instance of a service provided at the customer (an "asset" at the customer) | | **Service mapping** | Definition of the bills of materials and processes needed to fulfill a service | | **Service portfolio** | All your services with offers, categories and add-ons | | **Shipping** | Fulfillment step in which parcels are formed and sent to the customer | | **Standalone customer** | Company with its own equipme license that connects with you via Partner Connect or an invitation ID. Shown as "End customer" in the customer list | | **Sub-client** | Hosted customer managed under your provider company | | **Supplier profile** | Company data of your provider company incl. bank details and Partner Connect profile | | **System role** | Role predefined by equipme, e.g. "Administrator" or "Fulfillment Operator" | | **Tenant ID** | Unique identifier of your company, required for API communication | | **Transaction type** | Type of a fulfillment position, e.g. "Order", "Pre-order", "Delivery call-off", "Return", "Change", "Replacement" or "Cancellation" | | **White label** | Running the customer portal under your brand: your own branding, your own portal domain, your own terms and conditions, privacy policy and legal notice | | **Workflow / flow** | Automated process in the automation module | --- # 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/help/glossary.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.