> 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/classes/portal-quick-setup/marketplace-setup-internal-shop/supplier-provided-services.md). # Supplier provided Services Most companies already have suppliers they trust: IT resellers, leasing providers, retailers, service partners. **Suppliers** brings all of them into Equipme, so your employees order everything through one marketplace instead of switching between shops, emails and phone calls. ### Two kinds of suppliers Some of your suppliers already run on Equipme. You connect with them, and they maintain their own offers. Orders reach them directly through the platform. Many don't, and they don't have to. You add them yourself, create their offers in your portfolio and place orders with them the way you always have. We keep the record, so every order is tracked like any other. Your employees never see the difference. They browse one marketplace and follow the same approval flows, whoever delivers in the end. {% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/TNrGaMs9i5vovnZSvmJs" %} [Suppliers](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/offer-management/suppliers) {% endcontent-ref %} ### What suppliers can provide A supplier can provide anything your employees need, for example: * Hardware and workplace equipment * Software subscriptions and licences * Managed IT services * Installation, support or logistics services * Office supplies and furniture ### You stay in control Suppliers is not an open marketplace where anyone can list services. Every supplier in your list is there because you connected or created it. You decide which offers appear in your marketplace, and your employees only see what's relevant and approved 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/classes/portal-quick-setup/marketplace-setup-internal-shop/supplier-provided-services.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.