# Customer/Vendor Selection

The entity picker for Order Form pages. Lets the cashier or sales rep search a customer (or vendor) by name, email, or phone, and select one. Once picked, the entity is published to the page's session state — Address, Customer Field, Order Lines, and other blocks read from there automatically.

The block also handles a few common shortcuts: auto-set the logged-in user as the entity, or auto-set the location's default customer.

> **Note on naming:** The palette label is **Customer/Vendor Selection**. Some older docs and the underlying file call it *Customer Select*.

## Available in

* Order Form modules **only**

## When to use

* Any Order Form page where the order is associated with a customer or vendor (which is most of them).
* Place it at the **top of the page** so downstream blocks have an entity to read from.
* For Vendor-driven order flows (e.g. drop-ship, purchase orders), set Entity Type to *Vendor*.

For lookup-only flows (no order being created), use **Entity Search** instead.

## Settings

| Setting                                | Description                                                                                                                                         |
| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Title**                              | Heading text shown above the picker. Default: *Customer/Vendor*.                                                                                    |
| **Default Entity ID (optional)**       | Pre-select a specific entity by ID when the page loads.                                                                                             |
| **Auto-set Entity for Logged In User** | If the signed-in user is themselves a Customer or Vendor entity, auto-select them. Default: No.                                                     |
| **Use Location Default Customer**      | Auto-select the location's configured default customer (useful for retail POS where every walk-in defaults to a *Cash Sale Customer*). Default: No. |
| **Entity Type**                        | What this picker searches for: Customer or Vendor. Default: Customer.                                                                               |

## How it works

1. The user types a name, email, or phone fragment.
2. Matches are fetched live from NetSuite via the entity search.
3. The user picks an entry from the results.
4. The picked entity is written to the page's session state — `selectedCustomer` / `customerDetails`.
5. Downstream blocks (Address, Customer Field, Order Lines, Customer Hold Status) read from that state and re-render.

If the user clears the selection manually, the auto-set rules don't re-apply — preventing the picker from "fighting" the user.

{% hint style="info" %}
Click the **Eye icon** next to a selected entity to open a modal showing their full contact info and addresses — useful for quick verification without leaving the page.
{% endhint %}

## Examples

**Cashier register.** Customer/Vendor Selection at top with *Use Location Default Customer* enabled. Walk-in sales auto-default to the *Cash Sale Customer*; named transactions override by typing a customer name.

**B2B portal.** Customer/Vendor Selection with *Auto-set Entity for Logged In User* enabled. The logged-in customer's account is selected automatically — no search needed.

**Vendor PO entry.** Customer/Vendor Selection with Entity Type set to *Vendor*. Used at the top of a Drop Ship workflow.

## Related

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Address</strong></td><td>Reads the selected customer to populate billing/shipping addresses.</td><td><a href="/pages/mz9aKhtOjrSU4uu6KToN">/pages/mz9aKhtOjrSU4uu6KToN</a></td></tr><tr><td><strong>Entity Search</strong></td><td>The lookup-only alternative for non-Order-Form contexts.</td><td><a href="/pages/YG0JVvulp0T0QNjVYaQI">/pages/YG0JVvulp0T0QNjVYaQI</a></td></tr><tr><td><strong>Customer Hold Status</strong></td><td>Reads the selected customer's hold status and warns the cashier.</td><td><a href="/pages/CqpoPOnhKc67FeMefdKr">/pages/CqpoPOnhKc67FeMefdKr</a></td></tr></tbody></table>


---

# Agent Instructions: 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:

```
GET https://docs.in8sync.com/client-admin-guide/active-workflows/getting-started/entity-components/customer-select.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.