> 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/b2b-registration/all-customers.md).

# All customers (unified B2B list)

The **Registration** page has two views you switch between with buttons at the top:

* **Applications** — the inbox of sign-up requests waiting for review (the default)
* **All customers** — aggregated list of every active B2B customer, regardless of how they were added

The All customers view answers "who are my B2B customers and what tier are they on?" without you needing to flip between Customer Groups, Companies, and Registrations.

***

## What the table shows

| Column      | What it means                                                                                                  |
| ----------- | -------------------------------------------------------------------------------------------------------------- |
| **Email**   | Customer's email (from Shopify or, for unresolved/pending, from the submission)                                |
| **Name**    | Display name (Shopify's full name, or composed from first/last in submission)                                  |
| **Tier**    | Customer Group badge (Gold / Silver / Bronze...). Dash if not in any group.                                    |
| **Company** | Company badge if they're a contact of one. "Direct" otherwise.                                                 |
| **Origin**  | Registered (came through the storefront form) or Manual (you added them via Customer Groups or Companies page) |
| **Added**   | Date they were added/approved                                                                                  |

Each customer dedupes to one row, even if they're in multiple sources (e.g. a company contact who also signed up via the form).

***

## Filters

### Buyer-type buttons

Top row, exclusive choice:

* **All** — every B2B customer
* **Individual buyers** — solo wholesale customers who are NOT in any Company
* **Company contacts** — customers added inside a Company record

### Tier dropdown

Next to the search box. Independent of the buyer-type buttons (mutually exclusive in the current UI — picking a tier clears the buyer-type selection back to "All"):

* **All tiers** (default) — don't filter by tier
* **A specific group** (Gold, Silver, Bronze, ...) — show only customers in that group
* **No tier yet** — surface customers without any tier (usually new approvals you still need to assign a discount group to)

***

## Empty state

If your shop has zero B2B customers yet, the table is replaced with an empty state card explaining the two ways customers get added:

* Storefront registration form approvals
* Manual add via Customer Groups or Companies

Two action buttons:

* **Manage Customer Groups** — jump to Customer Groups to add a buyer manually
* **Configure registration form** — open the form settings drawer

***

## Search

Type in the search box (above the table) to filter by email or display name. Search is client-side filter on top of the current buyer-type + tier filter — so you can drill down two dimensions at once (e.g. "Company contacts" + search "@acme.com").

***

## What's NOT here

* **Pending applications** — those live in the **Applications** view (button at top). They aren't in this list until you approve them.
* **Deleted customers** — if a customer was deleted in Shopify, the orphan ID is filtered out so you don't see blank rows. The weekly cleanup job removes the orphans from the DB too.

***

## Help card below the table

The page has an "About this list" card explaining the data sources, filters, and origin badge with example scenarios. Open it when you're not sure why a customer is/isn't showing up.


---

# 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/b2b-registration/all-customers.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.