> For the complete documentation index, see [llms.txt](https://orbit-b2b.gitbook.io/orbit-b2b-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://orbit-b2b.gitbook.io/orbit-b2b-docs/companies/create-company.md).

# Create a Company

Go to **Companies** in the admin sidebar, click **Create company**. The editor has 3 tabs for the create flow.

***

## Tab 1 — General

| Field            | What goes here                                                                                                                      |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Company name** | The business's legal/trading name (e.g. "Acme Distributors"). Required. Used in invite emails + admin lists.                        |
| **Email**        | The company's main billing/contact email. Required. Used as the fallback recipient when sending invites without a specific address. |
| **Phone**        | Main phone number with country selector. Required.                                                                                  |
| **Note**         | Internal note for your team (not shown to the customer).                                                                            |
| **Status**       | Active or Inactive. See [Status](/orbit-b2b-docs/companies/status.md) for the difference.                                           |

***

## Tab 2 — Customer group

Pick the pricing tier (Customer Group) this company should belong to. Every contact of this company will automatically get the group's tag and inherit its wholesale pricing.

* **No group assigned** — the company has no tier; its contacts won't get any wholesale tag automatically. Useful if you want to set tiers per contact instead.
* **A specific group** (Gold, Silver, Bronze, etc.) — every contact gets that group's tag.

> If you haven't created any Customer Groups yet, do that first under **Customer Groups** in the sidebar. See [Customer Groups overview](/orbit-b2b-docs/customer-groups/overview.md).

***

## Tab 3 — Address

The company's main billing/shipping address. Today, one address per company (multi-location support is on the roadmap).

| Field             | Required |
| ----------------- | -------- |
| Address line 1    | Yes      |
| Address line 2    | No       |
| City              | Yes      |
| State / Province  | Yes      |
| Country           | Yes      |
| ZIP / Postal code | Yes      |

***

## What happens after you save

* The Company is created in the app database
* A unique **registration slug** is generated for it (the slug is part of the invite link, see [Invite contacts](/orbit-b2b-docs/companies/invite-contacts.md))
* If you set a Customer Group, contacts you add next will automatically be tagged
* An email is **not** sent at this point — emails go out when you add contacts or send invites

The view switches to the full Company editor with 5 tabs (General, Customer group, Address, Registration, Contacts) where you can now add contacts and share the invite link.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://orbit-b2b.gitbook.io/orbit-b2b-docs/companies/create-company.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.