> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/b2b-bulk-order/features/customer-and-product-targeting.md).

# Customer & Product Targeting

Every Quick Order Form, Variant Table, and Collection Quick Order has a **Visibility** tab (and, for product targeting, a **Products**/**Product targeting** tab) that controls who sees it. All rules are checked live against the shopper viewing the page — there's nothing to publish separately.

{% hint style="info" %}
Variant Table's Visibility tab only has **customer** targeting (see below) — there's no page/display-location setting, since it always appears on the product page it's assigned to via its Products tab.
{% endhint %}

## Who can see the form

Under **Customer visibility**, the **"Who can see this form?"** setting has four options:

* **All customers**
* **Logged-in customers only**
* **Guest customers only**
* **Customers with tags** — reveals **Include customer tags** and **Exclude customer tags** chip pickers

{% hint style="info" %}
There's no built-in "B2B" or "wholesale" customer type. If you want to limit a form to your B2B customers, tag those customer accounts in Shopify with a tag of your choice (for example, `b2b` or `wholesale`), then select that tag under **Include customer tags**.
{% endhint %}

If you choose **Customers with tags** without adding one, saving shows: **"Add at least one customer tag."**

## Where the form appears

Quick Order Form and Collection Quick Order also have a **Display location** setting, where you tick the pages the form is allowed to show on, then pick specific targets for each:

{% tabs %}
{% tab title="Quick Order Form" %}
Home page, Wholesale page, B2B page, Collection page, Landing page, Product page — each with a page/product/collection picker. (Home, Wholesale, and B2B page options map to a general "landing page" placement.)
{% endtab %}

{% tab title="Collection Quick Order" %}
Home page, Collection page, Search page, Featured and related products — each with a collection target picker.

{% hint style="warning" %}
If nothing is selected: **"No display locations selected. This form will appear on all pages where the app can render it."**
{% endhint %}
{% endtab %}
{% endtabs %}

Variant Table doesn't have this setting — it's only shown on the product(s) you assign it to in its Products tab, so its Visibility tab only asks who can see it, not where.

## Product conditions

Collection Quick Order (and any widget using its Products tab) supports a **Conditions** targeting mode in addition to All products / Specific products. Build one or more rules:

* **Field**: Product title, Product type, Vendor, Price, In stock, Tag, Collection
* **Operator**: depends on the field — text fields offer Equals / Not equals / Contains / Not contains; numeric fields (like Price) offer Greater than / Greater than or equal / Less than / Less than or equal
* **Match**: whether a product must match **All conditions** or **Any condition**

Use **Add another condition** to add more rules. Saving without a complete rule shows **"Please add at least one complete condition."**; an incomplete rule shows **"Enter value for {{field}} {{operator}}."**


---

# 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://docs.samita.io/b2b-bulk-order/features/customer-and-product-targeting.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.