> 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/getting-started/initial-setup.md).

# Initial setup (checklist)

Checklist for the initial setup of Equipme Pro: supplier profile, users and roles, white-label portal, default settings, portfolio, offers, customers, warehouse, fulfillment, billing.

This checklist walks you through setting up Equipme Pro in a sensible order. Most steps are done by a user with the role "Administrator".

{% hint style="info" %}
You don't have to set everything up at once. Steps 1 to 5 are enough to get started: after that you can create customers and receive your first orders. Add warehouse, purchasing and automation when you need them.
{% endhint %}

## 1. Company and team

* [ ] **Maintain your supplier profile:** company data and, if you want to be found in the partner directory, your partner profile. → [Supplier profile](/pro/administration/supplier-profile.md)
* [ ] **Name customer attributes** (optional): up to three custom fields that you maintain per customer and show in the customer list, e.g. sales region or contract number. → [Supplier profile](/pro/administration/supplier-profile.md)
* [ ] **Create users** and invite them. → [Users](/pro/administration/users.md)
* [ ] **Assign roles**, e.g. "Account Manager" or "Sales" for customer care, "Portfolio Manager", "Purchasing Manager", "Warehouse Manager", "Fulfillment Manager". → [Roles and permissions](/pro/administration/roles-and-permissions.md)
* [ ] **Set up email notifications**, e.g. "New lead" (new customer registered), "Order authorization requested" and "New partnership". → [Email notifications](/pro/administration/email-notifications.md)

## 2. Customer portal (white label)

* [ ] **Theme:** logo, favicon, app title, primary color and, if needed, toolbar color gradient and button colors. → [Customer portal: Theme](/pro/customers/customer-portal.md#theme)
* [ ] **Legal notice:** links to terms and conditions, privacy notice and legal notice, per language. → [Customer portal: Legal notice](/pro/customers/customer-portal.md#legal-notice)
* [ ] **Support note** and **order settings** (approval notes, text of the order button, phone number in the delivery address). → [Customer portal (white label)](/pro/customers/customer-portal.md)
* [ ] **Your own portal address** (optional): if you want customers to register themselves via your own domain, contact [support](/pro/help/support.md).

## 3. Default settings for new customers

* [ ] Under "Customer Portal Settings" → "Default module settings", define which modules new customers get automatically (invoice view, inventory module) and whether they inherit your global portfolio. → [Default settings for new customers](/pro/customers/customer-portal.md#default-module-settings)
* [ ] Check the **system products** and **Workplace as a Service**. → [Customer portal (white label)](/pro/customers/customer-portal.md#system-products)

## 4. Portfolio and offers

* [ ] Create or import **product master data**. → [Product master data](/pro/portfolio/products.md), [Product import](/pro/portfolio/product-import.md)
* [ ] Put together **services** in the service portfolio. → [Service portfolio](/pro/portfolio/service-portfolio.md)
* [ ] Define **offers and prices** and release them for all or selected customers. → [Offers and prices](/pro/portfolio/offers-and-pricing.md)
* [ ] **Connect partners** (optional), e.g. distributors whose offers you resell. → [Partner Connect](/pro/portfolio/partner-connect.md)

## 5. Customers

* [ ] **Create your first customer** and check their portal settings (order authorization, automatic order confirmation, modules). → [Create and invite customers](/pro/customers/create-and-invite-customers.md), [Customer details](/pro/customers/customer-details.md)
* [ ] **Connect Standalone customers** who have sent you their invitation ID. → [Connecting Standalone customers](/pro/customers/create-and-invite-customers.md#connecting-standalone-customers)
* [ ] **Take over existing data** (optional): import your customers' existing contracts and devices. → [Customer details: Import](/pro/customers/customer-details.md#active-services-and-import)

## 6. Warehouse and purchasing

* [ ] Set up the **warehouse** and book in stock. → [Warehouse](/pro/warehouse.md)
* [ ] **Purchasing** via order proposals and purchase orders with your suppliers. → [Purchasing](/pro/procurement.md)

## 7. Fulfillment

* [ ] Define the flow of confirmation, picking, production, shipping and activation. → [Fulfillment at a glance](/pro/fulfillment.md)
* [ ] Decide per customer whether orders are **confirmed automatically** or go through the [Order Inbox](/pro/sales/order-reception.md).

## 8. Billing

* [ ] Check the billing date and billing module per customer. → [Customer details](/pro/customers/customer-details.md#portal-settings)
* [ ] Review billing runs. → [Billing](/pro/sales/billing.md)

## 9. Optional

* [ ] **Integrations** such as an API key or single sign-on. → [Integrations](/pro/administration/integrations.md)
* [ ] **Automation** for workflows and connectors. → [Automation](/pro/automation.md)
* [ ] **Equipme Operate ticket system** for supporting your customers: activation for Hosted customers via equipme. → [Ticket system (Equipme Operate)](/pro/operations/tickets.md)

## Frequently asked questions

**In what order should I proceed if I want to go live quickly?**

Theme and legal texts, then portfolio and offers, then your first customer. Without released offers, your customer's marketplace is empty.

**Do changes to the default settings also apply to existing customers?**

No. Default settings only apply to customers created afterwards. You adjust existing customers individually in the [customer details](/pro/customers/customer-details.md#portal-settings). One exception is "Workplace as a Service": there you also select existing customers directly.


---

# 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/getting-started/initial-setup.md?ask=<question>&goal=<user_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.